summaryrefslogtreecommitdiffstats
path: root/docs/scenario/featurematrix.rst
diff options
context:
space:
mode:
authorSofia Wallin <sofia.wallin@ericsson.com>2016-11-23 14:49:15 +0100
committerSofia Wallin <sofia.wallin@ericsson.com>2016-11-24 16:21:30 +0100
commitd438301ca7244e66d5082312e3e84fcfb219f11b (patch)
tree858fc757706d451ac52e17ba75e4c0d7b4a2ef6d /docs/scenario/featurematrix.rst
parent978b48ae0117c80d3dc7cced5e09e08e9efe929b (diff)
Adjusted the docs repo structure for D release work
Change-Id: I9befe06c424c726e17d754bc480413b2430549ba Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
Diffstat (limited to 'docs/scenario/featurematrix.rst')
-rw-r--r--docs/scenario/featurematrix.rst39
1 files changed, 0 insertions, 39 deletions
diff --git a/docs/scenario/featurematrix.rst b/docs/scenario/featurematrix.rst
deleted file mode 100644
index 2d00a4097..000000000
--- a/docs/scenario/featurematrix.rst
+++ /dev/null
@@ -1,39 +0,0 @@
-Each scenario provides a set of platform capabilities and features that it supports. It is
-possible to identify which features are provided by reviewing the scenario name, however
-not all features and capabilities are discernible from the name itself.
-
-Brahmaputra feature support matrix
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The following table provides an overview of the available scenarios and supported features
-in the Brahmaputra release of OPNFV.
-
-.. image:: ../images/brahmaputrafeaturematrix.jpg
- :alt: OPNFV Brahmaputra Feature Matrix
-
-The table above provides an overview of which scenarios will support certain feature capabilities.
-The table does not indicate if the feature or scenario has limitations. Refer to the
-`Configuration Guide <http://artifacts.opnfv.org/opnfvdocs/brahmaputra/docs/configguide/configoptions.html#opnfv-scenarios>`_
-for details on the state of each scenario and further information.
-
-Feature development in the Brahmaputra release often consisted of the development of specific
-requirements and the further integration and validation of those requirements. This results in some
-features only being supported on the platform when a specific scenario, providing the
-capabilities necessary to run the feature, is deployed.
-
-Scenario Naming
-^^^^^^^^^^^^^^^
-
-In OPNFV, scenarios are identified by short scenario names. These names follow a scheme that
-identifies the key components and behaviours of the scenario, the rules for scenario naming are as follows:
-
- os-[controller]-[feature]-[mode]-[option]
-
-For example: *os-nosdn-kvm-noha* provides an OpenStack based deployment using neutron including
-the OPNFV enhanced KVM hypervisor.
-
-The [feature] tag in the scenario name describes the main feature provided by the scenario.
-This scenario may also provide support for features, such as advanced fault management, which are
-not apparent in the scenario name.
-The following section describes the features available in each scenario.
-