On Sun, 5 Aug 2018, 22:52 Hetz Ben Hamo, <hetz(a)hetz.biz> wrote:
No it doesn't. Think about a situation that your whole machines
are down.
When you'll boot them up currently, only the HE will go up, nothing more in
terms of additional vm's.
Once engine is up, it will make sure that all your HA vm are up.
I don't think we have any dependency management for controlling vm start
order. I guess that something like systemd-for-cluster can be useful.
Arik and Martin know more anout this.
תודה,
*חץ בן חמו*
אתם מוזמנים לבקר בבלוג היעוץ <
http://linvirtstor.net/> או בבלוג הפרטי שלי
<
http://benhamo.org>
On Sun, Aug 5, 2018 at 10:48 PM, Greg Sheremeta <gshereme(a)redhat.com>
wrote:
> Does this help?
>
> "What is High Availability?
> High availability is recommended for virtual machines running critical
> workloads. A highly available virtual machine is automatically restarted,
> either on its original host or another host in the cluster, if its process
> is interrupted, such as in the following scenarios:"
>
>
>
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/...
>
> On Sun, Aug 5, 2018 at 3:44 PM Hetz Ben Hamo <hetz(a)hetz.biz> wrote:
>
>> I just found out that there is no option for autostart VM's.
>>
>> This functionality is extremely crucial when a system is going down
>> after a UPS ran out of juice (or that it didn't work when the power failed).
>>
>> Starting VMs automatically help the recovery process, and editable
>> startup list could help a lot more (for example: if 10 VMs are dependent on
>> AD services, the Windows 2012 should be booted 2nd, right after HE, and
>> then the other machines).
>>
>> Autostart VM's could help a lot with UPS if the list can go
"backward"
>> to power off VMs in a serialized matter, so when a UPS detects a power
>> loss, it could signal the HE to start shutting down VMs by a list.
>>
>> Any chance to have this feature in 4.3?
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>>
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ODMICTDBI4E...
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> <
https://www.redhat.com/>
>
> gshereme(a)redhat.com IRC: gshereme
> <
https://red.ht/sig>
>
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/BUV2CMUDAMW...