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/Chapter3.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/Chapter3.rst')
| -rw-r--r-- | docs/Chapter3.rst | 8 |
1 files changed, 4 insertions, 4 deletions
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. |