What is L3VPN  

Layer 3 Virtual Private Networks (l3vpn): L3VPN is a technology based on PE. It uses MPLS to forward VPN packets over service provider backbones.

L3VPN comprises the following types of devices:

            Customer edge (CE) device—A CE resides on a customer network and has one or more interfaces directly connected to service provider networks. It can be a router, a switch, or a host. 

·           Provider edge (PE) device—A PE resides at the edge of a service provider network and connects one or more CEs. On an MPLS network, all VPN services are processed on the PEs.

·           Provider (P) device—A P device is a core device on a service provider network. It is not directly connected to any CE. It has only basic MPLS forwarding capability.

Introduction 

This project is part of ONOSFW for OPNFV. The SFC creation is primarily driven by Openstack Neutron. The SFC component in ONOS implements the SFC L3VPN creation requests from Openstack Neutron. All the required information for creating a service chain are supplied by Neutron using REST based APIs. Using these information, the SFC component prepares the flow rules as per the IETF NSH header and downloads the flow rules into OVS (OVS version 2.5.90 with official NSH Patch - https://github.com/yyang13/ovs_nsh_patches)

Architecture

SFC is implemented as a bundle within the VTN application in ONOSFW.

Refer to ONOSFW architecture.

What we do

1. SFC is implemented as a bundle within the VTN application in ONOSFW
2. The processing of REST based APIs from Neutron are implemented in ONOS as part of SFC project
3. REST APIs such as create port-pair(SF), create port-pair-group(SF group), create port-chain, create flow classifier rules are processed in ONOS
4. SFC resources such as SFs, SF groups, flow classifier rules are stored in ONOS for processing the create chain request
5. Interaction with VTN Resouce manager, VTNManager for various API
6. Implement the logic for service chain creation and flow rule download to classifier and SFFs
7. Extend the ONOS-Loxi for NSH header information download to OVS

Goals

Hummingbird Release

Implement basic foundation for SFC

Integrate with Openstack Neutron and service the REST based APIs

Interact with VTN Resource Manager and VTN Manager. Store the SFC resources. Define service chain logic in SFC.

Basic flow rule download to classifier and SFF.

App. It provides a Rest Api for north app to use. When getting creation requests , the L3VPN component prepares the configuration informations and downloads the configuration informations into PE devices.

The Project is primarily driven by Yang Model.

Architecture

The architecture of L3VPN as below:

                               Image Added

Basic Network diagram for L3VPN model:

                                      Image Added

Call Flow

Image Added

What we do

NetL3VPN manager

It's a application. 

• Provide REST services.
• Provide distributed store for L3VPN instances.
• Provide Resource Allocation for L3VPN instance.

How we do

• Build onos and start onos cli session.

• Activate the below necessary apps in cli

  Info
  title Applications to activate
  app activate org.onosproject.yang app activate org.onosproject.config app activate org.onosproject.restconf app activate org.onosproject.protocols.restconfserver app activate org.onosproject.netconf app activate org.onosproject.netconfsb app activate org.onosproject.l3vpn app activate org.onosproject.drivers.huawei

• Configure all the necessary pre-configuration on the device to establish a netconf connection and then connect to the devices by following NETCONF#ConnectyourowndevicetoONOS

• Configure L3VPN instance by sending via json.
  
  

  Code Block
  title URI : http://127.0.0.1:8181/onos/restconf/data
  { "ietf-l3vpn-svc:l3vpn-svc":{ "vpn-services":{ "vpn-svc":[{ "vpn-id":"vpna", "customer-name":"jan" }] } } }

  Code Block
  title URI : http://127.0.0.1:8181/onos/restconf/data/ietf-l3vpn-svc:l3vpn-svc
  { "ietf-l3vpn-svc:sites":{ "site":[ { "site-id":"100", "site-network-accesses":{ "site-network-access":[ { "site-network-access-id":"500", "bearer":{ "l3vpn-svc-ext:bearer-attachment": { "pe-mgmt-ip":"172.16.11.12" }, "requested-type":{ "l3vpn-svc-ext:requested-type-profile": { "physical":{ "physical-if":"Ethernet3/0/0" } } } }, "vpn-attachment":{ "vpn-id":"vpna", "site-role" :"any-to-any-role" }, "ip-connection":{ "ipv4":{ "addresses":{ "provider-address":"50.1.1.1", "mask":"24" } } } }, { "site-network-access-id":"501", "bearer":{ "l3vpn-svc-ext:bearer-attachment": { "pe-mgmt-ip":"172.16.11.13" }, "requested-type":{ "l3vpn-svc-ext:requested-type-profile": { "physical":{ "physical-if":"Ethernet3/0/0" } } } }, "vpn-attachment":{ "vpn-id":"vpna", "site-role" :"any-to-any-role" }, "ip-connection":{ "ipv4":{ "addresses":{ "provider-address":"50.1.1.2", "mask":"24" } } } } ] } } ] } }