| 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 | ||||||
|---|---|---|---|---|---|---|
|
- Get the full URL of the service-instance object when using the Nodes query to retrieve it.
- Pass query parameter "?format=resource_and_url" or "?format=simple"
Item 6. Specific decisions made for each attribute
Refer to BBS Modeling Model Design diagram for "HSIA CFS":
...
|
Item 5. Use “format” query parameter on Node Query to find service instance hierarchy
Refer to discussion https://lists.onap.org/g/onap-discuss/message/15390 on https://lists.onap.org/g/onap-discuss/topic/29688799 and
| Jira Legacy | |||||
|---|---|---|---|---|---|
|
...
|
...
- Stavros Kanarakis to add specific decisions made for each attribute based on the options described in JIRA
...
Metadata Entry
(under HSIA CFS Service Instance)
CPE PNF object relates to it
Internet Profile Generic-VNF relates to it
...
Metadata Entry
(under HSIA CFS Service Instance)
Access Connectivity Generic-VNF relates to it
...
Metadata Entry
(under HSIA Internet Service Instance)
...
Metadata Entry
(under HSIA CFS Service Instance)
Access Connectivity Generic-VNF relates to it
...
Metadata Entry
...
|
- Get the full URL of the service-instance object when using the Nodes query to retrieve it.
- Pass query parameter "?format=resource_and_url" or "?format=simple"
Item 6. Specific decisions made for each attribute
Refer to BBS Modeling Model Design diagram for "HSIA CFS":
- 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 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) | Access Connectivity Generic-VNF CPE PNF object relates to it Internet Profile Generic-VNF relates to it | Metadatum EdgeRules only | ||||||||||||||||
| OLT NameService Type | Metadata Entry (under HSIA Access CFS Service Instance) PON_UNI cp Access Connectivity Generic-VNF relates to it OLT_NNI cp Internet Profile Generic-VNF relates to itit | Metadatum EdgeRules only | |||||||||||||||||
| OLT PON portAccess ID | Metadata Entry (under HSIA Access Internet Service Instance) PON_UNI cp relates to it | Metadatum EdgeRules only | |||||||||||||||||
| OLT PON slotUpstream Speed | Metadata Entry (under HSIA Access CFS Service Instance) PON_UNI cp Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | Metadatum EdgeRules only | |||||||||||||||||
| CVLANDownstream Speed | Metadata Entry (under HSIA Access CFS Service Instance) PON_UNI cp Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to it | Metadatum EdgeRules only | |||||||||||||||||
| SVLAN OLT Name | Metadata Entry (under HSIA Access Service Instance) OLTPON_NNI UNI cp relates to it Metadatum OLT_NNI cp relates to it | Metadatum EdgeRules only | |||||||||||||||||
| Expected ONT IDOLT PON port | 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 | 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-typevendor: string | None | |||||||||||||||||
| CPE Serial NumberModel | PNF object serialequip-numbermodel: string | None | |||||||||||||||||
| CPE SW VersionEquipment Type | PNF object sw-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) attachmentlink-pointname: string | New PNF object property | ONT NNI Port (Not sure if we need it. Could be hard-coded) | ? | OLT NNI Slot (Not sure if we need it) | ? | OLT NNI Port (Not sure if we need it) | ? | BNG Name (Static configuration. Put into A&AI via a script)(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 Edge Access Service Instance) BNG Generic-VNF ONT_NNI cp relates to it | Metadatum EdgeRules only | |||||||||||||||||
BNG UNI OLT NNI Slot (Static configuration. Put into A&AI via a script) | Metadata Entry (under HSIA Edge Access Service Instance)BNG-UNI | Metadatum EdgeRules only | |||||||||||||||||
BNG UNI Port (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 |
Item 7. Other current work
...
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 |
Moving forward based on https://groups.io/g/onap-bbs/message/160
and https://groups.io/g/onap-bbs/message/161
Item 7. Add robot test cases
- BBS use case related items added for AAI to https://gerrit.onap.org/r/gitweb?p=testsuite.git;a=tree;f=robot/resources/aai;hb=HEAD
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2184
Item 8. Other current work
tbc
Various Discussion List Messages
- AAI relationship-list https://lists.onap.org/g/onap-discuss/message/15607
- PNF change https://lists.onap.org/g/onap-discuss/message/15640
- BBS use case mapping https://lists.onap.org/g/onap-discuss/message/15683 / https://lists.onap.org/g/onap-discuss/message/15726
- BBS use case data relationships https://lists.onap.org/g/onap-discuss/message/15731
Possible Future 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