Hello Patrice,
you make very valid points and we're aware of those limitations. They have
actually been reflected on the documentation:
http://opennebula.org/documentation:rel3.0:nm#considerations_limitations
The problem is that the network management is based on the hook subsystem,
but we have
I apologize, the message was both for Patrice and Alberto Picón, who raised
the initial questions.
On Thu, Oct 27, 2011 at 11:30 AM, Jaime Melis jme...@opennebula.org wrote:
Hello Patrice,
you make very valid points and we're aware of those limitations. They have
actually been reflected on
As you mention, we have implemented a static vlan configuration for the
moment.
We are glad to know that these issues could be addressed in Opennebula
v3.2.
Please, consider our help for testing whatever you may need.
Thank you very much for your help and such a great product,
Best Regards,
Hello
In previous version there was a cluster feature that was replaced in
OpenNebula 3.0 by ozones.
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?
Patrice
2011/9/27 Alberto Picón Couselo
Hello,
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.
However, there are another states where VLANs and bridges
