...
Host: Tony Hansen
Discussion Topics:
1 | Time (est) | Topics | Requester/Assignee | Notes/Links | ||||||||||
2 | Project Status | START RECORDING PARTICIPANT LIST
| ||||||||||||
3 | Self Release process | Self Releases Workflow (Nexus2)
Open Issue: IT-17166 Self release support for projects with independent sub-project Impacts following repo
| ||||||||||||
4 | Globaljjb migration (DCAEGEN2-1578) | Status checkpoint review and open issues - global-jjb Migration Tracker Key Changes
Migrated Jobs with issues
Completed Work
Outstanding work
| ||||||||||||
5 | El-Alto Commitments Early Drop artifacts | Release candidate EarlyDrop (Code completion and artifact released by August 2, 2019) 5.0.0
Branching will be done with released component by tomorrow; master branch can be used for Frankfurt work (need minor version updated to avoid conflict with El-Alto patch/bug fixes) Second/Final El-Alto drop (Code completion and artifact released by Sep 6, 2019) 5.1.0
| ||||||||||||
6 | MS Blueprint Impact | DCAEGEN2-1686 - Blueprints should import Cloudify type files version 4.5.5 Possible impact for components using k8s plugin 1.6.x and up; Jack verifying this currently and will confirm next week
| ||||||||||||
7 | SECCOM updates | 8/15 & 8/8 - OJSI issues (201 is critical and impacts DCAE passing badge) 7/25
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
| ||||||||||||
8 | CL format change | Control Loop Event Standarization using VES
| ||||||||||||
Discussed SECCOM-251 - 255 |
During the meeting, I thought these were related to crypto_used_network |
, but instead these are about VES supporting authentication and authorization. That is, there must be no more unauthenticated and unauthorized VES reports. The various requirements deal with how an authentication identity is to be implemented and authorized. |
Open Action Items
- Henrik AnderssonFormer user (Deleted) Joseph O'Leary, Michael Serpico (ms236b@att.com) - Blueprint-generation tool to be checked with valid Spec files for Dmaap plugin integrated cloudify blueprint
- Pending Bp-gen issues (DCAEGEN2-1700) to be fixed
- 2019/8/22 - fix is in progress
New Action items
Seeking Community support
Topic/JIRA | Current Status | Planned Work |
---|---|---|
Docker build consistentency ( DCAEGEN2-1579) | JIRA cover broad aspect of standardizing DCAE component build process and docker tagging.
| Need volunteer from community to support
|
Viewtracker report |
---|
View file | ||||
---|---|---|---|---|
|