...
The SDN-R related feature sources are provided to repository [ccsdk/features]/sdnr. The jenkins production will compile bundles and provide artifacts to nexus.
Moved to here: SDN-C/SDN-R images
SDN-R Images
The artifacts are bundled into a docker container in repository [sdnc/oam]. The relevant projects for creating the images are
...
| project file | in Container | meaning |
|---|---|---|
| src/main/scripts/startODL.sh | /opt/onap/sdnc/bin/startODL.sh | Startup script and entry point
|
| pom.xml: ccsdk.features.version | specifies the ccsdk/feature to be included. | |
| src/main/docker/Dockerfile: repository | $ODL_HOME/etc/org.apache.karaf.feature.cfg | Repository of features to be loaded. |
SDN-C/SDN-R Image dependencies
...
/opt/onap/sdnc
add
Points
- Clean up sdnr/wt
...
- dependency is in sli and sdnc: Remove bundle dependency from sdnc/
...
odlbasefeatures
ccsdkfeatures by startscript
...
add sli related features and repositories and boot features
sdnr/northbound
...
onap/ccsdk-alpine-image
...
- Move sdnr-wt from SDNC back to CCSDK. Means remove from sdnc/oam
- oam
- Install by sdnc install script.
- Cleanup environment variables and specify at one location
- Use Docker ARG by default
- ENV only for variables, used by script
- There are several startup scripts. How to harmonize this
- startODL in ccsdk startODL Can we harmonize this?
- Script directories in sdnc
- opt/onap/sdnc
- opt/onap/ccsdk
- Same script names different versions.
- startODL.sh in ccsdk
- startODL.sh in sdnc
- startODL.oom.sh in OOM project
- ODL Startup
- featuresboot modified
- by Dockerfile
- and by startup
- script (
- Only startupscript should define featureboot with custom features.
- odlbasefeatures are specified by ccsdk-odlsli-alpine-imange dockerfile
- At the moment featurerepositories are added by Dockerfile and startup scripts
- Only dockerfile should add featurerepositories
...