Versions Compared

Old Version 2

changes.mady.by.user James Forsyth

Saved on

compared with

New Version 3

changes.mady.by.user James Forsyth

Saved on

Key

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

...

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1419
 - the schema ingest library allows for a streamlined approach to using the AAI schema.  Also allows for multiple OXM files so users can insert their own types at run-time.

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

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:


enricher

Enables complementing AT&T data with federated data from additional sources. Exsiting seed code contributed from ECOMP

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1331

cacher

The Response Caching Microservice (Cacher) 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/

. Existing seed code from ECOMP

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1337

validation

Microservice used to invoke validation mechanism. Used by POMBA, exsiting seed code from ECOMP

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


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 BeijingCasablanca.  
    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 reposPlan is to reach target of 0 severe or critical exceptions 
  2. Scalability and Resiliency
    1. Relying on kubernetes to manage AAI resilienceresiliency, multiple instances of each stateless application serveserver
    2. Single-site failover
  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 72 stability soak test
  4. Manageablility
    1. 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.
    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 LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyAAI-494Follow the new guidelines for providing API documentation
    2. User guide for the AAI UI

Information/Data Model Alignment

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMODELING-61

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