diff options
| author |   Steven Wright <sw3588@att.com> | 2018-03-20 11:40:54 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2018-03-20 11:40:54 +0000 |
| commit | 7a0850e419756b9b61c86aa00d2dfa20f94ec395 (patch) | |
| tree | 026c3ec311a3aa1f39fba007a9d64114441d0890 /docs/Chapter2.rst | |
| parent | 62aa8a359bccd4d79b0c03219f41c03bab2cb6db (diff) | |
| parent | b25f0d92accbae23e21e35588edc2774a04979b0 (diff) | |
Merge "VNFRQTS - Update chapter 1,2 and 3 for PNfs"
Diffstat (limited to 'docs/Chapter2.rst')
| -rw-r--r-- | docs/Chapter2.rst | 6 |
1 files changed, 3 insertions, 3 deletions
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 |