| 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
...
Refer to discussion on https://groups.io/g/onap-bbs/topic/29523804 . Possible extra field in PNF to assist nomadic ONT scenario.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Item 4. Change PNF unique key to be pnf-id
Change PNF unique key to be pnf-id instead of pnf-name attribute: Jira Legacy
Attachment Point (Not a real BBS modeling property, since its constituent parts are captured in other model properties) | Logical Link object (bridged to the PNF object representing ONT) link-name: string (will hold attachment point in the form of olt-name/pon-slot/pon-port e.g. olt1/1/1) link-type: string (will hold literal value 'attachmentPoint') | None (EdgeRule logical-link-to-pnf already exists)
|
Item 4. Change PNF unique key to be pnf-id
Change PNF unique key to be pnf-id instead of pnf-name attribute:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| BBS Properties 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 | Metadatum EdgeRules only | |||||||||
| Service Type | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | Metadatum EdgeRules only | |||||||||
| Access ID | Metadata Entry (under HSIA Internet Service Instance) | Metadatum EdgeRules only | |||||||||
| Upstream Speed | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | Metadatum EdgeRules only | |||||||||
| Downstream Speed | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | Metadatum EdgeRules only | |||||||||
OLT Name | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it OLT_NNI cp relates to it | Metadatum EdgeRules only | |||||||||
| OLT PON port | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | Metadatum EdgeRules only | |||||||||
| OLT PON slot | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | Metadatum EdgeRules only | |||||||||
CVLAN | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | Metadatum EdgeRules only | |||||||||
| SVLAN | Metadata Entry (under HSIA Access Service Instance) OLT_NNI cp relates to it | Metadatum EdgeRules only | |||||||||
| Expected ONT ID | Metadata Entry (under HSIA Access Service Instance) PON_UNI cp relates to it | Metadatum EdgeRules only | |||||||||
| 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 BBS modeling property, since its constituent parts are captured in other model properties) | Logical Link object (bridged to the PNF object representing ONT) link-name: string (will hold attachment point in the form of olt-name/pon-slot/pon-port e.g. olt1/1/1) link-type: string (will hold literal value 'attachmentPoint') | None (EdgeRule logical-link-to-pnf already exists)
| |||||||||
ONT NNI Port | Metadata Entry (under HSIA Access Service Instance) ONT_NNI cp relates to it | Metadatum EdgeRules only | |||||||||
OLT NNI Slot | Metadata Entry (under HSIA Access Service Instance) | Metadatum EdgeRules only | |||||||||
OLT NNI Port | Metadata Entry (under HSIA Access Service Instance) | Metadatum EdgeRules only | |||||||||
BNG Name (Static configuration. Put into A&AI via a script) | Metadata Entry (under HSIA Edge Service Instance) BNG Generic-VNF relates to it | Metadatum EdgeRules only | |||||||||
BNG UNI Slot (Static configuration. Put into A&AI via a script) | Metadata Entry (under HSIA Edge Service Instance) BNG-UNI cp relates to it | Metadatum EdgeRules only | |||||||||
BNG UNI Port (Static configuration. Put into A&AI via a script) | Metadata Entry (under HSIA Edge Service Instance) BNG Generic-VNF relates to it | Metadatum EdgeRules only |
...
- 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