From 12ed03757850a229241c0ec0a07467b064459740 Mon Sep 17 00:00:00 2001 From: ChristopherPrice Date: Mon, 22 Feb 2016 21:26:30 +0100 Subject: Adding aligned structure and segmenting the configguide. Also set heading levels for readability and added missing licence headers. Copied the header where I copied content, so please be mindful and inform me if you disagree. Removal parts of userguide duplicated with configguide. Take the others into faq.rst Removal duplicated references in installerconfig. Removal redundant png files. Release notes update for Brahmaputra release. Change-Id: I6e1a101107752f4bc7b6e3bbaea0738690d07af8 Signed-off-by: ChristopherPrice Signed-off-by: Justin-chi (cherry picked from commit 3eab3cd722870e6c02ee1337d3536dc68f89b13e) --- docs/configguide/postinstall.rst | 50 ++++++++++++++++++++++------------------ 1 file changed, 28 insertions(+), 22 deletions(-) (limited to 'docs/configguide/postinstall.rst') diff --git a/docs/configguide/postinstall.rst b/docs/configguide/postinstall.rst index 1702cea5..050f77c3 100644 --- a/docs/configguide/postinstall.rst +++ b/docs/configguide/postinstall.rst @@ -1,26 +1,32 @@ - post installation procedures -====================================== -Add a brief introduction to the methods of validating the installation -according to this specific installer or feature. +.. This work is licensed under a Creative Commons Attribution 4.0 International Licence. +.. http://creativecommons.org/licenses/by/4.0 -Automated post installation activities --------------------------------------- -Describe specific post installation activities performed by the OPNFV -deployment pipeline including testing activities and reports. Refer to -the relevant testing guides, results, and release notes. +.. commented as there is no content for this file at this time. -note: this section should be singular and derived from the test projects -once we have one test suite to run for all deploy tools. This is not the -case yet so each deploy tool will need to provide (hopefully very simillar) -documentation of this. +.. post installation procedures +.. ====================================== +.. Add a brief introduction to the methods of validating the installation +.. according to this specific installer or feature. - post configuration procedures --------------------------------------- -Describe any deploy tool or feature specific scripts, tests or procedures -that should be carried out on the deployment post install and configuration -in this section. +.. Automated post installation activities +.. -------------------------------------- +.. Describe specific post installation activities performed by the OPNFV +.. deployment pipeline including testing activities and reports. Refer to +.. the relevant testing guides, results, and release notes. + +.. note: this section should be singular and derived from the test projects +.. once we have one test suite to run for all deploy tools. This is not the +.. case yet so each deploy tool will need to provide (hopefully very simillar) +.. documentation of this. + +.. post configuration procedures +.. -------------------------------------- +.. Describe any deploy tool or feature specific scripts, tests or procedures +.. that should be carried out on the deployment post install and configuration +.. in this section. + +.. Platform components validation +.. --------------------------------- +.. Describe any component specific validation procedures necessary for your +.. deployment tool in this section. -Platform components validation ---------------------------------- -Describe any component specific validation procedures necessary for your -deployment tool in this section. -- cgit 1.2.3-korg