| Producer | Consumer | AAI Representation | Scenario and References |
|---|
| 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 |
| SO | ExtAPI | (see above?) | (see above?) |
| 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 |
| 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 |
| 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 |
| tbc | etc |
|
|
