...
| Code Block |
|---|
% docker images REPOSITORY TAG IMAGE ID CREATED SIZE onap/ccsdk-odlsli-image 0.3-STAGING-latest dc4309c12ee4 31 seconds ago 1.81GB onap/ccsdk-odlsli-image 0.3.2-SNAPSHOT dc4309c12ee4 31 seconds ago 1.81GB onap/ccsdk-odlsli-image 0.3.2-SNAPSHOT-STAGING-20181108T170427Z dc4309c12ee4 31 seconds ago 1.81GB onap/ccsdk-odlsli-image latest dc4309c12ee4 31 seconds ago 1.81GB nexus3.onap.org:10001/onap/ccsdk-odl-oxygen-image 0.3.2-STAGING ebc754e1a8b0 37 hours ago 1.69GB onap/ccsdk-odl-oxygen-image 0.3.2-STAGING ebc754e1a8b0 37 hours ago 1.69GB ... |
To minimize confusion, I chose to rename the image to something meaningful for the proof-of-concept: oof-pci/ccsdk-odlsli-image:0.3.2-SNAPSHOT.
Create a custom SDNC Docker image
...
The relevant part of sdnc/oam/installation/sdnc/pom.xml is:
| Code Block |
|---|
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <parent> <groupId>org.onap.ccsdk.parent</groupId> <artifactId>odlparent-lite</artifactId> <version>1.1.2-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <packaging>pom</packaging> <groupId>org.onap.sdnc.oam</groupId> <artifactId>installation-sdnc</artifactId> <version>1.4.2-SNAPSHOT</version> <name>sdnc-oam :: installation :: ${project.artifactId}</name> <description>Creates SDN Controller Docker container</description> <properties> <image.name>onap/sdnc-image</image.name> <sdnc.project.version>${project.version}</sdnc.project.version> <sdnc.northbound.version>1.4.2-SNAPSHOT</sdnc.northbound.version> <ccsdk.docker.version>0.3-STAGING-latest</ccsdk.docker.version> <sdnc.keystore>keystore.sdnc.p12</sdnc.keystore> <sdnc.keypass>onap3.0</sdnc.keypass> <sdnc.secureport>8443</sdnc.secureport> <docker.buildArg.https_proxy>${https_proxy}</docker.buildArg.https_proxy> <docker.push.phase>deploy</docker.push.phase> <docker.verbose>true</docker.verbose> <maven.build.timestamp.format>yyyyMMdd'T'HHmmss'Z'</maven.build.timestamp.format> </properties> ... |
It specifies Notice that the version number for the Casablanca branch of SDNC is 1.4.2-SNAPSHOT, which differs from the version for CCSDK: 0.3.2-SNAPSHOT. Also, it specifies a property for the tag of the CCSDK Docker image as "0.3-STAGING-latest." The file sdnc/oam/installation/sdnc/installation/sdnc/src/main/docker/Dockerfile shows:
| Code Block |
|---|
# Base ubuntu with added packages needed for open ecomp FROM onap/ccsdk-odlsli-image:${ccsdk.docker.version} ... |
One can set the tag for the CCSDK Docker image in either file. I chose to set it in the Dockerfile.
| Code Block |
|---|
# Base ubuntu with added packages needed for open ecomp # FROM onap/ccsdk-odlsli-image:${ccsdk.docker.version} FROM onap/ccsdk-odlsli-image:0.3.2-SNAPSHOT ... |
With that single change, one can navigate to sdnc/oam/installation/sdnc and execute the command "mvn clean install -P docker" to create the custom SDNC image. One now has these images.
| Code Block |
|---|
% docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
onap/sdnc-image 1.4-STAGING-latest 4bb8c2f04a35 12 seconds ago 1.85GB
onap/sdnc-image 1.4.2-SNAPSHOT 4bb8c2f04a35 12 seconds ago 1.85GB
onap/sdnc-image 1.4.2-SNAPSHOT-STAGING-20181108T173140Z 4bb8c2f04a35 12 seconds ago 1.85GB
onap/sdnc-image latest 4bb8c2f04a35 12 seconds ago 1.85GB
onap/ccsdk-odlsli-image 0.3-STAGING-latest dc4309c12ee4 27 minutes ago 1.81GB
onap/ccsdk-odlsli-image 0.3.2-SNAPSHOT dc4309c12ee4 27 minutes ago 1.81GB
onap/ccsdk-odlsli-image 0.3.2-SNAPSHOT-STAGING-20181108T170427Z dc4309c12ee4 27 minutes ago 1.81GB
onap/ccsdk-odlsli-image latest dc4309c12ee4 27 minutes ago 1.81GB
oof-pci/ccsdk-odlsli-image 0.3.2-SNAPSHOT dc4309c12ee4 27 minutes ago 1.81GB
nexus3.onap.org:10001/onap/ccsdk-odl-oxygen-image 0.3.2-STAGING ebc754e1a8b0 37 hours ago 1.69GB
onap/ccsdk-odl-oxygen-image 0.3.2-STAGING ebc754e1a8b0 37 hours ago 1.69GB
... |