...
Other updates:
AAI will use AAF for Authentication/Authorization RBAC - currently planning on using Basic auth, since we haven't had success integrating with AAF to prove out a 2-way x509 cert exchange with AAF. We believe that this close to API freeze, forcing all clients to 2-way TLS is too steep a climb. We believe there also may be potential for integration with the proposed Pluggable Security Microservice, proposed by Andrew Baxter
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| enricher | Enables complementing AT&T data with federated data from additional sources. Exsiting seed code contributed from ECOMP
| ||||||||||
| cacher | The Response Caching Microservice (Cacher) is built to deliver multiple mechanisms of making API calls and populating the responses into a JSON datastore. Existing seed code from ECOMP
| ||||||||||
| validation | Microservice used to invoke validation mechanism. Used by POMBA, exsiting seed code from ECOMP
|
S3P Updates
- Security
- AAI core:
- AAI UI:
- AAI used 1-way TLS on APIs in Beijing and will continue in Casablanca.
- AAI → Cassandra w/ TLS
SONAR code coverage. Plan is to maintain >50% on all repos. - Nexus IQ scans: Plan is to reach target of 0 severe or critical exceptions
- AAI core:
- Scalability and Resiliency
- Relying on kubernetes to manage AAI resiliency, multiple instances of each stateless application server
- Single-site failover
- Performance and stability
- Focus to this point has been security and scalability/resiliency. We will participate in the integration team's performance testing
- Seeking to meet 72 stability soak test
- Manageablility
- Logging/EELF - Will adopt the ONAP logging specification to the best of our ability. We are currently very close, may not get the custom headers for this release.
- AAI services can be instantiated in < 1hr
- Usability
- Follow the new guidelines for providing API documentation
- User guide for the AAI UI
...