Table of Contents

maxLevel	1
type	flat

2020.04.28

2020.04.21

No meeting. LFN Technical Event
Update: Setting up ONAP RC0 in Swisscom lab for BBS integration testing before RC1
- New hosts file: BBS Swisscom Lab

...

Stavros Kanarakis Prakash E David Perez Caparros to check error when updating service instance metadata for AccessConnectivity and add to InternetProfile section
Stavros Kanarakis Madhukar Shetty Prakash E to coordinate merge of Nokia and Huawei changes into SDNC DG vnf-topology-operation and commit code to ONAP's SDNC repo
Stavros Kanarakis Former user (Deleted) to coordinate on application.clversion expected by APEX policy and update default bbs-ep default config accordingly
Former user (Deleted) Stavros Kanarakis David Perez Caparros to test the latest APEX policy in swisscom lab

- Swisscom lab:

- New SDNC DG:

Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key SDNC-1021
Ran 1st test of new DGs in Swisscom lab
Feedback from Prakash E: SO is triggering vnf-topology-operation DG with svc-action as "create" and request-action as "createnetworkinstance". Since request-action "createnetworkinstance" is not present in vnf-topology-operation, it's returned without calling any corresponding BBS DGs
We may need changes in the SO BPMN recipe "CreateSDNCNetworkResource" or in the vnf-topology-operation SDNC DG

- SO:

We need to double check the PNF READY timeout issue in Swisscom lab and provide logs in
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key SO-2608
Closed
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key SO-1994
, we did not see this issue happening again in El Alto release

- DCAE:

Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key DCAEGEN2-2047
> the effort due to the new introduced changes in DCAE SDK is bigger than expected, but still feasible to implement by M4
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key DCAEGEN2-1583
> the scope of the task has been reduced in Frankfurt

- Policy:

We cannot keep BBS APEX policy in ONAP's Policy repository. It was agreed in R4 that use case code will not be a part of the platform repos.
New repository in gitlab for BBS APEX policy: https://gitlab.com/onap-bbs/apex-policy
Closed ticket
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key POLICY-2333
Once the policy is ready, we need to consider moving the policy code to https://gerrit.onap.org/r/admin/repos/demo

Action items:

Stavros Kanarakis and Prakash E to check the feasibility of adding the request-action "createnetworkinstance" to vnf-topology-operation DG. Otherwise, we need to propose a modification of the CreateSDNCNetworkResource BPMN in SO
David Perez Caparros to double check whether the PNF READY timeout issue is still happening and if so, provide feedback in SO-2608
David Perez Caparros to get an update on SO-2609 and SO-2611
dbalsige and David Perez Caparros to test the Access SDN M&C + OLT + ONT setup in Swisscom lab

...

- Integration testing

No recommendation on which library/framework to use for a mock 3rd party controller from the Integration team
We can start with our BBS's edge controller implementation and evaluate the option to make it generic and use it for Access. The mock should reply to CRUD calls coming from SDNC (AccessConnectivity, InternetProfile) and generate VES events (PNF registration, CPE authentication).
- Tim Carey to draft a proposal including CDS for 3rd party controllers in March (not for Frankfurt)
Lab in UNH-IOL. No update for now