[VNFRQTS] break up larger rst files into toxtree

Broke all chapter files up so they follow the same patter

Change-Id: I8a2152b92f0568cf4858615054bb66fabf0ea343
Issue-ID: VNFRQTS-253
Signed-off-by: stark, steven <ss820f@att.com>

1 files changed, 25 insertions, 0 deletions

diff --git a/docs/Chapter1/index.rst b/docs/Chapter1/index.rst
new file mode 100644
index 0000000..a0b917e
--- /dev/null
+++ b/docs/Chapter1/index.rst
@@ -0,0 +1,25 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2017 AT&T Intellectual Property.  All rights reserved.
+
+Purpose
+=======
+
+- The purpose of these requirements is to accelerate adoption of xNF best
+  practices which will increase innovation, minimize customization needed to
+  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 xNF requirements across the industry in order to drive
+  interoperability, simplify management, and reduce cost to build, deploy and
+  manage xNFs.
+- These requirements serve multiple purposes:
+    - 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
+      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.