summaryrefslogtreecommitdiffstats
path: root/docs/templates/release/scenarios/scenario.name/scenario.description.rst
diff options
context:
space:
mode:
authorSofia Wallin <sofia.wallin@ericsson.com>2017-02-15 13:25:03 +0100
committerAric Gardner <agardner@linuxfoundation.org>2017-02-20 19:07:51 +0000
commit5b6b3ed958264ecddc586624ba23bfc2d5c88a4c (patch)
treec7c931b741afe52a6ea8cd78dedd414c5961475a /docs/templates/release/scenarios/scenario.name/scenario.description.rst
parent557f19ce936999835754e0fa917f635a4bf54e1c (diff)
Adjusted titles
Updated according to comments and added the SFC feature configuration as template under release/configguide. Adjusted all titles so they are handled through the index file. Change-Id: Icb0339fb19394940dc969725ddfe0420cb547955 Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
Diffstat (limited to 'docs/templates/release/scenarios/scenario.name/scenario.description.rst')
-rw-r--r--docs/templates/release/scenarios/scenario.name/scenario.description.rst15
1 files changed, 6 insertions, 9 deletions
diff --git a/docs/templates/release/scenarios/scenario.name/scenario.description.rst b/docs/templates/release/scenarios/scenario.name/scenario.description.rst
index 9c45b7da4..8c2cbabd1 100644
--- a/docs/templates/release/scenarios/scenario.name/scenario.description.rst
+++ b/docs/templates/release/scenarios/scenario.name/scenario.description.rst
@@ -2,40 +2,37 @@
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-=========================
-OPNFV <Scenario Name>
-=========================
-
This document provides scenario level details for <RELEASE> of <COMPONENT>.
.. contents::
:depth: 3
:local:
+============
Introduction
----------------
+============
.. In this section explain the purpose of the scenario and the types of capabilities provided
Scenario components and composition
--------------------------------------
+===================================
.. In this section describe the unique components that make up the scenario,
.. what each component provides and why it has been included in order
.. to communicate to the user the capabilities available in this scenario.
Scenario usage overview
-----------------------------
+=======================
.. Provide a brief overview on how to use the scenario and the features available to the
.. user. This should be an "introduction" to the userguide document, and explicitly link to it,
.. where the specifics of the features are covered including examples and API's
Limitations, Issues and Workarounds
----------------------------------------
+===================================
.. Explain scenario limitations here, this should be at a design level rather than discussing
.. faults or bugs. If the system design only provide some expected functionality then provide
.. some insight at this point.
References
------------------
+==========
For more information on the OPNFV Danube release, please visit
http://www.opnfv.org/danube