...
- Security
- AAI core:
- AAI UI:
- 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
- SONAR code coverage. Plan is to get to >50% on all repos.
- Nexus IQ scans: We are in the process of migrating off AJSC to Spring Boot - Our first microservice has been converted and (aai/resources) 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
- Manageablility
- Logging/EELF - WIP
- Instantiation in < 1hr
- Scalability and Resiliency
- 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 - Relying on kubernetes to manage AAI resilience, multiple instances of each stateless application server
- 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
- Working closely with OOM and MSB teams
- Performance and stability
- Focus to this point has been security and scalability/resiliency. We will participate in the integration team's performance testing.
- Manageablility
- Logging/EELF
- Instantiation in < 1hr
Information/Data Model Alignment
...