DRAFT PROPOSAL FOR COMMENTS
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Beijing |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Amdocs, ZTE, Orange, TechmahindraTech Mahindra |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
Describe the MVP for this releaseThe scope of the Beijing Release of AAI will address CII Badging Security Program and Platform Maturity Requirements, as well the approved Release 2 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.
Use Cases
AAI will support to the best of its ability the Release 2 Use Cases
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.
- ESR - External System Registry component
Stretch goal for Beijing: - IM - Image Manager. CRUD of image files/metadata.
Functionalities
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.
...
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 fixVersion = "Beijing Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
This presentation was given by AT&T's Phil Blackwood on AAI's weekly meeting: 2018-01-05 AAI Weekly Meeting notes
| View file | ||||
|---|---|---|---|---|
|
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Move to Active OpenSource Graph database | A&AI is currently using titan which is not actively being developed . We want to explore and implement a replacement FOSS solution which is being actively developed. | ||
| 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 | ||
| IM | Exectuable - stretch goal |
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.
...
Indicate where your project fit within the ONAP Archiecture Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
...
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.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||||
|---|---|---|---|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API descriptionDMaaP | Eventing bus | |||
| MSB | Service registry | |||||||
| SDC | A&AI Model loader consumes model objects | |||||||
| Multi-VIM | Image storage, cloud-infrastracture update | https://wiki.onap.org/download/attachments/13599038/MultiVIM-onap-draft-r1-0822.doc?version=1&modificationDate=1503406573000&api=v2 |
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description|
|---|---|---|---|---|---|---|---|---|---|
| SO | REST API | TBD | TBD | ||||||
| APPC | REST API | TBD | TBD | ||||||
| POLICY | REST API | TBD | TBD | ||||||
| VID | REST API | TBD | TBD | ||||||
| SDNC | REST API | TBD | TBD | ||||||
| HOLMES | REST API | TBD | TBD | ||||||
| VF-C | REST API | TBD | TBD | ||||||
| CLI | REST API | TBD | TBD | ||||||
| MultiVim | REST API | TBD | TBD | ||||||
| SDC | REST API(upload/query images) | TBD | TBD |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version |
|---|---|---|
| To fill out | To fill out | To fill out |
...
| 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 | |
| AJSC | Open-source Microservice application sever | 6 |
| ElasticSearch | Search framework | 2.4.1 |
| HAPROXY | microservice front end | 1.7 |
Testing and Integration Plans
...
| 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
...