Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Contributors
Use Case Outlines
| Use Case Summary | ONAP Release Target |
|---|
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 upon microservice startup
| Amsterdam, Beijing |
AAI Schema - 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 upon microservice startup
| Casablanca |
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 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 upon ONAP-project-clients startup
| 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 upon AAI Schema Service startup
- distributed via run-time API to AAI-internal-clients
- effective 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 upon ONAP-project-clients startup
| 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 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 deployment tools to ONAP-project-clients without change to JAR files
- effective upon ONAP-project-clients startup
| 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 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 startup
| 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 via run-time API to ONAP-project-clients
- effective upon ONAP-project-clients run-time refresh
| G release and beyond |
|
|