User Tools

Site Tools


sdnvpn

This is an old revision of the document!


Project Name: SDN distributed routing and VPN

  • Proposed name for the project: SDN distributed routing and VPN
  • Proposed name for the repository: sdnvpn
  • Project Categories: Collaborative Development

Project Description

Many telecom network functions are relying on layer-3 infrastructure services, within a VNF between components, or towards existing external networks. In many cases, these external networks are implemented in MPLS/BGP technology in existing service provider wide-area-networks (WAN). This proven technology provides a good mechanism for inter-operation of a NFV Infrastructure (NFVI) and WAN.

This has lead to a number of activities both in OpenDaylight andOpenStack targeting to implement such functionality, including:

The proposed architecture in the VPN Service proposal both links NFVI networking services seamlessly into the WAN network architecture and provides a solution for distributed routing functionality in the virtual Switches using standard ODL southbound interfaces.

To assure integration into the NFVI, a collaborative project is needed, linking the work done in ODL and OpenStack on this item and assuring the integration of these functions into the OPNFV reference platform. A key objective is to validate the solution and to create visibility for that OPNFV has a viable solution.

Scope

Scope of the project is to address integration and deployment of VIM and Virtual networking components to provide Layer 3 VPN services in the OPNFV platform. The project will be done in collaboration with the related bgpvpn project in OpenStack and supported implementations in SDN controllers to make sure that the functionality can be integrated on the OPNFV reference platform for the Brahmaputra release and onwards.

Included in the scope are:

  • Alignment of ODL Neutron NBI interface with OpenStack neutron API for BGPVPN, as soon as that is finalized (Liberty timeframe)
  • Development of OPNFV R2 requirements on L3VPN reference implementation and related test cases
  • Analysis and implementation of required OVS features to support performant distributed routing
  • Identification of DC gateway reference platforms and functional requirements on them

Testability

All defined use cases will be identified and test cases to validate the functionality will be implemented in this project. This will include in the Brahmaputra timeframe platform functional testing in functest, deployment and scenario testing in YardStick.

Documentation

Use cases and user guide documentation will be provided. (per SDN solution as needed) Deployment and installation documentation will be provided. (per deployment tool as needed)

Dependencies

The project has the most relevant dependencies on: • The BGPVPN project in OpenStack. • The VPN Service project in OpenDaylight. • L3VPN functionality in OpenContrail

Committers and Contributors

Project lead:

  • Tim Irnich (tim.irnich@ericsson.com)

Committers:

  • Thomas Morin (tmorin@orange.com)
  • Diego Garcia (diego.garcia_del_rio@alcatel-lucent.com)
  • Prem Sankar (prem.sankar.g@ericsson.com)
  • Jan Scheurich (jan.scheurich@ericsson.com)

Other contributors:

  • tbd

Planned deliverables

The project will deliver an integrated solution and associated documentation for L3VPN for the Brahmaputra release and associated documentation and test cases. The project will further develop L3 VPN services for future releases and establishing consistent capabilities across SDN controller for L3 VPN services. Another deliverable, will be reference integrated solutions demonstrating the integration of proprietary SDN solutions into the platform. These references will not be delivered as OPNFV, however will be used to validate the OPNFV solution in commercial application.

Planned release schedule

Phase 1 will deliver L3 VPN services in Brahmaputra.

Further releases will evolve these services to include additional capabilities such as Service Chaining and additional network topologies.

Key Project Facts

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

sdnvpn.1438112768.txt.gz · Last modified: 2015/07/28 19:46 by Tim Irnich