- kata-dev - lists.katacontainers.io

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 27 Aug '20

27 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

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 21 Aug '20

21 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 18 Aug '20

18 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 16 Aug '20

16 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

vPTG October 2020 Team Signup
by Kendall Nelson 13 Aug '20

13 Aug '20

Greetings! As you hopefully already know, our next PTG will be virtual again, and held from Monday October 26th to Friday October 30th. We will have the same schedule set up available as last time with three windows of time spread across the day to cover all timezones with breaks in between. *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. Again, you need to fill out BOTH the ethercalc AND the survey to complete your team's sign up. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Once your team is signed up, please register! 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! Continue to check back for updates at openstack.org/ptg. -the Kendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openstackfoundation.formstack.com/forms/june2020_virtual_ptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/126u8ek25noy [3] PTG Registration: https://october2020ptg.eventbrite.com

1 2

Boot timer prod removal
by Voicu, Luminita 11 Aug '20

11 Aug '20

Hello, We are discussing an API change regarding the boot timer feature in Firecracker. The boot timer device supports logging the boot time of the guest since InstanceStart command. In the past, this was handled using PIO for x86_64 and MMIO for aarch64. In order to unify the code in a generic mechanism, we came up with a MMIO boot timer 'device'. The implementation for x86_64 involved changing PIO writes to 0x03f0 to MMIO writes to 0xd0000000. For aarch64 the mechanism did not change. This boot time functionality is used only during testing, therefore we decided to load the device only when specified, instead of activating it by default. A dedicated --boot-timer parameter would be added to the cmdline options in order to request the boot timer feature. This is an API breaking change for those who use the boot timer. Please let us know about any concerns you may have around it. Thank you, Luminita on behalf of the Firecracker Team Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.

1 0

Up for a challenge? Unit testing y'all!
by Hunt, James O 11 Aug '20

11 Aug '20

Hi All, - Want to learn more about the internals of Kata but don't know where to start? - Are you keen to contribute to Kata? - Can you code in golang or rust? If you answer yes to those questions, read on...! ;) # Summary We're looking to increase the unit test coverage for the development versions of the Kata 2.0 [1]. Specifically, we want to increase coverage levels for the following Kata 2.0 components: - runtime (written in golang) [2] - the new agent (written in rust) [3] The unit test coverage levels have slipped for the runtime and the new agent is so new it still lacks tests in certain areas. This is an important activity as you have the chance to find (and potentially fix!) bugs before they are unleashed into the wild. # Details There is a top-level issue for each component (runtime [4], agent [5]). Each of those top-level issues has a number of related issues that breaks the work down into smaller chunks (there is an issue per directory/module, or even per file in some cases). # Tracking I've added all those task issues into the Kata 2.0 GitHub project [6]. # Get involved If you'd like to be involved, please let us know by adding a comment to [4] or [5] and we can help you find an interesting area to work on with us. Conversely, please don't start writing tests without telling us to avoid disappointment when we discover multiple people are writing the same set of tests! # Advice You should definitely read [7] first and you may find [8] and [9] helpful (the latter for golang tests). Before writing any new tests, please look at the existing tests for inspiration. Note also that some tests must run as root, whereas others must run as a non-privileged user. It's important to always consider which users your tests should run as (and we have infrastructure to ensure the tests DTRT). # Team effort If you want to volunteer to write some tests for a particular area and are happy to do that on your own, great! However, please don't think this is expected - if you volunteer, we're more than happy to help you out - remember that GitHub issues can be assigned to multiple users :-) Cheers, James [1] - Although we're focussing on 2.0, these new tests will also be backported where possible. [2] - https://github.com/kata-containers/kata-containers/tree/2.0-dev/src/runtime [3] - https://github.com/kata-containers/kata-containers/tree/2.0-dev/src/agent [4] - https://github.com/kata-containers/kata-containers/issues/237 [5] - https://github.com/kata-containers/kata-containers/issues/275 [6] - https://github.com/kata-containers/kata-containers/projects/2 [7] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [8] - https://github.com/kata-containers/tests/blob/master/Unit-Test-Advice.md [9] - https://github.com/kata-containers/kata-containers/tree/2.0-dev/src/runtime… --- 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 1

Plan for organizing the kata issue backlog
by Ariel Adam 11 Aug '20

11 Aug '20

Hi everyone. As part of the work we are doing to reduce and organize the issue backlog we have thought about a potential split of the open issues into *buckets* and a proposed plan to work on these buckets. Overall there are currently 1,019 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+sort…> . Out of these there are 106 open issues with attached PRs <https://github.com/issues?page=1&q=is%3Aissue+is%3Aopen+org%3Akata-containe…> and as Christophe suggested, these issues will be moved into an in-progress on the issue backlog board <https://github.com/orgs/kata-containers/projects/23> and will not be part of our backlog grooming work. Looking at the remaining issues we propose to split them as follows: - Issues opened this year (333 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…>) and everything else (686 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…> ) - Another split of issues opened this year which are bugs (112 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…>) and not bugs (174 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…> ) - For not bugs splitting to kata-2.0-features (45 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…>) and not (129 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…> ) - Once we finish with this years issues we will move on to handle the previous year issues *Our proposed approach is as following:* - Every week we will focus as a community on one of the buckets and will also use the bi-monthly backlog review meetings to help focus - For each issue reviewed the reviewer should check if that issue can be closed (duplicate, not relevant, etc...) or is a valid issue - If you believe this is a valid issue remove the "needs-review" label to indicate the issue has been triaged (or ping James/me to to do it) - Later on once we have finished with reviewing the issue backlog we can then move on to decide on adding new labels (such as MVP) and removing/joining old labels *Propose timeframe:* - 2nd week of August - 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…> ) - 3rd week of August - issues opened this year which are bugs (112 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…> ) - 4th week of August - issues opened this year which are not bugs and are not labeled kata-2.0-features (129 open issues <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea…> ) - 1st week of September - starting to work on issues from previous years depending on our progress Let us know if this plan makes sense, if you have comments or other suggestions. Thanks.

4 3

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

11 Aug '20

Hi All, This week's Kata Herders [1] are: - Fabiano (https://github.com/fidencio) - Christophe (https://github.com/c3d) - Eric (https://github.com/egernst) - Salvador (https://github.com/chavafg) # Statistics ## PRs - We currently have 62 open PRs (96 if you include WIP and DNM). - PRs closed last week: 14. ## Issues - We currently have 1,021 open issues. - Issues closed last week: 32. # 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.

2 3

Call for agenda for August 11th architecture committee call
by Eric Ernst 11 Aug '20

11 Aug '20

Hey Kata-folk - Don't see anything yet on the agenda for tomorrow's AC call. Any topics ya'll want to discuss? Thanks! --Eric

2 1

Virtual PTG October 2020 Dates & Registration
by Kendall Nelson 11 Aug '20

11 Aug '20

Hello Everyone! I'm sure you all have been anxiously awaiting the announcement of the dates for the next virtual PTG! After polling the community[1] and balancing the pros and cons, we have decided the PTG will take place the week after the Open Infrastructure Summit[2][3] from October 26th to October 30th, 2020. PTG registration is now open[4]. Like last time, it is free, but we will again be using it to communicate details about the event (schedules, passwords, etc), so please register! Later this week we will send out info about signing up teams. Also, the same as last time, we will have an ethercalc signup and a survey to gather some other data about your team. -the Kendalls (diablo_rojo & wendallkaters) [1] ML Poll for PTG Dates: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016098.html [2] Summit Site: https://www.openstack.org/summit/2020/ [3] Summit Registration: https://openinfrasummit2020.eventbrite.com [4] PTG Registration: https://october2020ptg.eventbrite.com

1 0

Areas of interest wiki page
by Hunt, James O 10 Aug '20

10 Aug '20

Hi All, You may not be aware of an interesting wiki page in the community repo - the "Areas of Interest" page: https://github.com/kata-containers/community/wiki/Areas-of-interest As the name suggests, this maps users to topics. The page is used to help folks find a point of contact for, say, issue or PR discussions, or simply someone to chat to about a topic on irc/slack. Note that you do *not* need to be a subject expert to be listed on this page, just someone with an interest in a particular topic! I've refreshed it to make it more structured, however I'm aware that it needs more love. Hence: - If you are mentioned on the page, please check to see if they are still correct. - If you are not mentioned on the page and would like to list your areas of interest, feel free to add yourself to the appropriate tables. - Either way, if you spot a mistake / omission, please fix it! Thanks very much. Cheers, James --- 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

Issue backlog
by Hunt, James O 09 Aug '20

09 Aug '20

# TL;DR Our issue backlog is huge. We intend to resolve this. If you'd like to get involved, please let us know! # Background As discussed in the Architecture Committee meeting earlier today, we're planning to attack the issue backlog as it hasn't been reviewed holistically for... maybe ever! I've added details on the issues to the Kata Rota wiki page [1], so if you are on the rota it would be great if you could start looking at issues too. We currently have 1,023 open issues [2], 922 of which don't have associated PRs (meaning they are _not_ "in progress") so we have a bit of work to do! ;-) # Work done so far 1) Ariel and I have had a brainstorming session to come up with a simple plan for attacking the backlog. 2) We've created a new GitHub project Kanban board [3] with the intention of using this to manage the issue backlog. 3) We've written a simple CLI tool using hub [6] that can add issues to github projects. # The plan 1) Make use of one of the GitHub actions [4][5] that can be used to auto-add newly opened issues from *all* the Kata repos into the new project. 2) Run the hub script as a "one off" to add the existing open issues in all the repos into the new project. 3) Hold a regular (probably weekly) meeting to review the backlog on the Kanban board [3]. 3.1) Consider re-enabling the stalebot [3.1] trigger [3.2] that used to auto-close issues that hadn't seen activity for a long time [3.3]. 4) Start making better use of labels to allow us to categorise and data-mine the backlogs. For example, more intelligent handling of bug and feature issues for example, ensuring they are applied and also back-ported and forward-ported as appropriate. We actually have a YAML database that documents all our GitHub labels [7] along with some simple tooling to keep the list of labels across the repos in sync. 4.1) We probably need to review the (rather large) list of labels and refine it slightly. Once we have a more refined set of labels, we should consider trying to make better use of them (for issues and PRs) particularly at the issue triage stage to categorise the issues. 5) Report back to the Architecture Committee on progress and findings. 6) Consider creating a Kanban board for the PR backlog to make that easier to manage too. 7) Share what we've learnt with the community Explain the new Kanban process and best practises for labelling issues. # Feedback The task of actually reducing the issue backlog could take some time and we may need to modify our approach as we learn more. As always, if anyone has thoughts on the above, please let us know. We'll assume "silence means compliance"! :-) # Willing helpers (that means you!) If you'd like to get involved in any of the above (particularly the actual reviewing of issues), again, please let us know ;-) Cheers, James [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+>+ [3] - https://github.com/orgs/kata-containers/projects/23 [3.1] - https://github.com/apps/stale [3.2] - https://github.com/kata-containers/.github/blob/master/.github/stale.yml [3.3] - Maybe; I'd like to think that we won't need to use such a feature if we can reduce the backlog down to a more manageable size. [4] - https://github.com/marketplace/actions/assign-to-one-project [5] - https://github.com/marketplace/actions/github-project-automation [6] - https://github.com/github/hub [7] - https://github.com/kata-containers/tests/blob/master/cmd/github-labels/labe… --- 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.

4 6

CFP Deadline Tomorrow - Virtual Open Infrastructure Summit
by Sunny Cai 03 Aug '20

03 Aug '20

Hi everyone, It’s time to submit your Open Infrastructure virtual Summit presentations[1]! The CFP deadline is tomorrow. Submit sessions featuring open source projects including Kata Containers, Airship, Ansible, Ceph, Kubernetes, ONAP, OpenStack, OPNFV, StarlingX and Zuul. As a reminder, these are the 2020 Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops Open Development Private & Hybrid Cloud Public Cloud Security Get your presentations, panels, and workshops in before August 4 at 11:59 pm PT (August 5 at 6:59 am UTC). The content submission process for the Forum and Project Teams Gathering (PTG) will be managed separately in the upcoming months. The Summit Programming Committee has shared topics by Track for community members interested in speaking at the upcoming Summit. Check out the submission tips[2]! Then don’t forget to register[3] for the virtual Open Infrastructure Summit taking place October 19-23, 2020 at no cost to you. Need more time? Reach out to speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> with any questions or concerns. Cheers, Sunny [1] https://cfp.openstack.org/ <https://cfp.openstack.org/app/presentations> [2] https://superuser.openstack.org/articles/virtual-open-infrastructure-summit… <https://superuser.openstack.org/articles/virtual-open-infrastructure-summit…> [3] https://openinfrasummit2020.eventbrite.com <https://openinfrasummit2020.eventbrite.com/> Sunny Cai OpenStack Foundation sunny(a)openstack.org

1 0

Kat Herders for the week... and a request for help with the issue backlog
by Hunt, James O 03 Aug '20

03 Aug '20

Hi All, This week's Kata Herders [1] are: - Peng Tao (https://github.com/bergwolf) - Archana (https://github.com/amshinde) # Statistics ## PRs - We currently have 56 open PRs (88 if you include WIP and DNM). - Last week we closed 30 PRs. If you'd like to help get these PRs landed (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]. ## Issues We'd like the community to help process the issue backlog. Historically the community has focussed more on the PRs (as these are of course actual improvements so should land as soon as they are ready). But due to the rapid pace of development in Kata, that has meant that the community are perpetually reviewing the PR backlog and (I think) never quite managing to get round to a holistic review of the issues. But that doesn't mean we shouldn't! More information to follow on issues, but having "set the scene" slightly... gulp ... here's the main statistic: - 1,015 open issues [*] (yikes!) I've added a link to the issues backlog on [1]. If you'd like to help us get that number down to a more manageable level, please do get in touch [4] ! Cheers, James [*] - Note that we believe a lot of these can be closed but, we'd like help reviewing this rather large backlog ;) [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