Page Comparison

...

DCAE VES event  A&AI enrichment for previous use cases are defined here as reference.  The following describe those supporting CCVPN Closed Loop, 

Note:  pnfName = Nodeid and p-interface-name = tp-id

• The query logic from tp-id through service instance is that : p-interface   →   vpn-vpnbinding →  connectivity → service instance.  Then from service-instance to 'customer-request' for service instance recreation for phase 1.
• For event from different tp-id to be correlated:  p-interface →  logical link, then logic link is the same from ONAP domain.
• When link down event is detected, Closed Loop needs to update logical-link/p-interface's operational-status to “DOWN” for the recreated service instance picking up new links.

The following APIs are used to support the above looking up.

URL: https://<AAI host>:<AAI port>/aai/v14/network/connectivities/connectivity/{connectivityId}
Method: Get
Response  Body:
{
...
"access-ltp-id":"ltp id",
...
"relationship-list":{
    "relationship" : [
       {
           "related-to" : "service-instance",
           "related-link" : "url of service-instance",
           "relationship-data": [
              "relationship-key" : "service-instance.service-instance-id",
              "relationship-value": "some id"
            ]
       },
       {
           "related-to" : "",vpn-binding
           "related-link" : "url of vpn-binding",
           "relationship-data": [
              "relationship-key" : "vpn-binding.vpn-binding-id",
              "relationship-value": "some id"
            ]
       }
      ]
   }
}

...