Open Stack

Hi all,

I have created a blueprint for the Tail-f NCS integration with OpenStack networking: https://blueprints.launchpad.net/quantum/+spec/tailf-ncs

I would love a little bit of review before I submit it for consideration for Havana. Particularly - Kyle, Bob, does it still look like MechanismDriver code materializing in h2 is the right approach to take?

Cheers,
-Luke

13 maj 2013 kl. 09:14 skrev Luke Gorrie:

> I would like to develop a Quantum plugin for the Tail-f Network Control System (NCS - http://www.tail-f.com/network-control-system/). I want to do this in a tasteful way that helps to make Quantum better. I am an OpenStack newbie so I would appreciate some advice on the first steps :-)
> 
> For background, NCS is a network provisioning system that knows how to control Cisco/Juniper/etc devices. The goal for this plugin is for Quantum to notify NCS of network/port/etc changes so that NCS can perform relevant provisioning of the physical switches and routers that connect the OpenStack nodes to the world and to each other.
> 
> That is: NCS owns the switches and routers, LinuxBridge/OVS owns the hypervisor networking, and the plugin keeps them in sync.
> 
> I have been reading the Quantum code and it looks like the BigSwitch plugin is close to what we need, i.e. a plugin that proxies all Quantum provisioning events over a REST interface to an external system. I have the impression though that this replaces the LinuxBridge/OVS plugin whereas we want to run that in parallel. (I also don't necessarily need the Quantum network state cached in the Python plugin.)
> 
> Any tips on how to move this forward and thrash out a design that's good for Quantum? I have the impression there is a lot of related work going on at the moment...
> 
> Cheers,
> -Luke
> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev