August 2020 - kata-dev - lists.katacontainers.io

February 2020 Kata Containers Architecture Committee elections are open!
by Whaley, Graham 08 Oct '20

08 Oct '20

Hello Kata Citizens, On behalf of myself, Graham Whaley (from Intel), and Ricardo Aravena (rico) as the approved election officials, it's a pleasure to announce that the Kata Containers architecture committee elections for February 2020 are open! The timeline for the election process is: * Election officials approved by AC: February 4 * Candidacy open: February 5-12 * "Debate period": February 13-23 * Voting: February 24 - March 1 * Results: March 2 The window is now open for candidates to post their submissions. The process to submit a nomination is: 1) Review the responsibilities of the Architecture Committee members [1] 2) Between now and Feb 12 at 14:59 UTC, you can declare your candidacy for one of the open seats by submitting a textfile with your name (please put your name as the file name), the reason for running and your platform/objectives to this folder [2]. Please also send a message to the kata-dev ML with this same info, declaring your candidacy. Who can vote: Anyone who has had a commit merged into the project in the last 12 months will be eligible to vote. All eligible voters will receive an email with a link to the voting system once the voting period opens. More details of the election process are outlined at [3] and in the etherpad at [4]. Note, once candidacy entry has closed and we enter the debate period. We will be openly asking the candidates some questions around their candidacy. The community is encouraged to submit questions via the election officials and etherpad at [4] - get your thinking caps on now in preparation... we shall then filter, review, and choose a set of suitable questions for the candidates. Please let us know if you have any questions about running for a seat or the election process! [1] https://github.com/kata-containers/community/tree/master/elections#architec… [2] https://github.com/kata-containers/community/tree/master/elections/arch-com… [3] https://github.com/kata-containers/community/tree/master/elections [4] https://etherpad.openstack.org/p/KataArchCommElections_Feb2020 --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

7 12

Arch Committee Election: Q&A period open!
by Whaley, Graham 29 Sep '20

29 Sep '20

Hello all, We have three candidate submissions for the Architecture Committee election, where we have two seats available. Thus, we shall enter the Q&A and subsequently the voting phases. Candidates names and links to their github submissions are below. The next period (Feb13-23rd) is for asking questions to candidates via this mailing list; it's an opportunity to get familiar with the perspective they would bring as an Arch Committee member before voting opens on the 24th. To kick off the Q&A, I shall ask to the candidates: Q. What is the most important thing (be it an integration, a particular feature, adopting a policy, etc) Kata Containers needs to achieve in the next year and how should we get there? Candidates (in alphabetical order): -David Alan Gilbert [1] -Samuel Ortiz [2] -Xu Wang [3] [1] https://github.com/kata-containers/community/blob/master/elections/arch-com… [2] https://github.com/kata-containers/community/blob/master/elections/arch-com… [3] https://github.com/kata-containers/community/blob/master/elections/arch-com… --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

9 11

Proposals to improve our porting activities
by Hunt, James O 11 Sep '20

11 Sep '20

Hi all, I've raised [1] with thoughts on how we can simplify our porting activities (and make them more reliable). I've also added it to the Architecture Committee agenda for next week [2]. Please comment if you have thoughts so we can discuss on Tuesday. Cheers, James [1] - https://github.com/kata-containers/kata-containers/issues/634 [2] - https://etherpad.opendev.org/p/Kata_Containers_2020_Architecture_Committee_… --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 2

vPTG October 2020 Team Signup Reminder
by Kendall Waters 09 Sep '20

09 Sep '20

Hello Everyone! Wanted to give you all a reminder that the deadline for signing up teams for the PTG is approaching! The virtual PTG will be held from Monday October 26th to Friday October 30th, 2020. To signup your team, you must complete BOTH the survey[1] AND reserve time in the ethercalc[2] by September 11th at 7:00 UTC. We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions in with 4 rules/guidelines. 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Once your team is signed up, please register[3]! And remind your team to register! Registration is free, but since it will be how we contact you with passwords, event details, etc. it is still important! If you have any questions, please let us know. -The Kendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey <https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey> [2] Ethercalc Signup: https://ethercalc.openstack.org/7xp2pcbh1ncb <https://ethercalc.openstack.org/7xp2pcbh1ncb> [3] PTG Registration: https://october2020ptg.eventbrite.com <https://october2020ptg.eventbrite.com/>

2 1

Port forwarding support
by Ian Lewis 31 Aug '20

31 Aug '20

Hi kata folks, I have been looking into supporting port-forward in Kubernetes for gVisor and want to make sure that the solution is not too runtime specific. I have seen issue #697 <https://github.com/kata-containers/runtime/issues/697>. Is this still an issue for Kata? <https://github.com/kata-containers/runtime/issues/697>I've written some ideas in an issue <https://github.com/kubernetes/enhancements/issues/1846> in the Kubernetes enhancements repo. I'd appreciate it if folks from the Kata team could comment on the pros and cons and whether these ideas would work for Kata as well. After that, my thought is to get on the agenda and discuss at a sig-node meeting, ideally when folks from Kata could be present as well. Cheers, Ian -- Ian Lewis | Developer Advocate | ianlewis(a)google.com | +81 (03)4540-2465

2 2

gogo/protobuf issues
by Fabiano Fidêncio 27 Aug '20

27 Aug '20

Bin Liu reported a "Test latest CRI-O" (https://github.com/kata-containers/tests/pull/2775) issue, which is linked to an issue that I reported on CRI-O a few weeks ago (https://github.com/cri-o/cri-o/issues/3991) Turns out the same issue affects containerd (https://github.com/containerd/ttrpc/issues/62) My vague understanding of the issue is that due to an update done on golang/protobuf package, the one introducing its APIv2 is responsible for generating messages which are now incompatible with the v1 package. Considering the issue above, and the fact that gogo/protobuf is looking for new ownership (https://github.com/gogo/protobuf/issues/691) I think the best we can do to deal with the unavoidable breakage is replace all the gogo/protobuf usages on kata, containerd, and CRI-O by golang/protobuf. I'm not in the position to even measure how much work it'd be required, but I know folks from Ant Fin are familiar with protobuf and may be able to help with this. On the CRI-O side, the gogo/protobuf issues are coming mostly from vendored code, which I do believe that could be solved in one place and both containerd & CRI-O would take advantage of the same fix. Anyways, anyone interested on helping with this one? Best Regards, -- Fabiano Fidêncio

2 4

Kata 1.x <-> Kata 2.0 porting guide wiki page
by Hunt, James O 27 Aug '20

27 Aug '20

Hi All, I've just created [1] to help explain the "double fixing" / porting we need to be thinking about for *every* PR. Please read and feel free to tweak... ;) Cheers, James [1] - https://github.com/kata-containers/community/wiki/Porting-PRs-between-Kata-… --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

[Diversity] Diversity & Inclusion WG Meeting 8/31 - Removing Divisive Language
by Amy Marrich 26 Aug '20

26 Aug '20

The Diversity & Inclusion WG has taken on the task from this week's Board meeting to assist with the development of the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, August 31, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. <https://meetpad.opendev.org/osf-diversity-and-inclusion> The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz)

1 0

Kata 2.0, PR porting, and an idea
by Hunt, James O 26 Aug '20

26 Aug '20

Hi All, # TL;DR - See new project [4]. - See "Future plans" below. # Background As you probably know, we are developing Kata 2.0 in [1] but continuing to work on 1.x in the other repositories. When a PR gets raised on a 1.x branch, it often also makes sense to apply that (forward port it) to the 2.0 branch. We've been adding the "port-to-2.0" label as an indicator that this needs to happen. However, sometimes PRs get raised on the 2.0 branch first, and it makes sense for some of those PRs to be applied to a 1.x repo (backported). We do have a "backport" label but that hasn't been used much it appears. But there are also 1.x stable branches so 1.x bug-fix PRs may need to be back-ported to stable-${version} (and 2.0 bug fix PRs might need to be backported to both 1.x master and stable-*). # Challenge I've spent a bit of time looking at the "common repos" between 1.x and 2.0 [2] and -- unsurprisingly since us humans are fallible -- not all expected PRs have been back-ported or forward-ported. Since it's rather time-consuming working out the delta, I've focussed on PRs that haven't been applied to 2.0 but (potentially) should be (aka forward port PRs). However, we should look at the backporting delta more closely later/real-soon-now... I'm still working through agent and runtime repos, but I've raised new issues in [3] and created a new GitHub project [4] showing this backlog that needs to be cleared before 2.0 is released. Please take a look at this project as you may find you've got some work to do (I've tried to assign the issues to the original PR owners where possible). I may have been over-zealous and raised issues for PRs that have actually landed in 2.0. If so, please comment and close with a link to the PR so we have traceability. # Future plans How do we avoid this sort of "dangling back/forward port" problem happening in the future (aka from tomorrow :)? I think the simplest strategy is a semi-manual one: - Add two *pairs* of new labels to all our repos: - "needs-backport" and "no-backport-needed" - "needs-forward-port" and "no-forward-port-needed" - Add GitHub actions to all repos requiring that *one of each pair* is added to every PR before it can be merged (aka block all PRs being merged until that criteria is met for each!) This is somewhat simplistic but it will force the maintainers to think carefully about each PR before the PR can be merged. The idea being that they: - decide on an approach for each PR (does it need porting in either direction?) - atleast raise an issue for the back/forward port work (referencing the original PR). - apply the labels to the current PR to allow it to land. I've written a simple GitHub action [5] that can be turned into a set of PRs if we think this makes sense. What do we think? Cheers, James [1] - https://github.com/kata-containers/kata-containers/tree/2.0-dev [2] - agent (potentially), documentation, osbuilder, packaging, runtime. [3] - https://github.com/kata-containers/kata-containers [4] - https://github.com/orgs/kata-containers/projects/24 [5] - https://gist.github.com/jodh-intel/8686dd0ad04c9526cb5ba93283805561 --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 1

Updated invitation: Kata containers backlog review meeting @ Weekly from 5pm to 6pm on Tuesday (IDT) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 25 Aug '20

25 Aug '20

This event has been changed. Title: Kata containers backlog review meeting Purpose of this meeting is to review and clean the kata open issues backlog (https://github.com/kata-containers/kata-containers/issues?q=is%3Aopen+is%3A… idea is then to add additional labels to the cleaned backlog for identifying the high priority ones being actively worked on and track them closer. We can then help focus on completing those issues and unblocking them if needed. Meeting time is based on the doodle poll sent.  When: Weekly from 5pm to 6pm on Tuesday Israel Time (changed) Joining info: Join with Google Meet https://meet.google.com/ttm-kvqf-tog Join by phone (US) +1 225-434-0039 (PIN: 182743039) More joining options: https://tel.meet/ttm-kvqf-tog?pin=3794388642265&hs=0 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io * yuzhihong(a)gmail.com * Sun, Ning * Boeuf, Sebastien * Wainer dos Santos Moschetta * Venegas Munoz, Jose Carlos * Montes, Julio * Shinde, Archana M * James O Hunt * ffidenci(a)redhat.com * Randy Martin * raravena80(a)gmail.com * Peng Tao Event details: https://www.google.com/calendar/event?action=VIEW&eid=N3FmMDBrOGl1aGVzZ2wyZ… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account kata-dev(a)lists.katacontainers.io because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0