From 988cf64e3a7601396e40b08a1aae07a524bf8c74 Mon Sep 17 00:00:00 2001 From: 10013968 Date: Mon, 18 Jul 2016 23:51:00 +0800 Subject: 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 --- docs/information/pharos.rst | 46 +++++++++++++++++++++++---------------------- 1 file changed, 24 insertions(+), 22 deletions(-) (limited to 'docs/information/pharos.rst') diff --git a/docs/information/pharos.rst b/docs/information/pharos.rst index 87739dd0..24e46d97 100644 --- a/docs/information/pharos.rst +++ b/docs/information/pharos.rst @@ -13,24 +13,25 @@ Pharos Project Information Introduction ------------ -The `Pharos Project `_ deals with developing an OPNFV lab infrastructure -that is geographically and technically diverse. -This will greatly assist in developing a highly robust and stable OPNFV platform. Community labs are hosted by -individual companies and there is also an OPNFV lab hosted by the Linux Foundation that has controlled access for key -development and production activities. The **Pharos Specification** defines a "compliant" deployment and test -environment. Pharos is 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 goal is to provide easy visibility of all lab capabilities -and their usage at all-times. - -A requirement of Pharos labs is to provide *bare-metal* for development, deployment and testing. This is resource -intensive from a hardware and support perspective while providing remote access can also be very challenging due to -corporate IT policies. Achieving a consistent *look and feel* of a federated lab infrastructure continues to be an -objective. Virtual environments are also useful and provided by some labs. Jira is currently used for tracking lab -operational issues as well as for Pharos project activities. - -Future lab capabilities are currently focussed on 1) Deployment automation 2) Dashboards (for capability and usage) -3) *Virtual Labs* for developer on-boarding. +The `Pharos Project `_ deals with developing an OPNFV lab +infrastructure that is geographically and technically diverse. This will greatly assist in +developing a highly robust and stable OPNFV platform. Community labs are hosted by individual +companies and there is also an OPNFV lab hosted by the Linux Foundation that has controlled access +for key development and production activities. The **Pharos Specification** defines a "compliant" +deployment and test environment. Pharos is 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 goal is to provide easy visibility of all lab capabilities and their usage at all-times. + +A requirement of Pharos labs is to provide *bare-metal* for development, deployment and testing. +This is resource intensive from a hardware and support perspective while providing remote access can +also be very challenging due to corporate IT policies. Achieving a consistent *look and feel* of a +federated lab infrastructure continues to be an objective. Virtual environments are also useful and +provided by some labs. Jira is currently used for tracking lab operational issues as well as for +Pharos project activities. + +Future lab capabilities are currently focussed on 1) Deployment automation 2) Dashboards (for +capability and usage) 3) *Virtual Labs* for developer on-boarding. * `Pharos page `_ * `Pharos project Wiki `_ @@ -62,8 +63,8 @@ Pharos Lab Process Current Labs ------------ -An interactive map of OPNFV lab locations, lab owners and other lab information is maintained on the `Pharos Wiki -`_ +An interactive map of OPNFV lab locations, lab owners and other lab information is maintained on the +`Pharos Wiki `_ +----+---------------+----------------------------------------------------------------------------+-------------------+ | # | **Hosted by** | **Home page** | **Location** | @@ -116,5 +117,6 @@ Pharos project Key Facts **Key Project Facts are maintained in the Pharos INFO file in the project repo** - * Can be viewed on the project Wiki `INFO `_ - * Project key facts in repo: pharos/INFO + * Can be viewed on the project Wiki + `INFO `_ + * Project key facts in repo: pharos/INFO -- cgit 1.2.3-korg