| Table of Contents | ||||
|---|---|---|---|---|
|
...
2020.
...
04.
...
28
...
- DCAE:
- Issues with
- Piotr Zachwieja Stavros Kanarakis what was the solution?
- Please update the installation steps for BBS-ep here: BBS Documentation (Frankfurt)
- jenkins job (jjb template), working with LFN IT team. This is not a blocker for BBS.
- Integration testing:Updated SDNC DGs (
- Blocker:
DCAEGEN2Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key
2165SO- Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2166 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2167 - BBS Documentation (Frankfurt) has been updated accordingly
- Blocker:
- Policy
- Former user (Deleted) status update? error handling in BBS APEX policy
- SDNC
2827 - 2: Frankfurt Release Integration Testing Status
- RC1 is scheduled for April 30. See https://lists.onap.org/g/onap-release/message/1603
- Closure of Swisscom Lab on Apr 30
- Lab set up in UNH-IOL
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
2020.04.14
- No meeting
- Waiting on RC0 in order to start E2E integration testing in the labs
2020.04.07
- No meeting
- Waiting on RC0 in order to start E2E integration testing in the labs
2020.03.31
- DCAE
- Issues with bbs-ep blueprint and jenkins job
- Policy
- APEX policies in BBS repo: https://git.onap.org/integration/usecases/bbs/tree/policy/apex/json
- To be tested in Frankfurt RC0
- SDNC
- Integration testing
- BBS use case repo: https://git.onap.org/integration/usecases/bbs/tree/
- ONAP master not in a healthy state, many last minute changes before RC0
- Problems with NBI, SO
- Difficult to do integration testing for now
- RC0 scheduled for Apr 2: TSC 2020-03-26
- 2: Frankfurt Release Integration Testing Status
- Documentation
2020.03.24 (no meeting)
- DCAE
- Issues with cloudify manager in Swisscom Lab, slow response in CLI - solution: both bootstrap and cloudify manager pods were restarted
- Please update the installation steps for BBS-ep here: BBS Documentation (Frankfurt)
- Issues deploying VES mapper and RESTCONF Collector due to k8splugin and cloudify types versions. See JIRA issues below
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2165 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2166 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2167 - BBS Documentation (Frankfurt) has been updated accordingly
- Policy
- Former user (Deleted) status update? error handling in BBS APEX policy (Status: Code has been merged to gitlab (https://gitlab.com/onap-bbs/bbs-apex-policy/-/tree/e233588388f13261116648f7ee90a57a543b0082). Need to test and verify)
- SDNC
- Updated SDNC DGs (https://gitlab.com/onap-bbs/bbs-sdnc-dg)
- New errors in Swisscom lab when storing AccessConnectivity and InternetProfile in AAI 20200318_sdnc-karaf.log.zip
- Rahul Tamrkar any update?
- The JSON payload of the createInternetProfile API call towards the Edge SDN M&C needs to have s/c-vlan values as int and not string
- Integration Testing
- Edge SDN M&C in Swisscom lab was updated to make the mac address optional when creating the InternetProfile. See this commit: https://gitlab.com/onap-bbs/bbs-sdnc-dg)
- New errors in Swisscom lab when storing AccessConnectivity and InternetProfile in AAI 20200318_sdnc-karaf.log.zip
- Rahul Tamrkar any update?
...
- vbng/commit/2cae2accf18feb87af1aa29f4746bb2608f41b0a
- ONAP master is available in Swisscom lab, see new hosts file here: BBS Swisscom Lab
- BBS related configs were applied (SO, DCAE, SDNC, Policy, DMaaP...)
- ToDo: BBS service needs to be modeled in SDC and distributed
- TSC approved the creation of BBS repository: TSC 2020-03-19
- The repository has been created: https://git.onap.org/integration/usecases/bbs/
- RC0 is still planned for Mar 26. It's unlikely we can do all integration tests before that date, especially when code is still being pushed to master
2020.03.17
- DCAE
- Stavros Kanarakis status update: bbs-event-processor.
- Working on blueprints, not a blocking issue for testing. To be finished before RC0.
...
- 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
2020.02.04
Notes
- Swisscom lab:
- ONAP ElAlto is up again
- 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
, we did not see this issue happening again in El Alto releaseJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SO-1994
- DCAE:
> the effort due to the new introduced changes in DCAE SDK is bigger than expected, but still feasible to implement by M4Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2047
> the scope of the task has been reduced in FrankfurtJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-1583
- 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
...
- Stavros Kanarakis to create JIRA tasks related to BBS-ep
- 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