Versions Compared

Old Version 33

changes.mady.by.user David Perez Caparros

Saved on

compared with

New Version Current

changes.mady.by.user David Perez Caparros

Saved on

Key

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

BBS Integration Testing

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2166

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2165

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2167

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2776

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2827

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2955

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-2399

BBS Development Status 

Project

PTL

JIRA Epic / User Story*

Requirements

SO
Seshu Kumar Mudiganti

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1938

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2608

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2609

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1994

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2611

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2668

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2672

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-134

Note: we need to split SO-1938 in multiple tickets (DONE)

PNF PnP workflow migration to Building Blocks#WaitForPnfReadyBB

DCAE
Vijay Kumar

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1990

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1918

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1583

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2047

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2088


SDNC
Dan Timoney

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-1021


Policy


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2333

https://gitlab.com/onap-bbs/apex-policy/issues/1

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
Morgan Richomme

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-1444
 

https://gerrit.onap.org/r/c/integration/+/103110


Current Issues

AreaContributorIssues 
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
colourRed
titleNOT IN FRANKFURT


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
Status
colourRed
titleNOT IN FRANKFURT


Policy

Former user (Deleted) (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

Stavros Kanarakis (Nokia)


Define proper namespace for CPE Authentication events
Status
colourRed
titleNOT IN FRANKFURT
Remove the RGW MAC validation from BBS-event-processor microservice
Issues with RESTCONF Collector (RCC)

Status
colourGreen
titleDone

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

  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. 
    Status
    colourRed
    titleNOT IN FRANKFURT
Use CLAMP for BBS policy: 
Status
colourYellow
titleStretched for FRANKFURT


SDN-C

Stavros Kanarakis (Nokia), Prakash E (Huawei)


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
Status
colourYellow
titleStretched for FRANKFURT
Update service attributes after PNF re-registration using SDNC DG. Current DG fails to do so


Testing

dbalsige , David Perez Caparros (Swisscom), Lincoln Lavoie (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
colourYellow
titleStretched for FRANKFURT


Documentation

David Perez Caparros (Swisscom)


Improve documentation on BBS use case provisioning


DemoLead: 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
  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.


...