Scenario Lifecycle Document - First version with content

1.step(patchset 1&2): provide index.rst and overview
2.step(patchset 3): provide sceleton
3.step(patchset 4): fix comments and provide first content
patchset 5: fix comments in 8 files, one file deleted.
patchset 6: fix more comments
patchset 7: fix more comments adding some editors notes

Jira OCTO-162
Change-Id: I8928953da29aef2bddeb42510fb5983eee9ea30f
Signed-off-by: ulik <ulrich.kleber@huawei.com>

1 files changed, 50 insertions, 0 deletions

diff --git a/docs/scenario-lifecycle/current-status.rst b/docs/scenario-lifecycle/current-status.rst
new file mode 100644
index 0000000..08a3776
--- /dev/null
+++ b/docs/scenario-lifecycle/current-status.rst
@@ -0,0 +1,50 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) 2017 OPNFV Ulrich Kleber (Huawei)
+
+
+Current Status
+---------------
+
+tdb: this chapter will summarize the scenario analysis.
+
+Arno
+^^^^^^^^
+
+In Arno release, the scenario concept was not created yet.
+Looking back, we can say we had one scenario with OpenStack, ODL and KVM,
+that could be deployed in two ways, by the two installers available in Arno.
+
+Brahmaputra
+^^^^^^^^^^^^^^^^
+
+tbd
+
+Colorado
+^^^^^^^^^^^^
+
+tbd
+
+Danube
+^^^^^^^^^^
+
+tbd: Analysis of the 58 scenarios
+The analysis can be found in the slides at
+https://wiki.opnfv.org/display/INF/Scenario+Consolidation
+and will be explain with some text here.
+The text will also use the diagrams from the slides, e.g.
+show a scenario tree:
+
+.. figure:: scenario-tree.png
+
+and an idea about possible generic scenarios:
+
+.. figure:: scenario-tree+idea.png
+
+as well as possible ways to reach this.
+
+
+
+
+
+