AT&T has recently been driving the vendor community to come up with an NFV-ready networking architecture for OpenStack. Working with OPNFV they identified a set of networking use-cases use-cases that are not cleanly addressed with Neutron.
Gluon is our initial attempt at creating a model-driven approach to implement these use cases. We started by creating a new set of APIs specificially for L3 VPNs. At OPNFV in Berlin we demonstrated interoperability between four vendors' SDN controllers within a single Openstack cloud. Our framework allows us to create new network models rapidly, switch new models in and out without impact, and for those models to serve multiple controllers and clouds within a telco network.
In this panel we will discuss use cases needed by the operator; the networking services needed for these use cases; how the vendor community is participating in this engagement; and how we want to work with OpenStack to implement these services.
- What was the scope of this challenge and how did we solve it?
- Who are the partners of this successful engagement?
- Why did this specific cooperation succeed?
- How can this type of community effort be repeated?
- What are the key NFV networking requirements?
- How do we work in an area of continuing innovation?