Versions Compared

Old Version 1

changes.mady.by.user David Perez Caparros

Saved on

compared with

New Version 2

changes.mady.by.user David Perez Caparros

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
titleWork in Progress
Work in Progress

Current Issues

AreaContributorIssues 
AAI/ESRLead: ?- Register external controllers via ESR/AAI. Investigate topology discovery considerations.
Service OrchestrationLead: Huawei?

- Custom BPMN workflow that:
1) reads remote-id/CVLAN/SVLAN from PNF_READY event and not from service attributes stored in AAI
2) 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

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.
DCAELead: Nokia / Huawei- Define proper namespace for CPE Authentication events
- 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.

A) May be mandated by ONAP community to start these via CLAMP and certain Policy related data being injected into them dynamically
B) May be mandated by ONAP community to adhere to some development standards that are now missing
C) For BBS-event-processor also check item 'AAI - Register external controllers via ESR/AAI' above.

SDN-CLead: Nokia- the BBS use case was broken in when the SO team issued a bug fix (SO-1393). The correct SDN-C graph (network-topology-operation) is no longer called (This may imply reviewing BBS modeling)
- Reevaluate the SDN-C technical-debt implementation (choosing between Access SDN M&C vendors based on flags found in core DGs)
- Develop a BBF WT-411 standards based DG for the Use case in the Access and Edge
TestingLead: 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)
DocumentationLead: Swisscom- Improve documentation on BBS use case provisioning
Demo

- 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
A) Circuit-ID should be read from PNF events provided by the BNG, providing access to/notification of this information in the operator OSS/BSS
B) VES notifications from BNG rely on demo specific SourceNames, which will not be available to a BNG within a typically deployment.

...