...

PNF support - existing schema is sufficient looks like we need to add an attribute in support of PNF use case

Scale in/out - existing schema is sufficient

...

1. Security
   1. AAI core:

      

   2. AAI UI:
      

      

   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 and (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 Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-591

      Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key 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 Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-539

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. Instantiation in < 1hr
   3. 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
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-494

Information/Data Model Alignment

...

New custom-query to support HPA use case

New attribute on PNF object

Clients will use legacy APIs thru MSB

...