...
So CCSDK has created a component meta-feature for each of the SLI repositories, and we will encounter commands in the Maven pom.xml files and directory and file structures to implement them.
| Anchor | ||||
|---|---|---|---|---|
|
Yet another aspect for the context of the installer is that CCSDK changed the procedure to install karaf features from Beijing to Casablanca, but some elements of the prior procedure are still present. Prior to Casablanca, all of the CCSDK features were copied into a directory in the ccsdk home directory '/opt/onap/ccsdk/features/,' and the entry point script in the Docker container would install them. The contents of the ccsdk home directory and features directory for Beijing are shown here.
...
Below is the annotated pom.xml file. It executes two maven phases: prepare-package and package. Although Maven executes the prepare-package phase before the package phase, the code for the prepare-package code appears after the prepare code in the pom.xml file. In the annotations, we discuss the code in the sequence is indicated by number.
in which it is executed rather than the sequence in which it appears.
Installer pom.xml file part 1
install-feature.sh script
As we described in the previous section, the installation folder in CCSDK_FEATURE_DIR for a particular feature contains the zipped maven repository for that feature and an installation script, shown here.
| Code Block | ||||
|---|---|---|---|---|
| ||||
ODL_HOME=${ODL_HOME:-/opt/opendaylight/current}
ODL_KARAF_CLIENT=${ODL_KARAF_CLIENT:-${ODL_HOME}/bin/client}
INSTALLERDIR=$(dirname $0)
REPOZIP=${INSTALLERDIR}/${features.boot}-${project.version}.zip
if [ -f ${REPOZIP} ]
then
unzip -d ${ODL_HOME} ${REPOZIP}
else
echo "ERROR : repo zip ($REPOZIP) not found"
exit 1
fi
${ODL_KARAF_CLIENT} feature:repo-add ${features.repositories}
${ODL_KARAF_CLIENT} feature:install ${features.boot} |