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/lab-description/templates.rst | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) (limited to 'docs/lab-description/templates.rst') diff --git a/docs/lab-description/templates.rst b/docs/lab-description/templates.rst index f845457d..c207cfa7 100644 --- a/docs/lab-description/templates.rst +++ b/docs/lab-description/templates.rst @@ -8,15 +8,16 @@ Pharos Templates and Configuration Files **************************************** -Lab and POD templates are provided to help lab owners document capabilities, configurations and network topologies. -Compute, network and storage specifications with network topology details are required to help developers use lab -resources efficiently while minimizing support needs. This also greatly assists with troubleshhoting. It is the -responsibility of the lab owner to keep individual lab documents updated and determine appropriate level of detail -that is exposed publically through the Wiki or maintained in a secure Pharos repo with controlled access. +Lab and POD templates are provided to help lab owners document capabilities, configurations and +network topologies. Compute, network and storage specifications with network topology details are +required to help developers use lab resources efficiently while minimizing support needs. This also +greatly assists with troubleshhoting. It is the responsibility of the lab owner to keep individual +lab documents updated and determine appropriate level of detail that is exposed publically through +the Wiki or maintained in a secure Pharos repo with controlled access. -While human readable configuration files are needed, the goal is for full automation of deployments. This requires -a common machine readable format for POD configurations as input to every installer. This is the "POD inventory" -common format file. +While human readable configuration files are needed, the goal is for full automation of deployments. +This requires a common machine readable format for POD configurations as input to every installer. +This is the "POD inventory" common format file. .. toctree:: -- cgit 1.2.3-korg