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

Plan for organizing the kata issue backlog - updates 11th August 2020
by Ariel Adam 25 Aug '20

25 Aug '20

Hi everyone. Today we have finished reviewing the first bucket of issues we targeted: - *issues opened this year which are not bugs and are labeled kata-2.0-features (45 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…>)* - We have removed all the *"needs-review"* labels from issues we looked at and also moved some issues to close or attached PRs (no need to review issues with PRs) - For issues we thought are mandatory for the kata 2.0 release (feature freeze end of the month) we added the *"release-gating"* label (the label that made most sense to us :-) ) - The updated list contains 3 issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…> We now want to move to the next bucket of issues: - *Issues opened this year which are bugs (115 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…>)* - We'd appreciate if you could review these issue hopefully based on repositories related to you or topics related to you - Once you reviewed an issue remove the *"needs-info"* label - If you think it's not a valid issue close it - If you know of a PR related to the issue link it - If you think this issue is mandatory for the 2.0 release add the *"release-gating"* label - If you have any questions ping me or James - Target is to finish this bucket by next week We would really appreciate your help in moving this forward. Thanks.

2 4

Call for volunteers - Sep Kata AC election officials
by Sunny Cai 25 Aug '20

25 Aug '20

Hi everyone, As you might have known that we have the September Kata Architecture Committee election coming up, we need two volunteers who can help to facilitate this election process. Anyone can be the election officials, except for the people running for the elected seats. Thanks Ricardo Aravena for volunteering to be the official. Is anyone else interested in helping to facilitate this round of election? Please email me (sunny(a)openstack.org <mailto:sunny@openstack.org>) before September 8th if you would like to help! Thanks, Sunny Cai OpenStack Foundation sunny(a)openstack.org

1 0

Kat Herders for the week
by Hunt, James O 24 Aug '20

24 Aug '20

Hi All, This week's Kata Herders [1] are: - Chelsea (https://github.com/cmaf) - Christophe (https://github.com/c3d) - Julio (https://github.com/devimc) - Ricardo (https://github.com/raravena80) - Me (https://github.com/jodh-intel) # Statistics ## Issues Issues opened last week: 40 Issues closed last week: 59 Open issues: 1003 ## PRs PRs opened last week: 39 PRs closed last week: 35 Open PRs: 99 Open PRs (excluding dnm+wip): 70 # Help us out If you'd like to help get the open PRs merged and open issues resolved (or get involved in other ways with Kata), take a look at the contributing guide [2] and the rota process [3]. Any problems, just ask us [4]. Cheers, James [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [3] - https://github.com/kata-containers/community/blob/master/Rota-Process.md [4] - https://github.com/kata-containers/community/blob/master/README.md#join-us --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Kata release next week - help backport
by Fuentes, Salvador 20 Aug '20

20 Aug '20

Hello Kata folks, We are planning to have a Kata release next week - 1.12-alpha1 and stable releases 1.11.3 and 1.10.7. If you have made a commit to master since the last release that is a bug or security fix, please open a PR to backport commits to stable branches in 1.x. Any help identifying changes that need to be backported would also be appreciated. Thanks. Salvador Fuentes.

1 0

Want to contribute a Kata PR? We're finding more good first issues!
by Hunt, James O 18 Aug '20

18 Aug '20

If you're keen to get involved with Kata, but don't know where to start... The current Issue backlog squishing project [1] is surfacing some interesting "good first issues" [2]. These may be appropriate for those wanting to start work on a "small" [3] PR. There are a bunch of issues related to writing new unit tests (golang, rust), some documentation changes (markdown), shell scripting fixes (bash), etc. As usual, please read and agree to the project Code of Conduct [4], then have a read of the contributing guide [5]. If you get stuck, come and talk to us! [6] Keep an eye on [2] as it will grow... ;) Cheers, James [1] - https://github.com/orgs/kata-containers/projects/23 [2] - https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+labe… [3] - "quick to write", "simple to implement", "achievable in a relatively small amount of time". [4] - https://github.com/kata-containers/community/blob/master/CODE_OF_CONDUCT.md [5] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [6] - https://github.com/kata-containers/community/blob/master/README.md#join-us --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

For developers: Rusty on rust?
by Hunt, James O 18 Aug '20

18 Aug '20

Hi All, # TL;DR - The new agent is written in rust [2]. - We need the community to be more familiar with the rust language. - I've written some brief notes on rust, along with a very simple program written in both golang and rust (to allow you to "diff the implementations") for educational purposes. See [6]. # The Kata agent As you may be aware, the current Kata agent is written in golang [1]. But we also have a newer agent written in rust [2]. That implies we need more rust programmers in the community to: - Work on rust PRs. - Write new tests in rust (our test advice document explains how to write tests in both golang and rust [3]). - Have some rust knowledge to help ask awkward questions [4] on the code when they review PRs ;) # Is this you? Since much of the container ecosystem is currently written in golang, you may not be familiar with rust yet. Or maybe you looked at learning rust ages ago and gave up in frustration whilst also wondering what all the fuss was about? # Rust docs There is a lot of material on rust available including the excellent official documentation [5]. However, it can all be a little overwhelming initially due to the sheer size and scope of available material. If you already know golang and want a very quick "jump start", my (very brief and incomplete) notes plus example program written in go and rust may be useful [6]. Usual caveats apply [7]. # Learning rust I think all those who have learnt or are currently learning rust will concede that it is not an easy language to become fully comfortable with. It requires a significant investment in time to learn, but, like many difficult things in life, it really is worth the effort! As usual, perseverance pays off. Read and write as much rust as possible! Cheers, James [1] - https://github.com/kata-containers/agent [2] - https://github.com/kata-containers/kata-containers/tree/2.0-dev/src/agent [3] - https://github.com/kata-containers/tests/blob/master/Unit-Test-Advice.md [4] - https://github.com/kata-containers/community/blob/master/PR-Review-Guide.md [5] - https://www.rust-lang.org/learn [6] - https://github.com/jamesodhunt/go-vs-rust [7] - The notes are in *no way comprehensive* and the example code isn't using fully idiomatic rust, but hopefully does provide a framework for experimentation and education. Blah, blah, blah. --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Forum Brainstorming
by Kendall Nelson 17 Aug '20

17 Aug '20

Hello Everyone! The Virtual Forum is approaching. We would love 1 volunteer from the community for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. In addition to calling for volunteers for the Forum selection committee, this email kicks off the brainstorming period before the CFP tool opens for formal Forum submissions. The categories for brainstorming etherpads have already been setup here[1]. Please add your etherpads and ideas there! The CFP tool will open on August 31st and will close September 14th. For information on the upcoming virtual Summit[2]. For more information on the Forum[3]. Please reach out to jimmy(a)openstack.org or knelson(a)openstack.org if you're interested. Volunteers should respond on or before August 31, 2020. Thanks! Kendall (diablo_rojo) [1] Virtual Forum 2020 Wiki: https://wiki.openstack.org/wiki/Forum/Virtual2020 [2] Virtual Open Infra Summit Site: https://www.openstack.org/summit/2020 [3] General Forum Wiki: https://wiki.openstack.org/wiki/Forum

1 0

Kat Herders for the week
by Hunt, James O 17 Aug '20

17 Aug '20

Hi All, This week's Kata Herders [1] are: - Carlos (https://github.com/jcvenegas) - Zhihong Yu (https://github.com/tedyu) # Statistics ## PRs - Open PRs: 67 - Open PRs including WIP and DNM: 99 - PRs closed last week: 16 ## Issues - Open issues: 1,019 - Issues closed last week: 25 # Help us out If you'd like to help get the open PRs merged and open issues resolved (or get involved in other ways with Kata), take a look at the contributing guide [2] and the rota process [3]. Any problems, just ask us [4]. Cheers, James [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [3] - https://github.com/kata-containers/community/blob/master/Rota-Process.md [4] - https://github.com/kata-containers/community/blob/master/README.md#join-us --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Supported OSes, packaging plans for the future & some ideas
by Fabiano Fidêncio 17 Aug '20

17 Aug '20

Folks! We have discussed during this week's Architecture's meeting what could be a plan for the future with regards to packaging and I'd like to drop a suggestion here and then have it discussed in the August 25th meeting. The current situation is that the kata project builds kata pieces (which may differ considering whether you're using 2.x or 1.x branches) and distributes those together with our own qemu built statically and the kernel / initrd / image to be used. And, sincerely, this is *a* *lot* to take care of. My suggestion would be to reduce the amount of work we do, the amount of things we build, and start relying more on what the distros can provide us. Let me explain. For instance, we could ... Stop building & distributing our own VMMs ================================= While I understand the reason why it's done, it'd be better to rely on the VMMs shipped by the distros. In order to do this, we'd have to either approach the distros, or to do the tests ourselves, to ensure that their latest release has a VMM that's capable of running kata. If the distro has that, we document we support the distro. If the distro does not have that, we can provide instructions on how to build the VMM, but we take out of our back the work of building it statically and shipping to the consumers. With this, we can do better testing on specific distros and ensure to possible consumers of kata where they can run the project and, with that, also forward the non kata specific issues to the distros themselves. Keep building the kernel =================== Differently than the suggestion about the VMM, the kernel bits, IMHO, should still be built. The kernels we build can be used upstream, but we must ensure those are under no circumstances ready for production.Why? Because we have no power to track and fix CVEs as the distros do. So, we can keep shipping our own kernel and testing using it, but we should also incentive distros to use (and test) their own kernels with kata. The reason I say this is because it'd help the project to *not* require a distro to ship a non-tested kernel, which would drop a little bit the barrier of accepting kata as their official packages. Stop building & distributing our own distro packages ======================================== While I also understand that building the packages for several distros may help the users, I don't think this is something that should be on the kata developer's back. For this, I'd suggest we take advantage of the kata-operator, being worked by Harshal and Jens Freimann, and consolidate on that as the way to install kata in your distro. I foresee that we have to write some kind of "kata-osinfo" package (as in, a module, not as in an rpm or deb), where we can store information about the distro, which are the VMMs supported by the distro, which are the virt filesystems supported by that distro, etc; By doing this we can rely on a good documentation, or even on the operator to install the packages based on the info of each distro, but the only bit we'll distribute will be the kata binaries themselves. Doing this, we can keep it simple on our side, while relying more on the distros. Those things would already reduce the maintenance burden and, at the same time, show to our consumers what's supported and tested from our side. Of course, it goes without saying, but here I'm hoping our tests will follow the same approach and will use the distro packages, ensuring the basics would be working there and also reporting issues against the distro packages when needed. Please, take some time to think about the proposal. I'd love to hear feedback here in the Mailing List, but if you have something to add, please, also consider joining the Architecture's meeting on August 25th so we can take our final decision on this topic. Best Regards, -- Fabiano Fidêncio

7 11

Invitation: Kata containers backlog review meeting @ Tue Aug 18, 2020 5pm - 6pm (IDT) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 15 Aug '20

15 Aug '20

You have been invited to the following event. 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: Tue Aug 18, 2020 5pm – 6pm Israel Time 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 * James O Hunt * Peng Tao * Wainer dos Santos Moschetta * Sun, Ning * raravena80(a)gmail.com * Shinde, Archana M * Montes, Julio * Boeuf, Sebastien * yuzhihong(a)gmail.com * kata-dev(a)lists.katacontainers.io * Venegas Munoz, Jose Carlos * Randy Martin * ffidenci(a)redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=NzkyMzhmOWExZHAzMGdrc… 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