Page Comparison

...

Let's take more complicated example of path  In this case I would like to look at paths containing l-interface and lag-interface. There are paths defined by AAI API that contain both of these resources. For this exercise I will narrow down paths by focusing on paths that start with generic-vnf and end with l3-interface-ipv6-address-list.  There are 2 paths like that. They are:

/aai/v11/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}                                                                                                                                                  
/aai/v11/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address} 

These 2 paths differ by one element, which is vlan.

To uniquely identify first path we need following list of FQOIDs:

• generic-vnf.vnf-id
• lag-interface.interface-name
• l-interface.interface-name
• l3-interface-ipv6-address-list.3-interface-ipv6-address

To uniquely identify second path we need to add FQOID for vlan, so the list of FQOIDs will be:

• generic-vnf.vnf-id
• lag-interface.interface-name
• l-interface.interface-name
• vlan.vlan-interface
• l3-interface-ipv6-address-list.3-interface-ipv6-address

So the final request key string for first path will be:

<get-resource plugin="org.onap.ccsdk.sli.adaptors.aai.AAIService"
resource="l3-interface-ipv6-address-list"
key="generic-vnf.vnf-id = $tmp.val1 AND lag-interface.interface-name = $tmp.val2 AND l-interface.interface-name = $tmp.val3 AND l3-interface-ipv6-address-list.3-interface-ipv6-address = $tmp.val4"
...