summaryrefslogtreecommitdiffstats
path: root/docs/release/scenarios/scenario.name
diff options
context:
space:
mode:
authorjulien zhang <zhang.jun3g@zte.com.cn>2017-02-28 07:24:24 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-02-28 07:24:24 +0000
commit9a2b86ff190a16822ec3f68b2c1d070d54a47da9 (patch)
tree7315aac40f9aed6c91f83429791f591b74e79cb3 /docs/release/scenarios/scenario.name
parent69e33063b3703ae4529b556b63b3c4cc239c3d9a (diff)
parente243c1f9c40c5acee4fb89d99fae05f7a46768be (diff)
Merge "Release D doc update"
Diffstat (limited to 'docs/release/scenarios/scenario.name')
-rw-r--r--docs/release/scenarios/scenario.name/index.rst16
-rw-r--r--docs/release/scenarios/scenario.name/scenario.description.rst39
2 files changed, 55 insertions, 0 deletions
diff --git a/docs/release/scenarios/scenario.name/index.rst b/docs/release/scenarios/scenario.name/index.rst
new file mode 100644
index 0000000..a857e62
--- /dev/null
+++ b/docs/release/scenarios/scenario.name/index.rst
@@ -0,0 +1,16 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+
+****************************************
+<scenario name> overview and description
+****************************************
+.. This document will be used to provide a description of the scenario for an end user.
+.. You should explain the purpose of the scenario, the types of capabilities provided and
+.. the unique components that make up the scenario including how they are used.
+
+.. toctree::
+ :maxdepth: 1
+
+ scenario.description
+
diff --git a/docs/release/scenarios/scenario.name/scenario.description.rst b/docs/release/scenarios/scenario.name/scenario.description.rst
new file mode 100644
index 0000000..8c2cbab
--- /dev/null
+++ b/docs/release/scenarios/scenario.name/scenario.description.rst
@@ -0,0 +1,39 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters 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
+