closed-loop
The "closed-loop" query allows a client to provide A&AI a vserver and retrieve the other data needed as input to the closed loop action, such as the related VNF, service instance, VF modules, tenant and cloud region.
This query is meant to replace the named query "closed-loop-named-query", which had named query uuid "4ff56a54-9e3f-46b7-a337-07a1d3c6b469". The format closest to the original query can be achieved with ?format=simple
Input | Output | Users | Release(s) |
|---|---|---|---|
vserver | vserver generic-vnf model-ver model service-instance vf-module tenant cloud-region |
| Dublin |
Details
Example payload
{
"start" : "/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}",
"query" : "query/closed-loop"
}
The Traversal
Only objects at the end of a line will be returned.
vserver
vserver > generic-vnf
generic-vnf > model-ver
model-ver > model
generic-vnf > service-instance
service-instance > model-ver
model-ver > model
service-instance > generic-vnf
generic-vnf > vf-module
vf-module > model-ver
model-ver > model
vserver > tenant
tenant > cloud-region
Example Output
Hi Jimmy,
there are two requirements we see in closed loop. it would be great if following are supported.
Given IP address of the VM & Cloud-region-ID as input, A&AI returning ONAP identification information about VM, VNF instance it belongs to, service instance it belongs to and service it belongs to.
Given ID (VM ID as given by VIM) and Cloud-region-id as input, A&AI returns ONAP identification information about that VM, VNF instance, Service instance and service itself
Srini