...
Context for the installer
OpenDaylight Guidelines and Component Meta-Features
CCSDK is based on OpenDaylight and follows the recommended practices of that group. There are documented guidelines for karaf features, and another aspect is what OpenDaylight calls "component meta-features," in which several related features are grouped together to simplify their installation. For example, these features implement NETCONF in OpenDaylight:
...
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.
Procedure to install CCSDK features prior to Casablanca
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.
As we can see, there is a zip file and 'install-feature.sh' script for each feature. The zip file is simply the maven repository for the feature, as shown here for ccsdk-sliapi.
And here is the 'install-feature.sh' script.
Inspecting the installer pom.xml file
...