Page Comparison

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

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)

Projects of ONAP that are likely clients of AAI including:

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

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

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