--- Begin Message ---
Send Users mailing list submissions to
us...@ovirt.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ovirt.org/mailman/listinfo/users
or, via email, send a message with subject or body 'help' to
users-requ...@ovirt.org
You can reach the person managing the list at
users-ow...@ovirt.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Users digest..."
Today's Topics:
1. Timezones (Thomas Suckow)
2. Re: GlusterFS Distributed Replicate (Alexander Ludas)
3. Re: AcquireHostId problem (Pascal Jakobi)
4. Re: AcquireHostId problem (Federico Simoncelli)
5. Re: GlusterFS Distributed Replicate (Andrew Lau)
6. Re: oVirt 3.3.2 release (Markus Stockhausen)
----------------------------------------------------------------------
Message: 1
Date: Fri, 20 Dec 2013 10:54:26 -0800
From: Thomas Suckow <thomas.suc...@pnnl.gov>
To: us...@ovirt.org
Subject: [Users] Timezones
Message-ID: <52b49262.6050...@pnnl.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I have a setup of several linux guests and my EL6 guests routinely get
stuck at the fsck check when they boot up because the last modification
is in the future.
I assume I need to change something in the guest to tell it what
timezone the host is. I notice that for linux guests you cannot change
what the host reports to the guest, which makes me think the guest is
supposed to magically just know.
What is the proper way to deal with this situation?
-
Thomas
------------------------------
Message: 2
Date: Fri, 20 Dec 2013 20:04:35 +0100
From: Alexander Ludas <a.lu...@gmail.com>
To: Gianluca Cecchi <gianluca.cec...@gmail.com>,
gregoire.le...@retenodus.net <gregoire.le...@retenodus.net>
Cc: users <us...@ovirt.org>
Subject: Re: [Users] GlusterFS Distributed Replicate
Message-ID: <zarafa.52b494c3.2500.0d4e483a68105...@zarafa.ludas.info>
Content-Type: text/plain; charset=utf-8
Quorum can be set via Engine GUI and Gluster CLI.
Engine GUI:
Select gluster volume - Volume Options - Add
- cluster.quorum-count
- cluster.quorum-type
Gluster CLI:
http://www.gluster.org/community/documentation/index.php/Features/Server-quorum
Regards,
Alex
-----Original message-----
From: Gianluca Cecchi<gianluca.cec...@gmail.com>
Sent: Friday 20th December 2013 19:10
To: gregoire.le...@retenodus.net
Cc: Andrew Lau <and...@andrewklau.com>; users <us...@ovirt.org>; Alexander
Ludas <alexan...@ludas.info>
Subject: Re: [Users] GlusterFS Distributed Replicate
But where is configured this thing of quorum? Ovirt engine GUI or gluster wide?
------------------------------
Message: 3
Date: Fri, 20 Dec 2013 23:54:21 +0100
From: Pascal Jakobi <pascal.jak...@gmail.com>
To: Federico Simoncelli <fsimo...@redhat.com>, us...@ovirt.org
Subject: Re: [Users] AcquireHostId problem
Message-ID:
<cafakxwwebrsyaf0cgv5pq65grdcf0dtnwkdybbc_synwcdb...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog
Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0
(nowayout=0)
Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon...
Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179
Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [ OK ]
Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout
Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed
Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60
Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon.
Dec 20 23:45:33 lab2 rpc.mountd[2819]: authenticated mount request from
192.168.1.41:994 for /home/vdsm/data (/home/vdsm/data)
Dec 20 23:45:39 lab2 rpc.mountd[2819]: authenticated mount request from
192.168.1.41:954 for /home/vdsm/data (/home/vdsm/data)
Seems to work a bit.
However I still get "unable to attach storage" when creating a domain....
2013/12/20 Federico Simoncelli <fsimo...@redhat.com>
> ----- Original Message -----
> > From: "Pascal Jakobi" <pascal.jak...@gmail.com>
> > To: "Federico Simoncelli" <fsimo...@redhat.com>
> > Sent: Friday, December 20, 2013 4:44:56 PM
> > Subject: Re: [Users] AcquireHostId problem
> >
> > *Bug 1045512 created* <
> https://bugzilla.redhat.com/show_bug.cgi?id=1045512>
>
> It looks perfect. Thanks.
>
> --
> Federico
>
--
*Pascal Jakobi*
116 rue de Stalingrad
93100 Montreuil, France
*+33 6 87 47 58 19*pascal.jak...@gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ovirt.org/pipermail/users/attachments/20131220/94286c1d/attachment-0001.html>
------------------------------
Message: 4
Date: Fri, 20 Dec 2013 18:16:43 -0500 (EST)
From: Federico Simoncelli <fsimo...@redhat.com>
To: Pascal Jakobi <pascal.jak...@gmail.com>
Cc: us...@ovirt.org
Subject: Re: [Users] AcquireHostId problem
Message-ID:
<1878256692.9932035.1387581403394.javamail.r...@redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Pascal Jakobi" <pascal.jak...@gmail.com>
> To: "Federico Simoncelli" <fsimo...@redhat.com>, us...@ovirt.org
> Sent: Friday, December 20, 2013 11:54:21 PM
> Subject: Re: [Users] AcquireHostId problem
>
> Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog
> Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0
> (nowayout=0)
> Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon...
> Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179
> Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [ OK ]
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60
> Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon.
> Dec 20 23:45:33 lab2 rpc.mountd[2819]: authenticated mount request from
> 192.168.1.41:994 for /home/vdsm/data (/home/vdsm/data)
> Dec 20 23:45:39 lab2 rpc.mountd[2819]: authenticated mount request from
> 192.168.1.41:954 for /home/vdsm/data (/home/vdsm/data)
>
> Seems to work a bit.
> However I still get "unable to attach storage" when creating a domain....
It is probably a different error now. Anything interesting in vdsm.log?
--
Federico
------------------------------
Message: 5
Date: Sat, 21 Dec 2013 10:42:50 +1100
From: Andrew Lau <and...@andrewklau.com>
To: gregoire.le...@retenodus.net
Cc: users <us...@ovirt.org>
Subject: Re: [Users] GlusterFS Distributed Replicate
Message-ID:
<cad7df9fjr7ce+7bssjeqvmfejype_dnikfaiphp5ypwlph0...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
On Sat, Dec 21, 2013 at 4:43 AM, <gregoire.le...@retenodus.net> wrote:
> Hi,
>
> keepalived is only for grabbing the gluster volume info (eg. the servers
>> which host the bricks) > in which from what I've noticed your clients will
>> then connect to the gluster servers directly
>> (not using keepalived anymore).
>>
>
> Can't keepalived be replace by naming the hostname by localhost, as what
> Alex says ?
Yes it could sorry I forgot about that method, I used to do it that way but
we had plans on possibly implementing nodes without glusterfs bricks
possibly in the future so we moved to keepalived.
>
>
> If you disable quorum then you won't have the issue of "read only" when
>> you lose a host, but you > won't have protection from split brain (if your
>> two hosts lose network connectivity). VMs will
>> keep writing to the hosts, as you have the gluster server and client on
>> the same host this is
>> inevitable.
>>
>
> Ok, I get the problem caused by disabling the quorum. So, what if while
> I've two hosts the lack of HA is not so dramatic but will be necessary when
> I'll have more hosts ? (3 or 4). Here is the scenario I would like to have :
>
Quorum generally requires 3 hosts, I believe the default configuration when
you press "Optimize for virt store" will require a minimum of 2 bricks
connected before writing is allowed.
> 1) I have two hosts : HOSTA and HOSTB. They have glusterfs bricks
> configured as Distribute Replicated and data is replicated.
> => For now, I'm totally ok with the fact that if a node fails, then VM on
> this hosts are stopped and unreachable. However, I would like that if a
> node fails, the DC keeps running so that VM on the other hosts are not
> stopped and a human intervention make possible to start the VM on the other
> host. Would it be possible without disabling the quorum ?
>
For the 2 host scenario, disable quorum will allow you to do this.
>
> 2) In few months, I'll add two other hosts to the glusterfs volum. Their
> bricks will be replicated.
> => At that time, I would like to be able to make evolve my architecture
> (without shut my VM and export/import them on a new cluster) so that if a
> node fails, VM on this host start to run on the other host of the same
> brick (without manual intervention).
>
Later on you just enable quorum, it's only a setting in the gluster volume.
gluster volume set DATA cluster.quorum-type auto
>
> Is it possible ?
>
> Le 2013-12-20 16:22, a.lu...@gmail.com a ?crit :
>
> Hi,
>>
>> in a 2 node cluster you can set the path to localhost:volume. If one
>> host goes down and SPM role switches to the remaining running host,
>> your master domain is still accessible and so your VMs stay up and
>> running.
>>
>> Regards,
>> Alex
>>
>
> I tried it but still, the storage/cluster were shutdown, probably because
> of the quorum.
>
>
> Thank you very much,
> Regards,
> Gr?goire Leroy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ovirt.org/pipermail/users/attachments/20131221/59d87de8/attachment-0001.html>
------------------------------
Message: 6
Date: Sat, 21 Dec 2013 09:55:15 +0000
From: Markus Stockhausen <stockhau...@collogia.de>
To: Fabian Deutsch <fabi...@redhat.com>, Bob Doolittle
<b...@doolittle.us.com>
Cc: "annou...@ovirt.org" <annou...@ovirt.org>, engine-devel
<engine-de...@ovirt.org>, arch <a...@ovirt.org>, board
<bo...@ovirt.org>, "us...@ovirt.org" <us...@ovirt.org>
Subject: Re: [Users] oVirt 3.3.2 release
Message-ID: <9a3eqe9cmlqcfluko0wta6k1.1387619712...@email.android.com>
Content-Type: text/plain; charset="windows-1252"
We are on centos 6.5 and got similar dependency errors but simply replaced
ovirt-release with ovirt-release-el6 in the guide. Afterwards everything worked
smoothly.
Do not know if it helps
Von meinem Xperia?-Smartphone gesendet
Bob Doolittle <b...@doolittle.us.com> schrieb:
I think the problem may be other than I indicated, however, because I
don't see ovirt-engine-3.3.2 in the FC19 stable repo either. Here's the
error output of my update command:
Error: Package: ovirt-engine-3.3.1-2.el6.noarch (@ovirt-stable)
Requires: ovirt-engine-websocket-proxy = 3.3.1-2.el6
Removing: ovirt-engine-websocket-proxy-3.3.1-2.el6.noarch
(@ovirt-stable)
ovirt-engine-websocket-proxy = 3.3.1-2.el6
Updated By: ovirt-engine-websocket-proxy-3.3.2-1.el6.noarch
(ovirt-3.3.2)
ovirt-engine-websocket-proxy = 3.3.2-1.el6
Available: ovirt-engine-websocket-proxy-3.3.0-3.el6.noarch
(ovirt-stable)
ovirt-engine-websocket-proxy = 3.3.0-3.el6
Available: ovirt-engine-websocket-proxy-3.3.0-4.el6.noarch
(ovirt-stable)
ovirt-engine-websocket-proxy = 3.3.0-4.el6
Available: ovirt-engine-websocket-proxy-3.3.0.1-1.el6.noarch
(ovirt-stable)
ovirt-engine-websocket-proxy = 3.3.0.1-1.el6
Available: ovirt-engine-websocket-proxy-3.3.1-1.el6.noarch
(ovirt-stable)
ovirt-engine-websocket-proxy = 3.3.1-1.el6
I have attached my current repo config, after the update of
ovirt-release-el6-10-1
I'm not sure why it's not seeing
http://resources.ovirt.org/releases/3.3.2/rpm/EL/6/noarch/ovirt-engine-3.3.2-1.el6.noarch.rpm
I do see that repository enabled in "yum repolist enabled" output.
-Bob
On 12/20/2013 11:13 AM, Fabian Deutsch wrote:
> Am Freitag, den 20.12.2013, 11:12 -0500 schrieb Bob Doolittle:
>> I can't do an update of Engine for RHEL 6.
>>
>> The 3.3.2 packages do not seem to have been pushed here:
>>
>> http://resources.ovirt.org/releases/stable/rpm/EL/6/noarch/
> Thanks - I observed the same.
>
> - fabian
>
>> -Bob
>>
>> On 12/19/2013 09:03 AM, Sandro Bonazzola wrote:
>>> The oVirt development team is very happy to announce the general
>>> availability of oVirt 3.3.2 as of December 19th 2013. This release
>>> solidifies oVirt as a leading KVM management application and open
>>> source alternative to VMware vSphere.
>>>
>>> oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
>>> (or similar).
>>>
>>> This release of oVirt includes 175 bug fixes and the first release of the
>>> Backup and Restore API, which enables backup programs to integrate with
>>> oVirt.
>>> This release also simplifies the Guide Me VM-creation wizard. See the
>>> release
>>> notes [1] for a list of the new features and bugs fixed.
>>>
>>> IMPORTANT NOTE: If you're upgrading from a previous version, please update
>>> ovirt-release to the latest version (10) and verify you have the correct
>>> repositories enabled by running the following commands
>>>
>>> # yum update ovirt-release
>>> # yum repolist enabled
>>>
>>> before upgrading with the usual procedure. You should see the ovirt-3.3.2
>>> and
>>> ovirt-stable repositories listed in the output of the repolist command.
>>>
>>>
>>>
>>> [1] http://www.ovirt.org/OVirt_3.3.2_release_notes
>>>
>> _______________________________________________
>> Arch mailing list
>> a...@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL:
<http://lists.ovirt.org/pipermail/users/attachments/20131221/8675cdac/attachment.txt>
------------------------------
_______________________________________________
Users mailing list
us...@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
End of Users Digest, Vol 27, Issue 141
**************************************
--- End Message ---
