| 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) | from Former user (Deleted) : The actual fix DCAEGEN2-1644 https://gerrit.onap.org/r/#/c/dcaegen2/collectors/restconf/+/90759/
But we just can’t cherry pick above one since code changes traced back to below two fixes. So we have to take these too. DCAEGEN2-1587 https://gerrit.onap.org/r/#/c/dcaegen2/collectors/restconf/+/89117/
DCAEGEN2-1511 https://gerrit.onap.org/r/#/c/dcaegen2/collectors/restconf/+/88053/ | 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)
| 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.
|
|
|