From 5f2c7f4b2521108ed11e2e9ef6cd1b30dcea81d7 Mon Sep 17 00:00:00 2001 From: Jonas Bjurel Date: Wed, 13 Jan 2016 20:22:14 +0100 Subject: Documentation according to new template provided by the Docs team - The Config guide is not an atonomos document, but will be scraped into a bigger context. - The post install guide is not an atonomos document, but will be scraped into a bigger context. - Installation instructions is an atonomos document describing details on how to install Fuel@OPNFV - Build instructions is an atonomos document describing how to build Fuel@OPNFV - Release notes - Agreed with the community that binary image files shall be in the repo, as much as I hate it. DO NOT MERGE JIRA: FUEL-38 Change-Id: I88a93e20ef2c67a2c973147a7a1e332e3da55674 Signed-off-by: Jonas Bjurel (cherry picked from commit ef0b33dcc34ee38d090487eabba122ae018980a0) --- docs/configguide/postinstall.rst | 30 ++++++++++-------------------- 1 file changed, 10 insertions(+), 20 deletions(-) (limited to 'docs/configguide/postinstall.rst') diff --git a/docs/configguide/postinstall.rst b/docs/configguide/postinstall.rst index 52e0a5c30..b5d28e992 100644 --- a/docs/configguide/postinstall.rst +++ b/docs/configguide/postinstall.rst @@ -4,29 +4,19 @@ .. You should have received a copy of the license along with this work. .. If not, see . - post installation procedures -====================================== -Add a brief introduction to the methods of validating the installation -according to this specific installer or feature. +Fuel post installation procedures +================================= 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. +Fuel provides a fairly broad coverage of built in automated health checks. +These validate the installation in terms of configuration, services, +networking, storage, policies, etc. +The execution of the full range of health checks takes less than 30 minutes. -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. +For instructions on how to run health-checks, please refer to the installation instructions: Platform components validation ---------------------------------- -Describe any component specific validation procedures necessary for your -deployment tool in this section. +------------------------------ +Consult the feature sections in this document for any post-install +feature specific validation/health-checks. -- cgit 1.2.3-korg