Review modeling: Access Connectivity / Internet Profile as VNF? Remove remote-ID/CVLAN/SVLAN... from service metadata 

Register external controllers via ESR/AAI. Investigate topology discovery considerations

NOT IN FRANKFURT

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

NOT IN FRANKFURT

Migrate current APEX policy for ONT relocation to the new model. This enables the onboarding and activation of BBS policy via REST API

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)

Done

from @... :

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

1. May be mandated by ONAP community to start these via CLAMP and certain Policy related data being injected into them dynamically

2. May be mandated by ONAP community to adhere to some development standards that are now missing

3. 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

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). 

SO has changed its logic so that for Access-Connectivity and Internet-Profile VFs it no longer calls the ‘network-topology-operation’ which was the entry SDN-C Directed Graph (DG) we were using in Dublin. That DG contained the logic to trigger BBS use case code in SDN-C.

Instead, for these VFs, it now triggers the ‘vnf-topology-operation’ DG because they are marked as resources of type VNF. It only calls ‘network-topology-operation’ for resources other than VNF/GROUP/ALLOTED_RESOURCE.

See: https://github.com/onap/so/blob/elalto/bpmn/so-bpmn-infrastructure-common/src/main/groovy/org/onap/so/bpmn/infrastructure/scripts/CreateSDNCNetworkResource.groovy

Reevaluate the SDN-C technical-debt implementation (choosing between Access SDN M&C vendors based on flags found in core DGs). See CreateAccessConnectivityInstance in https://git.onap.org/sdnc/oam/tree/platform-logic/generic-resource-api/src/main/xml/GENERIC-RESOURCE-API_network-topology-operation.xml?h=dublin 

Develop a BBF WT-411 standards based DG for the Use case in the Access and Edge

Stretched for FRANKFURT

Update service attributes after PNF re-registration using SDNC DG. Current DG fails to do so

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

Improve documentation on BBS use case provisioning

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

1. Circuit-ID should be read from PNF events provided by the BNG, providing access to/notification of this information in the operator OSS/BSS

2. VES notifications from BNG rely on demo specific SourceNames, which will not be available to a BNG within a typically deployment.