[ovirt-users] Re: Shutdown procedure for single host HCI Gluster
On Wed, Mar 25, 2020 at 1:49 AM Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
On Wed, Mar 25, 2020 at 12:36 AM Nir Soffer <nsoffer(a)redhat.com> wrote:
>
> On Tue, Mar 24, 2020 at 1:39 PM Gianluca Cecchi
> <gianluca.cecchi(a)gmail.com> wrote:
> >
> > Hello,
> > I'm testing the single node HCI with ovirt-node-ng 4.3.9 iso.
> > Very nice and many improvements over the last time I tried it. Good!
> >
> > I have a doubt related to shutdown procedure of the server.
> > Here below my steps:
> > - Shutdown all VMs (except engine)
> > - Put into maintenance data and vmstore domains
> > - Enable Global HA Maintenance
> > - Shutdown engine
>
> I think the missing part here is stopping the SPM (if running on this
> host), and disconnecting
> from storage.
>
Yes, it is of course the SPM, because this is a single node HCI environment
>
> Both are done when you put a host to maintenance, but in hosted engine
> environment this
> is not possible from engine since engine runs on the storage you want
> to disconnect.
In fact. From here my question and doubts
Note that stopping the SPM and disconnecting from storage is not the same as
stopping vdsm service.
You need to use vdsm API to do this. This can be done with vdsm-tool command
or with vdsm client library.
> > - Shutdown hypervisor
> >
> > It seems that the last step doesn't end and I had to brutally power off the
hypervisor.
> > Here the screenshot regarding infinite failure in unmounting
/gluster_bricks/engine
> >
> >
https://drive.google.com/file/d/1ee0HG21XmYVA0t7LYo5hcFx1iLxZdZ-E/view?us...
> >
> > What would be the right step to do before the final shutdown of hypervisor?
>
> I think there is an ansible script to do what you need, or some other script.
>
> Simone, do you know where the clean shutdown script for HCI env?
>
> Nir
>
Let's say that in a "standard production" HCI environment, with suppose 3
nodes, you have a planned maintenance and you have to shutdown all three nodes: the same
applies when you have to shutdown the last node, but I imagine you have also to do
something with gluster when you shutdown the second node because you have not quorum
anymore, correct?
The flow should be:
1. put host 1 to maintenance
2. put host 2 to maintenance
At this point you have only host 3 connected to storage.
3. Stop the SPM
4. Disconnect from storage
At this point there is no gluster mount on any host, so there is no
quorum isssue.
You should be able to shutdown the hosts at this point. I guess that gluster
services handle shutdown gracefully like any service should.
Nir