From 810bb7f5c6615a2d90d9451337e6df6a01702e5b Mon Sep 17 00:00:00 2001 From: Trinath Somanchi Date: Thu, 31 Aug 2017 23:33:08 +0530 Subject: Adding OVN4NFV initial documentation for Euphrates release. Change-Id: Iaa3bcf3c1b1b356ee3a694dcbb2f96098c8173bc Signed-off-by: Trinath Somanchi --- docs/development/ovn-for-nfv.rst | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 docs/development/ovn-for-nfv.rst (limited to 'docs/development/ovn-for-nfv.rst') diff --git a/docs/development/ovn-for-nfv.rst b/docs/development/ovn-for-nfv.rst new file mode 100644 index 0000000..3ae9c99 --- /dev/null +++ b/docs/development/ovn-for-nfv.rst @@ -0,0 +1,23 @@ +OVN4NFV Project +=============== +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. + +OVN for OPNFV at OPNFV Design Summit, Nov, 2015 + - https://wiki.opnfv.org/_media/events/ovn-opnfv-summit2015.pdf + -- cgit 1.2.3-korg