...
SDNC uses the same procedures as CCSDK to create the Docker image. The relevant repository is sdnc/oam, and the Docker image is created in sdnc/oam/installation/sdnc/. The pom.xlm file operates in the same way as the CCSDK counterpart and gathers the features specified in the "dependencies" section, shown here.
| Code Block |
|---|
<dependencies>
<dependency>
<groupId>org.onap.sdnc.northbound</groupId>
<artifactId>generic-resource-api-installer</artifactId>
<version>${sdnc.northbound.version}</version>
<classifier>repo</classifier>
<type>zip</type>
</dependency>
<dependency>
<groupId>org.onap.sdnc.northbound</groupId>
<artifactId>vnfapi-installer</artifactId>
<version>${sdnc.northbound.version}</version>
<classifier>repo</classifier>
<type>zip</type>
</dependency>
<dependency>
<groupId>org.onap.sdnc.northbound</groupId>
<artifactId>vnftools-installer</artifactId>
<version>${sdnc.northbound.version}</version>
<classifier>repo</classifier>
<type>zip</type>
</dependency>
<dependency>
<groupId>org.onap.sdnc.northbound</groupId>
<artifactId>sdnc-northbound-features-installer</artifactId>
<version>${sdnc.northbound.version}</version>
<classifier>repo</classifier>
<type>zip</type>
</dependency>
</dependencies>
|
When building the docker image from Dockerfile, recall that CCSDK uses the OpenDaylight image as the starting point to which it adds the CCSDK features. SDNC, in contrast, begins with the CCSDK image, as shown here from sdnc/oam;installation/sdnc/src/main/docker/Dockerfile:
FROM onap/ccsdk-odlsli-image:${ccsdk.distribution.version}