[Starlingx-discuss] [build][meetings] Build team meeting minutes /21/2019

Young, Ken Ken.Young at windriver.com
Wed Mar 27 20:35:27 UTC 2019


Thank you for sending the minutes from last week.  I am looking forward to our call tomorrow.

For tomorrow, I would ask that the following be on the agenda:

  1.  CVE Correction Bugs
  2.  CVE Scanning for ISO

Ken Y

From: "Lara, Cesar" <cesar.lara at intel.com>
Date: Tuesday, March 26, 2019 at 6:20 PM
To: "starlingx-discuss at lists.starlingx.io" <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes /21/2019

Build team meeting

Agenda for 03/21/2019

- Update on build bugs and stories
- Multi Layer build proposal
- Mirror tool
- Opens


Update on build bugs and stories – just wanted to do a check on the stories and bugs assigned to the build team and make sure those are being worked on
Current stories

Need to check with Bruce/Saul if this one is still valid https://storyboard.openstack.org/#!/story/2003288

Current bugs


AR – Build team, please update your bugs o stories

Multi-Layer build proposal
So far we are on sync with most of the ideas of a multi-layer build on the PoC for Ubuntu that is happening as part of Multi-OS efforts (https://github.com/starlingx-staging/stx-packaging ) but we still need to get agreement on the requirements for enablement, we need to start building a discussion matrix to map these requirements and level set the team as far as to what are the problems that we are trying to solve. Scott also contributed his proposal in which we use the current tools to assign packages to layers, defined by the developer and build only those packages, taking from some of the build avoidance ideas.

AR- Cesar to start an Etherpad to facilitate brainstorming around this  https://etherpad.openstack.org/p/stx-build-requirements - done

Mirror tool
Erich presented a demo on this tool, currently at 90% development, and still need to integrate the logic behind build avoidance and the Cengn hosted mirror, spec is also on track to be finished and presented to TSC for approval.

CVE check integration to Intel build Automation, currently enabled for manual triggered scans on build automation, still working to have fully automated integration and then find a way to integrate this as part of Cengn automation.


Cesar Lara
Software Engineering Manager
OpenSource Technology Center

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190327/3b3ec212/attachment.html>

More information about the Starlingx-discuss mailing list