[ovirt-users] AutoStart VMs (was Re: Re: oVirt 4.4.0 Release is now generally available)

[Derek Atkins]

Hi,

(Sorry if you get this twice -- looks like it didn't like the python
 script in there so I'm resending without the code)

Gianluca Cecchi  writes:

> Hi Derek,
> today I played around with Ansible to accomplish, I think, what you currently
> do in oVirt shell.
> It was the occasion to learn, as always, something new: as "blocks" in Ansible
> dont' support looping, a workaround to get that.
> Furthermore I have a single host environment where it can turn usefull too...
[snip]

I found the time to work on this using the Python SDK.  Took me longer
than I wanted but I think I've got something working now.  I just
haven't done a FULL test, yet, but a runtime time on the online system
works (I commented out the start call).

I still have two files, a vm_list.py which is a config file that
contains the list of VMs, in order, and then the main program itself
(start_vms.py) which is based on several of the examples available in
github.

Unfortunately I can't seem to send the script in email because it's
getting blocked by the redhat server -- so I have no idea the best way
to share it.

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/X7KLBANUBJCMASFONU2SZQH5Z3HJU2SI/

Re: [ovirt-users] Autostart VMS

[Pavel Gashev]

I'd like to see the autostart feature as well. In my case I need to autostart a 
virtual router VM at remote site. The issue is that oVirt can't see the remote 
host until the virtual router is started on this host. So HA is not an option.

On Sat, 2016-04-09 at 08:50 +0200, Sven Kieske wrote:

On 06.04.2016 07:46, 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.



See this long standing bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1166657

also searching this ML for "autostart" and "VM"

turns up this same discussion every few months.

sadly no dev seems to grasp the importance of this feature, so it's
always rationalsed that it's not needed or the HA feature is enough (it
isn't).

I don't know why the already implemented libvirt autostart feature
does not get simply passed through.

This feature was at least requested by 4 or 5 different people, to no avail.

you might CC yourself to the bugreport(RFE) and vote on it, maybe
this way it will get some traction.

kind regards

Sven



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Sven Kieske]

On 06.04.2016 07:46, 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.

See this long standing bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1166657

also searching this ML for "autostart" and "VM"

turns up this same discussion every few months.

sadly no dev seems to grasp the importance of this feature, so it's
always rationalsed that it's not needed or the HA feature is enough (it
isn't).

I don't know why the already implemented libvirt autostart feature
does not get simply passed through.

This feature was at least requested by 4 or 5 different people, to no avail.

you might CC yourself to the bugreport(RFE) and vote on it, maybe
this way it will get some traction.

kind regards

Sven



signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

On Sat, 2016-04-09 at 01:17 +0300, Nir Soffer wrote:
> On Sat, Apr 9, 2016 at 1:09 AM, Brett I. Holcomb 
> m> wrote:
> > 
> > You are welcome.  I haven't filed a bug for it yet but will be glad
> > to do so
> > or would it be a Feature request?  I assume I go to the oVirt bug
> > tracker
> > site.
> Yes, here:
> https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
> 
> Component should be RFEs
> oVirt team is probably SLA
> 
> We have a voting feature now, so users interested in this feature
> can vote on the bug.
> 
> Thanks,
> Nir
> 
It is done.  I would be willing to do what I help with it within my
skill set.

  Bug 1325468 has been added to the database
  Email sent to:
  
  
s.kie...@mittwald.de, 
levi.har...@dart.biz, 
vanoppen.k...@gmail.com, 
sher...@redhat.com, 
d...@redhat.com, 
gkl...@redhat.com, 
b...@ovirt.org
  
Excluding:
  
  
biholc...@l1049h.com
  


  

> > 
> > 
> > 
> > 
> > 
> > On Sat, 2016-04-09 at 01:06 +0300, Nir Soffer wrote:
> > 
> > On Sat, Apr 9, 2016 at 12:07 AM, Brett I. Holcomb 
> > >
> > wrote:
> > 
> > On Fri, 2016-04-08 at 21:50 +0300, Nir Soffer wrote:
> > 
> > On Fri, Apr 8, 2016 at 9:33 PM, Brett I. Holcomb 
> > >
> > wrote:
> > 
> > On Fri, 2016-04-08 at 19:25 +0300, Nir Soffer wrote:
> > 
> > On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> > >
> > wrote:
> > 
> > On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
> > 
> > Hi,
> > 
> > 
> > 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.
> > 
> > 
> > The engine will try to keep the VM running. So if one host goes down,
> > it will restart the VM on some other host automatically. We will also
> > migrate the VM (or some other to free resources) when the current host
> > gets too loaded. We do not require any migration addons, it just
> > works. But of course we have usually more hosts in a cluster to make
> > this possible.
> > 
> > I do not really remember what happens when all hosts are restarted
> > (power outage) though as that is quite special case.
> > 
> > Regards
> > 
> > --
> > Martin Sivak
> > SLA / oVirt
> > 
> > 
> > 
> > Thanks.  I only have one host so who knows what will happen.  I'm working on
> > a script that will basically emulate what VMware does - start VMS in a given
> > order at startup of the host/engine.  I'll also file a feature request.
> > 
> > 
> > Why do you care about the order?
> > 
> > Isn't it enough to restart all the vms after a host was restarted?
> > 
> > Nir
> > 
> > 
> > Does the Engine start all VMs after the host is powered up and the engine
> > running if I set a watchdog on a VM?  I know it will try to restart the VM
> > if it goes down once oVirt is up and running.   If it will start the VMs at
> > reboot time that helps.
> > 
> > 
> > I think only HA vms are restarted. Adding Michal to add more info on this.
> > 
> > 
> > The reason for the order is that you need some servers such as DNS, file
> > servers, up first before other systems can resolve addresses or mount
> > shares.  For Windows you need domain controllers running before the other
> > windows systems that are part of the domain.  For applications such as Lotus
> > Notes the servers had to come up in the correct order.
> > 
> > 
> > Lets say you have a way to order the vms when some vms are down.
> > 
> > What will happen to when dns, file servers or domain controller will crash?
> > Do you have to restart all the vms depending on them or they can
> > recover and detect that vm they depend on were restarted?
> > 
> > Seems that what you need is a systemd for your data center - every
> > host define the host it depends on, and the system generate the
> > correct order to start the vms, starting vms in the same time when
> > possible.
> > 
> > Please reply also to the list, this thread may be useful to others.
> > 
> > Nir
> > 
> > 
> > Hopefully this will go to the list as i"ve been making sure users@ovirt.org
> > 
> > is in the To field.
> > 
> > I think we need to make sure we distinguish between the start up phase and
> > the running phase which is what happens after everyone is up and running
> > happily.  Based on my experience the crash of a server is considered
> > separately from startup.
> > 
> > As mentioned in my response to the list to someone else's comment the
> > startup sequence is the same as people flipping switches on physical servers
> > following a documented procedure to start or shutdown a datacenter as we did
> > in the "old days".  With physical boxes we had to shutdown/startup manually
> > and we did it in a sequence that we had written down.  With virtualization
> > and since we had VMware we could automate that process so as we spun up 

Re: [ovirt-users] Autostart VMS

[Nir Soffer]

On Sat, Apr 9, 2016 at 1:09 AM, Brett I. Holcomb  wrote:
> You are welcome.  I haven't filed a bug for it yet but will be glad to do so
> or would it be a Feature request?  I assume I go to the oVirt bug tracker
> site.

Yes, here:
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

Component should be RFEs
oVirt team is probably SLA

We have a voting feature now, so users interested in this feature
can vote on the bug.

Thanks,
Nir

>
>
>
>
> On Sat, 2016-04-09 at 01:06 +0300, Nir Soffer wrote:
>
> On Sat, Apr 9, 2016 at 12:07 AM, Brett I. Holcomb 
> wrote:
>
> On Fri, 2016-04-08 at 21:50 +0300, Nir Soffer wrote:
>
> On Fri, Apr 8, 2016 at 9:33 PM, Brett I. Holcomb 
> wrote:
>
> On Fri, 2016-04-08 at 19:25 +0300, Nir Soffer wrote:
>
> On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> wrote:
>
> On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
>
> Hi,
>
>
> 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.
>
>
> The engine will try to keep the VM running. So if one host goes down,
> it will restart the VM on some other host automatically. We will also
> migrate the VM (or some other to free resources) when the current host
> gets too loaded. We do not require any migration addons, it just
> works. But of course we have usually more hosts in a cluster to make
> this possible.
>
> I do not really remember what happens when all hosts are restarted
> (power outage) though as that is quite special case.
>
> Regards
>
> --
> Martin Sivak
> SLA / oVirt
>
>
>
> Thanks.  I only have one host so who knows what will happen.  I'm working on
> a script that will basically emulate what VMware does - start VMS in a given
> order at startup of the host/engine.  I'll also file a feature request.
>
>
> Why do you care about the order?
>
> Isn't it enough to restart all the vms after a host was restarted?
>
> Nir
>
>
> Does the Engine start all VMs after the host is powered up and the engine
> running if I set a watchdog on a VM?  I know it will try to restart the VM
> if it goes down once oVirt is up and running.   If it will start the VMs at
> reboot time that helps.
>
>
> I think only HA vms are restarted. Adding Michal to add more info on this.
>
>
> The reason for the order is that you need some servers such as DNS, file
> servers, up first before other systems can resolve addresses or mount
> shares.  For Windows you need domain controllers running before the other
> windows systems that are part of the domain.  For applications such as Lotus
> Notes the servers had to come up in the correct order.
>
>
> Lets say you have a way to order the vms when some vms are down.
>
> What will happen to when dns, file servers or domain controller will crash?
> Do you have to restart all the vms depending on them or they can
> recover and detect that vm they depend on were restarted?
>
> Seems that what you need is a systemd for your data center - every
> host define the host it depends on, and the system generate the
> correct order to start the vms, starting vms in the same time when
> possible.
>
> Please reply also to the list, this thread may be useful to others.
>
> Nir
>
>
> Hopefully this will go to the list as i"ve been making sure users@ovirt.org
> is in the To field.
>
> I think we need to make sure we distinguish between the start up phase and
> the running phase which is what happens after everyone is up and running
> happily.  Based on my experience the crash of a server is considered
> separately from startup.
>
> As mentioned in my response to the list to someone else's comment the
> startup sequence is the same as people flipping switches on physical servers
> following a documented procedure to start or shutdown a datacenter as we did
> in the "old days".  With physical boxes we had to shutdown/startup manually
> and we did it in a sequence that we had written down.  With virtualization
> and since we had VMware we could automate that process so as we spun up the
> hosts VMware started spinning up the guests in the order specified so we got
> our DNS boxes up first, then others.  For Active Directory we started the
> domain controllers first, then other servers such as file servers,
> application servers in the sequence needed for the applications to run.
>
> Crashing of DNS, File Server, Domain Controllers crashing after the
> datacenter is up and running is handled (or should be) by redundancy of
> servers or process the service provides.  You have multiple DNS servers and
> the resolver will try the secondary/tertiary/whatever if the primary is
> down.  File servers are the same.  For Gluster, CephFS, MS DFS you have (or
> should have setup) the ability to keep running if one of the servers goes
> down.  A redundant file 

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

You are welcome.  I haven't filed a bug for it yet but will be glad to
do so or would it be a Feature request?  I assume I go to the oVirt bug
tracker site.
On Sat, 2016-04-09 at 01:06 +0300, Nir Soffer wrote:
> On Sat, Apr 9, 2016 at 12:07 AM, Brett I. Holcomb 
> om> wrote:
> > 
> > On Fri, 2016-04-08 at 21:50 +0300, Nir Soffer wrote:
> > 
> > On Fri, Apr 8, 2016 at 9:33 PM, Brett I. Holcomb 
> > com>
> > wrote:
> > 
> > On Fri, 2016-04-08 at 19:25 +0300, Nir Soffer wrote:
> > 
> > On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> > com>
> > wrote:
> > 
> > On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
> > 
> > Hi,
> > 
> > 
> > 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.
> > 
> > 
> > The engine will try to keep the VM running. So if one host goes
> > down,
> > it will restart the VM on some other host automatically. We will
> > also
> > migrate the VM (or some other to free resources) when the current
> > host
> > gets too loaded. We do not require any migration addons, it just
> > works. But of course we have usually more hosts in a cluster to
> > make
> > this possible.
> > 
> > I do not really remember what happens when all hosts are restarted
> > (power outage) though as that is quite special case.
> > 
> > Regards
> > 
> > --
> > Martin Sivak
> > SLA / oVirt
> > 
> > 
> > 
> > Thanks.  I only have one host so who knows what will happen.  I'm
> > working on
> > a script that will basically emulate what VMware does - start VMS
> > in a given
> > order at startup of the host/engine.  I'll also file a feature
> > request.
> > 
> > 
> > Why do you care about the order?
> > 
> > Isn't it enough to restart all the vms after a host was restarted?
> > 
> > Nir
> > 
> > 
> > Does the Engine start all VMs after the host is powered up and the
> > engine
> > running if I set a watchdog on a VM?  I know it will try to restart
> > the VM
> > if it goes down once oVirt is up and running.   If it will start
> > the VMs at
> > reboot time that helps.
> > 
> > 
> > I think only HA vms are restarted. Adding Michal to add more info
> > on this.
> > 
> > 
> > The reason for the order is that you need some servers such as DNS,
> > file
> > servers, up first before other systems can resolve addresses or
> > mount
> > shares.  For Windows you need domain controllers running before the
> > other
> > windows systems that are part of the domain.  For applications such
> > as Lotus
> > Notes the servers had to come up in the correct order.
> > 
> > 
> > Lets say you have a way to order the vms when some vms are down.
> > 
> > What will happen to when dns, file servers or domain controller
> > will crash?
> > Do you have to restart all the vms depending on them or they can
> > recover and detect that vm they depend on were restarted?
> > 
> > Seems that what you need is a systemd for your data center - every
> > host define the host it depends on, and the system generate the
> > correct order to start the vms, starting vms in the same time when
> > possible.
> > 
> > Please reply also to the list, this thread may be useful to others.
> > 
> > Nir
> > 
> > 
> > Hopefully this will go to the list as i"ve been making sure users@o
> > virt.org
> > is in the To field.
> > 
> > I think we need to make sure we distinguish between the start up
> > phase and
> > the running phase which is what happens after everyone is up and
> > running
> > happily.  Based on my experience the crash of a server is
> > considered
> > separately from startup.
> > 
> > As mentioned in my response to the list to someone else's comment
> > the
> > startup sequence is the same as people flipping switches on
> > physical servers
> > following a documented procedure to start or shutdown a datacenter
> > as we did
> > in the "old days".  With physical boxes we had to shutdown/startup
> > manually
> > and we did it in a sequence that we had written down.  With
> > virtualization
> > and since we had VMware we could automate that process so as we
> > spun up the
> > hosts VMware started spinning up the guests in the order specified
> > so we got
> > our DNS boxes up first, then others.  For Active Directory we
> > started the
> > domain controllers first, then other servers such as file servers,
> > application servers in the sequence needed for the applications to
> > run.
> > 
> > Crashing of DNS, File Server, Domain Controllers crashing after the
> > datacenter is up and running is handled (or should be) by
> > redundancy of
> > servers or process the service provides.  You have multiple DNS
> > servers and
> > the resolver will try the secondary/tertiary/whatever if the
> > primary is
> > down.  File servers are the same.  For Gluster, CephFS, MS DFS you
> > have (or
> > should have setup) the ability to keep running if one of the
> > 

Re: [ovirt-users] Autostart VMS

[Nir Soffer]

On Sat, Apr 9, 2016 at 12:07 AM, Brett I. Holcomb  wrote:
> On Fri, 2016-04-08 at 21:50 +0300, Nir Soffer wrote:
>
> On Fri, Apr 8, 2016 at 9:33 PM, Brett I. Holcomb 
> wrote:
>
> On Fri, 2016-04-08 at 19:25 +0300, Nir Soffer wrote:
>
> On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> wrote:
>
> On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
>
> Hi,
>
>
> 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.
>
>
> The engine will try to keep the VM running. So if one host goes down,
> it will restart the VM on some other host automatically. We will also
> migrate the VM (or some other to free resources) when the current host
> gets too loaded. We do not require any migration addons, it just
> works. But of course we have usually more hosts in a cluster to make
> this possible.
>
> I do not really remember what happens when all hosts are restarted
> (power outage) though as that is quite special case.
>
> Regards
>
> --
> Martin Sivak
> SLA / oVirt
>
>
>
> Thanks.  I only have one host so who knows what will happen.  I'm working on
> a script that will basically emulate what VMware does - start VMS in a given
> order at startup of the host/engine.  I'll also file a feature request.
>
>
> Why do you care about the order?
>
> Isn't it enough to restart all the vms after a host was restarted?
>
> Nir
>
>
> Does the Engine start all VMs after the host is powered up and the engine
> running if I set a watchdog on a VM?  I know it will try to restart the VM
> if it goes down once oVirt is up and running.   If it will start the VMs at
> reboot time that helps.
>
>
> I think only HA vms are restarted. Adding Michal to add more info on this.
>
>
> The reason for the order is that you need some servers such as DNS, file
> servers, up first before other systems can resolve addresses or mount
> shares.  For Windows you need domain controllers running before the other
> windows systems that are part of the domain.  For applications such as Lotus
> Notes the servers had to come up in the correct order.
>
>
> Lets say you have a way to order the vms when some vms are down.
>
> What will happen to when dns, file servers or domain controller will crash?
> Do you have to restart all the vms depending on them or they can
> recover and detect that vm they depend on were restarted?
>
> Seems that what you need is a systemd for your data center - every
> host define the host it depends on, and the system generate the
> correct order to start the vms, starting vms in the same time when
> possible.
>
> Please reply also to the list, this thread may be useful to others.
>
> Nir
>
>
> Hopefully this will go to the list as i"ve been making sure users@ovirt.org
> is in the To field.
>
> I think we need to make sure we distinguish between the start up phase and
> the running phase which is what happens after everyone is up and running
> happily.  Based on my experience the crash of a server is considered
> separately from startup.
>
> As mentioned in my response to the list to someone else's comment the
> startup sequence is the same as people flipping switches on physical servers
> following a documented procedure to start or shutdown a datacenter as we did
> in the "old days".  With physical boxes we had to shutdown/startup manually
> and we did it in a sequence that we had written down.  With virtualization
> and since we had VMware we could automate that process so as we spun up the
> hosts VMware started spinning up the guests in the order specified so we got
> our DNS boxes up first, then others.  For Active Directory we started the
> domain controllers first, then other servers such as file servers,
> application servers in the sequence needed for the applications to run.
>
> Crashing of DNS, File Server, Domain Controllers crashing after the
> datacenter is up and running is handled (or should be) by redundancy of
> servers or process the service provides.  You have multiple DNS servers and
> the resolver will try the secondary/tertiary/whatever if the primary is
> down.  File servers are the same.  For Gluster, CephFS, MS DFS you have (or
> should have setup) the ability to keep running if one of the servers goes
> down.  A redundant file server setup will handle a server crash.  For Domain
> Controllers you should have at least two (we had six in our environment) and
> when one goes down the others keep the domain running by shifting the
> services to others and continuing to provide authentication, etc.  Generally
> what we did when a domain controller crashed is fix it if possible and if it
> was not fixable pull it's pieces out of the domain and spin up a new one.
> Same for DNS or file servers.  When they go down find out why, fix it or
> replace the server, and get 

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

On Fri, 2016-04-08 at 21:50 +0300, Nir Soffer wrote:
> On Fri, Apr 8, 2016 at 9:33 PM, Brett I. Holcomb 
> m> wrote:
> > 
> > On Fri, 2016-04-08 at 19:25 +0300, Nir Soffer wrote:
> > 
> > On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> > com>
> > wrote:
> > 
> > On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
> > 
> > Hi,
> > 
> > 
> > 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.
> > 
> > 
> > The engine will try to keep the VM running. So if one host goes
> > down,
> > it will restart the VM on some other host automatically. We will
> > also
> > migrate the VM (or some other to free resources) when the current
> > host
> > gets too loaded. We do not require any migration addons, it just
> > works. But of course we have usually more hosts in a cluster to
> > make
> > this possible.
> > 
> > I do not really remember what happens when all hosts are restarted
> > (power outage) though as that is quite special case.
> > 
> > Regards
> > 
> > --
> > Martin Sivak
> > SLA / oVirt
> > 
> > 
> > 
> > Thanks.  I only have one host so who knows what will happen.  I'm
> > working on
> > a script that will basically emulate what VMware does - start VMS
> > in a given
> > order at startup of the host/engine.  I'll also file a feature
> > request.
> > 
> > 
> > Why do you care about the order?
> > 
> > Isn't it enough to restart all the vms after a host was restarted?
> > 
> > Nir
> > 
> > 
> > Does the Engine start all VMs after the host is powered up and the
> > engine
> > running if I set a watchdog on a VM?  I know it will try to restart
> > the VM
> > if it goes down once oVirt is up and running.   If it will start
> > the VMs at
> > reboot time that helps.
> I think only HA vms are restarted. Adding Michal to add more info on
> this.
> 
> > 
> > The reason for the order is that you need some servers such as DNS,
> > file
> > servers, up first before other systems can resolve addresses or
> > mount
> > shares.  For Windows you need domain controllers running before the
> > other
> > windows systems that are part of the domain.  For applications such
> > as Lotus
> > Notes the servers had to come up in the correct order.
> Lets say you have a way to order the vms when some vms are down.
> 
> What will happen to when dns, file servers or domain controller will
> crash?
> Do you have to restart all the vms depending on them or they can
> recover and detect that vm they depend on were restarted?
> 
> Seems that what you need is a systemd for your data center - every
> host define the host it depends on, and the system generate the
> correct order to start the vms, starting vms in the same time when
> possible.
> 
> Please reply also to the list, this thread may be useful to others.
> 
> Nir
Hopefully this will go to the list as i"ve been making sure users@ovirt
.org is in the To field.
I think we need to make sure we distinguish between the start up phase
and the running phase which is what happens after everyone is up and
running happily.  Based on my experience the crash of a server is
considered separately from startup. 
As mentioned in my response to the list to someone else's comment the
startup sequence is the same as people flipping switches on physical
servers following a documented procedure to start or shutdown a
datacenter as we did in the "old days".  With physical boxes we had to
shutdown/startup manually and we did it in a sequence that we had
written down.  With virtualization and since we had VMware we could
automate that process so as we spun up the hosts VMware started
spinning up the guests in the order specified so we got our DNS boxes
up first, then others.  For Active Directory we started the domain
controllers first, then other servers such as file servers, application
servers in the sequence needed for the applications to run.
Crashing of DNS, File Server, Domain Controllers crashing after the
datacenter is up and running is handled (or should be) by redundancy of
servers or process the service provides.  You have multiple DNS servers
and the resolver will try the secondary/tertiary/whatever if the
primary is down.  File servers are the same.  For Gluster, CephFS, MS
DFS you have (or should have setup) the ability to keep running if one
of the servers goes down.  A redundant file server setup will handle a
server crash.  For Domain Controllers you should have at least two (we
had six in our environment) and when one goes down the others keep the
domain running by shifting the services to others and continuing to
provide authentication, etc.  Generally what we did when a domain
controller crashed is fix it if possible and if it was not fixable pull
it's pieces out of the domain and spin up a new one.   Same for DNS or
file servers.  When they go down find out why, fix it or 

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

On Fri, 2016-04-08 at 16:40 +, Michael Kleinpaste wrote:
> Actually this is used pretty regularly in VMware environments.  For
> instance I've seen MSSQL systems running under AD credentials so they
> can access UNC shares.  If the AD domain controllers aren't up prior
> to the database server starting up the MSSQL service won't start
> because it can't authenticate the user on the service.\
That was exactly what I had in one of my jobs where I had an AD domain
for a University and we had several MSSQL servers that needed the AD
credentials.  Plus I had an IBM FileNet ECM system with several servers
that had to be started in the correct order.  With AD you need to have
the domain controllers up and running or nothing works.  Our Linux
systems alsso had some that depended on others.  If they weren't
started in the correct order they had to be restarted again.  And it's
not really a VMware specific need but any environment whether it's
physical or virtual needs as startup sequence.  Before we virtualized
we had a written procedure on what servers came up and in what order
(and the reverse for a shutdown of the site).  When moving to
virtualization the virtualization system replaces people flipping
switches with it's startup/shutdown order or it should.

> On Fri, Apr 8, 2016 at 9:25 AM Nir Soffer  wrote:> > On 
> Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb  wrote:
> > 
> > > On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
> > 
> > >
> > 
> > > Hi,
> > 
> > >
> > 
> > >
> > 
> > > 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.
> > 
> > >
> > 
> > >
> > 
> > > The engine will try to keep the VM running. So if one host goes down,
> > 
> > > it will restart the VM on some other host automatically. We will also
> > 
> > > migrate the VM (or some other to free resources) when the current host
> > 
> > > gets too loaded. We do not require any migration addons, it just
> > 
> > > works. But of course we have usually more hosts in a cluster to make
> > 
> > > this possible.
> > 
> > >
> > 
> > > I do not really remember what happens when all hosts are restarted
> > 
> > > (power outage) though as that is quite special case.
> > 
> > >
> > 
> > > Regards
> > 
> > >
> > 
> > > --
> > 
> > > Martin Sivak
> > 
> > > SLA / oVirt
> > 
> > >
> > 
> > >
> > 
> > >
> > 
> > > Thanks.  I only have one host so who knows what will happen.  I'm working 
> > > on
> > 
> > > a script that will basically emulate what VMware does - start VMS in a 
> > > given
> > 
> > > order at startup of the host/engine.  I'll also file a feature request.
> > 

> > 
> > Why do you care about the order?
> > 

> > 
> > Isn't it enough to restart all the vms after a host was restarted?
> > 

> > 
> > Nir
> > 

> > 
> > >
> > 
> > > On Wed, Apr 6, 2016 at 9:10 PM, 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
> > 
> 

Re: [ovirt-users] Autostart VMS

[Nir Soffer]

On Fri, Apr 8, 2016 at 9:33 PM, Brett I. Holcomb  wrote:
> On Fri, 2016-04-08 at 19:25 +0300, Nir Soffer wrote:
>
> On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> wrote:
>
> On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
>
> Hi,
>
>
> 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.
>
>
> The engine will try to keep the VM running. So if one host goes down,
> it will restart the VM on some other host automatically. We will also
> migrate the VM (or some other to free resources) when the current host
> gets too loaded. We do not require any migration addons, it just
> works. But of course we have usually more hosts in a cluster to make
> this possible.
>
> I do not really remember what happens when all hosts are restarted
> (power outage) though as that is quite special case.
>
> Regards
>
> --
> Martin Sivak
> SLA / oVirt
>
>
>
> Thanks.  I only have one host so who knows what will happen.  I'm working on
> a script that will basically emulate what VMware does - start VMS in a given
> order at startup of the host/engine.  I'll also file a feature request.
>
>
> Why do you care about the order?
>
> Isn't it enough to restart all the vms after a host was restarted?
>
> Nir
>
>
> Does the Engine start all VMs after the host is powered up and the engine
> running if I set a watchdog on a VM?  I know it will try to restart the VM
> if it goes down once oVirt is up and running.   If it will start the VMs at
> reboot time that helps.

I think only HA vms are restarted. Adding Michal to add more info on this.

> The reason for the order is that you need some servers such as DNS, file
> servers, up first before other systems can resolve addresses or mount
> shares.  For Windows you need domain controllers running before the other
> windows systems that are part of the domain.  For applications such as Lotus
> Notes the servers had to come up in the correct order.

Lets say you have a way to order the vms when some vms are down.

What will happen to when dns, file servers or domain controller will crash?
Do you have to restart all the vms depending on them or they can
recover and detect that vm they depend on were restarted?

Seems that what you need is a systemd for your data center - every
host define the host it depends on, and the system generate the
correct order to start the vms, starting vms in the same time when
possible.

Please reply also to the list, this thread may be useful to others.

Nir

> On Wed, Apr 6, 2016 at 9:10 PM, 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.
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org

Re: [ovirt-users] Autostart VMS

[Michael Kleinpaste]

Actually this is used pretty regularly in VMware environments.  For
instance I've seen MSSQL systems running under AD credentials so they can
access UNC shares.  If the AD domain controllers aren't up prior to the
database server starting up the MSSQL service won't start because it can't
authenticate the user on the service.

On Fri, Apr 8, 2016 at 9:25 AM Nir Soffer  wrote:

> On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb 
> wrote:
> > On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
> >
> > Hi,
> >
> >
> > 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.
> >
> >
> > The engine will try to keep the VM running. So if one host goes down,
> > it will restart the VM on some other host automatically. We will also
> > migrate the VM (or some other to free resources) when the current host
> > gets too loaded. We do not require any migration addons, it just
> > works. But of course we have usually more hosts in a cluster to make
> > this possible.
> >
> > I do not really remember what happens when all hosts are restarted
> > (power outage) though as that is quite special case.
> >
> > Regards
> >
> > --
> > Martin Sivak
> > SLA / oVirt
> >
> >
> >
> > Thanks.  I only have one host so who knows what will happen.  I'm
> working on
> > a script that will basically emulate what VMware does - start VMS in a
> given
> > order at startup of the host/engine.  I'll also file a feature request.
>
> Why do you care about the order?
>
> Isn't it enough to restart all the vms after a host was restarted?
>
> Nir
>
> >
> > On Wed, Apr 6, 2016 at 9:10 PM, 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.
> >
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
-- 
*Michael Kleinpaste*
Senior Systems Administrator
SharperLending, LLC.
www.SharperLending.com
michael.kleinpa...@sharperlending.com
(509) 324-1230   Fax: (509) 324-1234
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Nir Soffer]

On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb  wrote:
> On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
>
> Hi,
>
>
> 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.
>
>
> The engine will try to keep the VM running. So if one host goes down,
> it will restart the VM on some other host automatically. We will also
> migrate the VM (or some other to free resources) when the current host
> gets too loaded. We do not require any migration addons, it just
> works. But of course we have usually more hosts in a cluster to make
> this possible.
>
> I do not really remember what happens when all hosts are restarted
> (power outage) though as that is quite special case.
>
> Regards
>
> --
> Martin Sivak
> SLA / oVirt
>
>
>
> Thanks.  I only have one host so who knows what will happen.  I'm working on
> a script that will basically emulate what VMware does - start VMS in a given
> order at startup of the host/engine.  I'll also file a feature request.

Why do you care about the order?

Isn't it enough to restart all the vms after a host was restarted?

Nir

>
> On Wed, Apr 6, 2016 at 9:10 PM, 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.
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
> Hi,
> 
> > 
> > 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.
> The engine will try to keep the VM running. So if one host goes down,
> it will restart the VM on some other host automatically. We will also
> migrate the VM (or some other to free resources) when the current
> host
> gets too loaded. We do not require any migration addons, it just
> works. But of course we have usually more hosts in a cluster to make
> this possible.
> 
> I do not really remember what happens when all hosts are restarted
> (power outage) though as that is quite special case.
> 
> Regards
> 
> --
> Martin Sivak
> SLA / oVirt
Thanks.  I only have one host so who knows what will happen.  I'm
working on a script that will basically emulate what VMware does -
start VMS in a given order at startup of the host/engine.  I'll also
file a feature request.
> On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb  wrote:
> > 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.
> > 
> > 
> > 
> > 
> > ___
> > Users mailing list
> > 
Users@ovirt.org> > 
http://lists.ovirt.org/mailman/listinfo/users
> > 
> > 
> > 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Martin Sivak]

Hi,

> 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.

The engine will try to keep the VM running. So if one host goes down,
it will restart the VM on some other host automatically. We will also
migrate the VM (or some other to free resources) when the current host
gets too loaded. We do not require any migration addons, it just
works. But of course we have usually more hosts in a cluster to make
this possible.

I do not really remember what happens when all hosts are restarted
(power outage) though as that is quite special case.

Regards

--
Martin Sivak
SLA / oVirt

On Wed, Apr 6, 2016 at 9:10 PM, 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.
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

On Wed, 2016-04-06 at 21:44 +0200, Joop wrote:
> 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
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
I'll do that.  It's really a needed feature to make administration
easier.
I finally got the ovirt-shell connected with the help of this https://b
ugzilla.redhat.com/show_bug.cgi?id=1186365.  The silly thing can't
handle no domain and the error doesn't tell you that.
Oh, well.  We'll play with this and then check out the A
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

On Wed, 2016-04-06 at 21:44 +0200, Joop wrote:
> 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
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
I'll do that.  It's really a needed feature to make administration
easier.
I finally got the ovirt-shell connected with the help of this https://b
ugzilla.redhat.com/show_bug.cgi?id=1186365.  The silly thing can't
handle no domain and the error doesn't tell you that.
Oh, well.  We'll play with this and then check out rest and SDK.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [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

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Brett I. Holcomb]

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.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Autostart VMS

[Adam Litke]

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.

--
Adam Litke
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Autostart VMS

[Brett I. Holcomb]

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.

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users