- kata-dev - lists.katacontainers.io

Updated invitation with note: Kata containers weekly use cases meeting @ Weekly from 3pm to 4pm on Thursday (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 16 Mar '21

16 Mar '21

This event has been changed with this note: "Changing the google meet to a zoom session curtesy of Sunny :-). " Title: Kata containers weekly use cases meeting Discussing kata container use cases and working on relevant tasks.Meeting notes:https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRT… will be recorded for those who can't attend. Join Zoom Meetinghttps://zoom.us/j/98038141932Passcode: kataMeeting ID: 980 3814 1932One tap mobile+12532158782,,98038141932# US (Tacoma)+13462487799,,98038141932# US (Houston)Dial by your location        +1 253 215 8782 US (Tacoma)        +1 346 248 7799 US (Houston)        +1 669 900 6833 US (San Jose)        +1 301 715 8592 US (Washington DC)        +1 312 626 6799 US (Chicago)        +1 646 876 9923 US (New York)Meeting ID: 980 3814 1932Find your local number: https://zoom.us/u/adGVd3H0IA (changed) When: Weekly from 3pm to 4pm on Thursday Israel Time Where: https://zoom.us/j/98038141932 (changed) Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io * Gupta, Sandeep * Liam Merwick * Boris Ostrovsky * Karl Heubaum * fgiudici(a)redhat.com * Boeuf, Sebastien * Ortiz, Samuel * slp(a)redhat.com * ffidenci(a)redhat.com Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=MzIxaGJjdjluZjRr… 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

AC meetings (Mar 16th, 2021): Add your topics to the agenda!
by Fabiano Fidêncio 15 Mar '21

15 Mar '21

Kata Folks, Please, if you have something you'd like to have discussed as part of the architecture committee meeting happening Tomorrow (Mar 16th, 2021), please, add the items to the list: https://etherpad.opendev.org/p/Kata_Containers_2021_Architecture_Committee_… Please, follow the guidelines for adding a topic to the agenda: https://github.com/kata-containers/community/blob/master/AC-Meeting-Guideli… If no topics are added till Tomorrow 12:00 UTC, the meeting will be cancelled. Best Regards, -- Fabiano Fidêncio

1 0

Weekly Kata Herders
by Hunt, James O 15 Mar '21

15 Mar '21

Hi All, This week's Kata PR and issue herder is: - Eric (https://github.com/egernst) If you have any spare cycles, please consider helping Eric out! # Statistics ## Issues Issues opened last week: 24 Issues closed last week: 30 Open issues: 1093 ## PRs PRs opened last week: 20 PRs closed last week: 23 Open PRs: 149 Open PRs (excluding dnm+wip): 109 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 # 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

Kata containers weekly use cases meeting summary - March 11th 2021
by Ariel Adam 11 Mar '21

11 Mar '21

Hi everyone. Following are the meetings notes from today's meeting: https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh… The meeting was recorded however I discovered now that since it was a google meet I can only share it with gmail accounts (and kata-dev@ isn't a gmail account). For those who want to see the recording please send me your gmail and I will add you. We will look for a different way to record the meeting next week. Thanks.

1 0

Kata containers weekly use cases meetings Thursday's 8AM EST
by Ariel Adam 11 Mar '21

11 Mar '21

Hi everyone. Following the doodle poll results the weekly kata use cases meeting will be on Thursday's 8AM EST. For the 1st meeting happening this Thursday we've added 3 questions to each of the use case we hope people could answer before the meetings: 1. How do you envision kata containers being used in this use case? 2. What do you think should be the outcome of this use case work? 3. What do you think are the tasks that should be done as part of this work? Google doc for the meeting with the questions: https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh… Thanks.

1 2

February 2021 Kata Containers Architecture Committee elections is over.
by Fabiano Fidêncio 10 Mar '21

10 Mar '21

Kata citizens, On behalf of myself, Fabiano Fidêncio, and Ricardo Avarena, as the approved election officials, we'd like to announce that the period for Architecture Committee elections submissions is now closed, and so is this round of elections. We are am happy to announce that we have had submissions from: - Peng Tao - Samuel Ortiz You can view those submissions at: https://github.com/kata-containers/community/tree/master/elections/arch-com… Given we have two open seats and two candidates, the election is now over. We'd like to invite everyone to welcome Peng Tao to his new role at the Architecture Committee, and to congratulate Samuel Ortiz for renewing his role! Last but not least, here's a reminder of the Architecture Committee Responsibilities. Architecture Committee members guide the technical direction of the Kata Containers project. This includes, but is not limited to: * Serving the Kata technical community * Driving technical direction * Handling interactions with other governance bodies * Acting as the final call in technical disputes * Ensuring inclusive, open collaboration and development * Identifying gaps in technical direction or community health * Attending Architecture Committee meetings * Regular participation (and advanced notice of absences) in online Arch Committee meetings and in-person meetings is expected * Actively participates in Kata Containers design and development * Not restricted to code contributions, but active input and guidance is expected Changes to our community documents will be done along this and the coming week to reflect the results of this election. Again, congratulations Samuel and Tao! Best Regards, -- Fabiano Fidêncio

2 1

[elections] [2021-02] Samuel Ortiz candidacy
by Samuel Ortiz 09 Mar '21

09 Mar '21

All, I'd like to run for renewing my AC seat, as part of the 2021-02 election round. Name: Samuel Ortiz Email: sameo(a)linux.intel.com Background: I am a Principal Software Engineer working for Intel, where I work on several projects related to virtualization and containers: Kata Containers, rust-vmm and Cloud Hypervisor. I started to work on Kata Containers a few years ago, back when I initially led the Clear Containers project at Intel. Since then I have contributed to many different areas of the project, from core components like the virtcontainers package to integration work with the CRI-O and containerd projects. Together with the folks from hyper.sh, we began the Kata Containers journey with the ambitious goal of providing stronger isolation to cloud native workloads, with minimal overhead. Three years ago, this was a fairly innovative approach and at some point I stopped counting the number of hours that Xu, Eric, Peng or myself spent at conferences, meetups or foundation booths demonstrating how Kata Containers met that promise. I believe it is now time to bring the next generation of hardware isolation and confidentiality technologies to the cloud native ecosystem, and in the upcoming months I'd like to help the Kata Containers project reach that goal.

1 0

AC meetings (Mar 8th, 2021): Add your topics to the agenda!
by Fabiano Fidêncio 09 Mar '21

09 Mar '21

Kata Folks, Please, if you have something you'd like to have discussed as part of the architecture committee meeting happening Tomorrow (Mar 8th, 2021), please, add the items to the list: https://etherpad.opendev.org/p/Kata_Containers_2021_Architecture_Committee_… Please, follow the guidelines for adding a topic to the agenda: https://github.com/kata-containers/community/blob/master/AC-Meeting-Guideli… If no topics are added till Tomorrow 12:00 UTC, the meeting will be cancelled. Best Regards, -- Fabiano Fidêncio

4 4

About the build of QEMU on Kata Containers
by Wainer dos Santos Moschetta 08 Mar '21

08 Mar '21

Hi all, While working on updating the version of QEMU [1] used on the project, for some occasions people outside asked me why the project builds QEMU from source instead of relying on distro's provided. When I started contributing to this project I asked it myself many times but I never looked for an answer. I can think on many reasons but I would be guessing. So If someone could share the rationale here, I would appreciate it. Perhaps more important, we could discuss if the scenario stands the same so that we should stick with that approach or if we could manage the QEMU build differently nowadays. [1] https://github.com/kata-containers/kata-containers/pull/1349 Thanks in advance, Wainer dos Santos Moschetta Software Engineer, Red Hat, Brazil

3 2

Weekly Kata Herders
by Hunt, James O 08 Mar '21

08 Mar '21

Hi All, This week's Kata PR and issue herders are: - bergwolf (https://github.com/bergwolf) - Chelsea (https://github.com/cmaf) # Statistics ## Issues Issues opened last week: 21 Issues closed last week: 22 Open issues: 1098 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 18 PRs closed last week: 22 Open PRs: 152 Open PRs (excluding dnm+wip): 112 # 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

Invitation: Kata containers weekly use cases meeting @ Weekly from 3pm to 4pm on Thursday (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 07 Mar '21

07 Mar '21

You have been invited to the following event. Title: Kata containers weekly use cases meeting Discussing kata container use cases and working on relevant tasks.Meeting notes:https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRT… will be recorded for those who can't attend.  When: Weekly from 3pm to 4pm on Thursday Israel Time Joining info: Join with Google Meet https://meet.google.com/szz-kxsy-mia?hs=224 Join by phone (IL) +972 73-359-9899 (PIN: 8002503033382) More joining options: https://tel.meet/szz-kxsy-mia?pin=8002503033382&hs=0 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=MzIxaGJjdjluZjRr… 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

Nominate Peng Tao as an AC candidate
by Xu Wang 03 Mar '21

03 Mar '21

Hi folks, I missed the last AC meeting because I had to attend the foundation board meeting because our company, Ant Group, has joined the OIF. And we commit we will keep working with Kata Containers for future great releases. Because I will work with the foundation board and other affairs, I nominate Peng Tao as an AC candidate. He is one of the Kata top contributors in our team, and a release manager of many kata releases. I believe he is the guy we could trust. I won't leave the community and I and all my team members will keep supporting Peng Tao's job. Name: Peng, Tao Email: bergwolf(a)hyper.sh, bergwolf(a)antgroup.com Background: Peng Tao is a staff engineer of Ant Group. In Ant Group, we have large deployments of Kubernetes and about 10K nodes of them are running Kata containers. Our team is responsible for the runtime and cloud-native storage of Ant Group. Peng Tao, together with Xu and other teammates, used to be the dev team of hyper.sh. The team was one of the creators of Kata Containers, and has kept working on Kata Containers since joining Ant Group. When the Kata Containers project was created, Peng Tao committed the first commit for it: https://github.com/kata-containers/proxy/commit/94a07ff010b80fad8235278032d… And he was known as the release manager of the Kata 2.0 as well. In 2021, Ant Group has joined the Open Infrastructure and become a member of the board of directors. We commit our team will keep working with the Kata Community for the following release cycles. -- Xu Wang (@gnawux) Senior Staff Engineer at Ant Financial A Member of Kata Containers Architecture Committee

1 0

Rust agent debug
by Qian Cai 03 Mar '21

03 Mar '21

I am chasing a bug that "crictl rm" returns ESRCH which ends up tracking down in the rust agent code: https://github.com/kata-containers/kata-containers/blob/a12772c6010f6886be7… I don't yet understand how to get some debugging messages outside of the agent, so I can see why it return ESRCH. I tried added things like, info!(sl!(), "KKK in do_signal_process()"); but I can't see that message anywhere. I even setup a debug console which allows me to connect to a shell, but that is. The only way I can get some message out (showed up in the CRI daemon logs) so far is, return Err(anyhow!("KKK in do_signal_process()")); which has to terminate the function. Do I have to use things like agent-ctl to capture those "info!" output? Anyway, it is even better if anyone has some ideas on the bug itself which is that if we do a "crictl rm" without "crictl start" first, it will error out. # crictl runp --runtime=kata pod-config.json # crictl create <sid> container-pod.json pod-config.json # crictl rm <cid> ERRO[0010] removing container "144cf0b64d154983da7419a5e8ae5bcb796cc7b054aa7fdcfbb6c44ad8f33621" failed: rpc error: code = Unknown desc = unable to stop container 144cf0b64d154983da7419a5e8ae5bcb796cc7b054aa7fdcfbb6c44ad8f33621: failed to stop container 144cf0b64d154983da7419a5e8ae5bcb796cc7b054aa7fdcfbb6c44ad8f33621: ESRCH: No such process: unknown FATA[0010] unable to remove container(s) # cat pod-config.json { "metadata": { "name": "alpine-sandbox", "namespace": "default", "attempt": 1, "uid": "hdishd83djaidwnduwk28bcsb" }, "log_directory": "/tmp", "linux": { } } # cat container-pod.json { "metadata": { "name": "alpine" }, "image":{ "image": "alpine" }, "command": [ "sleep", "3600" ], "log_path":"alpine.0.log", "linux": { } }

3 4

Kata containers community use cases weekly meeting
by Ariel Adam 03 Mar '21

03 Mar '21

Hi everyone. We have created a doodle poll for the kata community weekly use cases meeting: https://doodle.com/poll/ztmz3xiampncyemp?utm_source=poll&utm_medium=link Samuel and I tried finding timeslots we can both attend (challenging :-)). If these time slots don't work for you and you still want to attend please let us know. We'd appreciate it you could answer this poll by Thursday EOD so we can schedule the meeting accordingly. For those who are in very different time zones such as Australia (Atlassian for example) we will schedule a short early meeting as well so they can also attend. Thanks.

1 2

Impact of our current choice of PCI topology
by Christophe de Dinechin 03 Mar '21

03 Mar '21

With David's permission, let me forward a discussion regarding PCI topology in qemu. The discussion is how to accelerate hot-plugging in qemu guests, in order to reduce boot time. But that also brought an interesting summary of the impact of the choices Kata makes regarding PCI topology, which I thought was worth sharing with this list. > > On 15 Feb 2021, at 07:09, David Gibson <dgibson(a)redhat.com> wrote: > > On Mon, 8 Feb 2021 09:42:22 +0100 >>>> >>>> I'm curious if the device itself reacts faster than that. If so, could >>>> we consider making the delay a kernel command-line option? >>>> Maybe that's already done somewhere? >>> >>> Hm, if we're willing to play fast and loose with the spec, maybe. >> >> The assumption would be that this is only under virtualization, so >> we may have increased control of the "operator". That may be >> enough to compensate with "playing fast and loose". Maybe. > > Hm, true. My first inclination was to reject that idea, but thinking > about it further, we do really control both "sides" of the protocol, so > hacking in this way might be a reasonable compromise in the medium term > (longer term, I think ACPI hotplug is probably the answer). > >> [...] >> [...] >> [...] >> [...] >> >> Well, presently kata does something like this: >> >> -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=,max_ports=2 >> -device virtconsole,chardev=charconsole0,id=console0 >> -device virtio-scsi-pci,id=scsi0,disable-modern=false,romfile= >> -device virtio-rng-pci,rng=rng0,romfile= >> -device vhost-vsock-pci,disable-modern=false,vhostfd=3,id=vsock-908331243,guest-cid=908331243,romfile= >> -device vhost-user-fs-pci,chardev=char-9ebd3233988c581e,tag=kataShared,romfile= >> -device driver=virtio-net-pci,netdev=network-0,mac=9a:be:ea:cc:8f:8f,disable-modern=false,mq=on,vectors=4,romfile= >> >> >> whereas libvirt uses a root port: >> >> -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 >> -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 >> -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 >> -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 >> -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 >> -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 >> -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 >> -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 >> -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 >> -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-2-format,id=virtio-disk0,bootindex=1 >> -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:cd:ed:dd,bus=pci.1,addr=0x0 >> -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.6,addr=0x0 >> >> >> I remember someone mentioning that the kata approach was outdated, and introduced some limitations with respect to hotplugging, but I can't recall the details. What are the implications with respect to hotplug of using pci-bridge? > > There are several. > > 1. Using a bridge means we are using SHPC rather than PCI-e native > hotplug, which has the tradeoffs I discussed earlier. > > 2. On the other hand, using one bridge gives us 32 slots we can > potentially plug into, whereas each port just gives us one. This > makes managing the number of available hotplug slots much easier, > and is the main reason that Kata kind of prefers to use the bridge > at the moment. > > 3. Not strictly related to hotplug, but using a bridge does mean that > all the devices under it will be in the same *guest* IOMMU group, > even if they're in different host IOMMU groups. That has several > implications: > - It wouldn't be possible to hand in several VFIO devices and > give them each to *different* userspace drivers in the guest > (e.g. two separate DPDK applications running as different > processes). That's probably not all that likely in practice, > since putting separate DPDK apps in separate containers seems a > more likely choice. > - At also means we can't use some of the devices under the bridge > with DPDK while others are used by guest kernel drivers. Since > certain storage options involve hotplugging PCI devices to the > guest which are then bound to guest drivers, this would rule > out using DPDK with those storage configurations

1 0

PTG | Shall we do something for the event?
by Fabiano Fidêncio 02 Mar '21

02 Mar '21

During the Architecture Committee's meeting held on March 2nd, 2021, we discussed how we should approach the PTG, which are the discussions we'd like to have, which are the topics we'd like to present, and which are the topics we'd like to learn from. A document[0] has been created in order to gather ideas and then, to later on, map those ideas into slots (which will be announced at some point early next week). We, as Kata Containers, would love to get ideas and feedback from the community around the project about what the community thinks that could be interesting to see, what the community thinks that could be interesting to share with us. So, please, if you're a security enthusiast, a student hacking on the project, a writer planning to improve our documentation, someone who tried to use Kata Containers but ended up hitting some roadblock, you, a happy user and / or developer of this ecosystem, you, a member of this list, please, help us to brainstorm on how we could better use this time in benefit of the community. Please, while filling up the ideas, also add the timezone you're based in. This will help us to better prepare the schedule once we have the information about the slots. [0]: https://docs.google.com/document/d/1Zt2KRFlJLbyT2mFEq5dqbclOoRSL_T9kpXrbMjY… Best Regards, -- Fabiano Fidêncio

1 0

Backlog Review | Checking the issues with the higher priority are moving on
by Fabiano Fidêncio 02 Mar '21

02 Mar '21

During Today's Backlog Review meeting Ariel brought up a discussion about how to proceed in order to ensure high priority issues are moving, in order to understand whether something is blocking the development (either a CI failure, a review missing, or just bits & pieces that must be put together). One suggestion that came up is an email sent to the list, on a weekly basis, checking the status of those, CC'ing the people working on the issues themselves. We'd like to gather some feedback on what people from the community would be okay with such an approach before it's put in action. The intention here is *not* to add more pressure on the members working on the issue, the intention here is *not* to make the parts involved duplicate their communication work. The plan is rather to hint which are the areas the herders could be focusing on in order to help the community to solve the issues with a higher impact and higher priority. Please, let us know about your opinion on this. Best Regards, -- Fabiano Fidêncio, on behalf of the Kata Containers community.

1 0

April 2021 PTG Reg Info
by Sunny Cai 02 Mar '21

02 Mar '21

Hi Kata citizens, As you might have known that the next virtual PTG will take place April 19-23, 2021 [1]. The PTG registration is now open[2]. Like last time, it is free, but we will again be using it to communicate details about the event (schedules, passwords, etc), so please take two minutes to register! Early next week we will send out info to mailing lists 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. [1] https://www.openstack.org/ptg/ [2] https://april2021-ptg.eventbrite.com Thanks, Sunny Cai Open Infrastructure Foundation sunny(a)openstack.org

1 0

April 2021 PTG Dates & Registration
by Kendall Waters 01 Mar '21

01 Mar '21

Hello Everyone! I'm sure you all have been anxiously awaiting the announcement of the dates for the next virtual PTG[1]! The PTG will take place April 19-23, 2021! PTG registration is now open[2]. Like last time, it is free, but we will again be using it to communicate details about the event (schedules, passwords, etc), so please take two minutes to register! Early next week we will send out info to mailing lists 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. Can't wait to see you all there! -the Kendalls (diablo_rojo & wendallkaters) [1] https://www.openstack.org/ptg/ <https://www.openstack.org/ptg/> [2] https://april2021-ptg.eventbrite.com <https://april2021-ptg.eventbrite.com/>

1 0

February 2021 Kata Containers Architecture Committee elections are open!
by Fabiano Fidêncio 01 Mar '21

01 Mar '21

Hello Kata Citizens, On behalf of myself, Fabiano Fidêncio, and Ricardo Aravena, as the approved election officials, it's a pleasure to announce that the Kata Containers Architecture Committee Elections for February 2021 are open! There are two Architecture Committee seats up for election. The seats up for election are currently filled by `Xu Wang`, and `Samuel Ortiz`. The timeline for the election process is: • Election officials approved by AC: February 23 * February 24, 15:00 UTC - March 3, 2021 14:59 UTC: Candidate nominations open * March 4, 15:00 UTC - March 15, 2021 14:59 UTC: Q&A/Debate period * March 16, 15:00 UTC - March 22, 2021 14:59 UTC: Voting open * March 23, 2021, results announced The window will be open for candidates to post their submissions, from February 24th, 15:00 UTC. The process to submit a nomination is: 1) Review the responsibilities of the Architecture Committee members [1] 2) Between now and March 3 at 14:59 UTC, you can declare your candidacy for one of the open seats by submitting a text file with your name (please put your name as the file name), the reason for running, and your platform/objectives to this folder [2]. Please also send a message to the kata-dev ML with this same info, declaring your candidacy. Who can vote: Anyone who has had a commit merged into the project in the last 12 months will be eligible to vote. All eligible voters will receive an email with a link to the voting system once the voting period opens. More details of the election process are outlined at [3] and in the etherpad at [4]. Note, once candidacy entry has closed and we enter the debate period, where we will be openly asking the candidates some questions around their candidacy. The community is encouraged to submit questions via the election officials and etherpad at [4] - get your thinking caps on now in preparation... we shall then filter, review, and choose a set of suitable questions for the candidates. Please let us know if you have any questions about running for a seat or the election process! [1] https://github.com/kata-containers/community/tree/master/elections#architec… [2] https://github.com/kata-containers/community/tree/master/elections/arch-com… [3] https://github.com/kata-containers/community/tree/master/elections [4] https://etherpad.opendev.org/p/KataArchCommElections_Feb2021 Best Regards, -- Fabiano Fidêncio

1 1

AC meetings (Mar 2nd, 2021): Add your topics to the agenda!
by Fabiano Fidêncio 01 Mar '21

01 Mar '21

Kata Folks, Please, if you have something you'd like to have discussed as part of the architecture committee meeting happening Tomorrow (Mar 2nd, 2021), please, add the items to the list: https://etherpad.opendev.org/p/Kata_Containers_2021_Architecture_Committee_… The meeting on Mar 2nd is happening, as we already have topics to cover! Best Regards, -- Fabiano Fidêncio

1 0

Weekly Kata Herders
by Hunt, James O 01 Mar '21

01 Mar '21

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) - Snir (https://github.com/snir911) # Statistics ## Issues Issues opened last week: 35 Issues closed last week: 24 Open issues: 1098 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 27 PRs closed last week: 22 Open PRs: 155 Open PRs (excluding dnm+wip): 113 # 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

how kata suppports multi-nic(docker's network model does work well with kata)
by ylg 24 Feb '21

24 Feb '21

Hi,all: 1. how kata suppports multi-nic, could give your command line of kata-network 2. docker's network model does not work well with kata thanks

1 0

Kata backlog review updates status
by Ariel Adam 23 Feb '21

23 Feb '21

Hi everyone. After many many weekly backlog review meetings we have finally gotten the backlog of "needs-review" issues (opened since January 2020) to 0 open issues :-) <https://github.com/issues?page=1&q=is%3Aissue+is%3Aopen+org%3Akata-containe…> . Kudos to everyone who joined this effort and helped getting the numbers down week after week. Looking forward it would be great if the weekly herders could also review the open issues and help keep the numbers low. Moving to the next part of the backlog review work we are now focusing on the kata-containers/kata-containers repository (we figured it would be a good repository to start with) and the buckets we labeled in it (using "area/*"): https://github.com/kata-containers/kata-containers/labels?q=area%2F The goal is to review those issues and catagorize them into 3 priorities (using labels as well): - high-priority - medium-priority - low-priority This should help us later on understand where we should ask people from the community to focus on based on priority. Feel free to jump on those buckets and add priorities in areas you are familiar with or join our weekly meeting (after the AC call). Thanks.

1 0

Kata containers community use cases proposals for 2021
by Ariel Adam 23 Feb '21

23 Feb '21

Hi everyone. Samual and I would like to propose 2 use cases for the kata community to focus on in 2021 as a way to help the community create a roadmap and improve its overall presence. The use cases are *K8S CI/CD pipeline* and *confidential computing.* In the document below we provide additional details on the overall proposal, use cases, the why, the what and how. Generally speaking we thought it would be more useful to present concrete use cases and a proposed process to the community (weekly calls, commitment from companies etc..) instead of just raising it as an open question and high level ideas. We do however want to emphasize that this is only a proposal and we see it as a beginning of a discussion we hope to have in the community regarding the plans for 2021. Feel free to add comments/suggestions in the doc or reply on this mail thread with your comments/feedback. https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh… Thanks. Samual and Ariel.

3 8