| Rich Bennett | 4b00193 | 2017-10-16 09:25:01 -0400 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 4 | ============ |
| Rich Bennett | 4b00193 | 2017-10-16 09:25:01 -0400 | [diff] [blame] | 5 | Architecture |
| 6 | ============ |
| 7 | |
| 8 | .. note:: |
| 9 | * This section is used to describe a software component from a high level |
| 10 | view of capability, common usage scenarios, and interactions with other |
| 11 | components required in the usage scenarios. |
| 12 | |
| 13 | * The architecture section is typically: provided in a platform-component |
| 14 | and sdk collections; and referenced from developer and user guides. |
| 15 | |
| 16 | * This note must be removed after content has been added. |
| 17 | |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 18 | SDC As Part of ONAP |
| 19 | =================== |
| 20 | |
| 21 | .. image:: images/SDC_In_ONAP.png |
| 22 | |
| 23 | |
| 24 | High Level Architecture |
| 25 | ======================= |
| 26 | |
| 27 | The following diagram shows the high-level relationship between the system components: |
| 28 | |
| 29 | .. image:: images/High_Level_Architecture_SDC.png |
| 30 | |
| 31 | The SDC architecture uses the Jetty server as an application server. |
| 32 | |
| Idan Amit | 1aa38a4 | 2017-11-02 16:53:49 +0200 | [diff] [blame^] | 33 | - The **Jetty front end**: |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 34 | - supplies the static content of web pages, and all resources that required by the GUI |
| 35 | - serves as a proxy for the REST API requests coming from the GUI |
| 36 | |
| 37 | Every request originating from the GUI is passed to the Jetty front-end server before it is executed. |
| 38 | |
| Idan Amit | 1aa38a4 | 2017-11-02 16:53:49 +0200 | [diff] [blame^] | 39 | - The **Jetty back end** containes all the logic for the SDC. |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 40 | |
| 41 | SDC uses two storage components: Elastic Search(ES) and Cassandra |
| 42 | |
| Idan Amit | 1aa38a4 | 2017-11-02 16:53:49 +0200 | [diff] [blame^] | 43 | - **Elastic Search** is used to index the auditing data received from different operations in the SDC. |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 44 | |
| Idan Amit | 1aa38a4 | 2017-11-02 16:53:49 +0200 | [diff] [blame^] | 45 | This information can then be analyzed with Kibana. The **Kibana server** enables statistical analysis of the operations done, according to the business logic. |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 46 | |
| Idan Amit | 1aa38a4 | 2017-11-02 16:53:49 +0200 | [diff] [blame^] | 47 | - **Cassandra** is used to store auditing data, artifacts and data model objects. |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 48 | |
| Rich Bennett | 4b00193 | 2017-10-16 09:25:01 -0400 | [diff] [blame] | 49 | |
| 50 | Capabilities |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 51 | ============ |
| Rich Bennett | 4b00193 | 2017-10-16 09:25:01 -0400 | [diff] [blame] | 52 | |
| 53 | |
| 54 | Usage Scenarios |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 55 | =============== |
| Rich Bennett | 4b00193 | 2017-10-16 09:25:01 -0400 | [diff] [blame] | 56 | |
| 57 | |
| 58 | Interactions |
| Idan Amit | d90aab6 | 2017-11-02 13:42:29 +0200 | [diff] [blame] | 59 | ============ |