From de86b2f52503b94bd43447f5af4d12f281da5382 Mon Sep 17 00:00:00 2001 From: ChristopherPrice Date: Thu, 25 Feb 2016 09:51:47 +0100 Subject: Final editorials on release morning. Comment here! Change-Id: Ifbd43732a5282e63d9699dfc08b8e5b072c3b040 Signed-off-by: ChristopherPrice (cherry picked from commit 9a79923a96c78bdf809fae01d99320d391e64b75) --- docs/scenario/featurematrix.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs/scenario/featurematrix.rst') diff --git a/docs/scenario/featurematrix.rst b/docs/scenario/featurematrix.rst index ce8c24b6c..cc9c4d347 100644 --- a/docs/scenario/featurematrix.rst +++ b/docs/scenario/featurematrix.rst @@ -11,6 +11,16 @@ 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 `_ +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 +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. + Scenario Naming ^^^^^^^^^^^^^^^ -- cgit 1.2.3-korg