| Table of Contents | ||
|---|---|---|
|
Docker Diagram
Amsterdam:
Docker name | Description |
|---|---|
sdc-cassandra | The Docker contains our Cassandra server and the logic for creating the needed schemas for SDC. On docker startup, the schemes are created and Cassandra server is started. |
| sdc-elasticsearch | The Docker contains Elastic Search server and the logic for creating the needed mapping for SDC. On docker startup, the mapping is created and Elastic Search server is started. |
| sdc-kibana | The Docker contains the Kibana server and the logic needed for creating the SDC views there. On docker startup, the views are configured and the Kibana server is started. |
| sdc-backend | The Docker contains the SDC Backend Jetty server. On docker startup, the Jetty server is started with our application. |
| sdc-frontend | The Docker contains the SDC Fronted Jetty server. On docker startup, the Jetty server is started with our application. |
Beijing:
Docker name | Description |
|---|---|
sdc-cassandra | The Docker contains our Cassandra server . On docker startup the Cassandra server is started. |
| sdc-cassandra-init | The docker contains the logic for creating the needed schemas for SDC catalog server, On docker startup, the schemes are created. |
| sdc-onboard-cassandra-init | The docker contains the logic for creating the needed schemas for SDC onboarding server, On docker startup, the schemes are created. |
| sdc-elasticsearch | The Docker contains Elastic Search server. On docker startup, Elastic Search server is started. |
| sdc-init-elasticsearch | The Docker contains the logic for creating the needed mapping for SDC and the views for kibana. On docker startup, the mapping is created. |
| sdc-kibana | The Docker contains the Kibana server. On docker startup, the Kibana server is started. |
| sdc-onboard-backend | The Docker contains the onboarding Backend Jetty server. On docker startup, the Jetty server is started with the application. |
| sdc-backend | The Docker contains the catalog Backend Jetty server. On docker startup, the Jetty server is started with the application. |
| sdc-backend-init | The docker contains the logic for importing the SDC Tosca normative types and the logic for configuring external users for SDC external api's. on start, up the docker exacutes, the rest calls to the catalog server. |
| sdc-frontend | The Docker contains the SDC Fronted Jetty server. On docker startup, the Jetty server is started with our application. |
OOM/K8 deployment dependency map:
Connectivity Matrix
Docker name | API NAME | API purpose | protocol used | port number or range | TCP/UDP |
|---|---|---|---|---|---|
sdc-cassandra | SDC backend uses the two protocols to access the cassandra | trift/async | 9042/9160 | TCP | |
| sdc-elasticsearch | SDC backend uses the two protocols to access the ES | transport | 9200/9300 | TCP | |
| sdc-kibana | the API is used to access the kibana UI | http | 5601 | TCP | |
| sdc-onboard-backend | the APIs are used to access the SDC onboarding functionalty | http/https | 8081/8445 | TCP | |
| sdc-backend | the APIs are used to access the catalog functionalty | http/https | 8080/8443 | TCP | |
| sdc-frontend | the APIs are used to access the SDC UI and to proxy requests to the SDC back end | http/https | 8181/9443 | TCP |
...
Container/VM name | API name | API purpose | protocol used | port number or range used | TCP/UDP |
|---|---|---|---|---|---|
sdc-fe | /sdc1/feproxy/* | Proxy for all the REST calls from the SDC UI | HTTP/HTTPS | 8181/8443 | TCP |
| sdc-be | /sdc2/* | Internal APIs used by the UI. The request is passed through the Front end proxy server | HTTP/HTTPS | 8080/8443 | TCP |
| sdc-be | /sdc/* | External APIs offered to the different components for retrieving information from the SDC Catalog. These APIs are protected by basic authentication. | HTTP/HTTPS | 8080/8443 | TCP |
| sdc | /onboarding-api/* | Internal APIs used by the UI. | HTTP/HTTPS | 8081/8445 | TCP |
Status Information
Diagnostic:
...