t;>>>>> >>> >>>
>>>>>> >>> >>
>>>>>> >>> >> Ok, so you're aware about the limitation of the single point of
>>>>>> >>> >> failure.
>>>>>> >>&
it won't be able to connect to shared storage
>>>>> even if
>>>>> >>> >> the
>>>>> >>> >> other hosts in the cluster are up since the entry point is down.
>>>>> >>> >> Note that hyperconverge
each set up with gluster replica 3 across
>>>> the 6
>>>> >>> >>> disks volume name hosted-engine.
>>>> >>> >>>
>>>> >>> >>> Hostname hosted-storage configured in /etc//hosts to point to
>>>
t to the
>>> >>> >>> host1.
>>> >>> >>>
>>> >>> >>> Installed hosted engine on host1 with the hosted engine storage
>>> path
>>> >>> >>> =
>>> >>> >>> hosted
gt;> >>>
>> >>> >>> Install first engine on h1 successful. Hosts h2 and h3 added to
>> the
>> >>> >>> hosted engine. All works fine.
>> >>> >>>
>> >>> >>> Additional storage and non-hosted engine hosts added etc.
>> >>> >>>
>
t;
> >>> >>> The system is in production.
> >>> >>>
> >>> >>>
> >>> >>> Engine can be migrated around with the web interface.
> >>> >>>
> >>> >>>
> >>>
;> >>> Cinder VM). Additional VM's are hosted by other storage - cinder
>>>> and NFS.
>>>> >>>
>>>> >>> The system is in production.
>>>> >>>
>>>> >>>
>>>> >>> Engine can be mig
engine is
>>> >>> upgraded
>>> >>> first , new Centos kernel requires host reboot.
>>> >>>
>>> >>> - Engine placed on h2 - h3 into maintenance (local) upgrade and
>>> >>> Reboot
>>> >>>
t;> >>>
>>> >>>
>>> >>> - 3.6.4 upgrade released, follow the upgrade guide, engine is
>>> upgraded
>>> >>> first , new Centos kernel requires host reboot.
>>> >>>
>>> >>> - Engine placed on h2 - h3 into maintenance (loca
gt;
Sent: Monday, 11 April 2016 7:11 PM
To: Richard Neuboeck; Simone Tiraboschi; Roy Golan; Martin Sivak;
Sahina Bose
Cc: Bond, Darryl; users
Subject: Re: [ovirt-users] Hosted engine on gluster problem
On Mon, Apr 11, 2016 at 9:37 AM, Richard Neuboeck
mailto:h...@tbi.univie
;> - Engine starts after h1 comes back and stabilises
> >>>
> >>> - VM(cinder) unpauses itself, VM(reports) continued fine the whole
> time.
> >>> I can do no diagnosis on the 2 VMs as the engine is not available.
> >>>
> >>> - Local mainten
t; - VM(cinder) unpauses itself, VM(reports) continued fine the whole
>>> time. I can do no diagnosis on the 2 VMs as the engine is not available.
>>>
>>> - Local maintenance removed from h​1
>>>
>>>
>>> I don't believe the issue is wit
) unpauses itself, VM(reports) continued fine the whole time.
>>> I can do no diagnosis on the 2 VMs as the engine is not available.
>>>
>>> - Local maintenance removed from h1
>>>
>>>
>>> I don't believe the issue is with gluster itself as the volume rem
don't believe the issue is with gluster itself as the volume remains
>> accessible on all hosts during this time albeit with a missing server
>> (gluster volume status) as each gluster server is rebooted.
>>
>> Gluster was upgraded as part of the process, no issues were seen here.
>>
>>
>>
e without the upgrade by following
> the same sort of timeline.
>
>
> ________________
> From: Sandro Bonazzola
> Sent: Monday, 11 April 2016 7:11 PM
> To: Richard Neuboeck; Simone Tiraboschi; Roy Golan; Martin Sivak; Sahina
> Bose
> Cc: Bond, Darryl; use
ort of timeline.
From: Sandro Bonazzola
Sent: Monday, 11 April 2016 7:11 PM
To: Richard Neuboeck; Simone Tiraboschi; Roy Golan; Martin Sivak; Sahina Bose
Cc: Bond, Darryl; users
Subject: Re: [ovirt-users] Hosted engine on gluster problem
On Mon, Apr 11, 2016 at 9:37 AM, Richard Neu
On 04/11/2016 11:11 AM, Sandro Bonazzola wrote:
> On Mon, Apr 11, 2016 at 9:37 AM, Richard Neuboeck
> mailto:h...@tbi.univie.ac.at>> wrote:
>
> Hi Darryl,
>
> I'm still experimenting with my oVirt installation so I tried to
> recreate the problems you've described.
>
> My setup h
On Mon, Apr 11, 2016 at 9:37 AM, Richard Neuboeck
wrote:
> Hi Darryl,
>
> I'm still experimenting with my oVirt installation so I tried to
> recreate the problems you've described.
>
> My setup has three HA hosts for virtualization and three machines
> for the gluster replica 3 setup.
>
> I manua
Hi Darryl,
I'm still experimenting with my oVirt installation so I tried to
recreate the problems you've described.
My setup has three HA hosts for virtualization and three machines
for the gluster replica 3 setup.
I manually migrated the Engine from the initial install host (one)
to host three.
There seems to be a pretty severe bug with using hosted engine on gluster.
If the host that was used as the initial hosted-engine --deploy host goes away,
the engine VM wil crash and cannot be restarted until the host comes back.
This is regardless of which host the engine was currently running.
20 matches
Mail list logo