Delivery

SDC Dockers Containers

Overview

Name Content of the container On Startup
sdc-cs-init Logic for creating the schemas for SDC catalog server Create the schemas
sdc-cs-onboard init Logic for creating the schemas for SDC onboarding server Create the schemas
sdc-cs Cassandra server Starts Cassandra
sdc-onboard-BE Onboarding Backend Jetty server Starts Jetty with the application.
sdc-BE Backend Jetty server Starts Jetty with the application.
sdc-BE-init Logic for importing the SDC Tosca normative types Logic for configuring external users for SDC external api’s Executes the rest calls for the catalog server
sdc-FE SDC Frontend Jetty server Starts Jetty with our application.

Deployement dependency map

Connectivity Matrix

Name API purpose protocol port number / range TCP / UDP
sdc-cassandra SDC backend uses the two protocols to access Cassandra trift/async 9042 / 9160 TCP
sdc-onboard-backend Access the onboarding functionality http(s) 8081 / 8445 TCP
sdc-backend Access the catalog functionality http(s) 8080 / 8443 TCP
sdc-frontend Access SDC UI and proxy requests to SDC backend http(s) 8181 / 9443 TCP

Offered APIs

container / vm name address API purpose protocol port number TCP / UDP
sdc-fe /sdc1/feproxy/* Proxy for all REST calls from SDC UI HTTP(S) 8181 / 8443 TCP
sdc-be /sdc2/* Internal APIs used by the UI. Request is passed through front end proxy HTTP(S) 8080 / 8443 TCP
  /sdc/* External APIs offered to the different components for retrieving info from SDC catalog. HTTP(S) 8080 / 8443 TCP
sdc-onboarding-be /onboarding/api/* Internal APIs used by the UI HTTP(S) 8080 / 8443 TCP

Structure

Below is a diagram of the SDC project docker containers and the connections between them.