summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorrr929y <rr929y@att.com>2017-08-25 12:45:11 -0500
committerrr929y <rr929y@att.com>2017-08-25 12:45:11 -0500
commit5a0b2f1eff3cc48a0232ff71c8e4510a65713ccd (patch)
tree98fd5bb7097a5fcd1e3b61c0359d61e99af76571 /docs
parentdd1fc6cd21aa8656eea458dfd132180d7b6a2fb2 (diff)
VNFRQTS Requirements - Chapter 1
VNFRQTS Requirments - adding chapter 1 content Change-Id: I7e93fc4863db3a0affd241d3189460b4c4320a8d Issue-ID:VNFRQTS-58 Signed-off-by: rr929y <rr929y@att.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/Chapter1.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/Chapter1.rst b/docs/Chapter1.rst
index 2924ae7..1306efc 100644
--- a/docs/Chapter1.rst
+++ b/docs/Chapter1.rst
@@ -1,2 +1,8 @@
**1. Purpose**
==============
+- The purpose of these requirements is to accelerate adoption of VNF best practices which will increase innovation, minimize customization needed to onboard VNFs 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 requirements across the industry in order to drive interoperability, simplify management, and reduce cost to build, deploy and manage VNFs.
+- These requirements serve multiple purposes:
+ - Primarily it provides a detailed list of requirements for VNF providers to meet to be compatible with ONAP; VNF providers will use the VNF requirements to build VNFs that are compatible with ONAP
+ - It can also serve as a list of requirements that service providers can use in RFPs for selecting VNFs
+ - It will also be used as a basis for testing and certification of VNFs for compliance with ONAP; ONAP projects such as the VNF Validation Project will uses these VNFs requirements to build test cases to validate VNFs for compliance with ONAP. \ No newline at end of file