Open Stack

* Chris Wright (chrisw at redhat.com) wrote:
> * Dan Wendlandt (dan at nicira.com) wrote:
> > basically, we're creating a patch port between br-int and br-tun in this
> > example.  In your case, you'd want to create a brX for each ethX, and then
> > attach ethX to brX.  The easiest thing to do would probably be that for a
> > mapping of a local vlan A to a global vlan M on ethX, create a patch port
> > from br-int to brX, and put the br-int port of the patch as an access port
> > on VLAN A, and put the brX side port as an access port on VLAN M (note,
> > putting a port as an access port in OVS just means setting the 'tag'
> > property on the Port, see:
> > https://github.com/openstack/quantum/blob/master/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py#L126
> > )
> > 
> > veths would be very similar, just using a different library call to create
> > the pair of devices.  quantum.agent.linux.ip_lib has an add_veth() method
> > that let's you do this.
> 
> Should be functionally equivalent to something like:
> 
> ip link add name int-to-tun type veth peer name tun-to-int
> ovs-vsctl add-port br-int int-to-tun
> ovs-vsctl add-port br-tun tun-to-int
> 
> to connect the two.


     eth0              VM0.....N              eth1
 +-----|-----+        +-|-|-|-|-|-+       +-----|-----+
 | ovs phys0 |        | ovs int   |       | ovs phys1 |        
 +-----|-----+        +-|-------|-+       +-----|-----+
       +-veth0i--vethi0-+       +-vethi1--veth1i+


Just drew this to share with Bob to make sure we had the same mental picture.

thanks,
-chris