Page History

...

Term

Definition

AAI-internal-clients

Sub-projects of AAI that are direct clients of schema services (currently have dependency on aai-schema-ingest library) including:

data-router, gizmo, resources, router-core, sparky-be, spike, traversal, validation

Sub-projects of AAI that are indirect clients of schema services (via aai-common library) or are schema-agnostic including:

babel, cacher, chameleon, champ, eis, enricher, esr, gallifrey, graphadmin, graphgraph, logging-service, model-loader, rest-client, search-data-service, sparky-fe, tabular-data-service

ONAP-project-clients

Projects of ONAP that are definitely clients of AAI including:

DCAE (evidenced by https://gerrit.onap.org/r/#/c/73148/ change for rest-services/aai-client component)
APPC and CCSK (evidenced by
Jira
server ONAP JIRA
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CCSDK-740
/
Jira
server ONAP JIRA
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key CCSDK-741
bug for named-query and XSD schema of response data)
VID (evidenced by https://lists.onap.org/g/onap-discuss/topic/openlab_vid_beijing_how/28275492 query for SDC models by distribution status)
- but also VID is removing some AAI model POJOs
  Jira
  server ONAP JIRA
  serverId 425b2b0a-557c-3c0c-b515-579789cceedb
  key VID-361
  but not all POJOs https://gerrit.onap.org/r/gitweb?p=vid.git;a=tree;f=vid-app-common/src/main/java/org/onap/vid/aai
POMBA (sub-project of Logging) uses AAI-Validation, which uses schema-ingest
Jira
server ONAP JIRA
serverId 425b2b0a-557c-3c0c-b515-579789cceedb
key AAI-2295

Projects of ONAP that are likely clients of AAI including:

CLAMP, DMaaP, ExtAPI, Holmes, MSB, MultiVIM, OOM, Policy, Portal, SDC, SO, SDNC, VFC, VNFSDK, UUI

producer-consumer pairings

Apart from "internal" AAI data, the data in AAI is produced by a non-AAI component and then consumed by another non-AAI component. Therefore the schema definitions and intended meanings of each schema element is are not controlled by AAI itself.

Example1 in "service-instance" the "input-parameters" attribute is a "String capturing request parameters from SO to pass to Closed Loop.", so it is an SO-to-CLAMP pairing. See also reference id AAI-1353-2 in AAI-CCVPN Schema Proposal for Casablanca Release and AAI discussion on 2018-11-28 ExtAPI Meeting notes

Example2 in

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	VFC-1193

/

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	OPTFRA-268

/

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	OPTFRA-291

, there is an OOF-to-VFC pairing for this scenario:

VFC component sources the "flavor name" from OOF component
Then VFC searches AAI using "flavor name" to find the corresponding "flavor id"
Finally "flavor id" is used to create a VM
See also discussion at https://lists.onap.org/g/onap-oof/topic/critical_issue_found_in/28277232

Example3 in https://lists.onap.org/g/onap-discuss/topic/openlab_vid_beijing_how/28275492, there is SDC-to-VID pairing for this scenario:

SDC distributes models into AAI

Then VID calls custom query in AAI to get models by distribution status

Finally VID uses models for its functions (this is the main flow for VID)

See examples in AAI Schema Producer-Consumer Pairings

deployment tools

Tools (e.g. Helm, ansible, Docker Compose, etc) used to:

place the microservices into their run-time environment
distribute data files for initial configuration
perform the initial configuration of microservices
get the ONAP system running as intended

IDL Files

Some form of "Interface Definition Language" which unifies and replaces the OXM files and EdgeRule files as definition of AAI schema

Purple highlights

Highlight change from predecessor ONAP Release

...

Space shortcuts

Page tree

Versions Compared

Old Version 31

New Version Current

Key