This is an old revision of the document!
OVN for NFV
ovn4nfv
OVN complements the existing capabilities of OVS to add native support for virtual network abstractions such as virtual L2 & L3 overlays, L3 routing and security groups. Instead of treating ovsdb and Open Flow actions separately, OVN provides simpler interface for managing virtual networks. Besides the simpler interface, OVN takes care of transforming simple flow rules of virtual network to complex Open Flow rules on the Open vSwitches involved. The Openstack project networking-ovn implements the neutron api using OVN. As part of ovn4nfv project we would like to enable OVN along with the openstack neutron plugin networking-ovn as a deployable network control component in the OPNFV build. This would make it easier to manage virtual networks and push more of network intelligence to the edge onto the compute nodes. Since OVN has inherent support for containers, this would allow OPNFV to orchestrate container VNFs. Further this will make the controller architecture much more simpler and scalable by placing the controller (ovn-controller) next to the Open vSwitch
Integration will require that all relevant functional tests which pass in the OPNFV test infrastructure will also pass when OVN is deployed. The OPNFV functest project will report any gaps in features.
If any gap in functionality or performance is identified during the Test and Benchmarking phase, those features will be developed and upstreamed into the projects openstack/networking-ovn and OVN.
When OVN is available as a deployment option in OPNFV, it is envisaged that further development activities will be required such as:
This project plans to leverage existing test infrastructure.
For any additional functionality required in openstack/networking-ovn and OVN, the relevant project's documentation will need to be updated (e.g. man pages, install guides, etc) Relevant OPNFV release documentation will also need to be updated:
Use the above information to create a key project facts section on your project page
Project Name: Project Name (repo name)
Repo name:
Project Category:
Lifecycle State:
Primary Contact:
Project Lead:
Jira Project Name: Same as Project name
Jira Project Prefix: [10 Characters max [A-Z] ]
mailing list tag [Should match Jira Project Prefix]
Committers:
foo@bar.com
baz@qux.com
Link to TSC approval: Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html
Link to approval of additional submitters: Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html