diff options
| author |   ChristopherPrice <christopher.price@ericsson.com> | 2016-02-25 14:25:12 +0100 |
|---|---|---|
| committer | Christopher Price <christopher.price@ericsson.com> | 2016-02-25 13:54:14 +0000 |
| commit | db84d79902605ba2deaa917606b139fc9228d38b (patch) | |
| tree | 42b2d3c71846c8de5cb4a1df8800a9f507f38e48 /docs/scenario/featurematrix.rst | |
| parent | de86b2f52503b94bd43447f5af4d12f281da5382 (diff) | |
Final edits.brahmaputra.1.0
Change-Id: I3125c7d63dcbd46bc5595269fb15ed3d4454f8b5
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
(cherry picked from commit 877535dd9a0b43dea345b44e15796177d49879ba)
Diffstat (limited to 'docs/scenario/featurematrix.rst')
| -rw-r--r-- | docs/scenario/featurematrix.rst | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/scenario/featurematrix.rst b/docs/scenario/featurematrix.rst index cc9c4d347..2d00a4097 100644 --- a/docs/scenario/featurematrix.rst +++ b/docs/scenario/featurematrix.rst @@ -12,14 +12,14 @@ in the Brahmaputra release of OPNFV. :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 +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 has often consisted of the development of specific +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 is deployed, providing the -capabilities necessary to run the feature. +features only being supported on the platform when a specific scenario, providing the +capabilities necessary to run the feature, is deployed. Scenario Naming ^^^^^^^^^^^^^^^ @@ -33,6 +33,7 @@ For example: *os-nosdn-kvm-noha* provides an OpenStack based deployment using ne 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 advanced fault management features which is not apparent -in the scenario name. The following section describes the features available in each 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. |