Hi,<br>I'm not involved on the ovirt development, but here are my thoughts:<br>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.<br>
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.<br>
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.<br>
<br>If the oVirt developers think that i?m missing something or that I'm wrong, please come and correct me :-)<br><br>Alex<br><br><div class="gmail_quote">2012/12/9 Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12/09/2012 02:55 PM, Adrian Gibanel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is how I see it:<br>
<br>
Engine should have an offline database of its assigned hosts and their<br>
state (With state I mean properties. One of these properties would be<br>
the auto-start one).<br>
So when a host starts the engine starts and then loops assigned virtual<br>
machines. While looping the virtual machines checs its auto-start<br>
property. If it's set to true it starts the virtual machine.<br>
<br>
Not sure if what I am describing has an easy implementation with current<br>
oVirt architecture. Any comments from people who might understand better<br>
oVirt architecture on this use-case?<br>
<br>
I think the hosts should rely the least possible on the management server.<br>
</blockquote>
<br></div>
my concern is how to make sure engine only starts VMs it should in this case.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
*De: *"Itamar Heim" <<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>><br>
*Para: *"Adrian Gibanel" <<a href="mailto:adrian.gibanel@btactic.com" target="_blank">adrian.gibanel@btactic.com</a>><br>
*CC: *"users" <<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>><br>
*Enviados: *Viernes, 7 de Diciembre 2012 19:39:26<br>
*Asunto: *Re: [Users] Auto-start vms on boot?<div><div class="h5"><br>
<br>
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<br>
virtual machines when the host starts and, also, if the host is<br>
shutdown it should guest-shutdown the virtual machines.<br>
><br>
> Any doc on that pin option? How one is supposed to pin a virtual<br>
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 familiar for a similar requirement.<br>
(pinning a VM to host is done via the edit vm dialog).<br>
<br>
question on your use case - how would the engine know if the admin just<br>
shutdown a VM manually from a VM which should be auto started<br>
(should we<br>
add such a checkbox).<br>
in the use case i described, 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 original -----<br>
><br>
>> On 12/06/2012 10:34 PM, Adrian Gibanel wrote:<br>
>>> It would seem that oVirt does not provide an standard way of<br>
>>> forcing boot of virtual machines at boot.<br>
>>><br>
>>> Pools can have pre-started vms as stated here:<br>
>>><br>
<a href="https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/Prestarting_Virtual_Machines_in_a_Pool.html" target="_blank">https://access.redhat.com/<u></u>knowledge/docs/en-US/Red_Hat_<u></u>Enterprise_Virtualization/3.1/<u></u>html/Administration_Guide/<u></u>Prestarting_Virtual_Machines_<u></u>in_a_Pool.html</a><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>
>>> <a href="https://github.com/iranzo/rhevm-utils/blob/master/rhev-vm-start.py" target="_blank">https://github.com/iranzo/<u></u>rhevm-utils/blob/master/rhev-<u></u>vm-start.py</a><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 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>
>>><br>
>>> Just wanted to hear your thoughts before filling an RFE.<br>
>>><br>
>>><br>
>>> Thank you.<br>
>>><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>
>> host, 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>
>> automatically shutdown when host is moved to maintenance.<br>
>> so only relevant for VMs which are pinned to a host.<br>
<br>
--<br></div></div>
<<a href="http://www.btactic.com/" target="_blank">http://www.btactic.com/</a>>*<u></u>Adrián Gibanel*<div class="im"><br>
I.T. Manager<br>
<br>
<a href="tel:%2B34%20675%20683%20301" value="+34675683301" target="_blank">+34 675 683 301</a><br>
</div><a href="http://www.btactic.com" target="_blank">www.btactic.com</a> <<a href="http://btactic.com/" target="_blank">http://btactic.com/</a>><div class="im"><br>
<br>
<br>
*<br>
Ens podeu seguir a/Nos podeis seguir en:<br>
<br></div>
<<a href="http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133" target="_blank">http://www.facebook.com/<u></u>pages/btactic/118651634826400?<u></u>v=app_9953271133</a>><br>
i <<a href="http://twitter.com/btactic" target="_blank">http://twitter.com/btactic</a>>*<div class="im"><br>
<br>
Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi<br>
ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el<br>
medio ambiente. El medio ambiente es cosa de todos.<br>
<br>
AVIS:<br>
El contingut d'aquest missatge i els seus annexos és confidencial. Si no<br>
en sou el destinatari, us fem saber que estŕ prohibit utilitzar-lo,<br>
divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si<br>
heu rebut aquest missatge per error, us agrairem que ho feu saber<br>
immediatament al remitent i que procediu a destruir el missatge.<br>
<br>
AVISO:<br>
El contenido de este mensaje y de sus anexos es confidencial. Si no es<br>
el destinatario, les hacemos saber que está prohibido utilizarlo,<br>
divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si<br>
han recibido este mensaje por error, les agradeceríamos que lo hagan<br>
saber inmediatamente al remitente y que procedan a destruir el mensaje.<br>
<br>
<br>
<br></div><div class="im">
______________________________<u></u>_________________<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" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<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" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>