[ovirt-users] Autostart VMS

[Joop]

On 6-4-2016 21:10, Brett I. Holcomb wrote:
> On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
>> On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
>>> In VMware we could setup guests to autostart when the host started
>>> and define the order.  Is that doable in oVirt?  The only thing I've
>>> seen is the watchdog and tell it to reset but nothing that allows me
>>> to define who starts up when and if they autostart.  I assume it's
>>> there but I must be missing it or haven't found it in the web portal. 
>>
>>
>> In oVirt guests aren't tied to a host by default (although you can set
>> them to run only on a specific host if you want).  The closest thing I
>> can think of would be the High Availability features (VM->Edit).
>> oVirt will try to restart highly available VMs if they go down.  You
>> can also set the priority for migration and restart in that pane.
>> Hopefully a combination of host pinning and the  high availability
>> settings will get you close enough to where you want to be.
>>
>> Otherwise, you could always do some scripting with the ovirt REST API
>> using the SDK or CLI.
>>
>
> If you had the VMware migration extra add-on you could have hosts move
> as needed so they were not tied to any host either but we could set a
> startup order and specify auto, manual so that once the host started
> the VMs were brought up as specified no matter what host they were
> running on.  
>
> I am running hosted-engine deployment with the Engine VM on the host.
>
> I set highly available on, did not pin to any host, and also set the
> watchdog which should reset if they go down but I'm not sure that will
> start them if the host comes up and the VMs are not running.  I'll
> look at the CLI first.
>
> It would be nice if oVirt added this feature as it's really required
> for large installations and is a help for any size installation, even
> small ones.
>
Maybe there is a another way. It involves ovirt-shell and/or a sdk
script. The idea is the create a custom property and set that to for
example, y:01 or n:02 and yes that to read that back if the host comes
up and start the vms if they have 'y' and use the number for ordering.
If reading back the properties is a problem you might be able to 'use'
the tagging feature todo something similar.

You can always create a RFE on the ovirt bugtracker.

Joop