summaryrefslogtreecommitdiffstats
path: root/docs/release/configguide/featureconfig.rst
diff options
context:
space:
mode:
authorDeepak S <deepak.s@linux.intel.com>2017-07-17 09:53:00 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-07-17 09:53:00 +0000
commit6e83256f8180f44b9e299420f16f2a9f931887ae (patch)
treef9ce530af44f695dfec006a63033beca4b45abf0 /docs/release/configguide/featureconfig.rst
parenta0eb3c45ca8a89220caaefa43665a7a1eb6c1933 (diff)
parent272dd80f707564a7b810f46aef31b81994a0e1b4 (diff)
Merge "Documentation Compliance for Euphrates - Adding template"
Diffstat (limited to 'docs/release/configguide/featureconfig.rst')
-rw-r--r--docs/release/configguide/featureconfig.rst35
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/release/configguide/featureconfig.rst b/docs/release/configguide/featureconfig.rst
new file mode 100644
index 00000000..45f9a5fc
--- /dev/null
+++ b/docs/release/configguide/featureconfig.rst
@@ -0,0 +1,35 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) OPNFV, Intel Corporation and others.
+
+========
+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...)