Bridge

New time (Effective from 03/14/2019 - until DST Ends)

Thursday, 9.00 – 10.00 AM EDT/13.00 -14.00 PM UTC

Bridge - zoom.us/j/824147956 

Recording:

DCAE_Weekly_07252019.mp4

Attendees:

Host: Vijay Venkatesh Kumar


Discussion Topics:


1 Time (est) Topics Requester/Assignee Notes/Links
2
Project StatusVijay Venkatesh Kumar

START RECORDING

PARTICIPANT LIST

3
Docker build consistentcy ( DCAEGEN2-1579)

Piotr Bochenski

Marcin Migdal

Discuss proposal on docker build consistency for DCAE components  (across java, python, nodejs component)

optimized-dockers-jvm.pdf

Components migrated to new docker build process

  1. PRH
  2. PM-Mapper (In-progress)

Need followup on below:

  • Plugin list alignment with oparent TBD
  • Python build dependency on script to be reduced; need volunteer to support
  • Standard pom/jjb template for all dcae component (java and python) preferred; need further discussion.
4
Dmaap plugin and CBS Lib integration

Henrik Andersson

Status checkpoint review and open issues

  • Using CBS SDK - 1.1.6 (official released version from Dublin) Yongchao Wu
  • CBS Client version for El-Alto to be confirmed/availability ( @pawel.biniek@nokia.com, Piotr Jaszczyk )
    • Marcin Migdal confirmed all planned changes are completed; DCAEGEN2-1552 (tracked separate below)
  • DCAEGEN2-1651 in progress (related DR subscriber)
    • DCAE plugin
    • CCSDK plugin in gerrit pending review
  • PMMapper verified (changes in gerrit)
  • DFC is completed
5
 SECCOM updates

Tony Hansen /Vijay Venkatesh Kumar

7/25

  •     SEC-COM addressing some selected vulnerabilities as POC for some project; recommendation to other projects team will follow after POC is done
  •     Component owners may choose to address reported vulnerability for El-Alto if they have bandwidth


SEC-COM Vulnerabilities per project/component  https://wiki.onap.org/download/attachments/48531500/19_07_09_DublinVulnerabilitiesAnalysis.xlsx?api=v2 (from https://wiki.onap.org/display/DW/2019+SECCOM+meeting+input)

SECCOM proposing ONAP project wide updated for external libraries (Vulnerabilities) https://wiki.onap.org/download/attachments/64007424/ONAP%20Vulnerability%20management%20for%20El%20Alto%20release_PP_v4%20%282%29.pptx?version=1&modificationDate=1561385888000&api=v2

DCAE Impacted component are listed below


6
Globaljjb migration (DCAEGEN2-1578)

 Gerard Hickey

user-3784d

Status checkpoint review and open issues  - global-jjb Migration Tracker

Key Changes

  • Oparent migration to 2.0.0
  • New build job introduced (replaces old release job)
    • New jobs are required to be run on Centos

Migrated Jobs with issues

  • SDK dmaap client (izabela.zawadzka@nokia.com, @pawel.biniek@nokia.com, Piotr Jaszczyk )
  • HV_VES
  • PM-Mapper
  • InventoryAPI
  • ServiceChange Handler
  • DFC
  • RESTConf
  • VES
  • SON-handler
  • PRH
  • BBS-EP
  • DataLake-handlers
  • Mapper
  • TCA
  • TCA-gen2


OPEN ISSUE:

Except BBS-EP and DL, all other components have similar failure (permission issue) while invoking docker under maven-stage jobs on centos VM’s.There is apparently some restriction (possibly selinux) on centosVM  blocking docker layer creation (which would also explains issue with dcaegen2/sdk failing on docker-compose step). Need follow-up with Jessica Wagantall

7
CBS TLS Support - Migration

Vijay Venkatesh Kumar

Status check point - TLS support for CBS - Migration Plan

8
El-Alto Commitments Early Drop artifactsVijay Venkatesh Kumar

Release candidate

EarlyDrop  (Code completion and artifact released by August 2, 2019)

  • ConfigbindingService
  • CloudifyManager
  • Bootstrap
  • BlueprintGenerator
  • Plugins (k8s, Dmaap)
  • ServiceChangeHandler
  • InventoryAPI
  • TCA
  • DFC
  • PM-Mapper

Second/Final El-Alto drop (Code completion and artifact released by Sep 6, 2019)

  • VESCollector
  • SDK
  • RESTConf
  • Dashboard
  • HV-VES
  • PRH
  • ?
9
Policy Flow supportDavid Farrelly

Design flow with policy configuration will entail below -

  1. Parameters that are required to be managed dynamically are identified as policyeditable in spec by MS owner
  2. Tools to use spec as input and generate policy model (this step is currently manual)
  3. Tools to generate blueprint (type: dcae.nodes.policy or type: clamp.nodes.policy with policy_id input)
  4. New models to be added into Policy (currently this is done through SDC distribution; but policy might have other api’s which can be used to load the models also I think)
  5. Create a policy using this new model  (response from policy should include policy_id)
  6. During MS blueprint include policy_id as additional input

Marco will be doing a demo on steps for CL setup/configuration/deployment on next Control Loop weekly meeting 07/31 (10AM ET)

https://zoom.us/j/872748904

Open Action Items



Page viewed times