On Wed, May 20, 2020 at 7:46 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Wed, May 20, 2020 at 7:16 PM Derek Atkins <derek@ihtfp.com> wrote:
>
[snip]
> Granted, I suspect SOME of the reasons I have this script might be
> implemented in 4.4 (e.g. auto-start of VMs).  However, my understanding of
> the auto-start feature is that it's really an auto-restart -- it will
> restart a VM that was running if the datacenter crashes, but if I shut it
> down manually and then "reboot" the cluster, those VMs wont come back
> automatically.  As I am on a single-host system, I need it to start from a
> clean shutdown and bring up all the VMs in addition to dealing with
> power-outage reboots.
>
> I work from the "if it aint broke, don't fix it" camp.  So I think I'm
> going to stick with 4.3 until I can't anymore.

Why not open RFE to add the feature you need?

You can use the python SDK to do anything supported by oVirt API.
Did you look here?
https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples

> I am happy to share my startup script if someone else wants to port it to
> work with 4.4.  :-)
>
> -derek
>

In the mean time, just to better understand your environment, you say that you are in a single host environment.
Can you detail where does your engine live? Is it a server outside the host or are you in a Self Hosted Engine configuration?
And what are the kind of your storage domains, are they NFS served by the server itself or by Gluster on the host or external hosts or what?

Gianluca