summaryrefslogtreecommitdiffstats
path: root/docs/configguide/pharosconfig.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/configguide/pharosconfig.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/configguide/pharosconfig.rst')
-rw-r--r--docs/configguide/pharosconfig.rst15
1 files changed, 8 insertions, 7 deletions
diff --git a/docs/configguide/pharosconfig.rst b/docs/configguide/pharosconfig.rst
index 6b0783de..6b48100a 100644
--- a/docs/configguide/pharosconfig.rst
+++ b/docs/configguide/pharosconfig.rst
@@ -8,14 +8,15 @@
Pharos Configuration
********************
-OPNFV development, test and production activities rely on Pharos resources and support from the Pharos community. Lab
-owners and Pharos project committers/contributors will evolve the vision for Pharos as well as expand lab capabilities
-that are needed to help OPNFV be highly successful.
+OPNFV development, test and production activities rely on Pharos resources and support from the
+Pharos community. Lab owners and Pharos project committers/contributors will evolve the vision for
+Pharos as well as expand lab capabilities that are needed to help OPNFV be highly successful.
-Pharos configuration documents provide information on how to setup hardware and networks in a Pharos compliant lab. Jira
-is used to track Pharos activities including lab operations. PODs are connected to Jenkins and generally available 24/7
-other than scheduled maintenance and troubleshooting. Lab resources are declared as either for *Development (bare-metal
-or virtual)*, *Production latest (bare-metal)* or *Production stable (bare-metal)*
+Pharos configuration documents provide information on how to setup hardware and networks in a Pharos
+compliant lab. Jira is used to track Pharos activities including lab operations. PODs are connected
+to Jenkins and generally available 24/7 other than scheduled maintenance and troubleshooting. Lab
+resources are declared as either for *Development (bare-metal or virtual)*, *Production latest
+(bare-metal)* or *Production stable (bare-metal)*
.. toctree::