Delta from R2
AAI will follow very similar architecture to R2, and its position in the larger ONAP architecture remains consistent. Some additional microservices will be added, and we will make schema / edge rule changes in support of the various R3 use cases and functional requirements.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-1478
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 | ||||||
|---|---|---|---|---|---|---|
|
New microservices:
| 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 BeijingCasablanca.
- AAI → Cassandra w/ TLS
SONAR code coverage. Plan is to maintain >50% on all repos. - Nexus IQ scans: We are in the process of migrating off AJSC to Spring Boot - Our first microservice has been converted (aai/resources) and has 0 security and 0 policy violations. The other microservices will be similarly converted. This should clear the overwhelming majority of the current exceptions on the other reposPlan is to reach target of 0 severe or critical exceptions
- AAI core:
- Scalability and Resiliency
- Relying on kubernetes to manage AAI resilienceresiliency, multiple instances of each stateless application serveserver
- 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 36hr 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
- Working on splitting the API swagger so the readthedocs.io website can parse the RST
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-494Follow the new guidelines for providing API documentation - User guide for the AAI UI
- Working on splitting the API swagger so the readthedocs.io website can parse the RST
Information/Data Model Alignment
AAI's schema/edge rules will not change for the Casablanca release to align with the modelling subcommittee's proposed information/data/runtime service and instance models. AAI is participating in the discussions and will map existing data objects to the approved clean versions when they are approved, targeting Dublin for potential changes.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
API Updates
New endpoints for HPA use case
New custom-query to support HPA use case
New attribute on PNF object
Clients will use legacy APIs thru MSB