[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, 66 insertions, 0 deletions

diff --git a/docs/Chapter2/index.rst b/docs/Chapter2/index.rst
new file mode 100644
index 0000000..eab491d
--- /dev/null
+++ b/docs/Chapter2/index.rst
@@ -0,0 +1,66 @@
+.. 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.
+
+
+Scope
+=====
+
+- The audience for this document are xNF 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
+  developer needs to know to operate and be compliant with ONAP.
+- Requirements that are not applicable to xNF 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.
+- Network Service Descriptions are beyond the scope of these requirements.
+
+References
+-----------------------
+This section contains a list of normative and informative references along
+with information on acquiring the identified references.  Normative references
+are required to be implemented by this document. Informative references are
+for informational purposes only.
+
+Normative References
+^^^^^^^^^^^^^^^^^^^^^^^
++---------------+-----------------------------------------------------+
+| Reference     | Description                                         |
++===============+=====================================================+
+| [RFC 2119]    | IETF RFC2119, Key words for use in RFCs to Indicate |
+|               | Requirement Levels, S. Bradner, March 1997.         |
++---------------+-----------------------------------------------------+
+
+Informative References
+^^^^^^^^^^^^^^^^^^^^^^^^
++---------------+-----------------------------------------------------+
+| Reference     | Description                                         |
++===============+=====================================================+
+|               |                                                     |
++---------------+-----------------------------------------------------+
+
+Reference Acquisition
+^^^^^^^^^^^^^^^^^^^^^^^
+IETF Specifications:
+
+- Internet Engineering Task Force (IETF) Secretariat, 48377 Fremont Blvd.,
+  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