diff options
| -rw-r--r-- | docs/Chapter1.rst | 10 | ||||
| -rw-r--r-- | docs/Chapter2.rst | 6 | ||||
| -rw-r--r-- | docs/Chapter3.rst | 8 |
3 files changed, 12 insertions, 12 deletions
diff --git a/docs/Chapter1.rst b/docs/Chapter1.rst index 4b3d522..76a7a3d 100644 --- a/docs/Chapter1.rst +++ b/docs/Chapter1.rst @@ -5,10 +5,10 @@ **1. Purpose** ============== -- The purpose of these requirements 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. -- This initial release consolidates the requirements from Open-O and OpenECOMP to provide common VNF requirements across the industry in order to drive interoperability, simplify management, and reduce cost to build, deploy and manage VNFs. +- The purpose of these requirements 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. +- This initial release consolidates the requirements from Open-O and OpenECOMP to provide common VNF/PNF requirements across the industry in order to drive interoperability, simplify management, and reduce cost to build, deploy and manage VNFs/PNFs. - These requirements serve multiple purposes: - - Primarily it provides a detailed list of requirements for VNF providers to meet to be compatible with ONAP; VNF providers will use the VNF requirements to build VNFs that are compatible with ONAP - - It can also serve as a list of requirements that service providers can use in RFPs for selecting VNFs - - It will also be used as a basis for testing and certification of VNFs for compliance with ONAP; ONAP projects such as the VNF Validation Project will uses these VNFs requirements to build test cases to validate VNFs for compliance with ONAP. + - Primarily it provides a detailed list of requirements for VNF/PNF providers to meet to be compatible with ONAP; VNF/PNF providers will use the VNF/PNF requirements to build VNFs/PNFs that are compatible with ONAP + - It can also serve as a list of requirements that service providers can use in RFPs for selecting VNFs/PNFs + - It will also be used as a basis for testing and certification of VNFs/PNFs for compliance with ONAP; ONAP projects such as the VNF Validation Project will uses these VNFs/PNFs requirements to build test cases to validate VNFs/PNFs for compliance with ONAP. diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index 6237e38..5527215 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -5,9 +5,9 @@ **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. -- These requirements are strictly from a standpoint of what the VNF developer needs to know to operate and be compliant with ONAP. -- Requirements that are not applicable to VNF providers such as those that applicable to service providers are not included in this document. +- 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 requirements are strictly from a standpoint of what the VNF/PNF developer needs to know to operate and be compliant with ONAP. +- Requirements that are not applicable to VNF/PNF providers such as those that applicable to service providers are not included in this document. - These requirements are applicable to the Amsterdam release of ONAP. - Scope of the ONAP versions/release and future functionality diff --git a/docs/Chapter3.rst b/docs/Chapter3.rst index 88cddeb..c1eae6b 100644 --- a/docs/Chapter3.rst +++ b/docs/Chapter3.rst @@ -7,11 +7,11 @@ ==================== - These requirements are specific to the Amsterdam release of ONAP. It is the initial release of requirements based on a merge of the Open-O and OpenECOMP requirements. - Requirements are identified as either MUST, MUST NOT, SHOULD, SHOULD NOT, or MAY as defined in RFC 2119. -- Chapter 4 contains the VNF requirements involving the design and development of VNFs. These requirements help VNFs operate efficiently within a cloud environment. Requirements cover design, resiliency, security, modularity and DevOps. -- Chapter 5 describes the different data models the VNF provider needs to understand. There are currently 2 models described in this document - - The first model is the onboarding package data model. This is a TOSCA model that will describe how all the elements passed from the VNF Provider to the Service provider should be formatted and packaged. +- Chapter 4 contains the VNF/PNF requirements involving the design and development of VNFs/PNFs. These requirements help VNFs/PNFs operate efficiently within a cloud environment. Requirements cover design, resiliency, security, modularity and DevOps. +- Chapter 5 describes the different data models the VNF/PNF provider needs to understand. There are currently 2 models described in this document + - The first model is the onboarding package data model. This is a TOSCA model that will describe how all the elements passed from the VNF/PNF Provider to the Service provider should be formatted and packaged. - The second model is HEAT template used for orchestrating and instantiating virtual resources in an OpenStack environment. At this time the HEAT files will be passed to the Service provider as a data element within the TOSCA onboarding package. - Chapter 6 details the requirements specific to an implementation. The current implementations documented are OpenStack and Azure. -- Chapter 7 provides the comprehensive set of requirements for VNFs to be on-boarded, configured and managed by ONAP. +- Chapter 7 provides the comprehensive set of requirements for VNFs/PNFs to be on-boarded, configured and managed by ONAP. - Chapter 8 is the appendix that provide a number of detailed data record formats. |