The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Guilin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Amdocs, Orange, Huawei, ZTE, Nokia, IBM, TechMahindra, Fujitsu |
...
The scope of the Guilin Release of AAI will address CII Badging Security Program and Platform Maturity Requirements, as well the approved use cases.
Highest priority will be assigned to support security and platform maturity requirements. As next highest priority, AAI will support the approved use cases. Best-effort additional development will continue to support additional features not included in the approved use cases.
AAI R7 Guilin Release: TSC must have requirements
Requirements
Use Cases: AAI Use Case Impacts in R6R7 Guilin Release: Functional Use Cases
TSC MUST HAVES : AAI R7 Guilin Release: TSC must have requirements
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
- 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 (provided community can deliver support, update vulnerable dependencies, and maintain the project)
...
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=AAI and issuetype in (story) and status != "Closed" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Deliverable Name | Deliverable Description |
|---|---|
| A&AI resources | Executable. REST CRUD interface to graph database |
| A&AI traversal | Executable. REST Interface for complex queries |
| Data router | Executable |
| Search-data-service | Executable |
| Router-core | Library |
| Sparky-fe | Library |
| Sparky-be | Executable (AAI UI) |
| Schema-service | Executable (delivers schema to other AAI mS) |
| Graphadmin | Executable (graph administration functions) |
| ESR | Exectuable |
| OOM Config | Source code - configuration using AAI dockers in the k8 OOM environments |
| Cacher | Executable - caching interface |
Sub-Components
See Resources and Repositories (Deprecated)#ActiveandAvailableInventory
Architecture
High level architecture diagram
...
Please fill out the centralized wiki page: Guilin Release Platform Maturity
AAI data is filled out
API Incoming Dependencies
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 the release API Freeze freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | SO | REST API | M3 | TBD | APPC | REST API | M3 | TBD | POLICY | REST API | M3 | TBD | VID | REST API | M3 | TBD | SDNC | REST API | M3 | TBD | HOLMES | REST API | M3 | TBD | VF-C | REST API | M3 | TBD | CLI | REST API | M3 | TBD | MultiVim | REST API | M3 | TBD | SDC | REST API(upload/query images) | M3 | TBD | ExtAPI | REST API | M3 | TBD | UUI | REST API | M3 | TBD | OOFREST API | M3 | TBD | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Third Party Products Dependencies
...
| Name | Description | Version |
|---|---|---|
| JanusGraph | Open-source, distributed graph database | 0.2.3 |
| Cassandra | Open-source distributed storage system | 3.11 |
| Docker | VM container | |
| SpringBoot | Open-source Microservice application sever | 1.5.22 or 2.x |
| ElasticSearch | Search framework | 6.8 |
| HAPROXY | microservice front end | 1.8 |
| Centos/Alpine | OS | See docker config files |
...
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
AAI intends to move toward the SO model of gating for CSIT testing
AAI will participate in the Integration testing
AAI will do unit test within the WR AAI tenant space
AAI will contribute additional robot test tooling which does better regression testing
.
AAI R7 Guilin: Functional Test Cases
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
Please refer to Guilin Defect StatusTBD
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Please update any risk on the centralized wiki page - Guilin Risks
Resources
Fill out the Resources Committed to the Release centralized page.TBD
Release Milestone
The milestones are defined at the Guilin Release LevelPlanning and all the supporting project agreed to comply with these dates.
...
- Team contributions to the specific document related to he project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...
| title | Note |
|---|
...
- .
Other Information
Vendor Neutral
...