As an A&AI user, I need custom queries in support of vCE resiliency automation, so that I can query for the vPE connected to a vCE, A&AI stored values needed for an SO recreate request, and for vCEs on a particular physical host.

A&AI will...

• Create a custom query to identify the connected vPE for a given vCE (or the connected generic-vnfs/vservers for any given generic-vnfs/vservers, respectively). This relationship can be determined by traversing the interface stack and logical-link between the two virtual devices.

This "linked-devices" query should be limited to lookups between virtual devices (VNFs or VMs). The same traversal should satisfy both a VNF or VM start node, since they reuse the same lag-interface/l-interface/logical-link or l-interface/logical-link structures and edges.

In the future this query could be enhanced to include physical devices.

• Create a custom query that retrieves the generic-vnf, related model-ver, service-instance related model-ver and tenant for a given AIC 3.x vCE (or any other generic-vnf). POLO needs the attributes to create an MSO request but not the relationships, so they could run this query node only.

• Create a "vnfs-fromPserver" query that retrieves all generic-vnfs of a particular type for a given pserver. For now this query should take vnf-type as its input parameter, but this should really take some combination of nf-type, nf-function, nf role and/or nf-naming-code as additional inputs. vnf-type is targeted for deprecation.