On Thu, Feb 7, 2019 at 1:59 PM Greg Sheremeta <gshereme(a)redhat.com> wrote:
On Thu, Feb 7, 2019 at 5:28 AM Hetz Ben Hamo <hetz(a)hetz.biz> wrote:
> Hi,
>
> I'm migrating my VM's to oVirt from ESXI and I've only got one left on
> the ESXi side - a VM which provides me DNS, mail and DHCP services. Without
> this VM's, I can't access the internet.
>
I'm not sure about the feasability of running DNS or DHCP in a vm --
hopefully someone else can speak to that.
>
> The only issue that prevents me from migrating this VM to oVirt and
> "kill" the ESXi machine, is that I need to start this VM's upon oVirt
node
> power up (auto start), so if the power goes down and comes back, I'll have
> my infrastructure up and running automatically within minutes.
>
> Is there a way to auto start specific VM's
>
Yes, see
https://www.ovirt.org/documentation/vmm-guide/chap-Administrative_Tasks.h...
and maybe
https://www.ovirt.org/documentation/vmm-guide/chap-Additional_Configurati...
or better - start VM's based on specific orders upon boot of the nodes? I
> think it's a very important feature.
>
Affinity might help here, not sure.
https://www.ovirt.org/documentation/vmm-guide/chap-Administrative_Tasks.h...
We need to split the problems in two:
- the first step is bringing oVirt engine and oVirt hosted-engine is
designed for that purpose: ovirt-ha-agent will connect the storage and
bring up a VM with the engine in a matter of minutes (*)
- than, once you have a running engine, you can rely on the HA mechanism
with VM leases and so on to restart the VMs that you need to be in HA.
Please notice that at engine level you have a kind of HA priority mechanism
to influence the VM boostrap order without really setting dependencies or
something like that:
http://ovirt.github.io/ovirt-engine-api-model/master/#types/high_availabi...
Please notice that the graphical user interface (GUI) does not allow
specifying all the possible values, instead it only allows you to select
Low, Medium or High. If you need a finer granularity you have to set them
via REST APIs.
Then, in the second plane, you should also take a look to
VmStorageErrorResumeBehaviour:
http://ovirt.github.io/ovirt-engine-api-model/master/#types/vm_storage_er...
to eventually handle the resume after storage errors.
and you can also eventually define per VM watchdogs:
http://ovirt.github.io/ovirt-engine-api-model/master/#services/vm_watchdog
* Please notice that you should configure your env to be sure that your HE
hosts and the engine VM are able to correctly start even without a properly
running DHCP and DNS.
Best wishes,
Greg
>
> Thanks
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-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/users@ovirt.org/message/NJLGLSOTMNU...
>
--
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>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/7L4KXO3ESAF...