Content Comparison

For information about the functionality provided by the Acumos adapter and about the adapter's architecture, see this overview.

...

1. Download the Acumos adapter Helm chart from (TBD).
2. Populate the dependencies for the chart by entering the chart directory and executing
   helm dep up

3. Create a YAML file containing information about the Docker registry and the Acumos instance that the adapter will use.  The table below shows the properties that must be in this file.

   Property Name	Description
   dockerUser	User name to be used by the adapter to push images to the Docker registry
   dockerPass	Password to be used by the adapter to push images to the Docker registry
   dockerTargetRegistry	Address of the Docker registry where the adapter will push images, in the format host_name:port
   acumosCert	The certificate information needed for the adapter to authenticate itself to the Acumos instance, in PEM format.  The information contains the following elements, in this order: The unencrypted private key associated with the certificate The client certificate If the certificate has been signed by one or more intermediate certificate authorities, the intermediate certificate authority certificates Note that this property is a multi-line string in YAML.

   Here is an example of the file, with some sensitive information truncated or omitted.
   
   dockerUser: example-user
dockerPass: example-pass
dockerTargetRegistry: nexus.example.com:18448
acumosCert: |
  -----BEGIN PRIVATE KEY-----
  MII...
 (remainder of private key)
  -----END PRIVATE KEY-----
  -----BEGIN CERTIFICATE-----
  MII...
  (remainder of client certificate)
  -----END CERTIFICATE-----
  -----BEGIN CERTIFICATE-----
  MII...
 (remainder of intermediate CA certificate)
 -----END CERTIFICATE-----

   
   

4. Deploy the Acumos adapter using helm:
   helm install -n helm_release_name --namespace namespace_of_running_onap_instance -f /path/to/yaml_file /path/to/acumos_adapter_chart_directory
For example:
  Helm release name: testadapt
  Namespace of running ONAP instance: onap    YAML file with docker & cert info: ~/acumos-adapter-demo/overrides.yaml
       Executing in the directory holding the Acumos adapter Helm chart
   helm install -n testadapt --namespace onap -f ~/acumos-adapter-demo/overrides.yaml  .


5. If the Docker registry requires authentication for pulling an image, some additional configuration will be needed.  After you've imported a model and used DCAE MOD to create a flow, you will want to deploy the flow using the blueprints generated by MOD.   The Cloudify Manager component executes the deployment operation, using a Kubernetes plugin (k8splugin). The plugin needs the Docker pull credentials to pass to Kubernetes, so that Kubernetes can pull the Docker images created by the adapter.  There are two steps:
   1. Create a Kubernetes image pull secret. (See the Kubernetes documentation for details.  The secret must be created in the namespace where the ONAP instance is running.  The command has the form:
      kubectl -n onap_namespace create secret docker-registry secret_name --docker-server=docker_registry_server --docker-username=docker_user --docker-password=docker_password
For example, using the Docker information from the example in step 3 above and the namespace from the example in step 4, and choosing the name testadapt-adapter-pull-secret for the secret, the command would be:
      kubectl -n onap create secret docker-registry testadapt-adapter-pull-secret --docker-server=nexus.example.com:18448 --docker-username=example-user --docker-password=example-pass
      
      

Verification