...

• 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
• A&AI Core: Babel - Parses models received from SDC
• A&AI Core: Event-Client - publishes an event stream of changes to the database
• A&AI Core: Model-loader - Loading models parsed from SDC
• A&AI Core: Logging-service - Service to standardize logging for compliance and readability
• A&AI Core: GraphAdmin - suite of functionality to manage the graph database
• 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)Rest-Client - A library for an user to interface with the A&AI core APIs of resources and traversal

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.

...

Sub-Components

See Resources and Repositories (Deprecated)#ActiveandAvailableInventory

...