summaryrefslogtreecommitdiffstats
path: root/docs/Chapter2.rst
diff options
context:
space:
mode:
authorsteven stark <ss820f@att.com>2018-03-14 10:15:44 -0700
committersteven stark <ss820f@att.com>2018-03-14 10:16:48 -0700
commitb25f0d92accbae23e21e35588edc2774a04979b0 (patch)
treed0683c2cfce5b4b8f020e0a905f475212cc47854 /docs/Chapter2.rst
parentc4ace4929c2b2227c8f4df9eba035a96061424a0 (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/Chapter2.rst')
-rw-r--r--docs/Chapter2.rst6
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