...
A test environment has been established in the WindRiver POD-ONAP-01 instance, under the AAF Project. These components were deployed in separate kubernetes instances so they are not communicating via kubernetes service names yet. Likewise, a client attempting to communicate with these components needs to know the node port for proper mapping to the container.
| Component | Kubernetes Service | Node HTTP Address | Node HTTPS Address | Comments |
|---|---|---|---|---|
| AAF | 10.12.6.214 | 10.12.6.214 | This is the AAF instance provided by Jonathan. aka aaf-onap-test.osaaf.org GUI at: https://10.12.6.214:8200/gui | |
| Buscontroller | dmaap-bc | 10.12.5.64:30241 | 10.12.5.64:30242 | |
| Message Router | message-router | 10.12.7.22:30227 | 10.12.7.22:30228 |
AAF Pre-requisites
A client of an AAF Authenticated Topic must have an Application Identity (see AAF Environment - Beijing). This identity is used when attempting to publish or subscribe to an authenticated topic.
The Application Identity must be assigned to an AAF Role. The following steps are done by a human developer once in this AAF instance, and the changes will be saved as part of the AAF bootstrap provisioning process to be applied to other AAF deployments in the future:
- Login to the AAF GUI using a People Identity that has Administration privilege for the Application Namespace.
- Create a Role that makes sense for the client. e.g. A publisher client that has an identity within namespace org.onap.anapp might define a Role of org.onap.anapp.mrclient.
The AAF Command Line syntax would be:
role create org.onap.anapp.mrclient - Assign the Application Identity to the Role. Be careful about the ordering of the parts of the namespace.
The AAF Command Line syntax would be:
role user add anapp@anapp.onap.org org.onap.anapp.mrclient
...