Hi Brent, For kata-runtime, I tested kata container could be launched by both annotation and Runtime Class methods. Best Regards Shuicheng From: Rowsell, Brent <Brent.Rowsell@windriver.com> Sent: Thursday, January 2, 2020 9:42 PM To: Lin, Shuicheng <shuicheng.lin@intel.com>; Miller, Frank <Frank.Miller@windriver.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng, What testing has been done with kata-runtime ? Thanks, Brent From: Lin, Shuicheng [mailto:shuicheng.lin@intel.com] Sent: Wednesday, January 1, 2020 7:07 PM To: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Hi Frank, Happy New Year! How is the testing going for kata? Is there any issue I need check? Thanks. Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 19, 2019 8:56 AM To: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Here is the test list I did. 1. Pass daily sanity test by Ada's team for AIO-SX/AIO-DX/Multi/Multi+Storage. 2. Verify container's regression test cases in link: https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEm... 3. Verify no private registry/private insecure registry/private secure registry/multi private registry case. 4. Verify no docker proxy/with docker proxy case. 5. Verify IPv6 deployment. 6. Verify backup&restore for platform. Best Regards Shuicheng From: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>> Sent: Wednesday, December 18, 2019 10:16 PM To: Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: We took out your commits and did some basic testing so thanks for providing the list. One final question: where can we review the list of the tests you have done? Or can you summarize the test cases please. Frank From: Lin, Shuicheng [mailto:shuicheng.lin@intel.com] Sent: Friday, December 06, 2019 3:34 AM To: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, 1 more patch [0] is uploaded today. So there are 8 patches in total. With this patch, token server supports POST method for token fetch, so the WA in containerd is removed. [0]: https://review.opendev.org/697601 Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 5, 2019 4:11 PM To: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Glad to hear that. I have rebased all my patches to latest. And your link is correct. Feel free to contact me if you have any question with it. Thanks. Best Regards Shuicheng From: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>> Sent: Thursday, December 5, 2019 6:07 AM To: Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the updates. We would like to take out your changes for KATA containers for a test. Can you rebase your commits and let me know if these are all of the commits: https://review.opendev.org/#/q/topic:kata+(status:open) Once you have rebased we'll create a designer build and run a few tests and let you know if we find anything that needs to be addressed. Frank From: Lin, Shuicheng [mailto:shuicheng.lin@intel.com] Sent: Sunday, December 01, 2019 9:15 PM To: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I try to run busybox with kata containers by k8s, and it could run successfully in IPv6 environment. Best Regards Shuicheng From: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>> Sent: Saturday, November 30, 2019 4:03 AM To: Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the update. It looks like stx-openstack has not yet been tested with IPv6. But we have been testing IPv6 with kubernetes platform only and simple k8s apps. Can you confirm kata containers is working with IPv6 when stx-openstack is not applied/not used? Frank From: Lin, Shuicheng [mailto:shuicheng.lin@intel.com] Sent: Friday, November 29, 2019 12:48 AM To: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I created below LP for the IPv6 deployment issue I meet. Could you help check whether IPv6 deployment is verfied before and share me the BKM for it if there is? Thanks. https://bugs.launchpad.net/starlingx/+bug/1854316 Best Regards Shuicheng From: Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>> Sent: Tuesday, November 26, 2019 11:37 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: * 4 LPs are expected to land for stx.3.0 including the 2 Highs * 2 LPs to be marked invalid/not reproducible * 11 LPs to be re-gated to stx.4.0 * 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller@windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 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 November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components 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 >>