As of May 6, 2019 (AAF 2.1.13-SNAPSHOT-latest, dbc-client 1.0.9, dmaap-bc 1.1.5, dmaap-mr 1.1.13, dr-prov 2.1.0, dr-node 2.1.0)

All the old AAF dependencies have been resolved in 2.1.13-SNAPSHOT.

Known Issues:

some aaf pods are not reaching a ready status. This can be ignored as they are not utilized. Pods are "aaf-sms" and "aaf-sms-preload".

Resolution:

create override file ("dgl_overrides.yaml" in steps below) with following contents:

^{#################################################################}
^{# Enable/disable and configure helm charts (ie. applications)}
^{# to customize the ONAP deployment.}
^{#################################################################}
^aaf:
^{enabled: true}
^dmaap:
^{enabled: true}
^{message-router:}
^{enabled: true}
^dmaap-bc:
^{enabled: true}
^{dmaap-dr-node:}
^{enabled: true}
^{dmaap-dr-prov:}
^{enabled: true}

2. Deploy AAF separately first. This allows you to confirm aaf is running and separates aaf from dmaap k8s release for easier redeployment.

helm install --debug local/aaf -n central-aaf --namespace onap -f ~/dgl_overrides.yaml --timeout 900

3. In AAF GUI add (NOTE: new AAF GUI port 31113):

no changes needed!

4. Deploy dmaap.

helm install --debug local/dmaap -n central-dmaap --namespace onap -f ~/dgl_overrides.yaml --timeout 900