Virtual Customer Edge is the capability of connecting network entity endpoints to each other and integrating them within the network by allowing some access policy rules. It is also to virtualize those endpoints and/or to bring the functionality closer to the core of a platform. By using virtual customer premises equipment (vCPE), one can dynamically add and/or run new services as needed at the edge.

The UNI manager project enables the configuration and the provisioning of connectivity services for both physical and virtual elements, particularly carrier Ethernet services, as defined by the Metro Ethernet Forum (MEF). It supports the creation of links between two virtual switches by creating a Generic Routing Encapsulation (GRE) tunnel between the two endpoints.

This recipe requires two virtual switches. If you don't have any, you can use a Mininet-VM with OvS installed. You can download Mininet-VM from https://github.com/mininet/mininet/wiki/Mininet-VM-Images. Any version should work.

The following recipe uses a Mininet-VM with OvS 2.3.1 and a Mininet-VM with...

To complete this recipe, we will be using the Network Intent Composition and VpnService projects.

The scope of the usecase is to enable a MPLS VPN connection across customer sites in a single MPLS domain. Within the domain, MPLS Label is used to isolate traffic between the sites.

The Provider Edge routers (PE) and the Provider routers (P) are managed by OpenDaylight.

In order to create end-to-end VPN connectivity across customer sites, OpenDaylight shall provision MPLS intents to respective PEs and Ps that form the shortest route between the two sites.

Additionally, by adding constraint attributes to intents for protection and failover mechanisms, we can ensure end-to-end connectivity between endpoints to reduce the risk of connectivity failure due to a single link or port down event on a forwarding device:

• Protection constraint: This...

The unified secure channel (USC) is an OpenDaylight project geared to enable secured and performant communication channels between the SDN controller and network elements within wide area networks. Lately, we have seen a growth in the type of elements being part of an enterprise network, cloud infrastructure, IoT devices, and network devices (NETCONF, OpenFlow, and so on). USC provides centralized management of communication channels, allowing the establishment and removal of those pipelines. Finally, it provides statistics regarding the written and read bytes through a given channel.

The project architecture contains the USC plugin responsible for the communication between the controller and the network elements, supporting the TLS and DTLS protocols. It also maintains the live connections through inbound and outbound channels. The...

The IoT Data Management (IoTDM) project implements a subset of oneM2M protocol. Its purpose is to provide a common machine-to-machine layer that can be embedded with various kinds of devices and software. It follows the latest oneM2M specifications as closely as possible, publicly available at the following website:

http://www.onem2m.org/technical/published-documents

The OpenDaylight IoTDM project offers data-centric middleware acting as a oneM2M broker. It also enables authorized applications to access and get data uploaded by any device. The reason behind the data-centric architecture is to provide a single version of a global data space for applications of interest, optimizing network traffic, and application processing along with the addition and/or removal of devices from the IoT domain.

The IoTDM project is capable...

OpenDaylight's PacketCable Multimedia (PCMM) project is an interface that lets you control and manage service flow for cable modem termination system (CMTS) network elements. The service flow enables a dynamic quality of service (DQoS) between a CMTS and a cable modem (CM) using the Data Over Cable Service Interface Specification (DOCSIS) standard. The project is composed of a policy server allocating network resources per subscriber and application, an application manager specifying QoS requirements per-application to the policy server, a CMTS enforcing the policies based on bandwidth capacity, and a CM connecting to the client's network (cable system).