I apologize, the message was both for Patrice and Alberto Picón, who raised the initial questions.<br><div><br><div class="gmail_quote">On Thu, Oct 27, 2011 at 11:30 AM, Jaime Melis <span dir="ltr"><<a href="mailto:jmelis@opennebula.org">jmelis@opennebula.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello Patrice,<div><br></div><div>you make very valid points and we're aware of those limitations. They have actually been reflected on the documentation:</div>
<div><a href="http://opennebula.org/documentation:rel3.0:nm#considerations_limitations" target="_blank">http://opennebula.org/documentation:rel3.0:nm#considerations_limitations</a></div>
<div><br>The problem is that the network management is based on the hook subsystem, but we have realized there should be a specific driver for networking. We have created a feature ticket to develop this functionality:</div>
<div><a href="http://dev.opennebula.org/issues/863" target="_blank">http://dev.opennebula.org/issues/863</a></div><div>The target release for this functionality is OpenNebula 3.2.</div><div><br></div><div>For the moment, in OpenNebula 3.0, the only solution to the aforementioned problems is to create a static network configuration.</div>
<div><br></div><div>Regards,</div><div>Jaime</div><div><div></div><div class="h5"><div><br></div><div><div class="gmail_quote">On Mon, Oct 17, 2011 at 5:59 PM, Patrice LACHANCE <span dir="ltr"><<a href="mailto:patlachance@gmail.com" target="_blank">patlachance@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello<br><br>In previous version there was a cluster feature that was replaced in OpenNebula 3.0 by ozones.<br>Shouldn't opennebula make sure that all the nodes in a zone are able to run a vm and thus handle network creation on all nodes before starting a new VM?<br>
<br>Patrice<br><br><div class="gmail_quote"><div><div></div><div>2011/9/27 Alberto Picón Couselo <span dir="ltr"><<a href="mailto:alpicon1@gmail.com" target="_blank">alpicon1@gmail.com</a>></span><br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>
<u></u>
<div bgcolor="#ffffff" text="#000000">
<font face="Arial">Hello,<br>
<br>
We are testing hosted VLAN support in OpenNebula to implement
network isolation. This feature seems to work correctly when a new
instance is deployed, as it is stated in oned.conf, hm-vlan hook
is executed in PROLOG state.<br>
<br>
However, there are another states where VLANs and bridges should
be created (or its existence checked) before executing a concrete
operation:<br>
<br>
* Migration/Live migration of an instance to a hypervisor where
VLAN and bridge of the instance has never been created<br>
VLAN and bridge existence should be checked and created if
necessary before migration is executed. Opennebula 3.0 RC1
performs migration without doing these checks and fails to
migrate/live migrate the instance, leaving it in a FAILED state.<br>
<br>
* A failed instance cannot be redeployed to a hypervisor where </font><font face="Arial">VLAN and bridge of the instance has never been
created</font><br>
<font face="Arial">VLAN and bridge existence should be checked and
created if necessary to redeploy the image to the selected
hypervisor.</font><br>
<br>
* A stopped instance <font face="Arial">cannot be resumed if </font><font face="Arial">VLAN and bridge of the instance does not exist</font>.<br>
If we stop all instances of a concrete hypervisor and reboot the
hypervisor for maintenance purposes, all bridges and VLANs will be
deleted. Stopped instances won't resume because VLANs and bridges
requirements are not satisfied and will enter in a FAILED state
(performing a deletion of non persistent disks; BTW, we have removed
deletion lines in tm_delete script for the moment, :D). <br>
<br>
So, <font face="Arial">VLAN and bridge existence should be checked
and created if necessary to
resume/migrate/livemigrate/recover_from_failed_state the instance
to the selected hypervisor.</font> As it is stated in oned.conf,
hm-vlan hook could be executed on:<br>
<br>
# Virtual Machine Hooks (VM_HOOK) defined by:<br>
# name : for the hook, useful to track the hook (OPTIONAL)<br>
# on : when the hook should be executed,<br>
# - CREATE, when the VM is created (onevm create)<br>
# - PROLOG, when the VM is in the prolog state<br>
# - RUNNING, after the VM is successfully booted<br>
# - SHUTDOWN, after the VM is shutdown<br>
# - STOP, after the VM is stopped (including VM image
transfers)<br>
# - DONE, after the VM is deleted or shutdown<br>
# - FAILED, when the VM enters the failed state<br>
<br>
But I'm not able to find a procedure to implement these
functionalities in oned.conf for the states I mentioned.<br>
<br>
Please, can you give me any clues?<br>
<br>
Best Regards,<br><font color="#888888">
Alberto Picón<br>
<br>
<font face="Arial"><br>
</font>
</font></div>
<br></div></div><div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></div></blockquote></div><font color="#888888"><br><br clear="all"><br>-- <br>Patrice LACHANCE<br>Manager IT Consulting, Logica : <a href="http://www.logica.com" target="_blank">http://www.logica.com</a><br><br>Réseau Viaduc<br>
Consultez mon profil: <a href="http://www.viaduc.com/public/profil/?memberId=00226pj42r07h9f3" target="_blank">http://www.viaduc.com/public/profil/?memberId=00226pj42r07h9f3</a><br>
Vous inscrire sur le réseau: <a href="http://www.viaduc.com/invitation/00226pj42r07h9f3" target="_blank">http://www.viaduc.com/invitation/00226pj42r07h9f3</a><br><br>LinkedIn Network:<br> See my profile: <a href="http://www.linkedin.com/in/plachance" target="_blank">http://www.linkedin.com/in/plachance</a><br>
Join the network: <a href="http://www.linkedin.com" target="_blank">http://www.linkedin.com</a><br>
</font><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br></div><br clear="all"><div><br></div>-- <br></div></div>Jaime Melis<br>Project Engineer<div class="im"><br>OpenNebula - The Open Source Toolkit for Cloud Computing<br></div><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>
</div>