Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Work in Progress


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 considerationsNOT 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 belongsNOT 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 eventsNOT IN FRANKFURT
Remove the RGW MAC validation from BBS-event-processor microservice
Issues with RESTCONF Collector (RCC)

DONE

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. NOT IN FRANKFURT
Use CLAMP for BBS policy: STRETCHED 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). 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)
Develop a BBF WT-411 standards based DG for the Use case in the Access and EdgeSTRETCHED 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)STRETCHED FOR FRANKFURT
Documentation
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.

BBS Development Status 

Project

PTL

JIRA Epic / User Story*

Requirements

SOSeshu Kumar Mudiganti

SO-1938 - Getting issue details... STATUS
SO-1994 - Getting issue details... STATUS

Note: we need to split SO-1938 in multiple tickets
DCAEVijay Kumar

DCAEGEN2-1990 - Getting issue details... STATUS


SDNCDan Timoney

IntegrationMorgan Richomme

  • No labels