JIRA Labels
The Epics and Stories generated for the BBS Use Case should use one or more of the following labels:
- "BBS: Topology Discovery" (Used for issues related to the discovery and synchronization of the Broadband Service elements)
- "BBS: HSIA Service" (Used for lifecycle issues related to the lifecycle of a HSIA service (creation, activation, deletion)
- "BBS: Nomadic ONT" (Used for issues related to the registration and re-registration of the ONT; RG Activation)
All labels for BBS stories and epics should be pre-pended with "BBS: "
As more functionality is added to the BBS Use case new labels are expected to be defined.
These labels can be used as filters for looking at the work effort related to BBS.
Development Status
Project | PTL | JIRA Epic / User Story* | Requirements |
---|
AAI | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-1990 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-1996 |
---|
|
| AAI-BBS Proposals for Dublin Release |
CLAMP | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CLAMP-270 |
---|
|
|
|
DCAE | Vijay Venkatesh Kumar | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1057 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1055 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1056 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1059 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1060 |
---|
|
|
|
External API | Matthieu Geerebaert | EXTAPI-98 - Add notification for serviceInventory API IN PROGRESS
| Support for TMF 638 ServiceStateChangeNotification or ServiceAttributeValueChangeNotifications |
Modeling | |
|
|
Policy | | | |
SDNC | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-614 |
---|
|
| Update SDNC DG generic-resource-API with new DGs from BBS |
SO | | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1392 |
---|
|
|
|
*Each Requirement should be tracked by its own User Story in JIRA
Testing
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
Integration Team Liaison: Yang Xu
VNF/PNF
List of VNF/PNFs that the BBS use case will use
Showcase VNF/PNF | Provider | Test Environment |
---|
Integration Team Liaison | End to End flow to be Tested
| Comment |
---|
vBNG/vAAA/DHCP [VNF] | Swisscom, open source | Swisscom Lab | Considered as infrastructure and accessible through 3rd party controller (not deployed by ONAP) |
CPE (ONT+RG) [PNF] | Huawei, Nokia | Swisscom Lab, Nokia Lab | Accessible through Access SDN M&C (3rd party controller) |
OLT [PNF] | Huawei, Nokia | Swisscom Lab, Nokia Lab | Accessible through Access SDN M&C (3rd party controller) |
NFVI+VIM
NFVI+VIM | Provider |
---|
OpenStack | Swisscom (OPNFV Fraser) |
Access SDN M&C (3rd party controller) | Huawei, Nokia |
Edge SDN M&C (3rd party controller) | Swisscom |
**This should be a summary level Sequence diagram done in Gliffy** Test Cases and Status [WIP]
# | Test Case | Status |
---|
A | External System Registration |
1 |
There should be a test case for each item in the sequence diagram. Access SDN M&C registration | |
2. Edge SDN M&C registration | |
3. Manually inventory vBNG and transport link in AAI | |
4. BBS portal listener registration in ExternalAPI | |
B | PNF Onboarding and Service Creation & Distribution |
1. CPE (ONT+RG) onboarding in SDC | |
2 |
create additional requirements as needed for each discreet step | | . HSIA service creation | |
3. HSIA service distribution | |
C | Service Instantiation and Activation |
1. HSIA service instantiation | |
2. CPE registration | |
3. CPE authentication | |
4. HSIA service state change notification | |
D | Service Reconfiguration (Nomadic ONT) |
1. CPE PNF re-registration | |
2. HSIA service reconfiguration | |
3. CPE authentication (after relocation) | |
4. HSIA service state change notification (relocation) | |
E | Service Termination |
1. Terminate service instance and associate resources | |
3 | Test cases should cover entire Use Case | Status |
---|
colour | Yellow |
---|
title | Partially Complete |
---|
|
|
4 | Test Cases should include enough detail for testing team to implement the test | Status |
---|
colour | Red |
---|
title | Failed