Versions Compared

Old Version 7

changes.mady.by.user Keong Lim

Saved on

compared with

New Version 8

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 clients of schema services including:

  • babel, cacher, chameleon, champ, data-router, eis, enricher, esr, gallifrey, gizmo, graphadmin, graphgraph, logging-service, model-loader, resources, rest-client, router-core, search-data-service, sparky, spike, tabular-data-service, traversal, validation
ONAP-project-clients

Projects of ONAP that are clients of AAI including:

  • CLAMP, DCAE, DMaaP, ExtAPI, Holmes, MSB, MultiVIM, OOM, Policy, Portal, SDC, SO, SDNC, VFC, VNFSDK, VID, UUI
Purple highlightsHighlight change from predecessor ONAP Release


Use Case Outlines

ONAP Release TargetCasablancaDublinFrankfurtG I release and beyond
ONAP Release TargetUse Case SummaryDeprecated Functions
Amsterdam, Beijing

AAI Schema as:

  • single-data-file configuration, i.e. one OXM file and one EdgeRule file
  • distributed via source-code repository to AAI-internal-clients and ONAP-project-clients
  • built into and deployed as microservice JAR file
  • effective only upon microservice startup
Amsterdam, Beijing
Casablanca

AAI Schema as:

  • multiple-data-file configuration, i.e. multiple OXM files and multiple EdgeRule files
  • distributed via source-code repository to AAI-internal-clients and ONAP-project-clients
  • built into and deployed as microservice JAR file
  • effective only upon microservice startup
  • single-data-file configuration
Dublin

AAI Schema as:

  • multiple-data-file configuration
  • distributed via deployment tools to AAI-internal-clients, i.e. multiple OXM files and multiple EdgeRule files
  • deployed as data files to AAI-internal-clients without change to JAR files
    • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients, i.e. XSD files and generated POJOs
  • built into and deployed as ONAP-project-clients JAR file
    • effective only upon ONAP-project-clients startup
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
Dublin

AAI Schema as:

  • multiple-data-file configuration
  • distributed via deployment tools to AAI Schema Service, i.e. multiple OXM files and multiple EdgeRule files
    • effective only upon AAI Schema Service startup
  • distributed via run-time API to AAI-internal-clients
    • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients, i.e. XSD files and generated POJOs
  • built into and deployed as ONAP-project-clients JAR file
    • effective only upon ONAP-project-clients startup
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
  • distributed via deployment tools to AAI-internal-clients
El Alto

AAI Schema as:

  • multiple-data-file configuration
  • distributed via deployment tools to AAI Schema Service, i.e. multiple OXM files and multiple EdgeRule files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time API to AAI-internal-clients
    • effective upon AAI-internal-clients run-time refresh
  • distributed as data files via deployment tools to ONAP-project-clients without change to JAR files
    • effective only upon ONAP-project-clients startup
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
  • distributed via deployment tools to AAI-internal-clients
  • effective only upon AAI Schema Service startup
  • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients
  • XSD files and generated POJOs
El Alto
Frankfurt

AAI Schema as:

  • multiple-data-file configuration
  • distributed via deployment tools to AAI Schema Service, i.e. multiple OXM files and multiple EdgeRule files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time SDC API to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time API to AAI-internal-clients
    • effective upon AAI-internal-clients run-time refresh
  • distributed as data files via deployment tools to ONAP-project-clients without change to JAR files
    • effective only upon ONAP-project-clients startup
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
  • distributed via deployment tools to AAI-internal-clients
  • effective only upon AAI Schema Service startup
  • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients
  • XSD files and generated POJOs
G release

AAI Schema as:

  • multiple-data-file configuration
  • distributed via deployment tools to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time SDC API to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time API to AAI-internal-clients
    • effective upon AAI-internal-clients run-time refresh
  • distributed via run-time API to ONAP-project-clients
    • effective only upon ONAP-project-clients startup
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
  • distributed via deployment tools to AAI-internal-clients
  • effective only upon AAI Schema Service startup
  • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients
  • XSD files and generated POJOs
  • multiple OXM files and multiple EdgeRule files
  • distributed as data files via deployment tools to ONAP-project-clients
H release

AAI Schema as:

  • multiple-data-file configuration
  • distributed via deployment tools to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time SDC API to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time API to AAI-internal-clients
    • effective upon AAI-internal-clients run-time refresh
  • distributed via run-time API to ONAP-project-clients
    • effective upon ONAP-project-clients run-time refresh
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
  • distributed via deployment tools to AAI-internal-clients
  • effective only upon AAI Schema Service startup
  • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients
  • XSD files and generated POJOs
  • multiple OXM files and multiple EdgeRule files
  • distributed as data files via deployment tools to ONAP-project-clients
  • effective only upon ONAP-project-clients startup
H
I release and beyond

AAI Schema as:

  • federation of AAI instances with disjoint schemas and databases
    • facade to stitch disjoint schema and data back into a unified representation
    • schema change and version upgrade by deploying new AAI instance to join federation
    • rolling upgrade and data migration between AAI instances within federation
  • multiple-data-file configuration
  • distributed via deployment tools to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time SDC API to AAI Schema Service, i.e. multiple TOSCA files
    • effective upon AAI Schema Service run-time refresh
  • distributed via run-time API to AAI-internal-clients
    • effective upon AAI-internal-clients run-time refresh
  • distributed via run-time API to ONAP-project-clients
    • effective upon ONAP-project-clients run-time refresh
  • single-data-file configuration
  • distributed via source-code repository to AAI-internal-clients
  • built into and deployed as microservice JAR file
  • distributed via deployment tools to AAI-internal-clients
  • effective only upon AAI Schema Service startup
  • effective only upon AAI-internal-clients startup
  • distributed via source-code repository to ONAP-project-clients
  • XSD files and generated POJOs
  • multiple OXM files and multiple EdgeRule files
  • distributed as data files via deployment tools to ONAP-project-clients
  • effective only upon ONAP-project-clients startup
  • single unified AAI schema and database