diff options
| author |   Herb Patten <hp1256@att.com> | 2018-03-30 14:06:22 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2018-03-30 14:06:22 +0000 |
| commit | 8823fbb8518ca4b272c0eeb1764569299193671e (patch) | |
| tree | 1ddeb733a5d138e2ffe31a859879727e983327b9 | |
| parent | 70fe10e59cb36356456059f252b3c3c5d2618a0d (diff) | |
| parent | dabbd75dce7b563d1c38e48a29a3271781e798da (diff) | |
Merge "Fix other Doc8 errors (line-length)"
| -rw-r--r-- | docs/Chapter1.rst | 23 |
1 files changed, 17 insertions, 6 deletions
diff --git a/docs/Chapter1.rst b/docs/Chapter1.rst index 2f5c94d..f62c313 100644 --- a/docs/Chapter1.rst +++ b/docs/Chapter1.rst @@ -5,10 +5,21 @@ **Purpose** ============== -- 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. +- 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/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. - + - 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. |