summaryrefslogtreecommitdiffstats
path: root/docs/configguide/featureconfig.rst
diff options
context:
space:
mode:
authorBin Hu <bh526r@att.com>2016-01-13 18:56:20 +0000
committerGerrit Code Review <gerrit@172.30.200.206>2016-01-13 18:56:20 +0000
commitcdb9153fd229eab3ff3ca94e6902f04fd9bf0398 (patch)
tree4ee7d6d729bfaf20d574e0b6b7f6d7fe5547d4fc /docs/configguide/featureconfig.rst
parent28216228d58ea25520d98234567fe6cb87bd0644 (diff)
parentc7f20d6f115677bd3965d484667eb654be5104c9 (diff)
Merge "Added templates for feature configuration description/reference"
Diffstat (limited to 'docs/configguide/featureconfig.rst')
-rw-r--r--docs/configguide/featureconfig.rst24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/configguide/featureconfig.rst b/docs/configguide/featureconfig.rst
new file mode 100644
index 0000000..9189902
--- /dev/null
+++ b/docs/configguide/featureconfig.rst
@@ -0,0 +1,24 @@
+<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.
+
+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...)