Versions Compared

Old Version 19

changes.mady.by.user Keong Lim

Saved on

compared with

New Version 20

changes.mady.by.user Keong Lim

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TermDefinition
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 Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-740
    /
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCCSDK-741
    bug for named-query and XSD schema of response data)

Projects of ONAP that are likely clients of AAI including:

  • CLAMP, DMaaP, ExtAPI, Holmes, MSB, MultiVIM, OOM, Policy, Portal, SDC, SO, SDNC, VFC, VNFSDK, VID, 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 not controlled by AAI itself.

For example, 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.

Example2 in

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVFC-1193
, 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


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 highlightsHighlight change from predecessor ONAP Release

...