[Starlingx-discuss] StarlingX Containerization Meeting

[Miller, Frank]

Minutes from today's meeting:

Next meeting will be next week on Dec 17.  Then no meeting after that until January.

*       We did not have quorum to brainstorm the unit test approach.  Will re-schedule to Dec 17 meeting.
*       Mingyuan has created a nice tool to create/build container applications to run on StarlingX.  Request the container team members review his commit this week: https://review.opendev.org/#/c/697013/<https://review.opendev.org/>
*       For stx.3.0, 2 features still have open tasks.  Ran and Mingyuan described the remaining tasks (some are ready to merge) and took the action to create a small stx.4.0 storyboard to move these tasks to stx.4.0.  Then the stx.3.0 features can be marked complete:
o       Intel GPU device plugin: https://storyboard.openstack.org/#!/story/2005937<https://storyboard.openstack.org/>
o       QAT device plugin: https://storyboard.openstack.org/#!/story/2005514
*       Tingjie gave a good overview of Rook and ceph containerization.  One outstanding request is to look at how sysinv is being used and change the design so rook manages the ceph configuration and not sysinv.  We'll have a follow-up discussion at the Dec 17 meeting.

Frank

-----Original Appointment-----
From: Miller, Frank [mailto:Frank.Miller at windriver.com]
Sent: Monday, December 09, 2019 11:52 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] StarlingX Containerization Meeting
When: Tuesday, December 10, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada).
Where: https://zoom.us/j/342730236


Please join me for the bi-weekly containers meeting.

Agenda for December 10 meeting:
1. Unit Test strategy for containers repos - brainstorm session by all of us
    Reference from the config subproject: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006710.html
    Questions to discuss:
        - What level/type of automation testing would provide most benefit to the sub-project? - applicability, address current lack of coverage, other considerations
        - What area of the sub-project's code is most in need of additional coverage? - heat map of issues, rate of change, desire to 'open' to non-experts
        - Where should the sub-project invest to increase/maintain quality while enabling contributions?
        - What work is required - example testcases, documentation, test infrastructure to lower the bar for writing effective unit tests?

2. Review/discussion on Mingyuan's new user application generation tool: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-December/007159.html

3. Any last stx.3.0 gating items?
   - Intel GPU & QAT plugin SBs still have tasks open - these should be closed or split into a small stx.4.0 SB
   - 2 High LPs & 5 medium LPs: great progress by all to reduce the # of LPs (down from 18 at our last meeting)

4. Update on stx.4.0 & other features:
    - SB link: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.containers&tags=stx.4.0&project_group_id=86<https://storyboard.openstack.org/>
    - Updates on a subset:
       - 2005527: CEPH Containerization in StarlingX [Tingjie Chen]
       - 2006145: Kata container support [Shuicheng Lin]
       - 2006537: Decouple Container Applications from Platform [Bob Church]
     - 2006787: Smaller memory node support, aka containerize flock services [Austin Sun]



Etherpad:  https://etherpad.openstack.org/p/stx-containerization


Timeslot:  9:30am EST / 6:30am PDT / 1430 UTC
Call details
*       Zoom link: https://zoom.us/j/342730236
*       Dialing in from phone:
*       Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
*       Meeting ID: 342 730 236
*       International numbers available: https://zoom.us/u/ed95sU7aQ

Agenda and meeting minutes
Project notes are at https://etherpad.openstack.org/p/stx-containerization

Containerization subproject wiki:  https://wiki.openstack.org/wiki/StarlingX/Containers





  << File: ATT00002.txt >>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191210/24ee36dc/attachment.html>