Documentation according to new template provided by the Docs teambrahmaputra.1.rc1

- 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 <jonas.bjurel@ericsson.com>
(cherry picked from commit ef0b33dcc34ee38d090487eabba122ae018980a0)

1 files changed, 10 insertions, 20 deletions

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 <http://creativecommons.org/licenses/by/4.0/>.
 
-<Project> 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.
-
-<Project> 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: <TODO>
 
 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.