...
Architecture is described on another subpage: SDC Architecture
Subprojects
| Component | Description | |
|---|---|---|
| asdctool | Collection of standalone utilities used in different projects: import, export, migration etc. | |
build-tools | ||
| Catalog | catalog-be | Business logic of the app. Compiles to WAR. |
catalog-dao | Manages persistance layer:
// Contains dead Neo4j code. It may replace titan | |
catalog-fe | Proxy between ui and backend. Contains business logic as well. | |
catalog-model | Connection layer, serves models to other projects | |
catalog-ui | ||
| common | ||
common-app-api | Utils and logic shared between frontend and backend. | |
common-be | ||
dcae-d | ||
docs | ||
dox-sequence-diagram-ui | ||
jtosca | Generic TOSCA parser based on 1.1 spec | |
onap-ui | ||
openecomp-bdd | ||
openecomp-be | ||
openecomp-ui | ||
sdc-distribution-client | ||
sdc-docker-base | Docker creation project | |
sdc-os-chef | ||
sdc-titan-cassandra | ||
| sdc-tosca | TOSCA parser based on jtosca. Complies with ONAP SDC TOSCA model(?) | |
sdc-workflow-designer | Graphic tool for service lifecycle management | |
security-utils | ||
services | ||
| ui-ci |
Dependencies
SDC is a standalone application that, as such, does not require any other components to start. Deployed SDC enables to import or create an asset (design time). In order to take advantage of it (deploy a service) other components are required. For a start, please see :
...
Interfaces - API and clients
...