Copied template from the AAI project - filling out today 20180308Thank James Forsyth

Delta from R1

R2 Usecase schema updates:

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

 Started the library (for cassablanca)

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

Deliver python library 

Sonar must be above 50%, and address CLM

Future Cassablanca

1. We retrofitted the project as a Java project (jenkins, sonar)
2. We are developing a Java RI - planning completion for Cassablanca
   

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key

...

Scale in/out - existing schema is sufficient

Change management - existing schema is sufficient

R2 Usecase functionality updates:

Custom query for HPA usecase:

...

1. LOG-95

   
   

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-118

   
   
   
2. The Multicloud team has committed a python RI under

1. 
   

   Jira
   server ONAP JIRA

...

1. serverId 425b2b0a-557c-3c0c-b515-579789cceedb key

...

1. LOG-

...

Other updates:

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

...

1. 161

2. The Multicloud team is retrofitting our repo for python
   

1. Jira
   server ONAP JIRA

...

1. serverId 425b2b0a-557c-3c0c-b515-579789cceedb key

...

1. MULTICLOUD-

...

Datastore will be JanusGraph on Cassandra: 

...

1. 151

2. We are looking at alternatives to the sidecar for the filebeat container
   

   Jira
   server ONAP JIRA

...

1. serverId 425b2b0a-557c-3c0c-b515-579789cceedb key

...

1. LOG-

...

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. 169

2. we are looking at out of the box transaction tracing libraries like opentrace
   

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-104

3. we are looking to investigate logging in DCAEGEN2 - first step was to bring up the full DCAE stack
4. Security
   1. AAI core:

      Image Removed

   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
5. Scalability and Resiliency
   Working closely with OOM and MSB teams
   
   

   Jira
   server ONAP JIRA

   columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

   serverId 425b2b0a-557c-3c0c-b515-579789cceedb key

   OOM-591

   LOG-167

S3P Updates

...

1. Security
   1. Logging RI:  
      

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-877

   AAI-671
   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
      AAI-539 server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-186

      98% for 

      https://bestpractices.coreinfrastructure.org/projects/1578

       Image Added

   4. SONAR code coverage.  Plan is to get to >50% on all repos.
   5. TODO: communicate with security team
   6. Nexus IQ scans: 
2. Scalability and Resiliency
   
   1. Working closely with OOM team (all Logging developers are also OOM contributors)
   2. Relying on kubernetes to manage 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 /EELFFilebeat sidecar refactor
      Possible sidecar refactor to use a deamonset in 

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-169

   2. ELK stack AAI services can be instantiated in < 1hr - around 5-10 min as part of overall OOM deployment
5. Usability

Deployment Configuration Alignment

1. We are aligning with the centralized configuration work in OOMWorking on splitting the API swagger so the readthedocs.io website can parse the RST
   
   

   Jira
   server ONAP JIRA

   columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

   serverId 425b2b0a-557c-3c0c-b515-579789cceedb key

   AAI

   OOM-

   494

Information/Data Model Alignment

1. 740

   
   
   

API Updates

We currently have no logging library for Beijing - the stub work is in 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. Clients will use legacy APIs thru MSB

API Updates

New endpoints for HPA use case

New custom-query to support HPA use case

New attribute on PNF object