[MidoNet-dev] MidoNet: L2 gateway (connecting physical L2 into the virtual topology)

Pino de Candia gdecandia at midokura.com
Wed Feb 13 10:25:59 UTC 2013


On Tuesday, February 12, 2013 at 4:15 PM, Guillermo Ontañón wrote:
> I have a crucial comment...
>  
>  
> On Tue, Feb 12, 2013 at 3:24 PM, Pino de Candia <gdecandia at midokura.com (mailto:gdecandia at midokura.com)> wrote:
> > On Tuesday, February 12, 2013 at 9:53 AM, Dan Mihai Dumitriu wrote:
> > > Make it so Number One.
> > >  
> > >  
> >  
> >  
> > One? I think I'm employee number 4 or 5 - not counting the founders.
> >  
> > Ryu, Tomoe, when you guys have some free time (after the Grizzly commit deadline) could you give an opinion about whether the bonding and vlan adapters might be good extensions to the Quantum?  
> >  
> > Also, here are the MidoNet API changes I'm proposing to implement this model. For Bonding Adapters:
> > PortBonds will be a top level URI (obtained from ApplicationDto.getPortBonds - probably at path /port_bonds).
> > You create a new PortBond by doing a POST of a PortBondDto to ApplicationDto.getPortBonds. PortBondDto just has a name and an owner. Later we may add fields like 'forwardingMode' (for choosing between round-robin, xor and others) and 'enableLACP' for changing from static to dynamic link aggregation.
> > PortBondDto.upPort is the URI of the PortBond's interior uplink port. This port is created automatically (unlinked) when the PortBond is created. Although the URI is similar to other virtual port URIs (e.g. in /ports), attempting to DELETE it will result in an HTTP error.
> > If you do a GET on PortBondDto.upPort, the result is an InteriorPortDto - which should now be made an explicit and instantiate-able part of the port hierarchy.
> > PortBondDto.downPorts is the URI for the bond's down-ports. GET on this URI will return a list of ExteriorPortDto objects - which should now be made an explicit and instantiate-able part of the port hierarchy. POST on the 'downPorts' URI will create a new ExteriorPortDto. ExteriorPorts may be bound to host-interfaces.
> >  
> >  
> > For VLAN Adapters:
> > VlanDemuxes will be a top level URI (obtained from ApplicationDto.getVlanDemuxes - probably at path /vlan_demuxes).
> > You create a new VlanDemux by doing a POST of a VlanDemuxDto to ApplicationDto.getVlanDemuxes.VlanDemuxDto just has a name and an owner.
> > VlanDemuxDto.downPort (or call it muxPort?)  
> >  
> >  
> >  
>  
>  
> how about trunkPort?

I completely missed the obvious - trunkPort sounds great. --Pino 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.midonet.org/pipermail/midonet-dev/attachments/20130213/6adf40a5/attachment.html>


More information about the MidoNet-dev mailing list