restruct documents according to opnfvdocs

Use only development and release for we don't have test codes for now.

JIRA: PHAROS-311

Change-Id: Iacfcaba81a7a52e09cf999b8603cc9dc2f8f2b97
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>

1 files changed, 40 insertions, 0 deletions

diff --git a/docs/release/configguide/configguide.rst b/docs/release/configguide/configguide.rst
new file mode 100644
index 00000000..29466776
--- /dev/null
+++ b/docs/release/configguide/configguide.rst
@@ -0,0 +1,40 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) 2016 OPNFV.
+
+***************
+Lab Setup Guide
+***************
+
+Provides an overview for setting up a Pharos lab. A full set of
+:ref:`pharos_master` documents are maintained in the *pharos* repo.
+
+When setting up an OPNFV community lab ...
+
+* Provide the Pharos community with details of the intended setup, including ...
+
+  * Overview of resources are being offered to the community, intended purpose and known limitations
+  * Lab owner name with contacts
+  * Timelines for availablity for development, test, release production, ...
+
+* Update the Pharos Wiki with lab details
+
+  * Lab map, organization, contacts, status, location, resources, role, etc.
+  * `Community labs <https://wiki.opnfv.org/display/pharos#PharosHome-Overview>`_
+  * :ref:`pharos_wiki`
+
+* Update the Pharos project information file "Current Labs"
+
+  * :ref:`pharos_information`
+
+* Create new Wiki pages for lab and POD specific information
+
+  * Access procedures
+  * Usage guidelines for developers
+  * Update infomtation as PODs are re-assigned or usage/availability changes
+
+* Fill Lab and POD templates ... :ref:`pharos_lab` ... :ref:`pharos_pod`
+
+  * Note that security sensitive lab information should be stored in the secure Pharos repo
+
+* Connect PODs to Jenkins/CI