[Users] Auto-start vms on boot?
It would seem that oVirt does not provide an standard way of forcing boot of virtual machines at boot. Pools can have pre-started vms as stated here: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... but pools imply state-less virtual machines and I am talking more about normal virtual machines. I've found this script: https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py which could do to the trick if run at host boot. I've also thought (but not tried) to mark a virtual machine as "Highly Available" even if I have only one host (I mean, usually HA only makes sense when you have two hosts). Marking a VM as H.A. would do the trick? Any special reason why there isn't and standard way of marking which vms should be auto-started at boot? Just wanted to hear your thoughts before filling an RFE. Thank you. -- -- Adrián Gibanel I.T. Manager +34 675 683 301 www.btactic.com Ens podeu seguir a/Nos podeis seguir en: i Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge . AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje .
On 12/06/2012 10:34 PM, Adrian Gibanel wrote:
It would seem that oVirt does not provide an standard way of forcing boot of virtual machines at boot.
Pools can have pre-started vms as stated here: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... but pools imply state-less virtual machines and I am talking more about normal virtual machines.
I've found this script:
https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py
which could do to the trick if run at host boot.
I've also thought (but not tried) to mark a virtual machine as "Highly Available" even if I have only one host (I mean, usually HA only makes sense when you have two hosts).
Marking a VM as H.A. would do the trick? Any special reason why there isn't and standard way of marking which vms should be auto-started at boot?
Just wanted to hear your thoughts before filling an RFE.
Thank you.
what exactly is your use case? the one i'm familiar with is to tie the VM life cycle to a specific host, so a VM which is pinned to a specific host for a certain task (say, IDS), is always starting when the host starts, and will be automatically shutdown when host is moved to maintenance. so only relevant for VMs which are pinned to a host. Thanks, Itamar
My use case is that I just don't want to start manually the virtual machines when the host starts and, also, if the host is shutdown it should guest-shutdown the virtual machines. Any doc on that pin option? How one is supposed to pin a virtual machine to a host? Thank you. ----- Mensaje original -----
De: "Itamar Heim" <iheim@redhat.com> Para: "Adrian Gibanel" <adrian.gibanel@btactic.com> CC: "users" <users@ovirt.org> Enviados: Viernes, 7 de Diciembre 2012 15:49:36 Asunto: Re: [Users] Auto-start vms on boot?
On 12/06/2012 10:34 PM, Adrian Gibanel wrote:
It would seem that oVirt does not provide an standard way of forcing boot of virtual machines at boot.
Pools can have pre-started vms as stated here: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... but pools imply state-less virtual machines and I am talking more about normal virtual machines.
I've found this script:
https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py
which could do to the trick if run at host boot.
I've also thought (but not tried) to mark a virtual machine as "Highly Available" even if I have only one host (I mean, usually HA only makes sense when you have two hosts).
Marking a VM as H.A. would do the trick? Any special reason why there isn't and standard way of marking which vms should be auto-started at boot?
Just wanted to hear your thoughts before filling an RFE.
Thank you.
what exactly is your use case? the one i'm familiar with is to tie the VM life cycle to a specific host, so a VM which is pinned to a specific host for a certain task (say, IDS), is always starting when the host starts, and will be automatically shutdown when host is moved to maintenance. so only relevant for VMs which are pinned to a host.
Thanks, Itamar
-- -- Adrián Gibanel I.T. Manager +34 675 683 301 www.btactic.com Ens podeu seguir a/Nos podeis seguir en: i Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge . AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje .
On 12/07/2012 06:23 PM, Adrian Gibanel wrote:
My use case is that I just don't want to start manually the virtual machines when the host starts and, also, if the host is shutdown it should guest-shutdown the virtual machines.
Any doc on that pin option? How one is supposed to pin a virtual machine to a host?
just to be clear, we still don't have the behavior i described. I just stated the only use case i'm familiar for a similar requirement. (pinning a VM to host is done via the edit vm dialog). question on your use case - how would the engine know if the admin just shutdown a VM manually from a VM which should be auto started (should we add such a checkbox). in the use case i described, we would be adding a 'start/stop VM with host' for a VM pinned to a host.
Thank you.
----- Mensaje original -----
De: "Itamar Heim" <iheim@redhat.com> Para: "Adrian Gibanel" <adrian.gibanel@btactic.com> CC: "users" <users@ovirt.org> Enviados: Viernes, 7 de Diciembre 2012 15:49:36 Asunto: Re: [Users] Auto-start vms on boot?
On 12/06/2012 10:34 PM, Adrian Gibanel wrote:
It would seem that oVirt does not provide an standard way of forcing boot of virtual machines at boot.
Pools can have pre-started vms as stated here: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... but pools imply state-less virtual machines and I am talking more about normal virtual machines.
I've found this script:
https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py
which could do to the trick if run at host boot.
I've also thought (but not tried) to mark a virtual machine as "Highly Available" even if I have only one host (I mean, usually HA only makes sense when you have two hosts).
Marking a VM as H.A. would do the trick? Any special reason why there isn't and standard way of marking which vms should be auto-started at boot?
Just wanted to hear your thoughts before filling an RFE.
Thank you.
what exactly is your use case? the one i'm familiar with is to tie the VM life cycle to a specific host, so a VM which is pinned to a specific host for a certain task (say, IDS), is always starting when the host starts, and will be automatically shutdown when host is moved to maintenance. so only relevant for VMs which are pinned to a host.
Thanks, Itamar
------=_Part_136_25560618.1355057754260 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable This is how I see it:=20 Engine should have an offline database of its assigned hosts and their stat= e (With state I mean properties. One of these properties would be the auto-= start one).=20 So when a host starts the engine starts and then loops assigned virtual mac= hines. While looping the virtual machines checs its auto-start property. If= it's set to true it starts the virtual machine.=20 Not sure if what I am describing has an easy implementation with current oV= irt architecture. Any comments from people who might understand better oVir= t architecture on this use-case?=20 I think the hosts should rely the least possible on the management server.= =20 ----- Mensaje original -----
De: "Itamar Heim" <iheim@redhat.com> Para: "Adrian Gibanel" <adrian.gibanel@btactic.com> CC: "users" <users@ovirt.org> Enviados: Viernes, 7 de Diciembre 2012 19:39:26 Asunto: Re: [Users] Auto-start vms on boot?
On 12/07/2012 06:23 PM, Adrian Gibanel wrote:
My use case is that I just don't want to start manually the virtual machines when the host starts and, also, if the host is shutdown it should guest-shutdown the virtual machines.
Any doc on that pin option? How one is supposed to pin a virtual machine to a host?
just to be clear, we still don't have the behavior i described. I just stated the only use case i'm familiar for a similar requirement. (pinning a VM to host is done via the edit vm dialog).
question on your use case - how would the engine know if the admin just shutdown a VM manually from a VM which should be auto started (should we add such a checkbox). in the use case i described, we would be adding a 'start/stop VM with host' for a VM pinned to a host.
Thank you.
----- Mensaje original -----
On 12/06/2012 10:34 PM, Adrian Gibanel wrote:
It would seem that oVirt does not provide an standard way of forcing boot of virtual machines at boot.
Pools can have pre-started vms as stated here: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Vir=
tualization/3.1/html/Administration_Guide/Prestarting_Virtual_Machines_in_a= _Pool.html
but pools imply state-less virtual machines and I am talking more about normal virtual machines.
I've found this script:
https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py
which could do to the trick if run at host boot.
I've also thought (but not tried) to mark a virtual machine as "Highly Available" even if I have only one host (I mean, usually HA only makes sense when you have two hosts).
Marking a VM as H.A. would do the trick? Any special reason why there isn't and standard way of marking which vms should be auto-started at boot?
Just wanted to hear your thoughts before filling an RFE.
Thank you.
what exactly is your use case? the one i'm familiar with is to tie the VM life cycle to a specific host, so a VM which is pinned to a specific host for a certain task (say, IDS), is always starting when the host starts, and will be automatically shutdown when host is moved to maintenance. so only relevant for VMs which are pinned to a host.
"users" <users@ovirt.org><br><b>Enviados: </b>Viernes, 7 de Diciembr= e 2012 19:39:26<br><b>Asunto: </b>Re: [Users] Auto-start vms on boot?<br><b= r>On 12/07/2012 06:23 PM, Adrian Gibanel wrote:<br>> My use case is that= I just don't want to start manually the virtual machines when the host sta= rts and, also, if the host is shutdown it should guest-shutdown the virtual= machines.<br>><br>> Any doc on that pin option? How one is supposed = to pin a virtual machine to a host?<br><br>just to be clear, we still don't= have the behavior i described. I just <br>stated the only use case i'm fam= iliar for a similar requirement.<br>(pinning a VM to host is done via the e= dit vm dialog).<br><br>question on your use case - how would the engine kno= w if the admin just <br>shutdown a VM manually from a VM which should be au= to started (should we <br>add such a checkbox).<br>in the use case i descri= bed, we would be adding a 'start/stop VM with <br>host' for a VM pinned to = a host.<br><br>><br>> Thank you.<br>><br>> ----- Mensaje origin= al -----<br>><br>>> On 12/06/2012 10:34 PM, Adrian Gibanel wrote:<= br>>>> It would seem that oVirt does not provide an standard way o= f<br>>>> forcing boot of virtual machines at boot.<br>>>>= <br>>>> Pools can have pre-started vms as stated here:<br>>>= > https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virt= ualization/3.1/html/Administration_Guide/Prestarting_Virtual_Machines_in_a_= Pool.html<br>>>> but pools imply state-less virtual machines and I= am talking more<br>>>> about normal virtual machines.<br>>>= ><br>>>> I've found this script:<br>>>><br>>>>= ; https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py<br>>= ;>><br>>>> which could do to the trick if run at host boot.<= br>>>><br>>>> I've also thought (but not tried) to mark a= virtual machine as<br>>>> "Highly Available" even if I have only = one host (I mean, usually<br>>>> HA only makes sense when you have= two hosts).<br>>>><br>>>> Marking a VM as H.A. would do =
>>><br>>>> Just wanted to hear your thoughts before fill= ing an RFE.<br>>>><br>>>><br>>>> Thank you.<br>&= gt;>><br>>> what exactly is your use case?<br>>> the one = i'm familiar with is to tie the VM life cycle to a specific<br>>> hos= t, so a VM which is pinned to a specific host for a certain task<br>>>= ; (say, IDS), is always starting when the host starts, and will be<br>>&= gt; automatically shutdown when host is moved to maintenance.<br>>> s= o only relevant for VMs which are pinned to a host.<br></blockquote>-- <br>= <div><span name=3D"x"></span><font style=3D"font-weight: bold;" size=3D"3">= <a style=3D"color: rgb(0, 0, 0);" href=3D"http://www.btactic.com/"><span id= =3D"DWT100"><font class=3D"Apple-style-span" face=3D"verdana, helvetica, sa= ns-serif"><span class=3D"Apple-style-span" style=3D"background-color: rgb(2= 55, 255, 255);"></span></font></span></a></font><font style=3D"font-family:= 'Times New Roman';" color=3D"#5f5f5f" face=3D"Arial" size=3D"1"><font size= =3D"3"><span style=3D"font-family: verdana,helvetica,sans-serif; color: rgb= (0, 0, 0);"><font style=3D"font-family: helvetica;" size=3D"2"><strong>Adri= =C3=A1n Gibanel</strong><br>I.T. Manager<br><br>+34 675 683 301<br><a href= =3D"http://btactic.com/">www.btactic.com</a></font><br><br></span></font></= font><font color=3D"#008000" face=3D"Arial" size=3D"1"><img src=3D"http://w= ww.btactic.com/signaturabtacticmail/btacticsignature.png" style=3D"border-w= idth: 0px;"><br></font><font class=3D"Apple-style-span" face=3D"Arial"><b><= span class=3D"Apple-style-span" style=3D"font-family: Verdana; font-weight:= normal;"><span id=3D"bc4bed34-88ab-466b-a731-c40f5c09ab6c"><font color=3D"= #5f5f5f" face=3D"Arial" size=3D"1"><br>Ens podeu seguir a/Nos podeis seguir= en:<br> <br> </font></span><a href=3D"http://www.facebook.com/pages/btactic/118651634826= 400?v=3Dapp_9953271133"><img style=3D"border: 0pt none;" src=3D"http://www.= btactic.com/wp-content/themes/btactic/img/facebookfoot.jpg"></a> i <a href= =3D"http://twitter.com/btactic"><img style=3D"border: 0pt none;" src=3D"htt=
--=20 Adri=C3=A1n Gibanel=20 I.T. Manager=20 +34 675 683 301=20 www.btactic.com=20 Ens podeu seguir a/Nos podeis seguir en:=20 i=20 Abans d=C2=B4imprimir aquest missatge, pensa en el medi ambient. El medi am= bient =C3=A9s cosa de tothom. / Antes de imprimir el mensaje piensa en el m= edio ambiente. El medio ambiente es cosa de todos.=20 AVIS:=20 El contingut d'aquest missatge i els seus annexos =C3=A9s confidencial. Si = no en sou el destinatari, us fem saber que est=C3=A0 prohibit utilitzar-lo,= divulgar-lo i/o copiar-lo sense tenir l'autoritzaci=C3=B3 corresponent. Si= heu rebut aquest missatge per error, us agrairem que ho feu saber immediat= ament al remitent i que procediu a destruir el missatge .=20 AVISO:=20 El contenido de este mensaje y de sus anexos es confidencial. Si no es el d= estinatario, les hacemos saber que est=C3=A1 prohibido utilizarlo, divulgar= lo y/o copiarlo sin tener la autorizaci=C3=B3n correspondiente. Si han reci= bido este mensaje por error, les agradecer=C3=ADamos que lo hagan saber inm= ediatamente al remitente y que procedan a destruir el mensaje .=20 ------=_Part_136_25560618.1355057754260 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo= r: #000000'>This is how I see it:<br><br>Engine should have an offline data= base of its assigned hosts and their state (With state I mean properties. O= ne of these properties would be the auto-start one).<br>So when a host star= ts the engine starts and then loops assigned virtual machines. While loopin= g the virtual machines checs its auto-start property. If it's set to true i= t starts the virtual machine.<br><br>Not sure if what I am describing has a= n easy implementation with current oVirt architecture. Any comments from pe= ople who might understand better oVirt architecture on this use-case?<br><b= r>I think the hosts should rely the least possible on the management server= .<br><br><hr id=3D"zwchr"><blockquote style=3D"border-left:2px solid rgb(16= , 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;f= ont-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-seri= f;font-size:12pt;"><b>De: </b>"Itamar Heim" <iheim@redhat.com><br><b>= Para: </b>"Adrian Gibanel" <adrian.gibanel@btactic.com><br><b>CC: </b= the trick?<br>>>> Any special reason why there isn't and standard = way of marking<br>>>> which vms should be auto-started at boot?<br= p://www.btactic.com/wp-content/themes/btactic/img/twitterfoot.jpg"></a></sp= an></b></font><br><font color=3D"#008000" face=3D"Arial" size=3D"1"><br></f= ont><div><font color=3D"#008000" face=3D"Arial" size=3D"1">Abans d=C2=B4imp= rimir aquest missatge, pensa en el medi ambient. El medi ambient =C3=A9s cosa de= =20 tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio=20 ambiente es cosa de todos. </font><font color=3D"#5f5f5f" face=3D"Arial" size=3D"1">= <br> <br> AVIS: <br> El contingut d'aquest missatge i els seus annexos =C3=A9s confidencial. Si = no en sou el destinatari, us fem saber que est=C3=A0 prohibit utilitzar-lo,=20 divulgar-lo i/o copiar-lo sense tenir l'autoritzaci=C3=B3 corresponent. Si heu rebut=20 aquest missatge per error, us agrairem que ho feu saber immediatament <span class= =3D"Object" id=3D"OBJ_PREFIX_DWT103">al remitent i que procediu a destruir el missatge</span>.<br> <br> AVISO:<br> El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que est=C3=A1 prohibido utilizarlo,=20 divulgarlo y/o copiarlo sin tener la autorizaci=C3=B3n correspondiente. Si han recibid= o este mensaje por error, les agradecer=C3=ADamos que lo hagan saber=20 inmediatamente <span class=3D"Object" id=3D"OBJ_PREFIX_DWT104">al remitente y que procedan= a destruir el mensaje</span>.</font> </div><span name=3D"x"></span><br></div></div></body></html> ------=_Part_136_25560618.1355057754260--
On 12/09/2012 02:55 PM, Adrian Gibanel wrote:
This is how I see it:
Engine should have an offline database of its assigned hosts and their state (With state I mean properties. One of these properties would be the auto-start one). So when a host starts the engine starts and then loops assigned virtual machines. While looping the virtual machines checs its auto-start property. If it's set to true it starts the virtual machine.
Not sure if what I am describing has an easy implementation with current oVirt architecture. Any comments from people who might understand better oVirt architecture on this use-case?
I think the hosts should rely the least possible on the management server.
my concern is how to make sure engine only starts VMs it should in this case.
------------------------------------------------------------------------
*De: *"Itamar Heim" <iheim@redhat.com> *Para: *"Adrian Gibanel" <adrian.gibanel@btactic.com> *CC: *"users" <users@ovirt.org> *Enviados: *Viernes, 7 de Diciembre 2012 19:39:26 *Asunto: *Re: [Users] Auto-start vms on boot?
On 12/07/2012 06:23 PM, Adrian Gibanel wrote: > My use case is that I just don't want to start manually the virtual machines when the host starts and, also, if the host is shutdown it should guest-shutdown the virtual machines. > > Any doc on that pin option? How one is supposed to pin a virtual machine to a host?
just to be clear, we still don't have the behavior i described. I just stated the only use case i'm familiar for a similar requirement. (pinning a VM to host is done via the edit vm dialog).
question on your use case - how would the engine know if the admin just shutdown a VM manually from a VM which should be auto started (should we add such a checkbox). in the use case i described, we would be adding a 'start/stop VM with host' for a VM pinned to a host.
> > Thank you. > > ----- Mensaje original ----- > >> On 12/06/2012 10:34 PM, Adrian Gibanel wrote: >>> It would seem that oVirt does not provide an standard way of >>> forcing boot of virtual machines at boot. >>> >>> Pools can have pre-started vms as stated here: >>> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... >>> but pools imply state-less virtual machines and I am talking more >>> about normal virtual machines. >>> >>> I've found this script: >>> >>> https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py >>> >>> which could do to the trick if run at host boot. >>> >>> I've also thought (but not tried) to mark a virtual machine as >>> "Highly Available" even if I have only one host (I mean, usually >>> HA only makes sense when you have two hosts). >>> >>> Marking a VM as H.A. would do the trick? >>> Any special reason why there isn't and standard way of marking >>> which vms should be auto-started at boot? >>> >>> Just wanted to hear your thoughts before filling an RFE. >>> >>> >>> Thank you. >>> >> what exactly is your use case? >> the one i'm familiar with is to tie the VM life cycle to a specific >> host, so a VM which is pinned to a specific host for a certain task >> (say, IDS), is always starting when the host starts, and will be >> automatically shutdown when host is moved to maintenance. >> so only relevant for VMs which are pinned to a host.
-- <http://www.btactic.com/>*Adrián Gibanel* I.T. Manager
+34 675 683 301 www.btactic.com <http://btactic.com/>
* Ens podeu seguir a/Nos podeis seguir en:
<http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133> i <http://twitter.com/btactic>*
Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos.
AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge.
AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, I'm not involved on the ovirt development, but here are my thoughts: 1. oVirt makes sense on a datacenter scenario, where there is always a HA management server that takes care of everything, including the management of all VMs state. 2. If you want such a tight relation between the host and the VMs running on it, you don't need oVirt, just "plain" host virtualization, like the one that comes on every linux distro with virt-manager.There you can install and manage the VMs on a single host, forcing them to stop or start on host shutdown or boot. 3. This is what I've been doing myself. Virt-manager can manage all hosts running kvm/qemu but don't have this datacenter approach, where you store your VMs on a SAN/iSCSI and you run you VMs on diskless hosts and can migrate them as you which, for instance. If the oVirt developers think that i?m missing something or that I'm wrong, please come and correct me :-) Alex 2012/12/9 Itamar Heim <iheim@redhat.com>
On 12/09/2012 02:55 PM, Adrian Gibanel wrote:
This is how I see it:
Engine should have an offline database of its assigned hosts and their state (With state I mean properties. One of these properties would be the auto-start one). So when a host starts the engine starts and then loops assigned virtual machines. While looping the virtual machines checs its auto-start property. If it's set to true it starts the virtual machine.
Not sure if what I am describing has an easy implementation with current oVirt architecture. Any comments from people who might understand better oVirt architecture on this use-case?
I think the hosts should rely the least possible on the management server.
my concern is how to make sure engine only starts VMs it should in this case.
------------------------------**------------------------------** ------------
*De: *"Itamar Heim" <iheim@redhat.com> *Para: *"Adrian Gibanel" <adrian.gibanel@btactic.com> *CC: *"users" <users@ovirt.org> *Enviados: *Viernes, 7 de Diciembre 2012 19:39:26 *Asunto: *Re: [Users] Auto-start vms on boot?
On 12/07/2012 06:23 PM, Adrian Gibanel wrote: > My use case is that I just don't want to start manually the virtual machines when the host starts and, also, if the host is shutdown it should guest-shutdown the virtual machines. > > Any doc on that pin option? How one is supposed to pin a virtual machine to a host?
just to be clear, we still don't have the behavior i described. I just stated the only use case i'm familiar for a similar requirement. (pinning a VM to host is done via the edit vm dialog).
question on your use case - how would the engine know if the admin just shutdown a VM manually from a VM which should be auto started (should we add such a checkbox). in the use case i described, we would be adding a 'start/stop VM with host' for a VM pinned to a host.
> > Thank you. > > ----- Mensaje original ----- > >> On 12/06/2012 10:34 PM, Adrian Gibanel wrote: >>> It would seem that oVirt does not provide an standard way of >>> forcing boot of virtual machines at boot. >>> >>> Pools can have pre-started vms as stated here: >>> https://access.redhat.com/**knowledge/docs/en-US/Red_Hat_** Enterprise_Virtualization/3.1/**html/Administration_Guide/** Prestarting_Virtual_Machines_**in_a_Pool.html<https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/Prestarting_Virtual_Machines_in_a_Pool.html> >>> but pools imply state-less virtual machines and I am talking more >>> about normal virtual machines. >>> >>> I've found this script: >>> >>> https://github.com/iranzo/**rhevm-utils/blob/master/rhev-** vm-start.py<https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py> >>> >>> which could do to the trick if run at host boot. >>> >>> I've also thought (but not tried) to mark a virtual machine as >>> "Highly Available" even if I have only one host (I mean, usually >>> HA only makes sense when you have two hosts). >>> >>> Marking a VM as H.A. would do the trick? >>> Any special reason why there isn't and standard way of marking >>> which vms should be auto-started at boot? >>> >>> Just wanted to hear your thoughts before filling an RFE. >>> >>> >>> Thank you. >>> >> what exactly is your use case? >> the one i'm familiar with is to tie the VM life cycle to a specific >> host, so a VM which is pinned to a specific host for a certain task >> (say, IDS), is always starting when the host starts, and will be >> automatically shutdown when host is moved to maintenance. >> so only relevant for VMs which are pinned to a host.
-- <http://www.btactic.com/>***Adrián Gibanel*
I.T. Manager
+34 675 683 301 www.btactic.com <http://btactic.com/>
* Ens podeu seguir a/Nos podeis seguir en:
<http://www.facebook.com/**pages/btactic/118651634826400?** v=app_9953271133<http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133>
i <http://twitter.com/btactic>*
Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos.
AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge.
AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje.
______________________________**_________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org/mailman/listinfo/users>
______________________________**_________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org/mailman/listinfo/users>
On 12/09/2012 05:11 PM, Alexandre Santos wrote:
Hi, I'm not involved on the ovirt development, but here are my thoughts: 1. oVirt makes sense on a datacenter scenario, where there is always a HA management server that takes care of everything, including the management of all VMs state. 2. If you want such a tight relation between the host and the VMs running on it, you don't need oVirt, just "plain" host virtualization, like the one that comes on every linux distro with virt-manager.There you can install and manage the VMs on a single host, forcing them to stop or start on host shutdown or boot.
the 'tight' relation in the use case i mentioned is only for some of the VMs which serve a specific purpose on each host (say, an IDS virtual appliance for all traffic on a specific host). the rest of the VMs would be 'normal'.
3. This is what I've been doing myself. Virt-manager can manage all hosts running kvm/qemu but don't have this datacenter approach, where you store your VMs on a SAN/iSCSI and you run you VMs on diskless hosts and can migrate them as you which, for instance.
If the oVirt developers think that i?m missing something or that I'm wrong, please come and correct me :-)
I'm just trying to understand your use case to see how it can be resolved. (btw, you can probably easily script this via the api/sdk/cli with a small script checking a list of VMs are always up. I just wonder how you'll know they aren't meant to be down by admin) would the admin have to disable the 'auto start' config before shutting down the VM, or else the engine will auto-start it again?
Alex
2012/12/9 Itamar Heim <iheim@redhat.com <mailto:iheim@redhat.com>>
On 12/09/2012 02:55 PM, Adrian Gibanel wrote:
This is how I see it:
Engine should have an offline database of its assigned hosts and their state (With state I mean properties. One of these properties would be the auto-start one). So when a host starts the engine starts and then loops assigned virtual machines. While looping the virtual machines checs its auto-start property. If it's set to true it starts the virtual machine.
Not sure if what I am describing has an easy implementation with current oVirt architecture. Any comments from people who might understand better oVirt architecture on this use-case?
I think the hosts should rely the least possible on the management server.
my concern is how to make sure engine only starts VMs it should in this case.
------------------------------__------------------------------__------------
*De: *"Itamar Heim" <iheim@redhat.com <mailto:iheim@redhat.com>> *Para: *"Adrian Gibanel" <adrian.gibanel@btactic.com <mailto:adrian.gibanel@btactic.com>> *CC: *"users" <users@ovirt.org <mailto:users@ovirt.org>> *Enviados: *Viernes, 7 de Diciembre 2012 19:39:26 *Asunto: *Re: [Users] Auto-start vms on boot?
On 12/07/2012 06:23 PM, Adrian Gibanel wrote: > My use case is that I just don't want to start manually the virtual machines when the host starts and, also, if the host is shutdown it should guest-shutdown the virtual machines. > > Any doc on that pin option? How one is supposed to pin a virtual machine to a host?
just to be clear, we still don't have the behavior i described. I just stated the only use case i'm familiar for a similar requirement. (pinning a VM to host is done via the edit vm dialog).
question on your use case - how would the engine know if the admin just shutdown a VM manually from a VM which should be auto started (should we add such a checkbox). in the use case i described, we would be adding a 'start/stop VM with host' for a VM pinned to a host.
> > Thank you. > > ----- Mensaje original ----- > >> On 12/06/2012 10:34 PM, Adrian Gibanel wrote: >>> It would seem that oVirt does not provide an standard way of >>> forcing boot of virtual machines at boot. >>> >>> Pools can have pre-started vms as stated here: >>> https://access.redhat.com/__knowledge/docs/en-US/Red_Hat___Enterprise_Virtua... <https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/Prestarting_Virtual_Machines_in_a_Pool.html> >>> but pools imply state-less virtual machines and I am talking more >>> about normal virtual machines. >>> >>> I've found this script: >>> >>> https://github.com/iranzo/__rhevm-utils/blob/master/rhev-__vm-start.py <https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py> >>> >>> which could do to the trick if run at host boot. >>> >>> I've also thought (but not tried) to mark a virtual machine as >>> "Highly Available" even if I have only one host (I mean, usually >>> HA only makes sense when you have two hosts). >>> >>> Marking a VM as H.A. would do the trick? >>> Any special reason why there isn't and standard way of marking >>> which vms should be auto-started at boot? >>> >>> Just wanted to hear your thoughts before filling an RFE. >>> >>> >>> Thank you. >>> >> what exactly is your use case? >> the one i'm familiar with is to tie the VM life cycle to a specific >> host, so a VM which is pinned to a specific host for a certain task >> (say, IDS), is always starting when the host starts, and will be >> automatically shutdown when host is moved to maintenance. >> so only relevant for VMs which are pinned to a host.
-- <http://www.btactic.com/>*__Adrián Gibanel*
I.T. Manager
+34 675 683 301 <tel:%2B34%20675%20683%20301> www.btactic.com <http://www.btactic.com> <http://btactic.com/>
* Ens podeu seguir a/Nos podeis seguir en:
<http://www.facebook.com/__pages/btactic/118651634826400?__v=app_9953271133 <http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133>> i <http://twitter.com/btactic>*
Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos.
AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge.
AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje.
_________________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
_________________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/__mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
participantes (3)
-
Adrian Gibanel -
Alexandre Santos -
Itamar Heim