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

[Lin, Shuicheng]

Hi Brent & all,
I am sorry to forgot we still need dockerd to pull & push image to local registry, due to crictl doesn't support push image [0].
So we cannot remove dockerd currently.

There is another containerd CLI "ctr", which support pull & push image, but this tool is stated as "unsupported" [1].
So I prefer to keep use docker instead of ctr.
What is your suggestion?
Thanks.

[0]: https://github.com/kubernetes-sigs/cri-tools/issues/438
[1]: https://github.com/containerd/containerd/blob/master/cmd/ctr/app/main.go#L61

Best Regards
Shuicheng

From: Lin, Shuicheng
Sent: Monday, October 21, 2019 11:17 AM
To: Rowsell, Brent <Brent.Rowsell at windriver.com>; Miller, Frank <Frank.Miller at windriver.com>; starlingx-discuss at lists.starlingx.io
Cc: vm.rod25 at gmail.com
Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting

Hi Brent,

[BR] What is the plan to remove dockerd ?
[Shuicheng] We need switch armada to run with containerd first, then we should be able to remove dockerd.
Task 37231 is created to track it under the same story[0].
Task 36981 is for switch armada to run with containerd.

I prefer to do both task in later stage.

[0]: https://storyboard.openstack.org/#!/story/2006145

Best Regards
Shuicheng

From: Rowsell, Brent <Brent.Rowsell at windriver.com<mailto:Brent.Rowsell at windriver.com>>
Sent: Friday, October 18, 2019 9:20 PM
To: Lin, Shuicheng <shuicheng.lin at intel.com<mailto:shuicheng.lin at intel.com>>; Miller, Frank <Frank.Miller at windriver.com<mailto:Frank.Miller at windriver.com>>; starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Cc: vm.rod25 at gmail.com<mailto:vm.rod25 at gmail.com>
Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting

Thanks. See inline

Brent

From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com]
Sent: Thursday, October 17, 2019 9:00 AM
To: Miller, Frank <Frank.Miller at windriver.com<mailto:Frank.Miller at windriver.com>>; Rowsell, Brent <Brent.Rowsell at windriver.com<mailto:Brent.Rowsell at windriver.com>>; starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Cc: vm.rod25 at gmail.com<mailto:vm.rod25 at gmail.com>
Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting

Hi Frank & Brent & all,
I have updated my patches to remove the visible password for registry.
Please help review the update in ansible-playbooks/stx-puppet.
Here is the link for the patch list:
https://review.opendev.org/#/q/topic:kata+(status:open)

- Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed)
[shuicheng] do you mean change the "/var/lib/docker" directory to "/var/lib/containerd" for both docker and containerd?
If the answer is yes, I prefer to do it later, after docker runtime is not used at all. Currently, armada is still using docker.
- Add a test case for local registry pull/push and authentication
[BR] What is the plan to remove dockerd ?
[Shuicheng] No plan yet. We need switch armada to run with containerd first, then we should be able to remove dockerd.
Task 37231 is created to track it under the same story[0].
Task 36981 is for switch armada to run with containerd.

[shuicheng] With the new patch, local registry still could be accessed both by Kubernetes and crictl.
For crictl, username/password need be provided in CLI, similar to "docker login" for docker CLI.
- Update code to ensure admin password is not visible
[shuicheng] Done.

Best Regards
Shuicheng

From: Miller, Frank <Frank.Miller at windriver.com<mailto:Frank.Miller at windriver.com>>
Sent: Tuesday, October 15, 2019 10:16 PM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Cc: vm.rod25 at gmail.com<mailto:vm.rod25 at gmail.com>
Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting

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<mailto:starlingx-discuss at lists.starlingx.io>
Cc: vm.rod25 at gmail.com<mailto: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:
*        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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191023/922169b8/attachment-0001.html>