From 6f5cfeb4f0853d156d15f8c541ef6b6fd80dcdfc Mon Sep 17 00:00:00 2001 From: Brady Johnson Date: Thu, 16 Feb 2017 14:59:02 +0100 Subject: Moving installation docs to configguide - After talking to Sofia Wallin, we agreed that this is a better approach for the documentation. Change-Id: Ie3edcb11e4d7823b0d3362395a15bf73aeaaaf4b Signed-off-by: Brady Johnson --- docs/release/configguide/postinstall.rst | 26 -------------------------- 1 file changed, 26 deletions(-) delete mode 100644 docs/release/configguide/postinstall.rst (limited to 'docs/release/configguide/postinstall.rst') diff --git a/docs/release/configguide/postinstall.rst b/docs/release/configguide/postinstall.rst deleted file mode 100644 index 1702cea5..00000000 --- a/docs/release/configguide/postinstall.rst +++ /dev/null @@ -1,26 +0,0 @@ - post installation procedures -====================================== -Add a brief introduction to the methods of validating the installation -according to this specific installer or feature. - -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. -- cgit 1.2.3-korg