...
Refer to discussion on https://groups.io/g/onap-bbs/topic/29523804 . Possible extra field in PNF to assist nomadic ONT scenario.
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Item 4. Change PNF unique key to be pnf-id
...
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
See also item 6 below:
...
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 | ||||||
|---|---|---|---|---|---|---|
|
| Jira | ||||||
|---|---|---|---|---|---|---|
|
- 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 | |
|---|---|
|
|
...
|
...
- Stavros Kanarakis to add specific decisions made for each attribute based on the options described in JIRA
|
- 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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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 | |||||||||||
| BBS Properties Use Case Reference | A&AI Implementation Decision | A&AI Schema Impact | Possible Future Work | ||||||||
| RG MAC Address | Metadatum EdgeRules only | Service Type | Metadatum EdgeRules only | Access ID | Metadata Entry (under HSIA Internet Service Instance) | Metadatum EdgeRules only | Upstream SpeedMetadata 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 | ||
| Downstream SpeedService Type | Metadata Entry (under HSIA CFS Service Instance) Access Connectivity Generic-VNF relates to it Internet Profile Generic-VNF relates to itit | Metadatum EdgeRules only | |||||||||
| OLT NameAccess ID | Metadata Entry (under HSIA Access Internet Service Instance) PON_UNI cp relates to it OLT_NNI cp relates to it | Metadatum EdgeRules only | |||||||||
| OLT PON portUpstream 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 | |||||||||
| OLT PON slotDownstream 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 | |||||||||
CVLANOLT 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 | Metadatum EdgeRules only | SVLAN | Metadata Entry (under HSIA Access Service Instance) OLTPON_NNI UNI cp relates to it | Metadatum EdgeRules only | |||||||
| Expected ONT IDOLT 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 | 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 (bound 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') CPE PNF object relates to it | None (EdgeRule logical-link-to-pnf already exists)
| |||||||||
ONT NNI Port (Not sure if we need it. Could be hard-coded) | Metadata Entry (under HSIA Access Service Instance) ONT_NNI cp relates to it | Metadatum EdgeRules only? | |||||||||
OLT NNI Slot (Not sure if we need it) | Metadata Entry (under HSIA Access Service Instance) | Metadatum EdgeRules only? | |||||||||
OLT NNI Port (Not sure if we need it) | 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 |
Item 7. Add robot test cases
...
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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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
...
...
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Item 8. Other current work
...
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
...