aboutsummaryrefslogtreecommitdiffstats
path: root/docs/templates/release/configguide/featureconfig.rst
diff options
context:
space:
mode:
authorStuart Mackie <wsmackie@juniper.net>2017-08-29 05:21:36 -0700
committerStuart Mackie <wsmackie@juniper.net>2017-08-29 05:21:36 -0700
commitfce102283bab73ed08c292fce03e39c52f4a1fe2 (patch)
tree299e9f8e5daca49f74f207cbe6699295b9115876 /docs/templates/release/configguide/featureconfig.rst
parent711967ae9639095ce41500bb0e6f80c8b80fab95 (diff)
Added doc directories
Change-Id: I671d7c3ad4f4e5e476c98f53780d867dc94b3089 Signed-off-by: Stuart Mackie <wsmackie@juniper.net>
Diffstat (limited to 'docs/templates/release/configguide/featureconfig.rst')
-rw-r--r--docs/templates/release/configguide/featureconfig.rst34
1 files changed, 34 insertions, 0 deletions
diff --git a/docs/templates/release/configguide/featureconfig.rst b/docs/templates/release/configguide/featureconfig.rst
new file mode 100644
index 0000000..287715d
--- /dev/null
+++ b/docs/templates/release/configguide/featureconfig.rst
@@ -0,0 +1,34 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+========
+Abstract
+========
+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...)