Derived from converging patches 16165, 16047 & 15937 into one patch.
Change-Id: I3c544ba2fa30856a50274bad9342a06eebc39d58
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
Co-Authored-By: Sofia Wallin <sofia.wallin@ericsson.com>
echo "Creating document links"
echo
targets="
-configguide/installer-config.rst
-configguide/feature-config.rst
-userguide/test-usage.rst
-userguide/feature-usage.rst
+configurationguide/configuration.options.render.rst
+configurationguide/installation.procedure.render.rst
+userguide/feature.userguide.render.rst
+testframework/framework.installation.procedure.render.rst
+testframework/framework.userguide.render.rst
"
-# configguide/post-install.rst
+# configurationguide/post-install.rst
for guide in $targets
do
mainfile="$WORKSPACE/docs/$guide"
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) Christopher Price (Ericsson AB)
-
-=====================
-Feature Configuration
-=====================
-
-The following sections describe the configuration options for specific platform features provided in Brahmaputra.
-Further details for each feature are captured in the referred project documentation.
-
-.. <project>/docs/configguide/featureconfig.rst files will be imported below by the build script.
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) Christopher Price (Ericsson AB)
-
-=======================
-Installer Configuration
-=======================
-
-Installing the OPNFV platform requires either a physical environment as defined in the
-Pharos lab specification, or a virtual infrastructure. When configuring a physical infrastructure
-it is strongly advised to follow the Pharos configuration material.
-
-.. toctree::
-
- pharos-config
-
-
-The following sections describe the per installer configuration options.
-Further details for each installer are captured in the referred project documentation.
-
-.. <project>/docs/configguide/installerconfig.rst files will be imported below by the build script.
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) <optionally add copywriters name>
-
-<Project> configuration
-=======================
-Add a brief introduction to configure OPNFV with this specific installer
-
-Pre-configuration activities
------------------------------
-Describe specific pre-configuration activities. Refer to Installations guide and release notes
-
-Hardware configuration
------------------------
-Describe the hardware configuration needed for this specific installer
-
-Jumphost configuration
------------------------
-Describe intial Jumphost configuration (network and software)needed in order to deploy the installer
-
-Platform components configuration
----------------------------------
-Describe the configuration of each component in the installer
-
-
-
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/pharos/configguide/configguide.rst
-.. include:: ../projects/pharos/configguide/jumpserverinstall.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) Christopher Price (Ericsson AB)
-
-=============================
-Post Configuration Activities
-=============================
-
-Once you have deployed and configured your scenario and features you should validate the
-state of the system using the following guides.
-
-Scenario validation activities
-==============================
-
-The following guides provide information on how to validate the installation of you scenario
-based on the tools and test suites available for the installation tool you have selected:
-
-.. toctree::
-
- postinstall-fuel
-
-.. toctree::
-
- postinstall-joid
-
-Feature validation activities
-=============================
-
-The following sections provide information on how to validate the features you have
-installed in your scenario:
-
-.. toctree::
-
- postinstall-copper
-
-.. toctree::
-
- postinstall-ipv6
-
-
-Additional testing and validation activities
-============================================
-
-Many of our testing tools can be manually installed to facilitate targeted testing
-of features and capabilities of your scenario. The following guides provide instruction on
-setting up these testing suites:
-
-.. toctree::
-
- postinstall-functest
-
-.. toctree::
-
- postinstall-vswitchperf
-
-.. toctree::
-
- postinstall-yardstick
-
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/copper/configguide/postinstall.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/fuel/configguide/postinstall.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/functest/userguide/introduction.rst
-.. include:: ../projects/functest/configguide/configguide.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/ipv6/configguide/postinstall.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/joid/configguide/postinstall.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/vswitchperf/configguide/installation.rst
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-.. include:: ../projects/yardstick/userguide/comp-intro.rst
-.. include:: ../projects/yardstick/userguide/03-installation.rst
-
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) <optionally add copywriters name>
-
-<Project> 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.
-
-<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.
-
-Platform components validation
----------------------------------
-Describe any component specific validation procedures necessary for your
-deployment tool in this section.
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) Christopher Price (Ericsson AB)
-
-.. This file will have links to other projects docs in composite doc build.
-
Abstract
========
-This document provides guidance and instructions for the configuration
-of the Brahmaputra release of OPNFV.
+This document provides guidance for the configurations available in the
+Colorado release of OPNFV.
The release includes four installer tools leveraging different
technologies; Apex, Compass4nfv, Fuel and JOID, which deploy
components of the platform.
-This document provides a guide for the selection of tools and
+This document also includes the selection of tools and
components including guidelines for how to deploy and configure
the platform to an operational state.
+
include different source components or configurations.
OPNFV Scenarios
-================
+===============
Each OPNFV scenario provides unique features and capabilities, it is important to understand
your target platform capabilities before installing and configuring your target scenario.
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
-.. (c) <optionally add copywriters name>
+.. (c) Sofia Wallin (Ericsson AB)
+
+Configuration of <feature>
+==========================
-<Project> configuration
-=======================
Add a brief introduction to configure OPNFV with this specific feature including
dependancies on platform components, this description should be at a level that
will apply to any installer providing the pre-requisite components.
----------------------
Describe the hardware configuration needed for this specific feature
-Feature configuration
----------------------
-Describe the procedures to configure your feature on the platform in order
-that it is ready to use according to the feature instructions in the platform
-user guide. Where applicable you should add content in the postinstall.rst
-to validate the feature is configured for use.
-(checking components are installed correctly etc...)
:maxdepth: 2
./abstract
- ./configoptions
- ./installer-config
- ./feature-config
- ./post-install
+ ./configuration.options.render
+ ./feature.configuration.description
+ ./installer.procedure.render
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) Sofia Wallin (Ericsson AB)
+
+=====================
+Installation of <xxx>
+=====================
+
+Introduction
+------------
+Describe the capabilities and associated features of each installer.
+
+Pre-installation activities
+---------------------------
+List the acitvites needed for pre-installation.
+
+Hardware requirement
+--------------------
+List the HW requirement for each installer
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) Sofia Wallin Ericsson AB
+
+**********************
+Installation procedure
+**********************
+
+.. toctree::
+ :numbered:
+ :maxdepth: 2
+
+ abstract.rst
+ scenario.installation.instruction
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+===================================
+<scenario> installation instruction
+===================================
+
+Preparing the installation
+--------------------------
+.. List the activities needed prior to installation and dependent feature configurations that
+.. need to be is to be configured during this process.
+
+HW requirements
+---------------
+.. A generic Pharos lab preparation instruction will be provided, this section should describe
+.. scenario has any specific hardware or hardware configuration needs.
+
+Installation instruction
+------------------------
+.. List of steps needed to install each verified installer.
+
+Post-installation activities
+----------------------------
+.. List the activities needed post installation.
+
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) <optionally add copywriters name>
-
-=======================
-<project> Release Notes
-=======================
-
-.. toctree::
- :numbered:
- :maxdepth: 4
-
- release-notes.rst
-
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+<test framework> preparation and installation
+=============================================
+
+.. Explain how to prepare for and install the test framework.
+.. Need to identify the target structure of this document with the testing WG
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+<test framework> userguide and reporting document
+=================================================
+
+.. Explain how to use the test framework and read reports/results.
+.. Need to identify the target structure of this document with the testing WG
+
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) Christopher Price (Ericsson AB)
+
+*****************************
+OPNFV Test Framework document
+*****************************
+
+.. toctree::
+ :maxdepth: 2
+
+ ./abstract
+ ./opnfv.testframework.overview
+ ./framework.installation.procedure.render
+ ./framework.userguide.render
+
OPNFV platform for the purpose of testing components and VNFs in the context of a
Brahmaputra deployment.
-.. <project>/docs/userguide/testusage.rst files will be imported below by the build script.
+Needs to be completed according to the testing WG needs.
+++ /dev/null
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) <optionally add copywriters name>
-
-<Testing> capabilities and usage
-================================
-Describe the specific capabilities and usage for <XYZ> testing.
-
-<Testing usage guidelines and example>
---------------------------------------
-Describe with examples how to use specfic test frameworks.
-
Code Review / opnfvdocs.git / commitdiff