- kata-dev - lists.katacontainers.io

The case to integrate the tests repository
by David Gibson 22 Jan '21

22 Jan '21

Hi all, I'm a pretty recently started Kata contributor. One of many things I found frustrating when I started working on Kata was the way the code was split into a whole batch of repositories. I'm relieved that they're now merged together for Kata 2.x. However, the tests repository is still separate, and AIUI there are no plans to integrate it. I still find that really annoying, so I want to make the case for integrating it into the kata-containers repository as well. 1. It removes delays fixing test bugs On several occasions when working on code changes, I've hit CI failures due to what turn out to be bugs in the tests code. These have often been problems with static checks essentially unrelated to what I'm actually trying to accomplish. To deal with this, I've had to file a separate issue and PR against the tests repo, wait for that to be tested and reviewed, and only then can I resume work on what I was actually trying to do. Especially since I'm a different timezone from most of the Kata team, that can easily be several days of delay. If the tests were integrated, I could include a fix for the test as a commit in the same PR, it would automatically fix the CI for that PR and could be reviewed with the same batch. 2. Allows tests to be commited along with new features Obviously it's desirable for new features to come with tests for those features. Integrating the tests repo means that can be done in the same PR, reducing the amount of github busywork involved in doing so. It also means the code and tests can be reviewed and discussed in the same place. In addition to being more convenient, that means we don't need to rerun basically the same tests for both the code PR and the tests PR. That means less demand on the CI infrastructure, which helps everyone. 3. Testing scripts can be simplified AFAICT the current scripts in the tests code have a bunch of conditionals for various different configurations: Kata1 vs. Kata 2.x, Rust agent vs. Go agent amongst others. If the tests repo is integrated we can cut down the test scripts to just the cases that are relevant for the current version of the code. Understanding how the test scripts work is a real barrier to debugging Kata at the moment, so simplifying them is valuable. 3. Removes a barrier to running CI tests locally At the moment debugging CI failures is really painful, because duplicating the problem in a debuggable environment is extremely awkward. One (certainly not the only) reason for that is that the code repo and tests repo need to be both assembled together in a suitable environment. The CI scripts do that, but this often involves downloading one or the other repo from a global URL. If you want to do frequently repeated tests on a local repo while debugging, that has to be worked around. If tests and code are in the same repo, it removes the need to download either one from a global URL, making it easier to replicate the CI test in a local environment and with an ad-hoc tree. It also allows some further simplifications of the CI scripts. I could probably come up with more reasons, but those 3 seem like a solid start. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson

3 5

Fwd: [rh-kata-dev] Kubernetes Pod Privilege Escalation using kata?
by Christophe de Dinechin 22 Jan '21

22 Jan '21

With permission, I am forwarding a message from Harshal Patil. I believe he's asking an interesting question. > Begin forwarded message: > > From: Harshal Patil <harpatil(a)redhat.com> > Subject: Kubernetes Pod Privilege Escalation using kata? > Date: 21 January 2021 at 11:25:11 CET > > It would be interesting to know how those attack scenarios turn out > when kata runtime used, > > https://labs.bishopfox.com/tech-blog/bad-pods-kubernetes-pod-privilege-esca… > We could list the various "doors" described in the article in our thread assessment document, and document the impact in the case of Kata, e.g. how Kata helps. - Privileged: Not available in Kata - HostPID: Not available in Kata. GuestPID would not be nearly as bad. - HostPath: Additional opportunities for filtering through virtiofs (e.g. extended attributes, UID/GID mapping, etc) - HostNetwork: That's the part I'm least at ease with. I think we need to distinguish between virtio and SR-IOV, but also take into account that in the SR-IOV case, you have dedicated hardware. - HostIPC: Not available in Kata? We probably should also have more info on container escapes in Kata.

1 0

CI improvement issues
by Cameron Meadors 20 Jan '21

20 Jan '21

As discussed in the Architecture meeting, here are three enhancements that were identified based on issues related to CI. They are also related to the discussion about merging the tests repo into the code repo. There were basically taken from https://docs.google.com/document/d/15YobCIUFMEvdNIGem0CJ_g30hJY4YH5Lr6ty7_8… , which was shared with the kata team a few months ago. I tried summarize them and add some acceptance criteria to make them more clear. I hope this helps. -- Cameron Meadors Principal Quality Engineer Red Hat OpenShift

1 0

Giving review powers to Pavel Mores and Snir Sheriber
by Fabiano Fidêncio 18 Jan '21

18 Jan '21

Kata folks, I'd like to ask whether Pavel Mores (https://github.com/pmores) and Snir Sheriber (https://github.com/snir911) could be granted reviewer powers (and responsibilities) for the following repos: * kata-containers/kata-containers * kata-containers/tests Pavel has been doing the most part of his reviews and work on osbuilder, while Snir has been doing the most part of his reviews and work on the runtime / agent. Of course, I do vouch for them, but I also would like to ask a second vouch from someone outside of Red Hat before having them added! Best Regards, -- Fabiano Fidêncio

4 7

Weekly Kata Herders
by Hunt, James O 18 Jan '21

18 Jan '21

Hi All, This week's Kata PR and issue herders are: - Julio (https://github.com/devimc) - Pavel (https://github.com/pmores) - Ricardo (https://github.com/raravena80) - Me (https://github.com/jodh-intel) # Statistics ## Issues Issues opened last week: 24 Issues closed last week: 24 Open issues: 1124 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 65 PRs closed last week: 62 Open PRs: 134 Open PRs (excluding dnm+wip): 98 # Get involved 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 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

AC meeting (Jan 19th, 2021): Add your topics to the agenda!
by Fabiano Fidêncio 18 Jan '21

18 Jan '21

Kata Folks, Please, if you have something you'd like to have discussed as part of the architecture committee meeting happening Tomorrow (Jan 19th, 2021), please, add the items to the list: https://etherpad.opendev.org/p/Kata_Containers_2021_Architecture_Committee_… If there are no items in the agenda by the end of Today, the meeting Tomorrow will be cancelled (and that's fine as well :-)). Best Regards, -- Fabiano Fidêncio

1 0

Only a few hours left: 2021 Board elections and Bylaws amendments
by Allison Price 14 Jan '21

14 Jan '21

Hi everyone, The 2021 Individual Director elections are currently open. All members who are eligible to vote should have received an email ballot earlier this week. You can review the candidates here: https://www.openstack.org/election/2021-individual-director-election/Candid… <https://www.openstack.org/election/2021-individual-director-election/Candid…>. If you are not currently a member of the Open Infrastructure Foundation, you can join here to vote in next year’s elections: https://openinfra.dev/join <https://openinfra.dev/join> This year, the election includes a set of amendments to the Foundation’s Bylaws. The amendments were approved unanimously by the Foundation Board in 2020. As a member class, the Individual Members must also approve these amendments. You can find more information in this mailing list post by Jonathan Bryce: http://lists.openstack.org/pipermail/foundation/2021-January/002939.html <http://lists.openstack.org/pipermail/foundation/2021-January/002939.html> The deadline to vote is this Friday, January 15 at 1800 UTC / 12pm CST. Please let me know if you have any questions. Allison Allison Price Open Infrastructure Foundation allison(a)openstack.org <mailto:allison@openstack.org>

1 0

Re: [kata-dev] Regarding, Kata 2.0.0, kata-runtime, qemu OVMF
by Gupta, Sandeep 13 Jan '21

13 Jan '21

[AMD Official Use Only - Internal Distribution Only] Hi Developers, One more please - for Kata 2.0.0, kata-runtime, qemu OVMF In /etc/kata-containers/configuration.toml -- ====== # WARNING: - any parameter specified here will take priority over the default # parameter value of the same name used to start the virtual machine. # Do not set values here unless you understand the impact of doing so as you # may stop the virtual machine from booting. # To see the list of default parameters, enable hypervisor debug, create a # container and look for 'default-kernel-parameters' log entries. kernel_params = " root=/dev/vda1 rootflags=data=ordered,errors=remount-ro agent.log=debug initcall_debug" # Path to the firmware. # If you want that qemu uses the default firmware leave this option empty #firmware = "/usr/local/share/qemu/OVMF_CODE.fd.kata" firmware = "" ========== If I use the default firmware - I get correct results : # ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest sh / # / # uname -a Linux sandeepg-ubuntu 5.6.0-sev-sev-es-5.6-v3.container #3 SMP Tue Nov 3 06:38:40 UTC 2020 x86_64 GNU/Linux / # # ps -eaf | grep -i qemu root 360867 1 0 15:56 ? 00:00:01 /usr/local/bin/qemu-system-x86_64 -name sandbox-sh -uuid 72820914-dcce-4cea-a01f-3cf9851d136d -machine q35,accel=kvm,kernel_irqchip -cpu host,pmu=off -qmp unix:/run/vc/vm/sh/qmp.sock,server,nowait -m 2048M,slots=10,maxmem=129755M -device pci-bridge,bus=pcie.0,id=pci-bridge-0,chassis_nr=1,shpc=on,addr=2,romfile= -device virtio-serial-pci,disable-modern=false,id=serial0,romfile= -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/vc/vm/sh/console.sock,server,nowait -device virtio-scsi-pci,id=scsi0,disable-modern=false,romfile= -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0,romfile= -device vhost-vsock-pci,disable-modern=false,vhostfd=3,id=vsock-1189071429,guest-cid=1189071429,romfile= -device virtio-9p-pci,disable-modern=false,fsdev=extra-9p-kataShared,mount_tag=kataShared,romfile= -fsdev local,id=extra-9p-kataShared,path=/run/kata-containers/shared/sandboxes/sh/shared,security_model=none,multidevs=remap -rtc base=utc,driftfix=slew,clock=host -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic --no-reboot -daemonize -object memory-backend-ram,id=dimm1,size=2048M -numa node,memdev=dimm1 -kernel /usr/share/kata-containers/vmlinuz-sev-es-5.6-v3.container -initrd /usr/share/kata-containers/kata-containers-initrd.img -append tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 cryptomgr.notests net.ifnames=0 pci=lastbus=0 quiet panic=1 nr_cpus=240 scsi_mod.scan=none root=/dev/vda1 rootflags=data=ordered,errors=remount-ro agent.log=debug initcall_debug -pidfile /run/vc/vm/sh/pid -smp 1,cores=1,threads=1,sockets=240,maxcpus=240 root 360966 360958 0 16:05 pts/2 00:00:00 grep --color=auto -i qemu But if I use : firmware = "/usr/local/share/qemu/OVMF_CODE.fd.kata" I get Error: # ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest s ctr: failed to launch qemu: exit status 1, error messages from qemu log: qemu: could not load PC BIOS '/usr/local/share/qemu/OVMF_CODE.fd.kata' : unknown Any suggestions please. --Thanking You --Sandeep

5 14

Add Maksym as reviewer
by Eric Ernst 12 Jan '21

12 Jan '21

Hey ya'll, Maksym, [1], has been getting more involved for both development and review for the rust-agent, as well as other aspects of the runtime itself. I think it would be helpful and aid in better velocity of code if we added him as a contributor and reviewer for the org. What ya'll think? --Eric [1] - https://github.com/mxpv

4 4

AC meeting (Jan 12th, 2021): add your topics to the agenda!
by Fabiano Fidêncio 11 Jan '21

11 Jan '21

Kata Folks, Please, if you have something you'd like to have discussed as part of the architecture committee meeting happening Tomorrow (Jan 12th, 2021), please, add the items to the list. We have at least one topic from the last meeting that we didn't have time to finish and we'll cover it Tomorrow. See you all tomorrow! -- Fabiano Fidêncio

1 1

[Diversity] Diversity &Inclusion WG Meeting reminder
by Amy Marrich 11 Jan '21

11 Jan '21

The Diversity & Inclusion WG invites members of all OSF projects to our meeting today, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz)

1 0

Weekly Kata Herders
by Hunt, James O 11 Jan '21

11 Jan '21

Hi All, This week's Kata PR and issue herders are: - Carlos (https://github.com/jcvenegas) - Zhihong Yu (https://github.com/tedyu) # Statistics ## Issues Issues opened last week: 27 Issues closed last week: 17 Open issues: 1122 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 20 PRs closed last week: 32 Open PRs: 131 Open PRs (excluding dnm+wip): 96 # Get involved 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 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

Booting OVMF with -bios?
by Christophe de Dinechin 07 Jan '21

07 Jan '21

Hello Laszlo, Happy New Year! I may need to pick your brain a little regarding an issue someone testing AMD SEV ran into with Kata. Basically, here are the questions I have: 1) Is it OK to pass an OVMF firmware to the -boot option of qemu? What about SecureBoot in that case? 2) Are there any expected behavioral differences between booting with the -bios option and using a -drive if=pflash option? In particular, anything that could prevent SEV from activating in the guest kernel? 3) Knowing that in the Kata case, we don't care about anything persisting across reboots, is there any problem passing only the OVMF_CODE.fd image readonly using the -drive option, without having an OVMF_VARS.fd? Asking to see if we need to create an OVMF_VARS.fd for each container. If you need a bit of context: https://github.com/kata-containers/kata-containers/issues/1231 and http://lists.katacontainers.io/pipermail/kata-dev/2021-January/001638.html Thanks! -- Cheers, Christophe de Dinechin (IRC c3d)

4 12

Kata Containers Glossary
by helena＠openstack.org 07 Jan '21

07 Jan '21

Greetings Kata Community! About 6 months ago we began an initiative to support SEO tactics, by creating a Kata Containers glossary. By creating this glossary, we are hoping to have greater visibility to potential contributors, users, and supporting organizations. The terms have been decided on and defined, however, now we must figure out where to have the glossary exist within [ https://katacontainers.io/ ]( https://katacontainers.io/ ). Feel free to view and edit the drafted glossary [ here ]( https://etherpad.opendev.org/p/Kata_Glossary ). Most other Open Infrastructure Foundation supported projects have their glossaries exist under “docs” (see example from [ Zuul ]( https://zuul-ci.org/docs/zuul/reference/glossary.html )). I am hoping to get community feedback on where the glossary should exist. As always, feel free to reach out with any questions. Cheers, Helena

1 0

Regarding, Kata 2.0.0, kata-runtime
by Gupta, Sandeep 05 Jan '21

05 Jan '21

[AMD Official Use Only - Internal Distribution Only] Hi Developers, 1. Trying version-1 syntax: (for /usr/local/bin/containerd -config /etc/containerd/config.toml), # cat /etc/containerd/config.toml [plugins.cri.containerd] no_pivot = false [plugins.cri.containerd.runtimes] [plugins.cri.containerd.runtimes.runc] runtime_type = "io.containerd.runc.v1" [plugins.cri.containerd.runtimes.runc.options] NoPivotRoot = false NoNewKeyring = false ShimCgroup = "" IoUid = 0 IoGid = 0 BinaryName = "runc" Root = "" CriuPath = "" SystemdCgroup = false [plugins.cri.containerd.runtimes.kata] runtime_type = "io.containerd.kata.v2" [plugins.cri.containerd.runtimes.kata.options] ConfigPath = "/etc/kata-containers/configuration.toml" [plugins.cri.containerd.runtimes.katacli] runtime_type = "io.containerd.runc.v1" [plugins.cri.containerd.runtimes.katacli.options] NoPivotRoot = false NoNewKeyring = false ShimCgroup = "" IoUid = 0 IoGid = 0 BinaryName = "/usr/local/bin/kata-runtime" Root = "" CriuPath = "" SystemdCgroup = false 1. kata-runtime version 1.1.0 is successful as follows : /usr/local/bin/kata-runtime --version kata-runtime : 1.1.0 commit : 292786890bd4792226c4fbf9b5268a92c27fe0f1-dirty OCI specs: 1.0.1 1. kata-runtime ver 1.1.0 works, as follows : # ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest sh / # / # ps -eaf PID USER TIME COMMAND 1 root 0:00 sh 6 root 0:00 ps -eaf / # / # uname -a Linux kata-container 5.6.0-sev-sev-es-5.6-v3.container #3 SMP Tue Nov 3 06:38:40 UTC 2020 x86_64 GNU/Linux / # 1. For kata-runtime, ver 1.1.0 : # ps -eaf | grep -i container root 98257 1 0 03:52 ? 00:00:19 /usr/local/bin/containerd root 98329 1 0 03:52 ? 00:00:33 /usr/local/bin/containerd-shim-kata-v2 -namespace default -address /run/containerd/containerd.sock -publish-binary /usr/local/bin/containerd -id bash root 98347 1 0 03:52 ? 00:00:51 /usr/local/bin/qemu-system-x86_64 -name sandbox-bash -uuid 27d16f68-1fc9-483f-a33b-e6224772273e -machine q35,accel=kvm,kernel_irqchip -cpu host, -qmp unix:/run/vc/vm/bash/qmp.sock,server,nowait -m 512M,slots=10,maxmem=129755M -device pci-bridge,bus=pcie.0,id=pci-bridge-0,chassis_nr=1,shpc=on,addr=2,romfile= -device virtio-serial-pci,disable-modern=false,id=serial0,romfile= -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/vc/vm/bash/console.sock,server,nowait -object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0,romfile= -device virtserialport,chardev=charch0,id=channel0,name=agent.channel.0 -chardev socket,id=charch0,path=/run/vc/vm/bash/kata.sock,server,nowait -device virtio-9p-pci,disable-modern=false,fsdev=extra-9p-kataShared,mount_tag=kataShared,romfile= -fsdev local,id=extra-9p-kataShared,path=/run/kata-containers/shared/sandboxes/bash/shared,security_model=none,multidevs=remap -rtc base=utc,driftfix=slew,clock=host -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic --no-reboot -daemonize -object memory-backend-ram,id=dimm1,size=512M -numa node,memdev=dimm1 -kernel /usr/share/kata-containers/vmlinuz-sev-es-5.6-v3.container -initrd /usr/share/kata-containers/kata-containers-initrd_alpine_1.12.0-rc0_agent_5cfb8ec960.initrd -append tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 cryptomgr.notests net.ifnames=0 pci=lastbus=0 iommu=off debug panic=1 nr_cpus=240 agent.use_vsock=false root=/dev/vda1 rootflags=data=ordered,errors=remount-ro agent.log=debug initcall_debug -pidfile /run/vc/vm/bash/pid -D /run/vc/vm/bash/qemu.log -smp 1,cores=1,threads=1,sockets=240,maxcpus=240 root 99602 99593 0 07:55 pts/1 00:00:00 grep --color=auto -i container 1. Exactly the same (above) environment, kata-runtime ver 2.0.0 is failing as follows: # /usr/local/bin/kata-runtime --version : 2.0.0 commit : <<unknown>> OCI specs: 1.0.1-dev /# ctr run --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest sh ctr: Failed to check if grpc server is working: unexpected EOF: unknown 1. I can discuss this Issue in, Kata AC call in 2021 on January 5th. --Thanking You --Best Regards, --Sandeep Gupta

3 5

Weekly Kata Herders
by Hunt, James O 04 Jan '21

04 Jan '21

Hi All, This week's Kata PR and issue herders are -- tentatively: - Eric (https://github.com/egernst) - Fabiano (https://github.com/fidencio) - Salvador (https://github.com/chavafg) I say tentatively since I've only just updated the rota [1], so if this week doesn't work for folk, feel free to switch around. Related: since the backlog is rather high at the moment due to the Christmas and New Year break (106 PRs and 1,113 issues) [5][6], if anyone has spare cycles, please feel free to get involved and help out ;-) # Get involved 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]. # Note An advance warning: herding activity over the next two weeks may be somewhat disrupted by the Christmas and New Year holidays. But don't let that stop you from raising issues and PRs folks! ;-) 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 [5] - https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+ [6] - https://github.com/pulls?page=1&q=is%3Aopen+is%3Apr+org%3Akata-containers+-… James --- 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

Architecture Committee meetings for 2021 (please, add your topics to the agenda!)
by Fabiano Fidêncio 04 Jan '21

04 Jan '21

Kata folks, I've created a new etherpad for 2021 meetings [0], as we keep one etherped per year. Our next meeting, and the first one of the year, is happening Tomorrow (January 5th, 2021), in case we have topics to be discussed. So, please, if you have something that you want to cover during the meetings, please, add it to our agenda (our etherpad [0]). [0]: https://etherpad.opendev.org/p/Kata_Containers_2021_Architecture_Committee_… Best Regards, -- Fabiano Fidêncio

1 0

Canceled event: Kata containers backlog review meeting @ Tue Dec 29, 2020 6pm - 7pm (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 16 Dec '20

16 Dec '20

This event has been canceled. 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 Dec 29, 2020 6pm – 7pm Israel Time Joining info: Join with Google Meet https://meet.google.com/ttm-kvqf-tog?hs=224 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 * 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 * fgiudici(a)redhat.com * cdupontd(a)redhat.com * Kumari, Madhuri * cmeadors(a)redhat.com * azaalouk(a)redhat.com * Fabiano Fidêncio * kata-dev(a)lists.katacontainers.io * Peng Tao * Larrew, Jesse Invitation from Google Calendar: https://calendar.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://calendar.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

Canceled event: Kata containers backlog review meeting @ Tue Dec 22, 2020 6pm - 7pm (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 16 Dec '20

16 Dec '20

This event has been canceled. 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 Dec 22, 2020 6pm – 7pm Israel Time Joining info: Join with Google Meet https://meet.google.com/ttm-kvqf-tog?hs=224 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 * 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 * fgiudici(a)redhat.com * cdupontd(a)redhat.com * Kumari, Madhuri * cmeadors(a)redhat.com * azaalouk(a)redhat.com * Fabiano Fidêncio * kata-dev(a)lists.katacontainers.io * Peng Tao * Larrew, Jesse Invitation from Google Calendar: https://calendar.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://calendar.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

Architecture Meetings will be back on January 5th, 2021
by Fabiano Fidêncio 16 Dec '20

16 Dec '20

Kata Folks, On behalf of the Architecture Committee I'd like to announce that the next meetings for this year are cancelled due to the holidays. The meetings will be back on January 5th, 2021. Enjoy the holidays, and be safe! -- Fabiano Fidêncio

1 0

Planning ahead for events!
by Fabiano Fidêncio 16 Dec '20

16 Dec '20

Kata Folks, During Today's Architecture Committee's meeting we've discussed the possibility of planning ahead for events, in order to brainstorm for Kata Containers talks in time before each CfP deadline. With a good reception of the idea, we'd like to ask the community which are the conferences that you see as interesting for the project. Right now, we're looking at: * FOSDEM (www.fosdem.org) * KubeCon, both North American (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/) and European (https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/) editions; * KVM Forum (https://events.linuxfoundation.org/kvm-forum/) * Open Source Summit, both North American (https://events.linuxfoundation.org/open-source-summit-north-america/) and European (https://events.linuxfoundation.org/open-source-summit-europe/) editions; * QCon (https://qconferences.com/) * The Open Infrastructure Summit (https://www.openstack.org/summit/) Please, feel free to add more conferences that you think that could be interesting to the project; It's been also brought up that we can talk about Kata Containers beyond the scope of the container runtimes, but also in focused areas such as: * CI/CD; * Observability; * Confidential Computing; * Containers Security; Please, feel free to add more areas that you think that could be used to cover Kata Containers in a presentation; Last but not least, it was mentioned that we could provide guidance and help folks to represent the Kata Containers community, in case you are interested in talking about the project. As usual, feedback is more than welcome! Best Regards, -- Fabiano Fidêncio

1 0

Impact of the XML vulnerabilities for Kata Containers
by Christophe de Dinechin 16 Dec '20

16 Dec '20

Hey Team, In case you have not seen it yet, a new vulnerability in how Go handles XML has just been disclosed: https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/ I suspect that we are indirectly impacted by this, although I have not read the disclosure in details yet. From a very cursory search in our code base, it looks like several vendored components may be directly hit. I don't see any immediate risk, in the sense that I don't think we expose any XML interface. But I may be wrong. What do you think? Thanks Christophe

2 1

Weekly Kata Herders
by Hunt, James O 15 Dec '20

15 Dec '20

Hi All, This week's Kata PR and issue herders are: - Christophe (https://github.com/c3d) - Gaby (https://github.com/GabyCT) - Jongwu (https://github.com/jongwu) # Statistics ## Issues Issues opened last week: 32 Issues closed last week: 17 Open issues: 1114 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 33 PRs closed last week: 9 Open PRs: 152 Open PRs (excluding dnm+wip): 115 # Get involved 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]. # Note An advance warning: herding activity over the next two weeks may be somewhat disrupted by the Christmas and New Year holidays. But don't let that stop you from raising issues and PRs folks! ;-) 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 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

Need your help in labeling the kata issue backlog
by Ariel Adam 14 Dec '20

14 Dec '20

Hi everyone. Following the discussion on labeling the backlog of kata issues we have using "area/*" labels, we need your help :-). On the weekly backlog issue meetings we continue to go over issues with "needs-review" labels and mark them with "area/*" labels. Problem is that we cover around 20 issues on average every meeting and since that's about the amount of issues opened every week our progress is slow. If we look at the overall issues we have opened this year that don't have "area/*" labels we are at 329 issues: https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+crea… We would appreciate if each of you could take a few minutes to review the subset of issues you opened or are assigned to you and label them (area/api, area/cli, area/config, area/documentation, area/logging, area/networking, area/performance, area/storage, area/tracing, area/packaging etc...). Once we have those labels we can finally move to a dashboard showing categories of issues which should help everyone focus on topics that fit their expertise. If you have any problems adding labels let us know and we will help you. Thanks.

2 2

Weekly Kata Herders
by Hunt, James O 10 Dec '20

10 Dec '20

Hi All, This week's Kata PR and issue herders are: - Chelsea (https://github.com/cmaf) - Christophe (https://github.com/c3d) - Julio (https://github.com/devimc) - Me (https://github.com/jodh-intel) - Ricardo (https://github.com/raravena80) # Statistics ## Issues Issues opened last week: 26 Issues closed last week: 22 Open issues: 1097 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 19 PRs closed last week: 23 Open PRs: 125 Open PRs (excluding dnm+wip): 90 # Get involved 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 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.

2 3