diff options
| -rw-r--r-- | docs/vnf_guidelines/vnf_guidelines.rst | 81 |
1 files changed, 44 insertions, 37 deletions
diff --git a/docs/vnf_guidelines/vnf_guidelines.rst b/docs/vnf_guidelines/vnf_guidelines.rst index 21a12db..3645e9a 100644 --- a/docs/vnf_guidelines/vnf_guidelines.rst +++ b/docs/vnf_guidelines/vnf_guidelines.rst @@ -7,24 +7,24 @@ :depth: 3 .. -============== -VNF Guidelines -============== +================== +VNF/PNF Guidelines +================== **1. Purpose** ============== -- This document focuses on setting and evolving VNF standards that will facilitate industry discussion, participation, alignment and evolution towards comprehensive and actionable VNF best practices and standard interface. -- The goal is to accelerate adoption of VNF best practices which will increase innovation, minimize customization needed to onboard VNFs as well as reduce implementation complexity, time and cost for all impacted stakeholders. -- The intent is to drive harmonization of VNFs across VNF providers, Network Cloud Service providers (NCSPs) and the overall Network Function Virtualization (NFV) ecosystem by providing both long term vision as well as short tem focus and clarity. +- This document focuses on setting and evolving VNF/PNF standards that will facilitate industry discussion, participation, alignment and evolution towards comprehensive and actionable VNF/PNF best practices and standard interface. +- The goal is to accelerate adoption of VNF/PNF best practices which will increase innovation, minimize customization needed to onboard VNFs/PNFs as well as reduce implementation complexity, time and cost for all impacted stakeholders. +- The intent is to drive harmonization of VNFs/PNFs across VNF/PNF providers, Network Cloud Service providers (NCSPs) and the overall Network Function Virtualization (NFV) ecosystem by providing both long term vision as well as short tem focus and clarity. **2. Scope** ============ -- The audience for this document are VNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle management requirements for VNFs to be compliant with ONAP. +- The audience for this document are VNF/PNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle management requirements for VNFs/PNFs to be compliant with ONAP. - These guidelines describe VNF environment and provide an overview of what the VNF developer needs to know to operate and be compliant with ONAP. -- These guidelines contains high level expectations and references to specific requirements documentation for VNFs which are applicable to the Amsterdam release of ONAP. +- These guidelines contains high level expectations and references to specific requirements documentation for VNFs/PNFs which are applicable to the Beijing release of ONAP. - Part of the guidelines also contains visionary recommendations for future functionality that could be desirable for ONAP future releases. -- Conformance requirements are in the VNF Requirements document(http://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/index.html). +- Conformance requirements are in the VNF/PNF Requirements document(http://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/index.html). **3. Introduction** =================== @@ -34,11 +34,11 @@ a. Motivation The requirements and guidelines defined herein are intended to facilitate industry discussion, participation alignment and evolution -toward comprehensive and actionable VNF best practices. Integration +toward comprehensive and actionable VNF/PNF best practices. Integration costs are a significant impediment to the development and deployment of new services. We envision developing open source industry processes and -best practices leading eventually to VNF standards supporting commercial -acquisition of VNFs with minimal integration costs. Traditional PNFs +best practices leading eventually to VNF/PNF standards supporting commercial +acquisition of VNFs/PNFs with minimal integration costs. Traditional PNFs have all been unique like snowflakes and required expensive custom integration, whereas VNF products and services should be designed for easier integration just like Lego\ :sup:`TM` blocks. For example, by @@ -75,19 +75,19 @@ agile processes and the emergence of industry supported open source communities imply corresponding changes in processes at many industry collaboration bodies. With limited operational experience and much more dynamic requirements, open source communities are expected to evolve -these VNF guidelines further before final documentation of those aspects +these VNF/PNF guidelines further before final documentation of those aspects necessary for standardization. This document and accompanying refer documents -provides VNF providers, NCSPs and other interested 3rd parties a set of +provides VNF/PNF providers, NCSPs and other interested 3rd parties a set of guidelines and requirements for the design, build and overall lifecycle management of VNFs. -**VNF Providers** +**VNF/PNF Providers** -Both suppliers transitioning from providing physical network functions -(PNFs) to providing VNFs as well as new market entrants should find -these VNF requirements and guidelines a useful introduction to the -requirements to be able to develop VNFs for deployment into a Network -Cloud. VNF Providers may also be interested to test their VNFs in the +PNF suppliers and those transitioning from providing physical network functions +to providing VNFs as well as new market entrants should find +these VNF/PNF requirements and guidelines a useful introduction to the +requirements to be able to develop VNFs/PNFs for deployment into a Network +Cloud. VNF/PNF Providers may also be interested to test their VNFs/PNFs in the context of an open source implementation of the environment. **Network Cloud Service Providers (NCSPs)** @@ -108,11 +108,11 @@ guidelines to meet the industry’s collective needs. Other parties such as solution providers, open source community, industry standard bodies, students and researchers of network technologies, as well as enterprise customers may also be interested in -the VNF Guidelines. Solution Providers focused on specific industry -verticals may find these VNF guidelines useful in the development of -specialized VNFs that can better address the needs of their industry -through deployment of these VNFs in NCSP infrastructure. Open Source -developers can use these VNF guidelines to facilitate the automation of +the VNF/PNF Guidelines. Solution Providers focused on specific industry +verticals may find these VNF/PNF guidelines useful in the development of +specialized VNFs/PNFs that can better address the needs of their industry +through deployment of these VNFs/PNFs in NCSP infrastructure. Open Source +developers can use these VNF/PNF guidelines to facilitate the automation of VNF ingestion and deployment. The emergence of a market for VNFs enables NCSPs to more rapidly deliver increased functionality, for execution on white box hardware on customer’s premises – such functionality may be of @@ -125,19 +125,19 @@ This document is part of a hierarchy of documents that describes the overall Requirements and Guidelines for ONAP. The diagram below identifies where this document fits in the hierarchy. -+----------------------------------------------------------------------------------------------+ -| ONAP Requirements and Guidelines | -+===================+==========================================================================+ -| VNF Guidelines | Future ONAP Subject Documents | -+-------------------+-------------------------------------+------------------------------------+ -| VNF Requirements | Future VNF Requirements Documents | Future Requirements Documents | -+-------------------+-------------------------------------+------------------------------------+ ++--------------------------------------------------------------------------------------------------+ +| ONAP Requirements and Guidelines | ++=======================+==========================================================================+ +| VNF/PNF Guidelines | Future ONAP Subject Documents | ++-----------------------+---------------------------------------+----------------------------------+ +| VNF/PNF Requirements | Future VNF/PNF Requirements Documents | Future Requirements Documents | ++-----------------------+---------------------------------------+----------------------------------+ Document summary: -**VNF Guidelines** +**VNF/PNF Guidelines** -- Describes VNF environment and overview of requirements +- Describes VNF/PNF environment and overview of requirements *VNF Requirements* @@ -721,7 +721,12 @@ terms of VM characteristics (often referred to as VM Flavors), VM sizes and cloud acceleration capabilities aimed at VNFs such as Linux Foundation project Data Plane Development Kit (DPDK). -**6. Summary** +**6. PNF Context** +================== + + + +**7. Summary** =============== The intent of these guidelines and requirements is to provide long term @@ -738,7 +743,7 @@ more detailed requirements documents. The subtending documents provide more detailed requirements and are listed in Appendix B - References. All documents are expected to evolve. -Some of these VNF guidelines may be more broadly applicable in the +Some of these VNF/PNF guidelines may be more broadly applicable in the industry, e.g., in other open source communities or standards bodies. The art of VNF architecture and development is expected to mature rapidly with practical deployment and operations experience from a @@ -748,7 +753,7 @@ enhancements to support their particular operational processes, but these guidelines are expected to remain broadly applicable across a number of service providers interested in acquiring VNFs. -We invite feedback on these VNF Guidelines in the context of the +We invite feedback on these VNF/PNF Guidelines in the context of the ONAP Project. We anticipate an ongoing project within the ONAP community to maintain similar guidance for VNF developers to ONAP.Comments on these guidelines should be discussed there. @@ -781,6 +786,8 @@ a. Glossary | VNFC | Virtual Network Function Component (VNFC) are the sub-components of a VNF providing a VNF Provider a defined sub-set of that VNF's functionality, with the main characteristic that a single instance of this component maps 1:1 against a single Virtualization Container. See Figure 3 for the relationship between VNFC and VNFs. | | | |image2| | +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| PNF | PNF is a vendor-provided Network Function(s) implemented using a bundled set of hardware and software. | ++-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ b. References --------------- |