Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Delta from R2

AAI-1353 - Getting issue details... STATUS

AAI-1350 - Getting issue details... STATUS



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) 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
      AAI-494 - Getting issue details... STATUS

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. 

MODELING-61 - Getting issue details... STATUS


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





  • No labels