10:44 a.m.
Hi,
I understood we have to put hosted-engine into maintenance mode and
shutdown the VMs if we want to power off the host (otherwise it will
reboot). I'm setting up a process to
- put the HestedEngine in global maintenance mode (*hosted-engine
--set-maintenance --mode=global*)
- shutdown the HostedEngine (*hosted-engine --vm-shutdown*)
- PowerOff the HostedEngine (*hosted-engine --vm-poweroff*)
- Power off the server (*shutdown -P*)
Everything works fine and I can start the server back up, remove the
HostedEngine from maintenance mode, and it will start automatically
running. The issue is when bringing up hosted-engine: all VMs come up but
one (*BigIP*) and I am trying to see if there is way to bring it up without
having to store the engine password (using the *ovirt_vm* API).
At the moment, I am having to look for the BigIP VM and then use
credentials to bring it up: it will not come up with 'hosted-engine
--vm-start'
Is there to make this specific VM start the same time as the others VM
automatically when HostedEngine starts?
Thanks for your help.
Regards,
Eugène NG
--
LesCDN <http://lescdn.com>
engontang(a)lescdn.com
------------------------------------------------------------
*Aux hommes il faut un chef, et au*
* chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te
voit on te juge!*
4:17 a.m.
On Fri, Jul 9, 2021 at 6:45 PM Eugène Ngontang <sympavali(a)gmail.com> wrote:
Hi,
I understood we have to put hosted-engine into maintenance mode and shutdown the VMs if
we want to power off the host (otherwise it will reboot). I'm setting up a process to
- put the HestedEngine in global maintenance mode (hosted-engine --set-maintenance
--mode=global)
- shutdown the HostedEngine (hosted-engine --vm-shutdown)
- PowerOff the HostedEngine (hosted-engine --vm-poweroff)
- Power off the server (shutdown -P)
You might also want to check:
https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/shutd...
Everything works fine and I can start the server back up, remove the HostedEngine from
maintenance mode, and it will start automatically running. The issue is when bringing up
hosted-engine: all VMs come up but one (BigIP) and I am trying to see if there is way to
bring it up without having to store the engine password (using the ovirt_vm API).
The HA services on the hosts are directly responsible only for
starting the engine VM.
All other VMs are handled by the engine after it's up.
Usually, the engine starts all VMs that are marked as HA.
At the moment, I am having to look for the BigIP VM and then use credentials to bring it
up: it will not come up with 'hosted-engine --vm-start'
Is this BigIP VM marked HA? If not, perhaps try to mark it so. There
might have been concrete reasons you (or your team) didn't - e.g. it
might rely on some other VMs to be up, or something like that.
Is there to make this specific VM start the same time as the others VM automatically when
HostedEngine starts?
There isn't, as part of the existing functionality of oVirt, other
than marking it HA.
I am pretty certain I heard (on this list?) about people having more
complex scripts to automate start of their env, with more complex
dependencies of VMs on other VMs. You might want to search the
archive. But generally speaking, I think they are doing more-or-less
what you are already working on.
Good luck,
--
Didi
5:08 a.m.
Hi Didi,
Yes I opened another thread where i indicated that I've solve the issue
marking BipIp HA.
Thx.
Eugène NG
Le dim. 18 juil. 2021 à 11:17, Yedidyah Bar David <didi(a)redhat.com> a
écrit :
On Fri, Jul 9, 2021 at 6:45 PM Eugène Ngontang
<sympavali(a)gmail.com>
wrote:
>
> Hi,
>
> I understood we have to put hosted-engine into maintenance mode and
shutdown the VMs if we want to power off the host (otherwise it will
reboot). I'm setting up a process to
>
> - put the HestedEngine in global maintenance mode (hosted-engine
--set-maintenance --mode=global)
> - shutdown the HostedEngine (hosted-engine --vm-shutdown)
> - PowerOff the HostedEngine (hosted-engine --vm-poweroff)
> - Power off the server (shutdown -P)
You might also want to check:
https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/shutd...
>
> Everything works fine and I can start the server back up, remove the
HostedEngine from maintenance mode, and it will start automatically
running. The issue is when bringing up hosted-engine: all VMs come up but
one (BigIP) and I am trying to see if there is way to bring it up without
having to store the engine password (using the ovirt_vm API).
The HA services on the hosts are directly responsible only for
starting the engine VM.
All other VMs are handled by the engine after it's up.
Usually, the engine starts all VMs that are marked as HA.
>
> At the moment, I am having to look for the BigIP VM and then use
credentials to bring it up: it will not come up with 'hosted-engine
--vm-start'
Is this BigIP VM marked HA? If not, perhaps try to mark it so. There
might have been concrete reasons you (or your team) didn't - e.g. it
might rely on some other VMs to be up, or something like that.
>
> Is there to make this specific VM start the same time as the others VM
automatically when HostedEngine starts?
There isn't, as part of the existing functionality of oVirt, other
than marking it HA.
I am pretty certain I heard (on this list?) about people having more
complex scripts to automate start of their env, with more complex
dependencies of VMs on other VMs. You might want to search the
archive. But generally speaking, I think they are doing more-or-less
what you are already working on.
Good luck,
--
Didi
1218
days inactive
1227
days old
2 comments
2 participants
participants (2)
-
Eugène Ngontang -
Yedidyah Bar David