GlusterFS storage domain disappears while deploying hosted-engine
by Christopher Pereira
Sandro,
Please take a look at BZ 1201355.
In my last comment, I posted a solution to keep the storage and the
hosted-engine VM alive during hosted-engine --deploy.
We just need to move the glusterfs process out from the vdsmd.service
cgroup, so the storage and VM are not killed during vdsmd restart.
Please let me know when I can test a patched nightly build.
Regards,
Christopher
9 years, 7 months
Re: [ovirt-devel] [vdsm] vdsm hosts clock sync
by Alon Bar-Lev
----- Original Message -----
> From: "Shahar Havivi" <shaharh(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: vdsm-devel(a)lists.fedorahosted.org
> Sent: Monday, April 6, 2015 3:05:20 PM
> Subject: Re: [vdsm] vdsm hosts clock sync
>
> On 06.04.15 08:00, Alon Bar-Lev wrote:
> >
> >
> > ----- Original Message -----
> > > From: "Shahar Havivi" <shaharh(a)redhat.com>
> > > To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> > > Cc: vdsm-devel(a)lists.fedorahosted.org
> > > Sent: Monday, April 6, 2015 2:54:07 PM
> > > Subject: Re: [vdsm] vdsm hosts clock sync
> > >
> > > On 06.04.15 07:50, Alon Bar-Lev wrote:
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > From: "Shahar Havivi" <shaharh(a)redhat.com>
> > > > > To: vdsm-devel(a)lists.fedorahosted.org
> > > > > Sent: Monday, April 6, 2015 2:44:06 PM
> > > > > Subject: [vdsm] vdsm hosts clock sync
> > > > >
> > > > > Hi,
> > > > >
> > > > > I want to add a new feature that reports migration actual downtime
> > > > > (the
> > > > > time
> > > > > that the VM was inaccessible to the user).
> > > > >
> > > > > Libvirt reports that information but the vdsm hosts need to be in
> > > > > sync by
> > > > > clock
> > > > > time.
> > > > > I can measure the ping for NTP server an report back to the user if
> > > > > the
> > > > > ping
> > > > > is too long (more then ~100ms or so) - a way to do that is via
> > > > > ntpstat
> > > > > shell
> > > > > command.
> > > > > The NTP delay can be report back via vdsStats and can be performed
> > > > > every
> > > > > few hours or so.
> > > > >
> > > > > Anyone knows of a better way that we can sync between hosts?
> > > >
> > > > I am unsure how a ping to clock source is helping, can you please
> > > > explain
> > > > more?
> > > In this case I can only report back to the user that its hosts clock is
> > > delayed and need to be set...
> > > >
> > > > If you assume clocks are synced why anything more is needed?
> > > Why do I assume that?
> > > >
> > > > Or would you like to have a solution in which you do not require clock
> > > > sync?
> > >
> > > I do need the clock to be in sync - if not libvirts "actual downtime
> > > migration" will be not accurate.
> >
> > you do not need clock to sync, you need to know the delta between hosts.
> >
> > but if you assume clock are in sync so what is the actual question?
>
> As I understand from your answer is by having configured ntp the hosts clock
> are in sync.
I do not follow.
1. if you are using ntpd on hosts and hosts are in sync you can use distributed timestamps.
detecting if host is synced can be done using either (based on what actually installed):
ntpq -c rv | grep -q clock_sync && echo ok
chronyc waitsync 1 && echo ok
2. you can also measure the time diff between hosts by clockdiff or similar process and avoid the need of ntpd deployed.
3. you may be able to calculate the time within in the handover is given to remote and eliminate the network time.
Not sure what your implementation is.
Alon
9 years, 7 months
Re: [ovirt-devel] [vdsm] vdsm hosts clock sync
by Sven Kieske
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OT:
you should not use "vdsm-devel(a)lists.fedorahosted.org"
any more.
use devel(a)ovirt.org instead.
kind regards
Sven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBAgAGBQJVJCZtAAoJEAq0kGAWDrql534MAMOCHuv1inVBxoCIPx0nMaFH
zvBkWwttQjO8Y1dJJRrfpz6zccgY4LZYtnUbqQIUtM/K92qyJuOU+OqnQa/0Akf4
TNCr8+XOWqoeIrJJT+92tlU0kQG+l5ZXoHKrN0V8/iwh8/D2r/T6UlOWOM7zsW9N
D2PGnm1+zGA6sWHxDaHRggxUQWio+seibmbd6g8SUmkMUFuQUrFejAbfDnRB7LXj
qN3haYfiUbkdWXevD31BA3og4IPIYGf51C0Nz95z4J+oAd5AK8uAWasn+uG9h6f1
PlRPgxVVJgI0qFQ7MAIZpm7duYmKRlekvKDv83TEwC8vEggExQBEbJD4leDHf6QG
PvtFh6lfWBq6vGgkr/OCdcn6OPPjWvHUoGzt2vXjCchUriixrJKq4ZOudbNW0UFT
FAAWBe5+iYObMlSgwpn4fhNvKRwE3PoHYaqPDoiEvhRiBcERXFZT1cqIxx2eeTgj
bLcYyBxYp1R6OMhtqrUqUNqdzqGzYY8eQtyCMeZgWQ==
=96CH
-----END PGP SIGNATURE-----
9 years, 7 months
vdsm hosts clock sync
by Shahar Havivi
Hi,
I want to add a new feature that reports migration actual downtime (the time
that the VM was inaccessible to the user).
Libvirt reports that information but the vdsm hosts need to be in sync by
clock
time.
I can measure the ping for NTP server an report back to the user if the ping
is too long (more then ~100ms or so) - a way to do that is via ntpstat shell
command.
The NTP delay can be report back via vdsStats and can be performed every
few hours or so.
Anyone knows of a better way that we can sync between hosts?
Thank you,
Shahar Havivi.
9 years, 7 months
SELinux issue with f20 libvirtd
by Simone Tiraboschi
Hi,
I found an issue with an SELinux denial trying to deploy hosted-engine from oVirt 3.5.1 on fedora 20 with libvirtd from @updates
The issue is:
time->Tue Mar 31 17:45:09 2015
type=PROCTITLE msg=audit(1427816709.311:914): proctitle=2F7362696E2F6C64636F6E666967002D70
type=SYSCALL msg=audit(1427816709.311:914): arch=c000003e syscall=59 success=yes exit=0 a0=23f9af0 a1=23f9bf0 a2=23f8b60 a3=7ffcc784f150 items=0 ppid=7037 pid=7038 auid=4294967295 uid=175 gid=175 euid=175 suid=175 fsuid=175 egid=175 sgid=175 fsgid=175 tty=(none) ses=4294967295 comm="ldconfig" exe="/usr/sbin/ldconfig" subj=system_u:system_r:ldconfig_t:s0 key=(null)
type=AVC msg=audit(1427816709.311:914): avc: denied { write } for pid=7038 comm="ldconfig" path="/dev/vport2p1" dev="devtmpfs" ino=9984 scontext=system_u:system_r:ldconfig_t:s0 tcontext=system_u:object_r:virtio_device_t:s0 tclass=chr_file permissive=0
and /dev/vport2p1 seams to be badly labeled:
crw-rw----. ovirtagent ovirtagent system_u:object_r:virtio_device_t:s0 /dev/vport2p1
I was using:
libvirt-daemon.x86_64 1.1.3.9-1.fc20 @updates
selinux-policy.noarch 3.12.1-197.fc20 @updates
selinux-policy-targeted.noarch 3.12.1-197.fc20 @updates
The issue doesn't reproduce enabling virt-preview repo and using a fresher libvirtd.
Should I open a bug to have something back-ported on f20 libvirt or should we explicitly require virt-preview repo for oVirt 3.5.2 as we are doing for master?
ciao,
Simone
9 years, 7 months