.. _opnfv-overview:
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. SPDX-License-Identifier: CC-BY-4.0
.. (c) Open Platform for NFV Project, Inc. and its contributors
================
Platform overview
================
Introduction
============
Network Functions Virtualization (NFV) is transforming the networking industry via
software-defined infrastructures and open source is the proven method for quickly developing
software for commercial products and services that can move markets.
Open Platform for NFV (OPNFV) facilitates the development and evolution of NFV
components across various open source ecosystems. Through system level integration,
deployment and testing, OPNFV constructs a reference NFV platform to accelerate the
transformation of enterprise and service provider networks.
As an open source project, OPNFV is uniquely positioned to bring together the work
of standards bodies, open source communities, service providers and commercial suppliers to deliver
a de facto NFV platform for the industry.
By integrating components from upstream projects, the community is able to conduct performance
and use case-based testing on a variety of solutions to ensure the platform’s suitability for
NFV use cases. OPNFV also works upstream with other open source communities to bring contributions
and learnings from its work directly to those communities in the form of blueprints, patches, bugs,
and new code.
OPNFV initially focused on building NFV Infrastructure (NFVI) and Virtualised Infrastructure
Management (VIM) by integrating components from upstream projects such as OpenDaylight,
OpenStack, Ceph Storage, KVM, Open vSwitch, and Linux.
More recently, OPNFV has extended its portfolio of forwarding solutions to include fd.io and ODP,
is able to run on both Intel and ARM commercial and white-box hardware, support VM, Container and
BareMetal workloads, and includes Management and Network Orchestration MANO components primarily
for application composition and management in the Danube release.
These capabilities, along with application programmable interfaces (APIs) to other NFV
elements, form the basic infrastructure required for Virtualized Network Functions (VNF)
and MANO components.
Concentrating on these components while also considering proposed projects on additional
topics (such as the MANO components and applications themselves), OPNFV aims to enhance
NFV services by increasing performance and power efficiency improving reliability,
availability and serviceability, and delivering comprehensive platform instrumentation.
OPNFV Platform Architecture
===========================
The OPNFV project addresses a number of aspects in the development of a consistent virtualisation
platform including common hardware requirements, software architecture, MANO and applications.
OPNFV Platform Overview Diagram
.. image:: ../images/opnfvplatformgraphic.png
:alt: Overview infographic of the opnfv platform and projects.
To address these areas effectively, the OPNFV platform architecture can be decomposed
into the following basic building blocks:
* Hardwar module clearwater {
namespace "http://localhost/ietf-inet-types.yang";
prefix "yang";
organization "HP";
contact "TBD";
description "This module defines a VNF Deployment Unit.";
revision "2014-05-18" {
description
"Initial version";
reference
"RFC XXXX";
}
container clearwater {
description
"Vdus used in a vnfd";
list ellis {
key id;
leaf id{
type string;
description "key ID for vdu1";
}
description
"Vdu key";
leaf instance-num {
type uint16{
range 1..6;}
default 1;
description
"Number of instances of the said VDU which shall be
instantiated";
}
leaf vm-image {
type string;
reference "uri";
description
"Reference to a VM image";
}
container resource {
description
"The required resource";
container cpu {
description
"The required computation resource";
leaf vCPU_num {
type uint32{
range 4;
}
description
"The number of virtual CPU units";
}
list vCPU-spec {
key "name";
description
"Processor characteristics for the VDU";
leaf name {
type string;
description
"Name of vCPU-spec";
}
leaf description {
type string;
description
"Description of vCPU-spec";
}
leaf value {
type uint32;
description
"Value of vCPU-spec";
}
}
}
container memory {
description
"The required memory resource";
leaf memory_size {
type uint32{
range 4096;
}
description
"Memory size, unit:MBytes";
}
list memory-spec {
key name;
description
"Memory characteristics for the VDU";
leaf name {
type string;
description
"Name of memory-spec";
}
leaf description {
type string;
description
"Description of memory-spec";
}
leaf value {
type uint32;
description
"Value of memory-spec";
}
}
}
container disk {
description
"The required storage resource";
leaf disk-size {
type uint32{
range 2048;
}
description
"Virtual storage size, unit:MBytes";
}
list disk-KQI {
key name;
description
"Storage characteristics in the VDU";
leaf name {
type string;
description
"Name of disk-KQI";
}
leaf description {
type string;
description
"Description of disk-KQI";
}
leaf value {
type uint32;
description
"Value of disk-KQI";
}
}
}
container vnic {
description
"Virtual network interface card (vnic) resource";
leaf vnic-num {
type uint32{
range 2;
}
description
"The total number of virtual vnic";
}
}
}
container workflow-script {
description
"VDU workflow script";
leaf init {
type string;
default "start.sh";
description
"VDU initialization script";
}
leaf terminate {
type string;
default "stop.sh";
description
"VDU termination script";
}
leaf graceful-shutdown {
type string;
default "shutdown.sh";
description
"VDU graceful shutdown script";
}
}
}
list bono {
key id;
leaf id{
type string;
description "key ID for vdu2";
}
description
"Vdu key";
leaf instance-num {
type uint16;
default 3;
description
"Number of instances of the said VDU which shall be
instantiated";
}
leaf vm-image {
type string;
reference "URI";
description
"Reference to a VM image";
}
container resource {
description
"The required resource";
container cpu {
description
"The required computation resource";
leaf vCPU_num {
type uint32{
range 3;
}
description
"The number of virtual CPU units";
}
list vCPU-spec {
key "name";
description
"Processor characteristics for the VDU";
leaf name {
type string;
description
"Name of vCPU-spec";
}
leaf description {
type string;
description
"Description of vCPU-spec";
}
leaf value {
type uint32;
description
"Value of vCPU-spec";
}
}
}
container memory {
description
"The required memory resource";
leaf memory_size {
type uint32{
range 2048;
}
description
"Memory size, unit:MBytes";
}
list memory-spec {
key name;
description
"Memory characteristics for the VDU";
leaf name {
type string;
description
"Name of memory-spec";
}
leaf description {
type string;
description
"Description of memory-spec";
}
leaf value {
type uint32;
description
"Value of memory-spec";
}
}
}
container disk {
description
"The required storage resource";
leaf disk-size {
type uint32{
range 3000;
}
description
"Virtual storage size, unit:MBytes";
}
list disk-KQI {
key name;
description
"Storage characteristics in the VDU";
leaf name {
type string;
description
"Name of disk-KQI";
}
leaf description {
type string;
description
"Description of disk-KQI";
}
leaf value {
type uint32;
description
"Value of disk-KQI";
}
}
}
container vnic {
description
"Virtual network interface card (vnic) resource";
leaf vnic-num {
type uint32{
range 2;
}
description
"The total number of virtual vnic";
}
}
}
container workflow-script {
description
"VDU workflow script";
leaf init {
type string;
default "start.sh";
description
"VDU initialization script";
}
leaf terminate {
type string;
default "stop.sh";
description
"VDU termination script";
}
leaf graceful-shutdown {
type string;
default "shutdown.sh";
description
"VDU graceful shutdown script";
}
}
}
}
}
