You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 37
Next »
BBS Development Status
Project | PTL | JIRA Epic / User Story* | Requirements |
---|
SO | |
SO-1938
-
Getting issue details...
STATUS
SO-2608
-
Getting issue details...
STATUS
SO-2609
-
Getting issue details...
STATUS
SO-1994
-
Getting issue details...
STATUS
SO-2611
-
Getting issue details...
STATUS
SO-2668
-
Getting issue details...
STATUS
SO-2672
-
Getting issue details...
STATUS
REQ-134
-
Getting issue details...
STATUS
| |
DCAE | |
DCAEGEN2-1990
-
Getting issue details...
STATUS
DCAEGEN2-1918
-
Getting issue details...
STATUS
DCAEGEN2-1583
-
Getting issue details...
STATUS
DCAEGEN2-2047
-
Getting issue details...
STATUS
DCAEGEN2-2088
-
Getting issue details...
STATUS
|
|
SDNC | |
SDNC-1021
-
Getting issue details...
STATUS
|
|
Policy | | | 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 | | |
|
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 | 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 | 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 | 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. NOT IN FRANKFURT
| Use CLAMP for BBS policy: 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) | 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.
|
|
|