This page will serve as a reference for how to use the A&AI DSL API and commonly used DSL queries.
Before You Start!
It's important that you engage the AAI team before running any adhoc DSL queries. The current process is to have the AAI team vet the DSL queries to make sure the traversal used is optimal and does not cause performance issues in A&AI. As edge rules and schema may change, it is important for clients to communicate the DSL queries that they use. It's important that, at the very least, we know who is using which queries so we can be cautious of changes in the future. And we can help you find the best way to get the data you need.
Getting Started with the DSL API
To execute a DSL query, a client will perform a PUT on the dsl endpoint and include a payload that includes the dsl query to be run. The version dictates which release's REST API version the output will be based on.
PUT /aai/v$/dsl?format={format}
|
When calling the dsl API, the client must specify the output format as a query string. DSL API supports all formats that are supported by custom query API.
count
Provides a count of the objects returned in the query.
Click here to expand...
{
"results": [
{
"generic-vnf": 4,
"p-interface": 1,
"vserver": 3,
"service-instance": 1,
"tenant": 1,
"pserver": 1
}
]
}
|
id
Provides an array of objects containing resource-type (A&AI's node type; i.e., generic-vnf) and a resource-link using the vertex ID from A&AI's graph.
Click here to expand...
{
"results": [
{
"resource-type": "generic-vnf",
"resource-link": "/aai/v16/resources/id/2388112"
},
{
"resource-type": "generic-vnf",
"resource-link": "/aai/v16/resources/id/4694112"
},...]
}
|
pathed
Provides an array of objects containing resource-type (A&AI's node type; i.e., generic-vnf) and a resource-link using the A&AI REST API pathed URIs.
Click here to expand...
{
"results": [
{
"resource-type": "generic-vnf",
"resource-link": "/aai/v16/network/generic-vnfs/generic-vnf/lab20105v"
},
{
"resource-type": "generic-vnf",
"resource-link": "/aai/v16/network/generic-vnfs/generic-vnf/ro-stack01"
},...]
}
|
resource
Provides the each object in the results array in the same format as A&AI's REST API with depth = 1 (first level children and cousin relationships).
Click here to expand...
{
"results": [
{
"complex": {
"physical-location-id": "complex5349-06",
"complex-name": "complexsa-test",
"resource-version": "1485403105490",
"physical-location-type": "Example Location",
"street1": "123 Example Street",
"city": "Example",
"state": "NJ",
"postal-code": "12345",
"country": "USA",
"region": "USA",
"latitude": "30.395968",
"longitude": "-84.135344",
"relationship-list": {
"relationship": [
{
"related-to": "pserver",
"related-link": "https://aai.onap:8443/aai/v16/cloud-infrastructure/pservers/pserver/pserver5349-06",
"relationship-data": [
{
"relationship-key": "pserver.hostname",
"relationship-value": "pserver5349-06"
}
],
"related-to-property": [
{
"property-key": "pserver.pserver-name2"
}
]
}
]
}
}
},...]
}
|
resource_and_url
Provides each object in the results array in the same format as A&AI's REST API with depth = 1 (first level children and cousin relationships) plus the pathed url for the result object in A&AI.
Click here to expand...
{
"results": [
{
"url": "https://aai.onap:8443/aai/v16/cloud-infrastructure/complexes/complex/EXAMPLE_COMPLEX_ID",
"complex": {
"physical-location-id": "EXAMPLE_COMPLEX_ID",
"complex-name": "Example",
"resource-version": "1486837035912",
"physical-location-type": "",
"street1": "123 Mule St",
"city": "MOSCOW",
"state": "RU",
"postal-code": "0",
"country": "RUS",
"region": "EMEA"
}
},...]
}
|
simple
Provides each result object in a simplified format. The node-type, graph vertex id, pathed url, object properties, and directly related objects in the graph are all returned. Both direct parent/child objects and cousin objects are included in the related-to array.
Click here to expand...
{
"results": [
{
"id": "739696712",
"node-type": "generic-vnf",
"url": "https://aai.onap:8443/aai/v16/network/generic-vnfs/generic-vnf/85f60b5e-6eff-49c8-9a79-550ee9eb4806",
"properties": {
"vnf-type": "WX",
"service-id": "d7bb0a21-66f2-4e6d-87d9-9ef3ced63ae4",
"equipment-role": "UCPE",
"orchestration-status": "created",
"management-option": "ONAP",
"ipv4-oam-address": "10.12.14.16",
"ipv4-loopback0-address": "18.20.22.24",
"nm-lan-v6-address": "2001:1890:e00e:fffe::1:2806",
"management-v6-address": "2001:1890:e00e:fffd::773",
"vcpu": 4,
"vmemory": 8,
"vmemory-units": "GB",
"vdisk": 150,
"vdisk-units": "GB",
"in-maint": false,
"is-closed-loop-disabled": false,
"resource-version": "1499958805125",
"vnf-id": "85f60b5e-6eff-49c8-9a79-550ee9eb4806",
"vnf-name": "VNF_NAME"
},
"related-to": [
{
"id": "739700808",
"node-type": "license",
"url": "https://aai.onap:8443/aai/v16/network/generic-vnfs/generic-vnf/85f60b5e-6eff-49c8-9a79-550ee9eb4806/licenses/license/EXAMPLE_LICENSE"
},
{
"id": "411750576",
"node-type": "service-instance",
"url": "https://aai.onap:8443/aai/v16/business/customers/customer/EXAMPLE_CUSTOMER/service-subscriptions/service-subscription/EXAMPLE_SERVICE_SUBSCRIPTION/service-instances/service-instance/EXAMPLE_SERVICE_INSTANCE"
},
{
"id": "15372328",
"node-type": "vnf-image",
"url": "https://aai.onap:8443/aai/v16/service-design-and-creation/vnf-images/vnf-image/78252548-efb6-4b42-9cf7-2b3900c5e7e2"
},
{
"id": "700920024",
"node-type": "vserver",
"url": "https://aai.onap:8443/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/Cloudy/McCloudface/tenants/tenant/EXAMPLE_TENANT/vservers/vserver/EXAMPLE_VSERVER"
}
]
}
]
}
|
Click here to expand...
Let's say you got back a large tree of output in the simple format and need to go through the list of objects to understand their relationships. For example, the output returned vnfs, vservers, pservers and complexes but you want to only look at the results of a particular complex. First, we'll find the JSON object for the complex by looking at the result objects for one with "node-type": "complex" and "physical-location-id": (the CLLI of the location you want to filter on) within the "properties" object. Next you would check the "related-to" object array for objects with "node-type": "pserver", take the "id"s and search for objects with those IDs in the results object array. You can keep crawling through the results in this way until you reach the objects you need. You can use this method for any property you want to filter on.
{
"results": [
...,
{
"id": "14147624",
"node-type": "complex",
"url": "https://aai.onap:8443/aai/v16/cloud-infrastructure/complexes/complex/EXAMPLE_COMPLEX_ID",
"properties": {
...
"physical-location-id": "EXAMPLE_COMPLEX_ID",
...
},
"related-to": [
{
"id": "2134056",
"node-type": "pserver",
"url": "https://aai.onap:8443/aai/v16/cloud-infrastructure/pservers/pserver/EXAMPLE_PSERVER"
},
{
"id": "2158632",
"node-type": "pserver",
"url": "https://aai.onap:8443/aai/v16/cloud-infrastructure/pservers/pserver/EXAMPLE_PSERVER2"
},...
]
},...
]
}
|
graphson
Provides the results using the graphson standard.
Click here to expand...
{
"id": 2213998664,
"label": "vertex",
"outE": {
"hasInstance": [
{
&nbs
|