Skip to end of metadata
Go to start of metadata

This document describes the OPNFV platform at a high level, based on the ETSI NFV architecture (link TBD). One purpose is to present where the different OPNFV projects are active, so the presentation is based on the existing OPNFV projects.

Contents

This document starts with an overview of the components that go into the OPNFV platform, with links to other pages that contain more details. All OPNFV projects are mapped to these components. There is also a Technical Introduction to OPNFV and a list of OPNFV Projects. References are on their own page.

Outline

The ETSI NFV Reference Architecture defines the key terms for Network Function Virtualization (NFV). A Virtualized Network Function (VNF) consists of components known by the acronym VNFC. The VNF components, which run in virtual machines, communicate with each other by using virtual networks. The NFV Infrastructure realizes the virtual machines and virtual networks. The virtual networks are realized with virtual switches, and the virtual machine management (including the hypervisor) creates, updates and destroys the virtual machines.

The Virtual Infrastructure Manager (VIM) decides where to run the virtual machines and what virtual networks should exist. In the case of OPNFV, the virtual infrastructure management includes OpenStack. The virtual infrastructure manager can create virtual networks itself or it can use a software defined networking (SDN) controller which can have more capabilities. 

The Management and Orchestration (MANO) layer communicates with both the virtual infrastructure manager and the virtualized network function, and can give instructions to virtualized infrastructure management based on a higher level view.

 

 

 

architecture overview

 

SDN

  • BGPVPN
  • SFC
  • Onos
  • ODL
  • OpenContrail
  • OVN

Network

  • Quagga
  • BGPVPN

Deployment

  • Versions
  • Components

Integration and testing

 

 

 

 

  • No labels

2 Comments

  1. Why there is no direct interface between MANO and NFVI? Does it mean we assume Physical hardware exists before we manage and orchestrate?Physical  Hardware like Server, Switches, Clusters , Network and Storage etc.?

  2. In Models meeting discussions it was highlighted that mapping of OPNFV projects to release architecture is more important to the title of the page. Plus the granularity of this diagram is useful but info graphics need not be high priority. Mapping between this and MANO terminology can be taken up later. More important is the upstream architecture and how they get integrated through specific projects in them. Visuals are only cue to perspective and can be many

    Refer to Feedback in Slides: Architecture and Release D2E Inputs.