All the old AAF dependencies have been resolved in 2.1.12-SNAPSHOT. However, a minor error has been introduced.
Known Issues:
- the permissions for the message-router identity are not correct. Symptom is that client authorization fails. This is why mirrormaker pod is not able to start.
- 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: false
dmaap-dr-prov:
enabled: false
2. Deploy AAF separately first.
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):
role user add org.onap.dmaap.mr.admin dmaapmr@mr.dmaap.onap.org
...
4. Deploy dmaap.
helm install --debug local/dmaap -n central-dmaap --namespace onap -f ~/dgl_overrides.yaml --timeout 900