Adding all releng octopus and pharos docs.

Please argue and remove as needed in the review.

Change-Id: Ia376d8be14c56f6a2fae3cd753ea53b869e5f784
Signed-off-by: agardner <agardner@linuxfoundation.org>

1 files changed, 29 insertions, 0 deletions

diff --git a/docs/specification/objectives.rst b/docs/specification/objectives.rst
new file mode 100644
index 0000000..0a0ad6a
--- /dev/null
+++ b/docs/specification/objectives.rst
@@ -0,0 +1,29 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) 2016 OPNFV.
+
+
+Pharos Compliance
+-----------------
+
+The **Pharos Specification** defines a hardware environment for deployment and testing of the
+**Brahmaputra** platform release. The **Pharos Project** is also responsible for defining lab
+capabilities, developing management/usage policies and process;  and a support plan for reliable
+access to project and release resources.  Community labs are provided as a service by companies and
+are not controlled by Pharos however our objective is to provide easy visibility of all lab
+capabilities and their usage at all-times.
+
+Pharos lab infrastructure has the following objectives:
+- Provides secure, scalable, standard and HA environments for feature development
+- Supports the full Brahmaputra deployment lifecycle (this requires a **bare-metal** environment)
+- Supports functional and performance testing of the Brahmaputra release
+- Provides mechanisms and procedures for secure remote access to Pharos compliant environments for
+  OPNFV community
+
+Deploying Brahmaputra in a Virtualized environment is possible and will be useful, however it does
+not provide a fully featured deployment and realistic test environment for the Brahmaputra release
+of OPNFV.
+
+The high level architecture is outlined in the following diagram:
+
+.. image:: ../images/pharos-archi1.jpg