BBS Meeting Notes (Frankfurt)

Owned by David Perez Caparros
Last updated: Apr 28, 2020
8 min read
[ 1 2020.04.28 ] [ 2 2020.04.21 ] [ 3 2020.04.14 ] [ 4 2020.04.07 ] [ 5 2020.03.31 ] [ 6 2020.03.24 (no meeting) ] [ 7 2020.03.17 ] [ 8 2020.03.10 ] [ 9 2020.03.03 ] [ 10 2020.02.25 ] [ 11 2020.02.18 ] [ 12 2020.02.11 ] [ 13 2020.02.04 ] [ 14 2020.01.28 ]

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

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

- SDNC

- Integration testing

- Documentation 

2020.03.24 (no meeting)

- DCAE

- Policy

- 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

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

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

  • 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

- DCAE

  • Issue with Jenkins job, not a blocking issue

  • Blueprint for cloudify can be provided after M4

  • Basic testing is done, no errors

  • New version of k8s plugin needed v1.7.2 in swisscom lab

- SO

- Policy

  • to improve exception handling when accessConnectivity creation fails

- Integration Testing

  • Pnf relocation testing in Swisscom lab. Some issues need to be solved before the next test round (see https://groups.io/g/onap-bbs/message/665):

    • Issues with VES event not reaching ONAP (to be checked in DMaaP logs. Events may be dropped somewhere else, e.g. RESTCONF collector, VES mapper)

    • Issue with InternetProfile creation -> need to change SDNC DG, string to int for c/s-vlan (SDNC)

    • Issue writing metadatum (SDNC) -> to be further investigated 

2020.03.03

- ExtAPI

- SDNC DG

  • New logs 20200227_pnf_relocation_2.zip

  • @Prakash E  to implement logic to handle service instance metadata in Huawei DGs during next week. See https://open.rocket.chat/channel/onap-bbs-public?msg=dnbZ4sAp5RxsN5fd6 

    • CreateAccessConnectivity DG already contains the logic to create service instance metadata. No change needed

    • DeleteAccessConnectivity DG needs to implement the deletion of service instance metadata related to AccessConnectivity (check code of CreateAccessConnectivity DG to fetch the list of metadata to be deleted)

    • CreateInternetProfile DG already contains the logic to create service instance metadata. No change needed

    • ChangeInternetProfile DG needs to implement the deletion of service instance metadata related to InternetProfile and the creation of the service instance metadata related to InternetProfile with the new values.

    • DeleteInternetProfile DG needs to implement the deletion of service instance metadata related to InternetProfile (check code of CreateInternetProfile DG to fetch the list of metadata to be deleted)

    • Remove Access SDN M&C credentials from sdnc log file when creating or deleting the AccessConnectivity resource

    • NEW: use 'int' and not 'string' for c/s vlan in json payload when creating/modifying the internetProfile instance
      ...

      "s_vlan":1000,
      "c_vlan":100
      ...

- SO

- DCAE

- Policy

  • @Former user (Deleted)  to improve exception handling when accessConnectivity creation fails

- Integration testing

  • @Morgan Richomme to initiate the process to get a dedicated repo for the BBS use case artefacts (DGs, policy, service model...)

  • Setting up master branch in Swisscom Lab after M4

  • UNH-IOL lab is also available for BBS testing. Will coordinate the ONAP setup after M4 with @Lincoln Lavoie

  • @dbalsige @David Perez Caparros  to run E2E tests with real ONT/OLT devices in Swisscom lab

  • @David Perez Caparros to review the use case documentation by M4. See https://lists.onap.org/g/onap-discuss/message/20159

2020.02.25

Notes

- ExtAPI

- SDNC DG

- SO

- DCAE

- Policy

  • Onboarded using new APEX framework, working ok

- Integration testing

2020.02.18

Notes

- SDNC DG

  • Missing remote_id value in bbs-access-connectivity-create.json. Change committed: SDNC-1021: Move BBS logic from network-topology-operation to vnf-topology-operation DGClosed



  • Error sending the request: Exception while posting http request to client javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    Solved SDNC-179: Failed to make HTTPS connection from SDNC to 3rd party controllerClosed

    kubectl exec -ti dev-sdnc-sdnc-0 -n onap -- bash openssl s_client -connect 172.30.0.55:26335 # copy server certificate and paste in /tmp/<CA_CERT_NAME>.crt sudo keytool -importcert -file /tmp/<CA_CERT_NAME>.crt -alias <CA_CERT_NAME>_key -keystore truststore.onap.client.jks -storepass adminadmin keytool -list -keystore truststore.onap.client.jks -storepass adminadmin | grep <CA_CERT_NAME>



- SO

- DCAE

  • Testing ongoing

  • Additional tests needed after SDK update

- Policy

  • New BBS apex policy successfully tested with CPE Authentication

  • Policy version will be updated to 1.0.2

  • PNF relocation will be tested later, after the new issue with PRH is solved

  • New policy models will be uploaded to https://gitlab.com/onap-bbs/bbs-apex-policy  

- Integration testing