DRAFT PROPOSAL FOR COMMENTS
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Amdocs, ZTE, Orange, Tech Mahindra, Nokia |
...
What is this release trying to address?
The scope of the Beijing Casablanca Release of AAI will address CII Badging Security Program and Platform Maturity Requirements, as well the approved
...
AAI will support to the best of its ability the release 3 ONAP Casablanca use cases and functional requirements.
AAI will provide support for the following use cases, currently planning on test support with no code or data model changes:
- vFW
- vDNS
- VoLTE
- vCPE
- CCVPN
- OSAM/PNF
AAI will support the functional requirements listed on the Casablanca Release Requirements page, in particular the following:
- Scaling
- committed to creating a new custom-query
- 5G/PNF
- schema updates and possible edge rule changes, but additional clarification is needed
- EA/Cloud Infrastructure for Distributed Edge Clouds
- schema updates and possible edge rule changes, but additional clarification is needed
Minimum Viable Product
- A&AI Core: Resources - CRUD REST API endpoints for A&AI inventory resources
- A&AI Core: Traversal - REST APIs for graph traversals. Some APIs use the Gremlin Server
- UI - An ONAP portal application used by operations for visualizing and searching
- Data Router: Makes decisions about workloads to be dispatched to search and tabular microservces. Includes logic to recognize and direct requests based on request archetypes.
- Search - Enable complex searches for sub graphs and functions that need to perform well across deeply nested structures using Elasticsearch. Used by the UI
- Champ - Abstraction from underlying graph storage systems that A&AI would interface with.
- Gizmo - CRUD Rest API endpoint for resources and relationships, delivering atomic interactions with the graph for improved scalability.
- Enricher - need words on this one- Enables complementing AT&T data with federated data from additional sources
- Cacher - The Response Caching Microservice (Cacher) is built to deliver multiple mechanisms of making API calls and populating the responses into a JSON datastore. The datastore is an embedded mongodb datastore, that stores cached API responses, which are updated via DMAAP events or can be synced by timed tasks or calls to the force sync endpoint.
- ESR - External System Registry component
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 2050 jqlQuery project=AAI and issuetype in (story) and fixVersion = "Casablanca Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|
| Gizmo | Executable. Atomic REST CRUD interface to graph database |
| A&AI resources | Executable. REST CRUD interface to graph database |
| A&AI traversal | Executable. REST Interface for complex queries |
| Data router | Executable |
| ESR | Exectuable |
| OOM Config | Source code - configuration recommendations for using AAI dockers in the OOM environments |
| Enricher |
| Executable - data federation service | |
| Cacher | Executable - caching interface |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
| Area | Actual Level | Targeted Level for current ReleaseCasablanca | How, Evidences | Comments | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 01 | 1The target is to capture baseline performance, but it is unclear what we'll be capturing. |
| |||||||||||
| Stability | 01 | 1 | Unclear what kinds of random transactions will be sent to AAI. Assuming it will be random runs of existing use cases w/ Robot or jmeter2 |
| ||||||||||
| Resiliency | 12 | 2 | AAI will leverage OOMs single site failure detection and recovery |
| ||||||||||
| Security | 01 | 1 (Stretch goal: 2, unlikely) | will get to AAI will maintain 50+ test coverage |
| ||||||||||
| Scalability | 01 | 1 | AAI will leverge OOM; currently working on a clustered solution for cassandra on docker
|
| ||||||||||
| Manageability | 11 | 2 | uses EELF and will continue to do so in Beijing needs to investigate the level of compliance we can reach with the ONAP logging specification 1.2 |
| ||||||||||
| Usability | 1 | 1 |
|
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| Name | Description | Version |
|---|---|---|
| JanusGraph | Open-source, distributed graph database | 0.2.0 |
| Ubuntu | Open-source software operating system | 16.0.4-LTS |
| Cassandra | Open-source distributed storage system | 3.11 |
| Docker | VM container | |
| AJSCSpringBoot | Open-source Microservice application sever | 61.5.12 |
| ElasticSearch | Search framework | 2.4.1 |
| HAPROXY | microservice front end | 1.78 |
Testing and Integration Plans
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...