Page 112 - ITU-T Focus Group IMT-2020 Deliverables

3 ITU-T Focus Group IMT-2020 Deliverables

the platform(s) to see if they work together. It is also an incubation environment to try out new software
features or hardware components. Establishment of OPNFV resulted from the realization that an open
reference platform was needed to validate key NFV concepts, leverage the growing open source community,
and accelerate the development and ultimately the adoption of NFV products and services.

OPNFV initially addressed the NFV Infrastructure (NFVI) and Virtualized Infrastructure Manager (VIM). For
2016, OPNFV expanded the scope to address Management and Orchestration (MANO) as well.

OPNFV projects range from those engaging directly with upstream projects, to internal projects that may be
classified as system features development (such as service function chaining or high availability), validation
and testing (including function, system, or performance testing), tools development (such as installers and
controllers) and documentation. Internal projects proposals, priorities, and scope, are motivated by the
community, and overseen by the OPNFV Technical Steering Committee.
OPNFV envisions a twice-yearly release cycle, adapting to the release cadence of the upstream projects. Each
release select new upstream functionalities that are verified against a Management and Orchestration
(MANO) VIM environment, and could ultimately include VNF lifecycle management (VNFM) and NFV
Orchestration (NFVO). The goal is not that of defining a complete standard framework for NFV, but rather to
provide and qualify a set of common building blocks for specific functions that could even not be all open.
The first release of OPNFV, named Arno, was issued in June 2015 and integrates the results from the
upstream projects OpenStack (VIM), KVM (hypervisor), Ceph, (distributed storage), OpenDaylight (SDN
Controller framework), and Open vSwitch (software switch), and other communities/blocks. Arno introduced
the OPNFV development environment: Continuous Integration, automated deployment and testing,
documentation, and tooling. Arno has been demonstrated running on platforms from multiple vendors
across the x86 and ARM processor architectures.
In February 2016, OPNF second release – Bramaputra – has been completed. It significantly supports the
upstream projects’ outcome, addresses multiple technology components across the ecosystem, and makes
advances in stability, performance and automation. This second release is lab-ready and improves stability,
validation and documentation; platform-level testing of NFV functionality is included. A rigorous upstream
integration process allowed including the latest code from partner communities and over 30 accepted
projects have contributed.

Brahmaputra offers many deployment scenarios that include additional SDN controllers, installers,
deployment options, and carrier-grade features. Continuous integration mechanisms provide a stable
framework for deploying and testing.

A recent upgraded release, Brahmaputra 3.0, includes key enhancements to SDN distributed routing, BGP
VPN support, Service Function Chaining (SFC), and other Layer 3 infrastructure support. Much of this is
addressed via the OPNFV “SDNVPN” project, which has reached deployment with Brahmaputra 3.0 SR.

References
[6.2.3-1] OPNFV: http://www.opnfv.org.

6.2.4 ONOS
6.2.4.1 Overview

The ONOS provides the control plane for a software-defined network (SDN), managing network components,
such as switches and links, and running software programs or modules to provide communication services to
end hosts and neighboring networks.

ONOS can run as a distributed system across multiple servers
The ONOS kernel and core services, as well as ONOS applications, are written in Java as bundles that are
loaded into the KarafOSGi container. OSGi is a component system for Java that allows modules to be installed
and run dynamically in a single JVM. Since ONOS runs in the JVM, it can run on several underlying OS
platforms such as Ubuntu or OS X.

106