...
role create org.onap.dmaap-bc.service
perm grant org.onap.dmaap-bc.api.access * read org.onap.dmaap-bc.service
perm grantorg.onap.dmaap.mr.access * * org.onap.dmaap-bc.service
perm grantorg.onap.dmaap.mr.topic * view org.onap.dmaap-bc.service
perm createorg.onap.dmaap.mr.topic * * org.onap.dmaap-bc.service
perm create org.onap.dmaap-dr.feed * * org.onap.dmaap-bc.service
perm create org.onap.dmaap-dr.sub * * org.onap.dmaap-bc.service
perm createorg.onap.dmaap.mr.topicFactory :org.onap.dmaap.mr.topic:org.onap.dmaap.mrcreate,destroy org.onap.dmaap-bc.service
role user add org.onap.dmaap-bc.servicedmaap-bc@dmaap-bc.onap.org
role user add org.onap.dmaap-bc.api.Controllerdmaap-bc@dmaap-bc.onap.org
3. Redploy Deploy dmaap
NOTES:
- the message-router-mirrormaker pod is dependent on topic provisioning and AAF permissions being granted, which is done as a result of the message-router post-install job. Sometimes this sequence takes a while and the message-router-mirrormaker pod status gets in a crashback loop. Patience: if all the steps above are taken, it should eventually reach a ready state. However, it will never succeed if the full topic provisioning wasn't successful.
- depending on your environment, the deployment of all the components takes a while and can easily exceed the default helm timeout. Recommend adding --timeout 900 to your helm install command line.