Copied from the AAI project - filling out today 20180309

Delta from R1

R2 Usecase schema updates:

HPA Schema Updates - new object types/edges still being defined

PNF support - looks like we need to add an attribute in support of PNF use case

Scale in/out - existing schema is sufficient

Change management - existing schema is sufficient

R2 Usecase functionality updates:

Custom query for HPA usecase:

Other updates:

Clients will call AAI thru MSB, stretch goal is to retire HAPROXY and use MSB for load balancing/mS selection

Datastore will be JanusGraph on Cassandra: 

Stretch goal: AAI will use AAF for Authentication/Authorization

A few microservices - mostly related to data integrity and data validation in the graph db, have been deferred to Casablanca.  This does not change any agreed scope or APIs with other ONAP systems.

S3P Updates

1. Security
   1. AAI core:

      

   2. AAI UI:
      

      Image Removed

   3. AAI used 1-way TLS on APIs in Amsterdam and will continue in Beijing.  There are still open questions about how the CA will be set up in Beijing, AAI uses a toy certificate signed by an openecomp CA which expires in December 2018

      
      

   4. SONAR code coverage.  Plan is to get to >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. Working closely with OOM and MSB teams
      

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-591

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-671

      team (all Logging developers are also OOM contributors)
   2. Relying on kubernetes to manage AAI resilience, multiple instances of each stateless application server
   3. AAI team has been working with on a clustered cassandra cluster.  We have a working PoC and will be leveraging the clustered approach in Beijing.  Single-site failover where we can lose a single node of the cassandra clustere which will be re-synced when kubernetes restores it.
      

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-539

   4. Logging ELK stack resilience
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 ELK stack can meet soak test requirements
4. Manageablility
   1. Logging/EELF
   2. AAI services ELK stack can be instantiated in < 1hr
5. Usability
   1. Working on splitting the API swagger so the readthedocs.io website can parse the RST
      

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-494

Information/Data Model Alignment

AAI's schema/edge rules will not change for the Beijing 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. 

API Updates

New endpoints for HPA use case

New custom-query to support HPA use case

New attribute on PNF object

...

1. 1. - around 5-10 min as part of overall OOM deployment
2. Usability

Deployment Configuration Alignment

API Updates