...
Architecture is described on another subpage: SDC Architecture
Subprojects
SDC is a huge component. In the road-map there is a plan to split SDC into smaller projects. To make it smooth in the future, we dont introduce new dependencies between groups of sub-projects. You can find a project and its group in the table below. There is also an informal agreement that committers have their responsibilities and focuses. If you make a change (of course, affecting subprojects from one group...), please make sure to add reviewers specialized in affected area - this will prevent the situation of having +2 without a merge. Reviewers and their responsibilities are listed below:
Commiters' specialization
| Group | Commiter |
|---|---|
| Catalog | |
| Onboarding | |
| Other | |
Subprojects
| Group | Component | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Catalog | asdctool | Collection of standalone utilities used in different projects: import, export, migration etc. | |||||||||
| 2 | Catalog | catalog-be | Business logic of the app. Compiles to WAR. | |||||||||
| 3 | catalog-dao | Manages persistance layer:
// Contains dead Neo4j code. It may replace titan | ||||||||||
| 4 | catalog-fe | Proxy between ui and backend. Contains business logic as well. | ||||||||||
| 5 | catalog-model | Connection layer, serves models to other projects | ||||||||||
| 6 | catalog-ui | |||||||||||
| 7 | common-app-api | Utils and logic shared between frontend and backend. | ||||||||||
| 8 | common-be | dcae-d|||||||||||
| 9 | docs | dox-sequence-diagram-ui | jtosca | Generic TOSCA parser based on 1.1 spec | ||||||||
| 10 | security-utils | |||||||||||
| 11 | sdc- | onap-ui | openecomp-bdd | openecomp-be | openecomp-ui | sdc-distribution-client | sdc-docker-base | Docker creation project | sdc-os-chef | sdc-titan-cassandra | ||
| 12 | sdc-tosca | TOSCA parser based on jtosca. Complies with ONAP SDC TOSCA model(?) | ||||||||||
| 13 | sdc-workflow-designer | Graphic tool for service lifecycle management | security-utils | |||||||||
| 14 | services | |||||||||||
| 15 | ui-ci | |||||||||||
| 16 | sdc-os-chef | |||||||||||
| 17 | test-apis-ci | |||||||||||
| 18 | utils | |||||||||||
| 19 | Onboarding | build-tools | ||||||||||
| 20 | common | |||||||||||
| 21 | dox-sequence-diagram-ui | |||||||||||
| 22 | services | |||||||||||
| 23 | onboarding | |||||||||||
| 24 | openecomp-bdd | |||||||||||
| 25 | openecomp-be | |||||||||||
| 26 | openecomp-ui | |||||||||||
| 27 | Other | jtosca | Generic TOSCA parser based on 1.1 spec | |||||||||
| 28 | onap-ui | |||||||||||
| 29 | dcae-d | |||||||||||
| 30 | sdc-distribution-client | |||||||||||
| 31 | sdc-docker-base | Docker creation project | 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 SDC Dependencies
...