...
| draw.io Diagram |
|---|
| border | true |
|---|
| |
|---|
| diagramName | onap_milkyway |
|---|
| simpleViewer | false |
|---|
| width | |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 701 |
|---|
| revision | 5 |
|---|
|
ONAP deployed on kubernetes with external databases
As most of applications ONAP requires some persistence layer in form of databases. As ONAP follows micro-service architecture principle in theory each component could ship its own database but in practice in commercial deployments its desired to configure ONAP to use external DB engines already existing in operators infrastructure.
| draw.io Diagram |
|---|
| border | true |
|---|
| |
|---|
| diagramName | onap_with_db |
|---|
| simpleViewer | false |
|---|
| width | |
|---|
| links | auto |
|---|
| tbstyle | top |
|---|
| lbox | true |
|---|
| diagramWidth | 781 |
|---|
| revision | 13 |
|---|
|
