<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body 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>
Alberto Picón<br>
<br>
<font face="Arial"><br>
</font>
</body>
</html>