doc adjust

change doc structrue

Change-Id: I66bea1f0a922930f0407dc04898fbb410d9305e9
Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
(cherry picked from commit 2943208b162c1fc4fc21cae98ec412b476ce95aa)

5 files changed, 83 insertions, 0 deletions

diff --git a/docs/development/overview/images/key_item.png b/docs/development/overview/images/key_item.png
new file mode 100644
index 0000000..f3e5882
--- /dev/null
+++ b/docs/development/overview/images/key_item.png
diff --git a/docs/development/overview/images/openo_component.png b/docs/development/overview/images/openo_component.png
new file mode 100644
index 0000000..cb73df3
--- /dev/null
+++ b/docs/development/overview/images/openo_component.png
diff --git a/docs/development/overview/images/vIMS_deploy.png b/docs/development/overview/images/vIMS_deploy.png
new file mode 100644
index 0000000..c3f71ad
--- /dev/null
+++ b/docs/development/overview/images/vIMS_deploy.png
diff --git a/docs/development/overview/index.rst b/docs/development/overview/index.rst
new file mode 100644
index 0000000..2566863
--- /dev/null
+++ b/docs/development/overview/index.rst
@@ -0,0 +1,12 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+*************************************
+OPNFV Opera Installation Instructions
+*************************************
+
+.. toctree::
+   :numbered:
+   :maxdepth: 4
+
+   overview.rst
diff --git a/docs/development/overview/overview.rst b/docs/development/overview/overview.rst
new file mode 100644
index 0000000..c3ca7df
--- /dev/null
+++ b/docs/development/overview/overview.rst
@@ -0,0 +1,71 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) by Yingjun Li (HUAWEI) and Harry Huang (HUAWEI)
+
+OPERA Project Overview
+======================
+
+Since OPNFV board expanded its scope to include NFV MANO last year,
+several upstream open source projects have been created to develop
+MANO solutions. Each solution has demonstrated its unique value in
+specific area. Open-Orchestrator (OPEN-O) project is one of such
+communities. Opera seeks to develop requirements for OPEN-O MANO
+support in the OPNFV reference platform, with the plan to eventually
+integrate OPEN-O in OPNFV as a non-exclusive upstream MANO. The
+project will definitely benefit not only OPNFV and Open-O, but can
+be referenced by other MANO integration as well. In particular, this
+project is basically use case driven. Based on that, it will focus
+on the requirement of interfaces/data models for integration among
+various components and OPNFV platform. The requirement is designed
+to support integration among Open-O as NFVO with Juju as VNFM and
+OpenStack as VIM.
+
+Currently OPNFV has already included upstream OpenStack as VIM, and
+Juju and Tacker have been being considered as gVNFM by different OPNFV
+projects. OPEN-O as NFVO part of MANO will interact with OpenStack and
+Juju. The key items required for the integration can be described as
+follows.
+
+.. figure:: images/key_item.png
+    :alt: key item
+    :figclass: align-center
+
+    Fig 1. Key Item for Integration
+
+Open-O is scoped for the integration
+====================================
+
+OPEN-O includes various components for OPNFV MANO integration. The initial
+release of integration will be focusing on NFV-O, Common service and Common
+TOSCA. Other components of Open-O will be gradually integrated to OPNFV
+reference platform in later release.
+
+.. figure:: images/openo_component.png
+    :alt: openo component
+    :figclass: align-center
+
+    Fig 2. Deploy Overview
+
+The vIMS is used as initial use case
+====================================
+
+based on which test cases will be created and aligned with Open-O first
+release for OPNFV D release.
+
+- Creatting scenario (os-nosdn-openoe-ha) to integrate Open-O with OpenStack Newton.
+- Integrating with COMPASS as installer, FuncTest as testing framework
+- Clearwater vIMS is used as VNFs, Juju is used as VNFM.
+- Use Open-O as Orchestrator to deploy vIMS to do end-2-end test with the following steps.
+
+1.  deploy Open-O as orchestrator
+2.  create tenant by Open-O to OpenStack
+3.  deploy vIMS VNFs from orchestrator based on TOSCA blueprintn and create VNFs
+4.  launch test suite
+5.  collect results and clean up
+
+.. figure:: images/vIMS_deploy.png
+    :alt: vIMS deploy
+    :figclass: align-center
+
+    Fig 3. vIMS Deploy
+