diff options
Diffstat (limited to 'docs/release/overview.rst')
| -rw-r--r-- | docs/release/overview.rst | 74 |
1 files changed, 26 insertions, 48 deletions
diff --git a/docs/release/overview.rst b/docs/release/overview.rst index c7614de5c..3014da40f 100644 --- a/docs/release/overview.rst +++ b/docs/release/overview.rst @@ -4,6 +4,8 @@ .. SPDX-License-Identifier: CC-BY-4.0 .. (c) Open Platform for NFV Project, Inc. and its contributors +NOTE: This Document will be updated for Anuket in the Lakelse Release. + ================= Platform overview ================= @@ -28,20 +30,16 @@ NFV use cases. OPNFV also works upstream with other open source communities to b and learnings from its work directly to those communities in the form of blueprints, patches, bugs, and new code. -OPNFV focuses on building NFV Infrastructure (NFVI) and Virtualised Infrastructure -Management (VIM) by integrating components from upstream projects such as OpenDaylight, ONOS, OpenContrail, -OVN, OpenStack, Kubernetes, Ceph Storage, KVM, Open vSwitch, and Linux. -More recently, OPNFV has extended its portfolio of forwarding solutions to include DPDK, 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. +OPNFV focuses on building NFV Infrastructure (NFVI) and Virtualized Infrastructure Management (VIM) by +integrating components from upstream projects such as OpenDaylight, OVN, OpenStack, Kubernetes, +Ceph Storage, KVM, Open vSwitch, Linux, DPDK and FD.io. OPNFV- is able to run on both Intel and +ARM commercial and white-box hardware, support VM, Container and BareMetal workloads. 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 +Concentrating on these components, OPNFV aims to enhance NFV services by increasing performance and power efficiency improving reliability, availability and serviceability, and delivering comprehensive platform instrumentation. @@ -55,7 +53,7 @@ platform including common hardware requirements, software architecture, MANO and OPNFV Platform Overview Diagram -.. image:: ../images/diagram_euphrates.png +.. image:: ../images/hunter.png :alt: Overview infographic of the opnfv platform and projects. @@ -64,7 +62,6 @@ into the following basic building blocks: * Hardware: Infrastructure working group, Pharos project and associated activities * Software Platform: Platform integration and deployment projects -* MANO: MANO working group and associated projects * Tooling and testing: Testing working group and test projects * Applications: All other areas and drive requirements for OPNFV @@ -88,9 +85,10 @@ performance characteristics. Community labs are hosted by OPNFV member companies on a voluntary basis. The Linux Foundation also hosts an OPNFV lab that provides centralized CI and other production resources which are linked to community labs. -Future lab capabilities will include the ability easily automate deploy and test of any -OPNFV install scenario in any lab environment as well as on a nested "lab as a service" -virtual infrastructure. + +The Lab-as-a-service (LaaS) offering provides developers to readily access NFV infrastructure on demand. +Ongoing lab capabilities will include the ability to easily automate deployment and test of any OPNFV install +scenario in any lab environment using a concept called “Dynamic CI”. OPNFV Software Platform Architecture ==================================== @@ -104,22 +102,21 @@ components in conjunction with our upstream communities. Virtual Infrastructure Management --------------------------------- -OPNFV derives it's virtual infrastructure management from one of our largest upstream ecosystems -OpenStack. OpenStack provides a complete reference cloud management system and associated technologies. -While the OpenStack community sustains a broad set of projects, not all technologies are relevant in -the NFV domain, the OPNFV community consumes a sub-set of OpenStack projects and the usage and -composition may vary depending on the installer and scenario. +OPNFV derives its Virtual Infrastructure Management from OpenStack and Kubernetes. OpenStack provides a +complete reference cloud management system and associated technologies. While the OpenStack community +sustains a broad set of projects, not all technologies are relevant in the NFV domain, the OPNFV community +consumes a sub-set of OpenStack projects and the usage and composition may vary depending on the installer and scenario. +Additionally, OPNFV also uses Kubernetes, the popular Container Orchestration Engine. Kubernetes is intended to be a VIM for +Cloud Native Network Functions (CNFs). For details on the scenarios available in OPNFV and the specific composition of components refer to the :ref:`OPNFV User Guide & Configuration Guide <opnfv-user-config>`. -OPNFV now also has initial support for containerized VNFs. - ----------------- Operating Systems ----------------- -OPNFV currently uses Linux on all target machines, this can include Ubuntu, Centos or SUSE Linux. The +OPNFV currently uses Linux on all target machines. The specific version of Linux used for any deployment is documented in the installation guide. Networking Technologies @@ -141,10 +138,8 @@ being worked on by the community during this release of OPNFV include: interface devices (e.g., vNICs) managed by other OpenStack services (e.g. Nova). * OpenDaylight: addresses multivendor, traditional and greenfield networks, establishing the industry’s de facto SDN platform and providing the foundation for networks of the future. -* OpenContrail: An open source SDN controller designed for cloud and NFV use cases. It has an - analytics engine, well defined northbound REST APIs to configure and gather ops/analytics data. -* OVN: A virtual networking solution developed by the same team that created OVS. OVN stands for - Open Virtual Networking and is dissimilar from the above projects in that it focuses only on overlay networks. +* OVN: a distributed control-plane on top of the popular Open vSwitch (OVS) offers network virtualization + services. ---------- Data Plane @@ -162,16 +157,6 @@ networks. * DPDK: a set of libraries that bypass the kernel and provide polling mechanisms, instead of interrupt based operations, to speed up packet processing. DPDK works with both OVS and FD.io. ----- -MANO ----- -OPNFV integrates open source MANO projects for NFV orchestration and VNF management. -New MANO projects are constantly being added, currently OPNFV integrates: -* OpenBaton: Open Baton is a ETSI NFV compliant Management and Orchestration (MANO) Framework. - It enables virtual Network Services deployments on top of heterogeneous NFV Infrastructures. - OpenBaton is also used to deploy vIMS (clearwater and openIMS). - - Deployment Architecture ======================= @@ -249,6 +234,9 @@ There are two types of test cases in Yardstick: * OPNFV feature test cases include basic telecom feature testing from OPNFV projects; for example nfv-kvm, sfc, ipv6, Parser, Availability and SDN VPN +With the addition of the Network Service Benchmarking (NSB) initiative, it is possible to use Yardstick NSB +for benchmarking the performance of VNFs and Network Services. + System Evaluation and compliance testing ======================================== @@ -257,12 +245,9 @@ behaviors and capabilities for NFV systems developed externally from the OPNFV e evaluate and measure their ability to provide the features and capabilities developed in the OPNFV ecosystem. -The Dovetail project will provide a test framework and methodology able to be used on any NFV platform, +The Dovetail project provides a test framework and methodology able to be used on any NFV platform, including an agreed set of test cases establishing an evaluation criteria for exercising -an OPNFV compatible system. The Dovetail project has begun establishing the test framework -and will provide a preliminary methodology for the Danube release. Work will continue to -develop these test cases to establish a stand alone compliance evaluation solution -in future releases. +an OPNFV compatible system. Additional Testing ================== @@ -287,13 +272,6 @@ NFVBench NFVbench is a lightweight end-to-end dataplane benchmarking framework project. It includes traffic generator(s) and measures a number of packet performance related metrics. ----- -QTIP ----- -QTIP boils down NFVI compute and storage performance into one single metric for easy comparison. -QTIP crunches these numbers based on five different categories of compute metrics and relies on -Storperf for storage metrics. - -------- Storperf -------- |