summaryrefslogtreecommitdiffstats
path: root/docs/specification/objectives.rst
diff options
context:
space:
mode:
author10013968 <zhang.jun3g@zte.com.cn>2016-07-18 23:51:00 +0800
committer10013968 <zhang.jun3g@zte.com.cn>2016-07-27 23:49:59 +0800
commit988cf64e3a7601396e40b08a1aae07a524bf8c74 (patch)
treec4faf0b011473671e833df539c04e79de4884608 /docs/specification/objectives.rst
parentd9a002cba4741400c8b8d34e5bddb8cf33fb4e3c (diff)
Reformat the rst documents
Main changes: Set the textwidth to 100, exceptions: tables and http links may be longer than the limits Cut off the table width as shorten as possible JIRA: PHAROS-227 Change-Id: I07861e675d76ab5063f388d3be7d0b51c8bad38b Signed-off-by: 10013968 <zhang.jun3g@zte.com.cn>
Diffstat (limited to 'docs/specification/objectives.rst')
-rw-r--r--docs/specification/objectives.rst19
1 files changed, 11 insertions, 8 deletions
diff --git a/docs/specification/objectives.rst b/docs/specification/objectives.rst
index f6cfabed..0a0ad6aa 100644
--- a/docs/specification/objectives.rst
+++ b/docs/specification/objectives.rst
@@ -6,20 +6,23 @@
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.
+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
+- 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.
+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: