<div dir="ltr">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.</div><br><div class="gmail_quote"><div dir="ltr">On Fri, Apr 8, 2016 at 9:25 AM Nir Soffer <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb <<a href="mailto:biholcomb@l1049h.com" target="_blank">biholcomb@l1049h.com</a>> wrote:<br>
> On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:<br>
><br>
> Hi,<br>
><br>
><br>
> I set highly available on, did not pin to any host, and also set the<br>
> watchdog which should reset if they go down but I'm not sure that will start<br>
> them if the host comes up and the VMs are not running. I'll look at the CLI<br>
> first.<br>
><br>
><br>
> The engine will try to keep the VM running. So if one host goes down,<br>
> it will restart the VM on some other host automatically. We will also<br>
> migrate the VM (or some other to free resources) when the current host<br>
> gets too loaded. We do not require any migration addons, it just<br>
> works. But of course we have usually more hosts in a cluster to make<br>
> this possible.<br>
><br>
> I do not really remember what happens when all hosts are restarted<br>
> (power outage) though as that is quite special case.<br>
><br>
> Regards<br>
><br>
> --<br>
> Martin Sivak<br>
> SLA / oVirt<br>
><br>
><br>
><br>
> Thanks. I only have one host so who knows what will happen. I'm working on<br>
> a script that will basically emulate what VMware does - start VMS in a given<br>
> order at startup of the host/engine. I'll also file a feature request.<br>
<br>
Why do you care about the order?<br>
<br>
Isn't it enough to restart all the vms after a host was restarted?<br>
<br>
Nir<br>
<br>
><br>
> On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb <<a href="mailto:biholcomb@l1049h.com" target="_blank">biholcomb@l1049h.com</a>><br>
> wrote:<br>
><br>
> On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:<br>
><br>
> On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:<br>
><br>
> In VMware we could setup guests to autostart when the host started and<br>
> define the order. Is that doable in oVirt? The only thing I've seen<br>
> is the watchdog and tell it to reset but nothing that allows me to<br>
> define who starts up when and if they autostart. I assume it's there<br>
> but I must be missing it or haven't found it in the web portal.<br>
><br>
><br>
> In oVirt guests aren't tied to a host by default (although you can set<br>
> them to run only on a specific host if you want). The closest thing I<br>
> can think of would be the High Availability features (VM->Edit).<br>
> oVirt will try to restart highly available VMs if they go down. You<br>
> can also set the priority for migration and restart in that pane.<br>
> Hopefully a combination of host pinning and the high availability<br>
> settings will get you close enough to where you want to be.<br>
><br>
> Otherwise, you could always do some scripting with the ovirt REST API<br>
> using the SDK or CLI.<br>
><br>
><br>
> If you had the VMware migration extra add-on you could have hosts move as<br>
> needed so they were not tied to any host either but we could set a startup<br>
> order and specify auto, manual so that once the host started the VMs were<br>
> brought up as specified no matter what host they were running on.<br>
><br>
> I am running hosted-engine deployment with the Engine VM on the host.<br>
><br>
> I set highly available on, did not pin to any host, and also set the<br>
> watchdog which should reset if they go down but I'm not sure that will start<br>
> them if the host comes up and the VMs are not running. I'll look at the CLI<br>
> first.<br>
><br>
> It would be nice if oVirt added this feature as it's really required for<br>
> large installations and is a help for any size installation, even small<br>
> ones.<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr"><b>Michael Kleinpaste</b><br><span>Senior Systems Administrator</span><br><span>SharperLending, LLC.</span><br><a>www.SharperLending.com</a><br><span>Michael.Kleinpaste@SharperLending.com</span><br><span>(509) 324-1230 Fax: (509) 324-1234</span></div>