os-odl-sfc_fdio-noha overview and description¶

Introduction¶

The os-odl-sfc_fdio-noha is intended to be used to install the OPNFV SFC project in a standard OPNFV Non-High Availability mode. The OPNFV SFC project integrates the OpenDaylight SFC project into the OPNFV environment. The OPNFV SFC Euphrates release uses the OpenDaylight Nitrogen SR1 release.

Scenario components and composition¶

This scenario installs everything needed to use the SFC OpenDaylight project in an OPNFV environment. Since this scenario is Non-High Availability, then only one controller and one compute node will be deployed. The classifier used in this scenario is implemented by the Netvirt OpenDaylight project.

Following is a detailed list of what is included with this scenario:

OpenDaylight features installed¶

The OpenDaylight SDN controller is installed in the controller node.

The following are the SFC features that get installed:

odl-sfc-model
odl-sfc-provider
odl-sfc-provider-rest
odl-sfc-ovs
odl-sfc-openflow-renderer

The following are the Netvirt features that get installed:

odl-netvirt-openstack
odl-sfc-genius
odl-neutron-service
odl-neutron-northbound-api
odl-neutron-spi
odl-neutron-transcriber
odl-ovsdb-southbound-impl-api
odl-ovsdb-southbound-impl-impl
odl-ovsdb-library

By simply installing the odl-netvirt-sfc feature, all the dependant features will automatically be installed.

The VNF Manager¶

In order to create a VM for each Service Function, a VNF Manager is needed. The OPNFV SFC project currently uses the Tacker OpenStack project as a VNF Manager. Tacker is installed on the controller node and manages VNF life cycle, and coordinates VM creation with the OpenDaylight SFC project.

Scenario usage overview¶

Once this scenario is installed, it will be possible to create Service Chains and classification entries to map tenant traffic to individual, pre-defined Service Chains. All configuration can be performed using the Tacker CLI.

Limitations, Issues and Workarounds¶

The client virtual machine needs to be located in a compute node where at least one of the service functions (SFs) is placed. This is due to a limitation in OpenDaylight, Nitrogen, which only installs the traffic classifier in the compute nodes where the SFs are.