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
« Previous
Version 6
Next »
Contributors
Glossary
| Term | Definition |
|---|
| 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.
|
References
Producer-Consumer Pairs
| Producer | Consumer | AAI Representation | Scenario and References |
|---|
| 1 | SO | Closed Loop | the "input-parameters" attribute of "service-instance" object described as: "String capturing request parameters from SO to pass to Closed Loop." | Closed loop scenario: - SO will create “service-instance” object in AAI
- SO will store “customer-request” string on service-instance object in AAI
- When Closed Loop call recreates the “service-instance”, it will query “service-instance” information first, to get the “customer-request”
References |
| 2 | SO | ExtAPI | (see above?) | (see above?) |
| 3 | OOF | VFC | - the "flavor name" attribute of "flavor" object
- the "flavor id" attribute of "flavor" object
| 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
References |
| 4 | SDC | VID | - /service-design-and-creation/models
- custom query
| 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)
References |
| 5 | Multi-VIM / Cloud | OOF | - /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones
| Scenario: - Multi-VIM / Cloud collects Availability-Zone capacity data from Clouds into AAI
- OOF retrieves Availability-Zone information of each Cloud Region from AAI
- OOF makes homing / placement decisions for VNFs to support "teaming" use case
References |
| 6 | MultiCloud | OOF | | Scenario: - MultiCloud collects HPA telemetry/time-series data into AAI
- OOF retrieves telemetry from AAI
- OOF makes decisions based on the telemetry
References: |
| 7 | VNFM / ESR | VIM / VFC | Question: - is it just a URL to a certificate file?
- or is it the literal contents of a certificate file?
| Scenario: - VIM is registered to ESR including SSL certificates
- VNFM is registered to ESR including SSL certificates
- VFC retrieves connection details including SSL certificates
- VFC logs in to perform its control functions
References: -
AAI-1104
-
Getting issue details...
STATUS
|
| 8 | VID / SO / SDNC / OOF MultiCloud CLAMP / DCAE / DMaaP | VID / SO / SDNC / OOF MultiCloud CLAMP / DCAE / DMaaP | - /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}
- ‘cloud-region-id’ used in VID/SO/SDNC/OOF
‘cloud-owner’ + ’cloud-region-id’ used by AAI and its consumers ‘vim-id’ = {‘cloud-owner’}_{‘cloud-region-id’} used by MultiCloud and its consumers dcaeLocation used by CLAMP, DCAE and DMaaP
|
|
| 9 | tbc | etc |
|
|