BBS Integration Testing
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-2166 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-2165 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-2167 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2776 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2827 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2955 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CCSDK-2399 |
---|
|
BBS Development Status
Project | PTL | JIRA Epic / User Story* | Requirements |
---|
SO | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1938 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2608 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2609 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1994 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2611 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2668 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-2672 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-134 |
---|
|
| |
DCAE | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1990 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1918 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1583 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-2047 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-2088 |
---|
|
|
|
SDNC | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDNC-1021 |
---|
|
|
|
Policy | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | POLICY-2333 |
---|
|
https://gitlab.com/onap-bbs/apex-policy/issues/1 | Notes: BBS apex policy will not be included in Policy repository. We need to find out another (External?) repository for it. Let's use gitlab for now |
Integration | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-1444 |
---|
| https://gerrit.onap.org/r/c/integration/+/103110 |
...
Current Issues
Area | Contributor | Issues |
---|
Modeling |
|
Review modeling: Access Connectivity / Internet Profile as VNF? Remove remote-ID/CVLAN/SVLAN... from service metadata |
|
|
AAI/ESR |
|
Register external controllers via ESR/AAI. Investigate topology discovery considerations | Status |
---|
colour | Red |
---|
title | NOT IN FRANKFURT |
---|
|
|
|
Service Orchestration | Lead: Huawei ?- |
Custom BPMN workflow that:
- Reads remote-id/CVLAN/SVLAN from PNF_READY event and not from service attributes stored in AAI
- Updates service instance metadata accordingly
|
| Inter-workflow calls time out after 60s due to HTTP. This invalidates the 14-day timeout for PNF registration |
| Service deletion of E2E services with PNF |
| Remove BBS-event-processor in favor of moving its functionality to Service-Orchestration where it mostly belongs | Status |
---|
colour | Red |
---|
title | NOT IN FRANKFURT |
---|
|
|
|
Policy | |
Migrate current APEX policy for ONT relocation to the new model. This enables the onboarding and activation of BBS policy via REST API |
|
|
DCAE | |
Define proper namespace for CPE Authentication events | Status |
---|
colour | Red |
---|
title | NOT IN FRANKFURT |
---|
|
| Remove the RGW MAC validation from BBS-event-processor microservice |
| Issues with RESTCONF Collector (RCC) | | DCAE service components (RESTCONF Collector & BBS-event-processor) are manually started inside Cloudify platform of DCAE - May be mandated by ONAP community to start these via CLAMP and certain Policy related data being injected into them dynamically
- May be mandated by ONAP community to adhere to some development standards that are now missing
- For BBS-event-processor also check item 'AAI - Register external controllers via ESR/AAI' above.
Status |
---|
colour | Red |
---|
title | NOT IN FRANKFURT |
---|
|
| Use CLAMP for BBS policy: Status |
---|
colour | Yellow |
---|
title | Stretched for FRANKFURT |
---|
|
|
|
SDN-C | | |
Testing | |
Provide lab environment for integration testing with multi-vendor OLT/ONT/Access SDN M&C |
| Support for integration testing |
| Enable automated testing of BBS use case via Robot (emulator of Access SDN M&C is needed for this) | Status |
---|
colour | Yellow |
---|
title | Stretched for FRANKFURT |
---|
|
|
|
Documentation | |
Improve documentation on BBS use case provisioning |
|
|
Demo | Lead: UNH-IOL / Swisscom |
BBS use case provisioning should be fully automated |
| Enhance BBS Portal to remove hard-coded segments and make it more user-friendly |
| Choose an appropriate allocation scheme for Remote-ID/CVLAN/SVLAN and remove the demo-oriented static mappings and PORT-VLAN calculation algorithm
- Circuit-ID should be read from PNF events provided by the BNG, providing access to/notification of this information in the operator OSS/BSS
- VES notifications from BNG rely on demo specific SourceNames, which will not be available to a BNG within a typically deployment.
|
|
BBS Development Status
Project | PTL | JIRA Epic / User Story* | Requirements |
---|
SO | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1938 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1994 |
---|
|
Note: we need to split SO-1938 in multiple tickets | DCAE | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | DCAEGEN2-1990 |
---|
|
| SDNC | | Integration | Morgan Richomme