diff options
| author |   hp1256 <hp1256@att.com> | 2017-11-07 11:23:44 -0800 |
|---|---|---|
| committer | hp1256 <hp1256@att.com> | 2017-11-07 11:23:44 -0800 |
| commit | c586c3483e93c58eaa8160025a425378e720ba39 (patch) | |
| tree | 37b30d4f6b21539773012b8eb3e374d44b07ba0e /docs/Chapter3.rst | |
| parent | eba3d2a528d1654a964a1ffc7027d287a0280f1c (diff) | |
VNFRQTS -Requirements Chg VNF Vendor to Provider
VNFRQTS -Requirements Changed the wording from VNF Vendor to VNF
Provider
Change-Id: I8806a7ca497ac2b5761024d83f3d688fb3934a89
Issue-ID:VNFRQTS-137
Signed-off-by: hp1256 <hp1256@att.com>
Diffstat (limited to 'docs/Chapter3.rst')
| -rw-r--r-- | docs/Chapter3.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Chapter3.rst b/docs/Chapter3.rst index a7a34f3..5681b4c 100644 --- a/docs/Chapter3.rst +++ b/docs/Chapter3.rst @@ -3,7 +3,7 @@ - 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 vendor needs to understand. There are currently 2 models described in this document +- 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. - 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. |