Page Comparison

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
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CCSDK-740

  /

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 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)

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

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.

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.

Example2 in

• 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)