Versions Compared

Old Version 42

changes.mady.by.user David Perez Caparros

Saved on

compared with

New Version Current

changes.mady.by.user David Perez Caparros

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel1
typeflat

...

2020.

...

04.

...

- ExtAPI

- SDNC DG

...

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

  • Issues with cloudify manager in Swisscom Lab, slow response in CLI - solution: both bootstrap and cloudify manager pods were restarted
  • Issues deploying VES mapper and RESTCONF Collector due to k8splugin and cloudify types versions. See JIRA issues below
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyDCAEGEN2-2165
       
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyDCAEGEN2-2166
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyDCAEGEN2-2167
    • BBS Documentation (Frankfurt) has been updated accordingly

- Policy

- SDNC

- 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

- 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

  • No progress on 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-2609

- 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 AccessConnectivity InternetProfile (check code of CreateAccessConnectivity of CreateInternetProfile 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

  • No progress on 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-2609

...

  • Status update on BBS-ep: looks good for M4, but still some changes needed. Tested in ElAlto release in Swisscom lab.
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyDCAEGEN2-2088
     still open

- Policy

- Integration testing

...

2020.02.04

Notes

- Swisscom lab:

  • ONAP ElAlto is up again

- New SDNC DG:

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDNC-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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-2608
  • Closed 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-1994
    , we did not see this issue happening again in El Alto release

- DCAE:

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyDCAEGEN2-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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyDCAEGEN2-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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyPOLICY-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