Thank you all for the information. I was having difficulties figuring out how to handle vlan tagging.<div>I realized the "dom0" must have a tagged interface connected to a seperate bridge (as Rangababu described).</div>
<div><br></div><div>Since OpenNebula allows you to specify the bridge in the vnet definition it all just works properly (given</div><div>the bridge is setup on all of the onehosts).</div><div><br></div><div>Our guest OSes have a pool of addresses from many disperse /24s. Using vlan tagging, allows us to use the</div>
<div>same IP address anywhere in the datacenter (no need to map which /24 must come up on a specific "dom0").</div><div>Also, useful when migrating VMs as well.</div><div><div><br></div><div>John</div><div><br><div class="gmail_quote">
On Mon, Dec 20, 2010 at 12:04 AM, Rangababu Chakravarthula <span dir="ltr"><<a href="mailto:rbabu@hexagrid.com">rbabu@hexagrid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I was referring to creating vlan devices with vconfig. So you create multiple vlan devices on the host and associate each with separate bridge. However the switch that is used to connect multiple hosts should not add its own VLAN tag. It must be capable of forwarding VLAN tagged traffic. This is only addressing separation of networks and intra-VM communication within the Cloud.<br>
<br>I think openvswitch does the same thing and more. Atleast what I gather from here. <a href="http://openvswitch.org/?page_id=146" target="_blank">http://openvswitch.org/?page_id=146</a><br><br>In case when you want a VM in the private cloud to be part of your organization VLAN then the packet leaving your VM should carry the VLAN tag configured in the switch. Obviously all the VM's using that bridge are part of one network.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Sun, Dec 19, 2010 at 11:05 AM, Shi Jin <span dir="ltr"><<a href="mailto:jinzishuai@gmail.com" target="_blank">jinzishuai@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
I am curious about the same thing. <div>Is it possible to setup libvirt to have different VMs on the same phyiscal NIC on the same physical machine to run under different VLAN? My understanding is that VLAN is setup on the switch for each physical port.</div>
<div>Thanks.</div><div><br></div><div>Shi<div><div></div><div><br><br><div class="gmail_quote">On Sun, Dec 19, 2010 at 5:43 AM, Gnep Zhao <span dir="ltr"><<a href="mailto:jass.zhao@gmail.com" target="_blank">jass.zhao@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div><br></div><div>Hi,</div><div><br></div><div>I don't really understant：</div><div><br></div><div>1) create VLAN on the host --- I suppose the vlan is configured on the switch. Do you mean the host-wide vlan? <div>
<br>2) link VLAN to an interface on the host<br>
</div></div><div><br></div><div>And what's the difference between your solution (802.1q) and openvswitch's?</div><div><br></div><div>Gnep</div><div><div></div><div><div><br></div><br><div class="gmail_quote">
On Sun, Dec 19, 2010 at 6:31 AM, Rangababu Chakravarthula <span dir="ltr"><<a href="mailto:rbabu@hexagrid.com" target="_blank">rbabu@hexagrid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">John<div>Yes you can use 802.1q VLAN tagging to your VM interface.</div><div><br></div><div>
The following steps will help you do that.</div>
<div>1) create VLAN on the host </div><div>2) link VLAN to an interface on the host</div>
<div>3) create a bridge on the host</div><div>4) associate interface to the bridge</div><div>5) Define the following in VM template<br><br></div><div><div>NIC=[</div><div> BRIDGE=<bridge name given above>,</div><div>
MAC=00:e5:8d:9f:c1:ba</div><div> ]</div></div><div><br></div><div>Hope this helps.</div><div>Ranga</div><div><br><div class="gmail_quote"><div><div>On Fri, Dec 17, 2010 at 7:45 PM, John Dewey <span dir="ltr"><<a href="mailto:john@dewey.ws" target="_blank">john@dewey.ws</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><div>I was curious if anyone has used 802.1q tagging with their VMs. It looks as though libvirt supports vlan tagging,<div>
but OpenNebula at this time does not generate an appropriate deployment stanza.</div><div><br></div><div>
I was hoping I could use network contextualization as a way to configure the guest's 802.1q tags.</div><div>I guess I don't understand vlan tagging when "dom0" bridging is in the mix.</div><div><br></div>
<div><div>Does anyone have anymore information on this topic, I would love to talk with you a bit more offline.</div><div><br></div><div>Thanks -</div><div>John</div></div>
<br></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></blockquote></div><br></div>
<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><br clear="all"><br></div></div><font color="#888888">-- <br><div>=================================================<font color="#0033ff" face="Arial"><font color="#000000"> </font></font></div>
<div><font color="#0033ff" face="Arial"><font color="#000000"> </font><b>Often wrong, Never in doubt</b></font><br>=================================================</div><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><br clear="all"><br></div></div>-- <br>Shi Jin, Ph.D.<br><br>
</div>
</blockquote></div><br>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">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></div>