diff options
| author |   joehuang <joehuang@huawei.com> | 2016-08-30 03:01:09 -0400 |
|---|---|---|
| committer | joehuang <joehuang@huawei.com> | 2016-08-30 03:10:13 -0400 |
| commit | 4809d2adf23b6acaf74b448109814287e7cd0b17 (patch) | |
| tree | 1d92c80bed7df89538f145414117dab57f1c2b30 /docs/configurationguide/configuration.options.render.rst | |
| parent | 6e8831dace9b8a773b21c643b22481fddd37409e (diff) | |
Update docs structure according to document structure guide
According to the document structure, feature projects are
expected to store their documentation as following,
<repo>/docs/userguide/feature.usage.rst
<repo>/docs/userguide/index.rst
<repo>/docs/installationprocedure/feature.configuration.rst
<repo>/docs/installationprocedure/index.rst
And as per previous release,
<repo>/docs/releasenotes/release.notes.rst
<repo>/docs/releasenotes/index.rst
In multisite repo that we have both an installation instruction
and a config guide. Need to combine these and then store them in
<repo>/docs/installationprocedure/feature.configuration.rst
And add release notes.
Change-Id: I9ba0663640063488e232b1342174b10266ac77fc
Signed-off-by: joehuang <joehuang@huawei.com>
Diffstat (limited to 'docs/configurationguide/configuration.options.render.rst')
| -rw-r--r-- | docs/configurationguide/configuration.options.render.rst | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/docs/configurationguide/configuration.options.render.rst b/docs/configurationguide/configuration.options.render.rst deleted file mode 100644 index f1dc11a..0000000 --- a/docs/configurationguide/configuration.options.render.rst +++ /dev/null @@ -1,27 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) Christopher Price (Ericsson AB) - -===================== -Configuration Options -===================== - -OPNFV provides a variety of virtual infrastructure deployments called scenarios designed to -host Virtualised Network Functions(VNFs). Each scenario provide specific capabilities and/or -components aimed to solve specific problems for the deployment of VNF's. A scenario may include -components such as OpenStack, OpenDaylight, OVS, KVM etc. where each scenario will include -different source components or configurations. - -OPNFV Scenarios -=============== - -Each OPNFV scenario provides unique features and capabilities, it is important to understand -your target platform capabilities before installing and configuring your target scenario. -This configuration guide outlines how to install and configure components in order to enable -the features you require. - -.. include:: ../scenario/scenariomatrix.rst - -This document will describe how to install and configure your target OPNFV scenarios. -Remember to check the associated validation procedures section following your installation for -details of the use cases and tests that have been run. |