From 9fa0278a6646da9a79a3384c1abf920ece189430 Mon Sep 17 00:00:00 2001 From: ShubhamRathi Date: Sat, 21 Jan 2017 23:01:46 +0530 Subject: Adding all templates under templates/ Templates for docs contribution have been added under templates/ .Templates for release/ have been added only. Most of these templates have been made by resuing the structure and content of previous releases to reduce rework on part of project teams. Change-Id: I13f9b7fbb372bd712ee64aed775a2cede771f429 Signed-off-by: ShubhamRathi --- .../release/configguide/featureconfig.rst | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 docs/templates/release/configguide/featureconfig.rst (limited to 'docs/templates/release/configguide/featureconfig.rst') diff --git a/docs/templates/release/configguide/featureconfig.rst b/docs/templates/release/configguide/featureconfig.rst new file mode 100644 index 000000000..8c063f06d --- /dev/null +++ b/docs/templates/release/configguide/featureconfig.rst @@ -0,0 +1,32 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + +======================== + 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. + +.. contents:: + :depth: 3 + :local: + +Pre-configuration activities +---------------------------- +Describe specific pre-configuration activities. This should include ensuring the +right components are installed by the installation tools as required for your +feature to function. Refer to the previous installer configuration chapters, +installations guide and release notes + +Hardware configuration +---------------------- +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...) -- cgit 1.2.3-korg