summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorlizi <li.zi30@zte.com.cn>2017-10-11 16:54:32 +0800
committerlizi <li.zi30@zte.com.cn>2017-10-11 16:54:32 +0800
commit62d9cb474f057cb5a5a80fd52e7c497bb7a77dca (patch)
tree1a2d16d6b1e89e35e9afb54527e7835742b0c2df
parentc7cbd5376f00cf2e5e060075a2a7666e6318fd29 (diff)
Add ESR architecture detail.
Change-Id: I3ffac8c813ee9f251b63bfd17a21edb03ff86d97 Issue-ID: AAI-427 Signed-off-by: lizi <li.zi30@zte.com.cn>
-rw-r--r--docs/platform/architecture.rst23
-rw-r--r--docs/platform/images/esr-architecture.PNGbin0 -> 130313 bytes
-rw-r--r--docs/platform/images/external-system-register-progress.PNGbin0 -> 28468 bytes
-rw-r--r--docs/platform/images/external-system-register-sequence-diagram.PNGbin0 -> 57223 bytes
-rw-r--r--docs/platform/images/vim-register-progress.PNGbin0 -> 27554 bytes
5 files changed, 23 insertions, 0 deletions
diff --git a/docs/platform/architecture.rst b/docs/platform/architecture.rst
index 18d38b0..cb658ef 100644
--- a/docs/platform/architecture.rst
+++ b/docs/platform/architecture.rst
@@ -4,4 +4,27 @@
Architecture
------------
+ESR contains two components: esr server module and esr gui module
+- ESR
+ - ESR server
+ - ESR gui
+
+ONAP-level Architecture
+^^^^^^^^^^^^^^^^^^^^^^^
+
+In ONAP architecture, ESR is a sub-project of A&AI. It provide a single point for users to manage the external system information. It provides a way to register/unregister external system dynamically.
+
+.. image:: images/esr-architecture.PNG
+
+How ESR works
+^^^^^^^^^^^^^^^^^^^^^^^
+
+The user register external system through esr-gui, esr-server will store the external system information to A&AI. And the other components such as VF-C/SDNC/Multi-Cloud then can query the external system information form A&AI. The process of VIM register may be a bit different from the VNFM/EMS/thirdparty SDNC. That because the registered VIM information is some basic information such as region/version/auth-url that things, Multi-Cloud will update the cloud information with more details, such as the volume and tenant details. The VNFM/EMS/thirdparty SDNC will not be updated by VF-C and SDNC.
+
+.. image:: images/vim-register-progress.PNG
+.. image:: images/external-system-register-progress.PNG
+
+The complete workflow is shown below in the form of a sequence diagram.
+
+.. image:: images/external-system-register-sequence-diagram.PNG \ No newline at end of file
diff --git a/docs/platform/images/esr-architecture.PNG b/docs/platform/images/esr-architecture.PNG
new file mode 100644
index 0000000..982a519
--- /dev/null
+++ b/docs/platform/images/esr-architecture.PNG
Binary files differ
diff --git a/docs/platform/images/external-system-register-progress.PNG b/docs/platform/images/external-system-register-progress.PNG
new file mode 100644
index 0000000..bcfce84
--- /dev/null
+++ b/docs/platform/images/external-system-register-progress.PNG
Binary files differ
diff --git a/docs/platform/images/external-system-register-sequence-diagram.PNG b/docs/platform/images/external-system-register-sequence-diagram.PNG
new file mode 100644
index 0000000..08731aa
--- /dev/null
+++ b/docs/platform/images/external-system-register-sequence-diagram.PNG
Binary files differ
diff --git a/docs/platform/images/vim-register-progress.PNG b/docs/platform/images/vim-register-progress.PNG
new file mode 100644
index 0000000..182e75d
--- /dev/null
+++ b/docs/platform/images/vim-register-progress.PNG
Binary files differ