...

2020.

...

04.28

• DCAE:
  • Issues with jenkins job (jjb template), working with LFN IT team. This is not a blocker for BBS.
• Integration testing:
  • Blocker: 

    Jira
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-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

• BBS DGs: https://gerrit.onap.org/r/c/sdnc/oam/+/104658 

- 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 

• https://docs.onap.org/en/latest/submodules/integration.git/docs/docs_BBS.html 

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
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DCAEGEN2-2165

     

  • Jira
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DCAEGEN2-2166

  • Jira
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DCAEGEN2-2167

  • BBS Documentation (Frankfurt) has been updated accordingly

- Policy

• user-f79d0 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/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.

- Policy

• user-f79d0 status update? error handling in bbs APEX policy 

- SDNC

• Decision on SDNC DGs and metadata ownership: https://groups.io/g/onap-bbs/message/677
  • C/S-VLAN: as explained by Tim during the call, there might be different interpretations for C/S-VLAN depending on where in the network are being used. We can differentiate between:
    • 1) C-VLAN between the ONT-NNI and OLT UNI (access-uni-cvlan)
    • 2) S/C-VLAN on the OLT-NNI side (access-nni-cvlan, access-nni-svlan)
    • 3) S/C-VLAN on the BNG UNI side (edge-nni-cvlan, edge-nni-svlan)
  • In BBS Frankfurt, we don't work with case 1), and assume that cases 2) and 3) have the same value. In future, if we want to align with BBF's WT-411, we may need to add the 3 cases to service metadata and differentiate between access-uni-cvlan, access-nni-cvlan, access-nni-svlan, edge-nni-cvlan, edge-nni-svlan.
  • The VLAN values that we store in AAI (svlan, cvlan) are the ones of edge-nni-cvlan, edge-nni-svlan, and they are used as an input when creating the InternetProfile resource

- DCAE

• Stavros Kanarakis status update: bbs-event-processor

- Policy

• user-f79d0 status update: error handling in bbs APEX policy 

- SDNC

• Decision on SDNC DGs and metadata ownership
• Repository in gitlab for SDNC DG https://gitlab.com/onap-bbs/bbs-sdnc-dg , need to add latest version of DGs
• Rahul Tamrkar Status update Huawei DGs ?

- Integration testing

• Lab presence may be restricted due to COVID-19, testing could be limited
• Remote access is still working
• Installation of ONAP master is ongoing in parallel to current ElAlto release
• 2: Frankfurt Release Integration Testing Status
• Need to clarify whether RC0 will also be delayed

2020.03.10

- ExtAPI

• https in NBI. No updates w.r.t how to adapt BBS portal
• See https://groups.io/g/onap-bbs/message/670

...