Open Stack

Hi Ian,

On 20/07/15 18:00, Ian Wells wrote:
> On 19 July 2015 at 03:46, Neil Jerram <Neil.Jerram at metaswitch.com 
> <mailto:Neil.Jerram at metaswitch.com>> wrote:
>
>     The change at [1] creates and describes a new 'routed' value for
>     provider:network_type.  It means that a compute host handles data
>     to/from the relevant TAP interfaces by routing it, and specifically
>     that those TAP interfaces are not bridged.
>
>
> To clarify that, the user uses provider:network_type in the API to 
> request a 'routed' network be created, and the Neutron plugin either 
> implements that or rejects the create call?  Or something else?

Yes, I believe so.  Could it be otherwise?

More specifically: I've used the ML2 plugin for all of my Neutron work 
so far.  With ML2 my understanding is that there can be multiple Type 
and Mechanism drivers configured as possibilities in ml2_conf.ini.  Then 
- I believe - any particular network creation request is matched against 
those available drivers, and handled by the one that can handle it.  If 
no configured driver can handle the requested network - e.g. if 
ml2_conf.ini has "type_drivers=routed" but a network is requested with 
provider:network_type = gre - I believe the request is failed.

Happy to be corrected in case that's wrong, of course!

     Neil