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)
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
PNF support - looks like we need to add an attribute in support of PNF use case
|
Deliver python library
Jira | |||||||
---|---|---|---|---|---|---|---|
|
Sonar must be above 50%, and address CLM
Future Cassablanca
- We retrofitted the project as a Java project (jenkins, sonar)
- 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:
...
LOG-95 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-118 - The Multicloud team has committed a python RI under
Jira server ONAP JIRA
...
serverId 425b2b0a-557c-3c0c-b515-579789cceedb key
...
LOG-
...
Other updates:
Clients will call AAI thru MSB, stretch goal is to retire HAPROXY and use MSB for load balancing/mS selection
...
161 - The Multicloud team is retrofitting our repo for python
Jira server ONAP JIRA
...
serverId 425b2b0a-557c-3c0c-b515-579789cceedb key
...
MULTICLOUD-
...
Datastore will be JanusGraph on Cassandra:
...
151 - We are looking at alternatives to the sidecar for the filebeat container
Jira server ONAP JIRA
...
serverId 425b2b0a-557c-3c0c-b515-579789cceedb key
...
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
169 - 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 - we are looking to investigate logging in DCAEGEN2 - first step was to bring up the full DCAE stack
- 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 (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
- Scalability and Resiliency
Working closely with OOM and MSB teamsJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
OOM-591serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-167
S3P Updates
Jira | ||
---|---|---|
|
...
|
- Security
- Logging RI:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-877 - 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-539LOG-186 98% for
https://bestpractices.coreinfrastructure.org/projects/1578
- SONAR code coverage. Plan is to get to >50% on all repos.
- TODO: communicate with security team
- Nexus IQ scans:
AAI-671 - Logging RI:
- Scalability and Resiliency
- Working closely with OOM team (all Logging developers are also OOM contributors)
- Relying on kubernetes to manage Logging ELK stack resilience
- Performance and stability
- Focus to this point has been security and scalability/resiliency. We will participate in the integration team's performance testing
- Seeking to meet 36hr stability ELK stack can meet soak test requirements
- Manageablility
- Logging /EELFFilebeat sidecar refactor
Possible sidecar refactor to use a deamonset inJira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-169 - ELK stack AAI services can be instantiated in < 1hr - around 5-10 min as part of overall OOM deployment
- Logging /EELFFilebeat sidecar refactor
- Usability
Deployment Configuration Alignment
- 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 columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
AAIserverId 425b2b0a-557c-3c0c-b515-579789cceedb key
494OOM-
Information/Data Model Alignment
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
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
API Updates
New endpoints for HPA use case
New custom-query to support HPA use case
New attribute on PNF object
|