Skip to end of metadata
Go to start of metadata

R1 Artifacts


Titan sits on top of a HBase storage backend -

Older Artifacts (Early 2017)

Active and Available Inventory (AAI) is the ONAP subsystem that provides real-time views of available Resources and Services and their relationships. AAI (sometimes referred to as A&AI) not only forms a registry of active, available, and assigned assets, it also maintains up-to-date views of the multidimensional relationships among these assets, including their relevance to different components of ONAP. 

In addition to inventory and topology management, AAI provides the ability to do inventory administration.  Data in AAI is continually updated in real-time as changes are made within the cloud. Because AAI is metadata-driven, new resources and services can be added quickly with Service Design and Creation (SDC) catalog definitions, using the AAI model loader, thus eliminating the need for lengthy development cycles. In addition, new inventory item types can be added quickly through schema configuration files.

The AAI subsystem uses graph data technology to store relationships between inventory items. Graph traversals can then be used to identify chains of dependencies between items. Relationships captured by AAI include "top-to-bottom" relationships such as those defined in SDC when products are composed of services, and services are composed of resources. It also includes “side-to-side” relationships such as end-to-end connectivity of virtualized functions to form service chains.

 AAI data views can be used by homing logic during real-time service delivery, root cause analysis of problems, impact analysis, and many other functions. 

The AAI API provides programmatic access to AAI.

Figure 1 provides a functional view of AAI.

Figure 1. Active and Available Inventory (AAI) functional diagram

Inventory and topology management 

AAI uses a central registry to create a global view of inventory and network topology. AAI receives updates from various inventory masters distributed throughout the ONAP infrastructure, and persists just enough to maintain the global view. As transactions occur, AAI persists asset attributes and relationships into the federated view based on configurable metadata definitions for each activity that determine what is relevant to the AAI inventory. AAI provides standard APIs to enable queries from various clients regarding inventory and topology. Queries can be supported for a specific asset or a collection of assets. The AAI global view of relationships is necessary for forming aggregate views of detailed inventory across the distributed master data sources. 


AAI also performs a number of administrative functions. Metadata models for the various assets are stored, updated, applied and versioned dynamically as needed without requiring a system shutdown for maintenance.  

  • No labels


  1. It would be good if the page can describe several flows of AAI and also how the models are stored in AAI from different modules of ONAP.For example, how  and what information does SDC store in AAI and how the information is converted, stored in form of graph (vertices and edges) and retrieved with some examples (such as vFW).

    1. Yeah, It's good if those things are updated. I was also having the same queries. Please update.

      1. This page looks like it was based on Amsterdam release.

        Maybe you would like to refer to ARC AAI Component Description - Dublin or Active and Available Inventory (AAI) (5/11/17) instead.

        For the specific case of SDC-to-AAI, you will probably want to talk to Tian Lee about the "Model Loader" component.