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
2 Comments
Maheswari R
Hi ,
This will work for Elalto version ?
Regards,
Maheswari.R
Maheswari R
Hi,
I have tried this workaround for Elalto onap version , I am getting Timed Out error.
Please help me on this
sudo helm install --debug local/dmaap -n central-dmaap --namespace onap -f dgl_overrides.yaml --timeout 1500
[debug] Created tunnel using local port: '38579'
[debug] SERVER: "127.0.0.1:38579"
[debug] Original chart version: ""
[debug] Fetched local/dmaap to /home/ubuntu/.helm/cache/archive/dmaap-5.0.0.tgz
[debug] CHART PATH: /home/ubuntu/.helm/cache/archive/dmaap-5.0.0.tgz
Error: timed out waiting for the condition
Regards,
Maheswari.R