From b127369752dd4f6a1b038c14c45f90df54a505fd Mon Sep 17 00:00:00 2001 From: agardner Date: Thu, 27 Apr 2017 11:46:29 +0200 Subject: Adding all releng octopus and pharos docs. Please argue and remove as needed in the review. Change-Id: Ia376d8be14c56f6a2fae3cd753ea53b869e5f784 Signed-off-by: agardner --- docs/scenario-lifecycle/current-status.rst | 50 ++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 docs/scenario-lifecycle/current-status.rst (limited to 'docs/scenario-lifecycle/current-status.rst') 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. + + + + + + -- cgit 1.2.3-korg