Hello Hutson,<div><br></div><div>Actually that's the expected behaviour of the 8021Q network drivers. We decided to keep the bridge and the physical device with the vlan tag in the host for the following reasons:</div>
<div><br></div><div>1) It doesn't hurt to leave the bridge and the tagged interface. It won't eat up system's resources.</div><div>2) If another VM with the same network ID is launched in the same host, you don't need to create it again, therefore (slightly) speeding up boot times</div>
<div><br></div><div>Do you agree with this? Do you think the default behaviour should be to remove the bridge and tagged interface?</div><div><br></div><div>Of course this behaviour can be modified by enhancing the clean script [1]. Take a look at the ebtables clean script [2]. You will probably need to develop a "deactivate" method in the ruby class that handles the 8021q network drivers [3].</div>
<div><br></div><div>[1] <a href="https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/802.1Q/clean" target="_blank">https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/802.1Q/clean</a></div><div>
[2] <a href="https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/ebtables/clean" target="_blank">https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/ebtables/clean</a><br>
[3] <a href="https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/802.1Q/HostManaged.rb" target="_blank">https://github.com/OpenNebula/one/blob/master/src/vnm_mad/remotes/802.1Q/HostManaged.rb</a></div><div>
<br></div><div>Regards,</div>
<div>Jaime</div><div><br></div><div><div class="gmail_quote">On Wed, Dec 14, 2011 at 10:54 PM, Hutson Betts <span dir="ltr"><<a href="mailto:hut101@tamu.edu" target="_blank">hut101@tamu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have been testing Host-managed VLANs, but I'm having an issue with<br>
cleanup.<br>
<br>
After creating a VNET and VM, I have the following:<br>
oneadmin@opennebula-server:~$ onevm show 5<br>
VIRTUAL MACHINE 5<br>
INFORMATION<br>
ID : 5<br>
NAME : vm-example<br>
USER : oneadmin<br>
GROUP : oneadmin<br>
STATE : ACTIVE<br>
LCM_STATE : RUNNING<br>
HOSTNAME : 10.1.0.101<br>
START TIME : 12/14 15:40:51<br>
END TIME : -<br>
DEPLOY ID : one-5<br>
<br>
VIRTUAL MACHINE<br>
MONITORING<br>
NET_TX : 0<br>
NET_RX : 390<br>
USED MEMORY : 524288<br>
USED CPU : 66<br>
<br>
VIRTUAL MACHINE<br>
TEMPLATE<br>
CPU=1<br>
DISK=[<br>
CLONE=YES,<br>
DISK_ID=0,<br>
IMAGE="Machine A",<br>
IMAGE_ID=1,<br>
READONLY=NO,<br>
SAVE=NO,<br>
SOURCE=/var/lib/one/images/643c79fb423c71730ffb84b1a88f06d0,<br>
TARGET=hda,<br>
TYPE=DISK ]<br>
MEMORY=512<br>
NAME=vm-example<br>
NIC=[<br>
BRIDGE=onebr2,<br>
IP=192.168.0.1,<br>
MAC=02:00:c0:a8:00:01,<br>
NETWORK="VLAN Test",<br>
NETWORK_ID=2,<br>
PHYDEV=eth2 ]<br>
OS=[<br>
INITRD=/initrd.img,<br>
KERNEL=/vmlinuz,<br>
ROOT=sda ]<br>
VMID=5<br>
oneadmin@opennebula-server:~$ onevnet show 2<br>
VIRTUAL NETWORK 2<br>
INFORMATION<br>
ID : 2<br>
USER : oneadmin<br>
GROUP : oneadmin<br>
PUBLIC : No<br>
USED LEASES : 1<br>
<br>
VIRTUAL NETWORK<br>
TEMPLATE<br>
BRIDGE=onebr2<br>
NAME="VLAN Test"<br>
NETWORK_ADDRESS=192.168.0.0<br>
NETWORK_SIZE=C<br>
PHYDEV=eth2<br>
TYPE=RANGED<br>
<br>
LEASES<br>
INFORMATION<br>
LEASE=[ IP=192.168.0.1, MAC=02:00:c0:a8:00:01, USED=1, VID=5 ]<br>
<br>
<br>
On the host system, I have the following, created as a result of the<br>
Host-managed VLAN script:<br>
<br>
eth2.502 Link encap:Ethernet HWaddr 00:1b:21:b8:cf:3d<br>
inet6 addr: fe80::21b:21ff:feb8:cf3d/64 Scope:Link<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:0<br>
RX bytes:0 (0.0 B) TX bytes:390 (390.0 B)\<br>
<br>
onebr2 Link encap:Ethernet HWaddr 00:1b:21:b8:cf:3d<br>
inet6 addr: fe80::9820:dff:fe31:9aab/64 Scope:Link<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:0<br>
RX bytes:0 (0.0 B) TX bytes:390 (390.0 B)<br>
<br>
vnet1 Link encap:Ethernet<br>
<br>
Next, I proceed to delete the VM and VNET using the following:<br>
<br>
oneadmin@opennebula-server:~$ onevm delete 5<br>
oneadmin@opennebula-server:~$ onevnet delete 2<br>
<br>
<br>
The "vnet0" tap was removed along with the VM, but the bridge and<br>
VLAN-tagged virtual interface are still there. Am I missing a<br>
configuration step to insure that those are removed when all remnants of<br>
the VM and VNET are deleted?<br>
<span><font color="#888888"><br>
--<br>
Hutson Betts<br>
Computer Science and Engineering<br>
Texas A&M University<br>
<br>
<br>
<br>
</font></span><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>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>