Area | Contributor | Issues |
---|
Modeling |
|
Review modeling: Access Connectivity / Internet Profile as VNF? Remove remote-ID/CVLAN/SVLAN... from service metadata |
|
|
AAI/ESR | Lead: ? |
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 | Lead: Huawei? |
Migrate current APEX policy for ONT relocation to the new model. This enables the onboarding and activation of BBS policy via REST API |
|
|
DCAE | Lead: Nokia / Huawei | |
SDN-C | Lead: Nokia |
|
Testing | Lead: Swisscom / UNH-IOL |
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 | Lead: Swisscom |
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.
|
|
|