| Section | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
In client code using AAI API, make use of "nodes query" as shown in newly published documentation to optimise some queries on AAI data:
- https://docs.onap.org/en/latest/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/nodesQuery.html
- Ludovic Robert For example instead of
- "GET /aai/v11/customers/{customerId}service-subscription/{service_subscriptionId}service-instance API/{service-instanceId}"
- use "GET /aai/v11/nodes/service-instances/service-instance/{service-instanceId}" instead
From Jimmy Forsyth (AT&T) to Everyone: 01:51 AM
@Adrian the answers are yes, service-instance-id is unique in ONAP and you can query it directly with the nodes query (see link above)
- See also
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-194
- https://docs.onap.org/en/latest/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/nodesQuery.html
...
- Attributes and EdgeRules to add to "cp", "generic-vnf" and "pnf" (options TBD):
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2154 - Stavros Kanarakis to add specific decisions made for each attribute based on the options described in JIRA
- Attributes and EdgeRules to add to "cp", "generic-vnf" and "pnf" (options TBD):
| BBS Use Case Reference |
|---|
| A&AI Implementation Decision | A&AI Schema Impact | Possible Future Work | |
|---|---|---|---|
| RG MAC Address | Metadata Entry (under HSIA CFS Service Instance) CPE PNF object relates to it Internet Profile Generic-VNF relates to it | None | |
| Service Type | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | None | |
| Access ID | Metadata Entry (under HSIA Internet Service Instance) | None | |
| Upstream Speed | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | None | |
| Downstream Speed | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | None | |
OLT Name | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it OLT_NNI cp relates to it | None | |
| OLT PON port | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | None | |
| OLT PON slot | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | None | |
CVLAN | |||
| SVLAN | |||
| Expected ONT ID | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | None | |
| CPE Manufacturer | PNF object equip-vendor: string | None | |
| CPE Model | PNF object equip-model: string | None | |
| CPE Equipment Type | PNF object equip-type: string | None | |
| CPE Serial Number | PNF object serial-number: string | None | |
| CPE SW Version | PNF object sw-version: string | None | |
Attachment Point (Not a real model property, since its constituent parts are captured in other model properties) | PNF object attachment-point: string | New PNF object property |
Item 7. Other current work
...
- Referring to https://groups.io/g/onap-bbs/message/151: how to distinguish, from the AAI-EVENT alone, what part of the “service-instance” object changed, and what was it changed from.
- tbc