diff options
| author |   Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-06-05 16:01:24 +0000 |
|---|---|---|
| committer | Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-06-05 16:04:00 +0000 |
| commit | 64f81faf1419edd20a9224ff5a695d5cc7ae1f92 (patch) | |
| tree | ea6762ae666e56470f0578f1d7c318f8174fbc1c /docs | |
| parent | 581d2c7a5ff99a5ec5e612669547e8e02ec5024c (diff) | |
VNFRQTS - Update Chapter 1 and 2
Updating the text in Chapter 1 and 2.
Change-Id: I9a14bc3881c5fe8e89e2b05343e556421c21a41a
Issue-ID: VNFRQTS-219
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Chapter1.rst | 20 | ||||
| -rw-r--r-- | docs/Chapter2.rst | 13 |
2 files changed, 23 insertions, 10 deletions
diff --git a/docs/Chapter1.rst b/docs/Chapter1.rst index f62c313..61dc2f3 100644 --- a/docs/Chapter1.rst +++ b/docs/Chapter1.rst @@ -5,21 +5,21 @@ **Purpose** ============== -- The purpose of these requirements is to accelerate adoption of VNF/PNF best +- The purpose of these requirements is to accelerate adoption of xNF best practices which will increase innovation, minimize customization needed to - onboard VNFs/PNFs as well as reduce implementation complexity, time and cost + onboard xNFs as well as reduce implementation complexity, time and cost for all impacted stakeholders. - This initial release consolidates the requirements from Open-O and OpenECOMP - to provide common VNF/PNF requirements across the industry in order to drive + to provide common xNF requirements across the industry in order to drive interoperability, simplify management, and reduce cost to build, deploy and - manage VNFs/PNFs. + manage xNFs. - These requirements serve multiple purposes: - - Primarily it provides a detailed list of requirements for VNF/PNF - providers to meet to be compatible with ONAP; VNF/PNF providers will use - the VNF/PNF requirements to build VNFs/PNFs that are compatible with ONAP + - Primarily it provides a detailed list of requirements for xNF + providers to meet to be compatible with ONAP; xNF providers will use + the xNF requirements to build VNFs/PNFs that are compatible with ONAP - It can also serve as a list of requirements that service providers can use in RFPs for selecting VNFs/PNFs - It will also be used as a basis for testing and certification of - VNFs/PNFs for compliance with ONAP; ONAP projects such as the VNF - Validation Project will uses these VNFs/PNFs requirements to build test - cases to validate VNFs/PNFs for compliance with ONAP. + xNFs for compliance with ONAP; ONAP projects such as the VNF + Validation Project will uses these xNFs requirements to build test + cases to validate xNFs for compliance with ONAP. diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index ceee9ed..11db2c5 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -51,3 +51,16 @@ IETF Specifications: Suite 117, Fremont, California 94538, USA; Phone: +1-510-492-4080, Fax: +1-510-492-4001. +Submitting Feedback +------------------------------------ +To report issues on this document, please perform one of the following steps: + + 1. Log a JIRA defect against the document within the VNF Requirements + (VNFRQTS) project at https://jira.onap.org/projects/VNFRQTS. + Note: This will require a Linux Foundation ID to login to JIRA. + 2. Send an email to onap-discuss@lists.onap.org with subject line + starting with the tag [vnfrqts]. Note: This will require subscribing + to the onap-discuss email discussion list. Refer to the following + instructions to subscribe to the mail list: + https://wiki.onap.org/display/DW/Mailing+Lists + |