diff options
| author |   steven stark <ss820f@att.com> | 2018-03-14 10:15:44 -0700 |
|---|---|---|
| committer | steven stark <ss820f@att.com> | 2018-03-14 10:16:48 -0700 |
| commit | b25f0d92accbae23e21e35588edc2774a04979b0 (patch) | |
| tree | d0683c2cfce5b4b8f020e0a905f475212cc47854 /docs/Chapter1.rst | |
| parent | c4ace4929c2b2227c8f4df9eba035a96061424a0 (diff) | |
VNFRQTS - Update chapter 1,2 and 3 for PNfs
Update the requirements chapter 1, 2 and 3 to widen the scope to include PNFs. Updates to include replacing VNF with VNF/PNF.
Change-Id: I1716a884d13875b4034595b30847eb77b78eafd2
Issue-ID: VNFRQTS-190
Signed-off-by: steven stark <ss820f@att.com>
Diffstat (limited to 'docs/Chapter1.rst')
| -rw-r--r-- | docs/Chapter1.rst | 10 |
1 files changed, 5 insertions, 5 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. |