Page Comparison

...

What is this release trying to address?

Describe the problem being solved by this releaseThe scope of the Amsterdam Release of A&AI will address the approved R1 Amsterdam use cases. 

Highest priority will be assigned to support the approved use cases; however, additional development will continue to support additional features not included in the approved use cases.

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

Use Case: Residential Broadband vCPE (Approved)

Use Case: vFW/vDNS (Approved)

Use Case: VoLTE(approved)

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.

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.

Epics

...

Stories

...