This is an old revision of the document!
Project: OpenContrail Virtual Networking for OPNFV
Proposed name for the project: OpenContrail Virtual Networking for OPNFV
Proposed name for the repository: ovno
Project Categories: Collaborative Development
Overview presentation - Dec 9, 2015 opencontrail_quick_tour.pptx
Project Description
This project will enable OpenContrail to be selected as the virtual networking technology in OPNFV deployments. The following diagram illustrates how the components of an OPNFV stack that includes OpenContrail map onto the ETSI NFV architecture.
The architecture of OpenContrail and details of how its virtual networking works is described in detail in http://www.opencontrail.org/opencontrail-architecture-documentation/.
The main tasks of the project will be integration of OpenContrail artifacts into the OPNFV continuous integration infrastructure, and ensuring support in the various installer projects. It is not planned that OpenContrail source code will be hosted in OPNFV systems, but rather that pre-built packages will be downloaded into the OPNFV artifact repository, and from there integrated into the various installers. Over time, as new versions become available, it will be desirable to be able to choose the OpenContrail version and underlying operating system when OpenContrail is selected in an installer.
The scope of the project is illustrated below.
Note that in the diagram, the process illustrated would involve integrating OpenContrail with other artifacts (specifically OpenStack) in each installer project within the OPNFV environment. An alternative is that a pre-integrated OpenStack/OpenContrail artifact could be downloaded from an installer's upstream repository. This is likely to the method employed for JOID.
OpenContrail supports overlay networking that can be applied in many use cases including:
Multi-tenant infrastructure as a service
Dynamic creation and application of network policy
Creation of service chains and application of network policy to direct traffic through them
Use of OpenStack Heat templates for application stack and service chain creation
Load balancing in service chains, reverse flow symmetry, flow stability during scaling
Use of KVM hypervisor and Docker containers for VNFs
EVPN and OVSDB integration with switches to support physical servers
Flow mirroring to a virtualized packet analyzer
Flow-based analytics on per-network, per-VM and per TCP port basis
Path visualization for flows between VMs
Infrastructure health monitoring
The use cases include scenarios, like service chaining, path visualization and flow mirroring, that are not supported in OpenStack natively. The Contrail controller provides support for these via its GUI and API.
It is planned that the initial release of OpenContrail for OPNFV will be included in the Brahmaputra ("B") release of OPNFV.
Scope
An OPNFV stack employing the OpenContrail virtual networking option will contain the following components:
The scope of tasks in the project includes the following areas of activity:
Integration of OpenContrail artifacts into the OPNFV CI environment
Working with installer projects to enable the OpenContrail stack to be deployed successfully. (May include supply of existing Puppet modules).
Test scripts to check for deployment success
Related Projects
Octopus provides an environment in which OPNFV components (platform builds based upon various combinations of components from upstream projects) can be maintained in sync with the upstream projects, and built from those source components into a cohesive set of images and packages, with associated metadata, that form the input artifacts for test and deployment projects.
Installer projects will provide a capability to quickly deploy a base configuration of components of OPNFV in order to support developer testing of OPNFV stacks and to aid Octopus CI development. OSCAR will use the BGS stack as one of its initially supported stacks in order to exercise the ability to deploy at scale and on multiple sites.
OpenContrail for OPNFV will follow the release cadencing of the Simultaneous Release project, once it is in place.
Documentation
Documentation will be provided that describes the OpenStack architecture, components, supported stacks, installation procedure, user interface, APIs, and configuration files.
Key Project Facts
Project Creation Date: August 4, 2015
Project Category: Collaborative project
Lifecycle State: Incubation
Primary Contact: Stuart Mackie
Project Lead: Stuart Mackie
Jira Project Name: ovno
Jira Project Prefix: [ovno]
Mailing list tag [ovno]
Link to TSC approval of the project: https://wiki.opnfv.org/wiki/tsc#august_4_2015
Committers:
Stuart Mackie (wsmackie@juniper.net) - Juniper Networks
Artur Tyloch (artur.tyloch@canonical.com)Canonical
Narinder Gupta (narinder.gupta@canonical.com), Canonical
Tim Rozet (trozet@redhat.com), Red Hat
…
Contributors:
Parviz Yegani(pyegani@juniper.net) - Juniper Networks
Parantap Lahiri(plahiri@juniper.net) - Juniper Networks
Avinash Seshadri(savinash@juniper.net) - Juniper Networks
James Buchanan (JBuchanan@advaoptical.com) - ADVA Optical Networking
Prakash Ramchandran(prakash.ramchandran@huawei.com) - Huawei
Vagish Shanmukh (vagish.shanmukh@huawei.com) - Huawei
Michael Brenner (mbrenner@clearpathnet.com) - ClearPath Networks
…
Planned Deliverables
OpenContrail artifacts into Octopus
Scripts and code into various OPNFV installer projects
Test code/scripts to be delivered into the appropriate Brahmaputra test projects
User documentation for OpenContrail OPNFV stack
Proposed Release Schedule: