From a43ef5023419467adb704ea6c2f0b2b488fd0e38 Mon Sep 17 00:00:00 2001 From: Hagop Bozawglanian Date: Wed, 17 Apr 2019 04:30:50 +0000 Subject: VNFRQTS - xNF to VNF or PNF Change-Id: I4a6a445a6c713c4be53be8cd79e158a1a10bc975 Issue-ID: VNFRQTS-571 Signed-off-by: Hagop Bozawglanian --- docs/Chapter2/index.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/Chapter2') diff --git a/docs/Chapter2/index.rst b/docs/Chapter2/index.rst index f8d490a..6e25788 100644 --- a/docs/Chapter2/index.rst +++ b/docs/Chapter2/index.rst @@ -16,18 +16,19 @@ Scope ===== -- The audience for this document are xNF providers, NCSPs and other +- The audience for this document are VNF or PNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle - management requirements for xNFs to be compliant with ONAP. -- These requirements are strictly from a standpoint of what the xNF + management requirements for VNFs or PNFs to be compliant with ONAP. +- These requirements are strictly from a standpoint of what the VNF or PNF developer needs to know to operate and be compliant with ONAP. -- Requirements that are not applicable to xNF providers such as those +- Requirements that are not applicable to VNF or PNF providers such as those that applicable to service providers are not included in this document. - These requirements are applicable to the current release of ONAP. - Scope of the ONAP versions/release and future functionality - The VNF Requirements should include support for the functionality of the ONAP E-E use cases. -- These requirements apply to xNFs at both ONAP Design-Time and ONAP Run-Time. +- These requirements apply to VNFs or PNFs at both ONAP Design-Time and ONAP + Run-Time. - Network Service Descriptions are beyond the scope of these requirements. References -- cgit 1.2.3-korg