Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Delta from R2

R3 Usecase schema updates:

R2 Usecase functionality updates:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1353

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1350



Other updates:

AAI will use AAF for Authentication/Authorization - 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.

New microservices:


enricherEnables complementing AT&T data with federated data from additional sources
cacher

The Response Caching Microservice (Cacher

...

Enricher

...

) is built to deliver multiple mechanisms of making API calls and populating the responses into a JSON datastore

https://jira.onap.org/projects/AAI/issues/AAI-1337

validationMicroservice used to invoke validation mechanism


S3P Updates

  1. Security
    1. AAI core:

      CII Best Practices

    2. AAI UI:

      CII Best Practices

    3. AAI used 1-way TLS on APIs in Beijing and will continue in Beijing.  
    4. AAI → Cassandra w/ TLS
      SONAR code coverage.  Plan is to maintain >50% on all repos.
    5. 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 repos
  2. Scalability and Resiliency
    1. Relying on kubernetes to manage AAI resilience, multiple instances of each stateless application serve
  3. Performance and stability
    1. Focus to this point has been security and scalability/resiliency.  We will participate in the integration team's performance testing
    2. Seeking to meet 36hr stability soak test
  4. Manageablility
    1. Logging/EELF
    2. AAI services can be instantiated in < 1hr
  5. Usability
    1. Working on splitting the API swagger so the readthedocs.io website can parse the RST
      Jira Legacy
      serverSystem Jira
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyAAI-494

...