summaryrefslogtreecommitdiffstats
path: root/docs/release/configguide/featureconfig.rst
diff options
context:
space:
mode:
authorDeepak S <deepak.s@linux.intel.com>2017-08-18 14:59:46 -0700
committerDeepak S <deepak.s@linux.intel.com>2017-08-20 15:55:06 -0700
commitbeecf87fb9e9b862994e5e3e6db2b1c378c971c1 (patch)
treeb8ce7029f060654c8768ceb8db1d6daae3adc900 /docs/release/configguide/featureconfig.rst
parent5046e1f7b1533506a480ba8d000c78e147d4b8aa (diff)
Remove unwanted files in docs folder
JIRA: SAMPLEVNF-73 Change-Id: Ia147cfef9f7bcacd50477b6ea3c7d0a1c6e93952 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Diffstat (limited to 'docs/release/configguide/featureconfig.rst')
-rw-r--r--docs/release/configguide/featureconfig.rst35
1 files changed, 0 insertions, 35 deletions
diff --git a/docs/release/configguide/featureconfig.rst b/docs/release/configguide/featureconfig.rst
deleted file mode 100644
index 45f9a5fc..00000000
--- a/docs/release/configguide/featureconfig.rst
+++ /dev/null
@@ -1,35 +0,0 @@
-.. 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...)