[Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting

[Miller, Frank]

Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today.

Minutes for Oct 15 meeting:
1. Review KATA containers feature with container Cores.  Shuicheng to present feature overview and current status.
    - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged)
    - Shuicheng presented his feature and what has been done so far (see his charts in separate email)
    Actions identified:
        - Concerns:  Interaction with registry, admin password is visible
        - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed)
        - Add a test case for local registry pull/push and authentication
        - Update code to ensure admin password is not visible
        - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22)

Frank

-----Original Appointment-----
From: Miller, Frank
Sent: Thursday, October 10, 2019 2:55 PM
To: Miller, Frank; starlingx-discuss at lists.starlingx.io
Cc: vm.rod25 at gmail.com
Subject: StarlingX Bi-Weekly Containerization Meeting
When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada).
Where: https://zoom.us/j/342730236


Apologies, re-sending without etherpad formatting.

Note: We agreed to a new day and time for these meetings.

For all who are working containerization features or LPs please join for our bi-weekly meeting.

Agenda for October 15 meeting:
1.  Review KATA containers feature with container Cores.  Shuicheng to present feature overview and current status.
    - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged)

2. Updates on other stx.3.0 container features for MS3 milestone:
    - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2
       - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms?
                  Or do we disable in stx.3.0 until issue can be addressed in stx.4.0?
    - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] -  require updated forecast
    - 2005514: QAT K8S device plugin support in StarlingX
        - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts
    - 2005860: Upversion container components [Al Bailey]
    - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea]

3. Update on stx.4.0 features:
    - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church]


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:
o       Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
o       Meeting ID: 342 730 236
o       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


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