From b2231a970fb73f4f5df72b59ed9d58a039644ac3 Mon Sep 17 00:00:00 2001 From: Trevor Cooper Date: Mon, 22 Feb 2016 15:12:18 -0800 Subject: Various Document edits to fix formatting issues and add contents Change-Id: I522bf15377fb00cb22e46050ee966884896afeac Signed-off-by: Trevor Cooper --- docs/configguide/configguide.rst | 61 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 55 insertions(+), 6 deletions(-) (limited to 'docs/configguide/configguide.rst') diff --git a/docs/configguide/configguide.rst b/docs/configguide/configguide.rst index f239c11c..d4e4abb4 100644 --- a/docs/configguide/configguide.rst +++ b/docs/configguide/configguide.rst @@ -3,13 +3,62 @@ .. (c) 2016 OPNFV. -===================================== -Pharos Lab Configuration requirements -===================================== +============================== +Pharos Lab Configuration Guide +============================== + +This section provides an overview for Pharos lab setup and operation. The tasks and expectations for configuring a +Pharos compliant lab are explained along with reference to relavant Pharos documents. + +Overview of Community Lab Expectations +-------------------------------------- + +* Designated lab owners and project committers participate in the Pharos community (discussions, meetings, ...) +* Jira is used to track activities including lab operations (requests and support) +* Production resources are connected to Jenkins and available 24/7 (other than scheduled maintenance and troubleshooting) +* Lab resources are declared as either: + + * Development (bare-metal or virtual) + * Production - latest (bare-metal) + * Production - stable (bare-metal) + +On-boarding Steps +----------------- + +* Provide Pharos community with details of intended setup, including ... + + * Resources being offered + * Lab owner name / contacts + * Timelines for availablity for development and use in upcomming releases + +* Update Pharos Wiki + * Lab with location, owner + +* Create and fill *New Lab* Wiki pages + + * Access policies + * Usage guidelines for developers + * Fill Lab and POD templates + * POD allocations (updated as PODs are assigned or revoked) + * Lab documentation with security sensitive infomation can be stored in the Pharos secure repo (will be available soon) + +* Network Information +* Update Pharos infomation file i.e. pharos.rst +* labupdateguide.rst ... how to update Pharos Wiki start page; how to update map info +* Connect to CI + +Jump Server Install +------------------- + +* jumpserverinstall.rst + +Lab Documentation +----------------- + +* Pharos Wiki page +* Map Info + -.. Add an overview for the Pharos configuration guide here. This should be informative regarding the tasks -.. and expectations when configuring a lab to be pharos compliant and refer to the relevant pharos docs published -from the project. Revision: _sha1_ -- cgit 1.2.3-korg