...
- Services are created by HELM using ONAP/Docker-hub or bitnami images.
- The images of SDNRDM and SDNRWEB are created as distribution by pom/dockerfile-projects.
Related tickets are:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-877 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-878 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-1013 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-885 |
|---|
|
Repositories
The code for ONAP Frankfurt SDN-R comes into the following repositieres
| Gerrit repository | Description |
|---|
| ccsdk/features/sdnr/wt | Features |
| sdnc/oam/installation/sdnc | Image creation SDNC with SDNR as feature |
| sdnc/oam/installation/sdnc-web | Image creation sdncweb using odlux feature |
| oom/kubernetes/common | Elasticsearch service |
| oom/kubernetes/sdnc | sdnr + sdnrweb |
Distributions/ Images
SDNRDM (Devicemanager) existing
- ONAP/Gerrit repository: SDNC/OAM
- pom.xml and dockerfile
- SDNR Controller, activated by feature SDNRWT
- Using ODL-Base image from CCSDK
SDNRDB (Database) new in helm/oom/sdnc
- ONAP/Gerrit repository: OOM/SDNC
- Database Elasticsearch 6.x
- Created by OOM/SDNC - scripts
- Created by Helm/Kubernets script
- Images are elasticsearch-oss 6.x and nginx
- Containers are directly loaded and configured from bitnami by helm
SDNRWEB (Web server) new
- ONAP/Gerrit repository: Where to place? → Where to create the pom.xml and Dockerfile?? (Dan)
- Based on linux and nginx: https://hub.docker.com/r/bitnami/nginx/
- Linux version: miniDEB
- No ODL dependency