January 2022 - kata-dev - lists.katacontainers.io

virtio-fs + VM Templating
by Mahalingam, Ganesh 01 Sep '25

01 Sep '25

Peng, Stefan, While working on enabling virtio-fs on Kata there was a small confusion on whether virtio-fs can work with VM Templating. With the current setup of kata, VM templating and virtio-fs are mutually exclusive (VM templating is enabled in qemu-lite and virtio-fs currently only with NEMU), but they will converge very soon. An open question we had was, would they both work with each other given that VM templating turns off memory sharing for all VMs other than the first one and virtio-fs expects guest memory be shared & file-backed for all VMs. Can both these features to be enabled in kata at the same time and if so, what are we missing to get to that end point? I will open a bug once we know what needs to be worked on to make this happen. -- Ganesh

7 20

Confidential Containers Community Meeting 1/27/22
by Tobin Feldman-Fitzthum 27 Jan '22

27 Jan '22

Hello, As usual we have a CC Community Meeting tomorrow at 2:00 PM UTC - 9 AM EST - 10PM CST. We will highlight some of the recent PRs and issues and share progress updates and blockers with the community. Next, we will talk about the recent proposal for secure storage. Finally, we will float some ideas regarding community governance. As usual, feel free to add to the agenda.[1] See you tomorrow, Tobin [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

1 0

Kata Annual Report
by Sunny Cai 27 Jan '22

27 Jan '22

Hi all, The 2021 Kata Containers annual report is live! Please see the links below: 2021 Kata annual report: https://medium.com/kata-containers/2021-openinfra-annual-report-kata-contai… You can also see the Kata annual report with all the other OpenInfra projects on the 2021 OpenInfra annual report: https://openinfra.dev/annual-report/2021 Thanks, Sunny Cai OpenInfra Foundation Marketing & Community

1 0

RFH: Confidential Containers Glossary
by Hunt, James O 27 Jan '22

27 Jan '22

Hi All, Hot on the heels of the Kata Containers glossary [1][2], we've started a glossary for Confidential Containers (CC) [3] in the wiki at [4]. As you'll see if you look at [4], CC uses a *lot* of acronymns and abbreviations, so please help the community by contributing to this important document. Cheers, James [1] - http://lists.katacontainers.io/pipermail/kata-dev/2022-January/002342.html [2] - https://github.com/kata-containers/kata-containers/wiki/Glossary [3] - https://github.com/confidential-containers/documentation/issues/13 [4] - https://github.com/confidential-containers/documentation/wiki/Glossary --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

April 2022 Virtual PTG Dates & Registration
by Kendall Nelson 25 Jan '22

25 Jan '22

Hello Everyone! We're happy to announce the next virtual PTG[1] will take place April 4-8, 2022! Registration is now open[2]. The virtual PTG is free to attend, but make sure to register so you receive important communications like schedules, passwords, and other relevant updates. Next week, keep an eye out for info regarding team sign-ups. Can't wait to see you all there! -Kendall Nelson (diablo_rojo) [1] https://www.openstack.org/ptg/ [2] https://openinfra-ptg.eventbrite.com/

1 0

Weekly Kata Herders
by Hunt, James O 24 Jan '22

24 Jan '22

Hi All, # Herders This week's Kata PR and issue herders [1] are: - Archana (https://github.com/amshinde) - bergwolf (https://github.com/bergwolf) - Jakob (https://github.com/Jakob-Naucke) # Statistics ## Issues Issues opened last week: 60 Issues closed last week: 49 Open issues: 527 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 55 PRs closed last week: 50 PRs merged last week: 39 Open PRs: 77 Open PRs (excluding dnm+wip): 57 # 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/main/CONTRIBUTING.md [3] - https://github.com/kata-containers/community/blob/main/Rota-Process.md [4] - https://github.com/kata-containers/community#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.

1 0

RFH: Kata Project Glossary
by Hunt, James O 22 Jan '22

22 Jan '22

Hi All, TL;DR - Get hacking on https://github.com/kata-containers/kata-containers/wiki/Glossary ## Intro Don't know what to do with all that spare time you'll have over the holidays? Looking for an easy way to get involved in the Kata community? Then help us work on the project glossary! ## Why? We have an in-tree glossary [1], but it's very minimal. By expanding this document, we help newcomers to the project get a better understanding of what Kata is, and faster! We also get the chance to cross reference to the existing documentation which might lead to interesting possibilities (docs needing updates, forgotten features / features you didn't even know Kata had?, docs that need writing, etc). ## Detail I've copied it into the wiki [2] to give the community a chance to help update and flesh out this important document. ## What to add? We need as many useful terms, acronymns and abbreviations related to Kata Containers (and the technologies, frameworks and project/products it touches) as possible. Acronymns and abbreviations should be added, defined in full and described (ideally in a single sentence). References to existing in-tree docs is encourage to avoid duplication where appropriate. ## Inspiration For ideas, tal at: - The existing documentation [5] (maybe starting with the architecture document). - Spell checker: you might also be able to harvest bits from the Kata spell checker word lists files [6]. - The versions databases [7], [8]. ## What next? Once the wiki version of the document starts to improve over time we can do one of: - Move the wiki version back into the repo. - Delete the in-tree version and just keeping the glossary in the wiki (might be better as it allows immediate update). ## Ground rules - Please try to retain the existing formatting. - Consider the doc requirements [3]. - Please don't add the many, many, many, many, many Confidential Container/Computing acronymns and abbreviations (since imho they should be handled in the CC organisation's own glossary (see [4])). ## Advice If you are comfortable with git, you might want to consider making your changes locally and then pushing directly. No PRs or issues required! ```bash $ git clone https://github.com/kata-containers/kata-containers.wiki $ cd kata-containers.wiki $ << hack >> $ git commit -asm "glossary: my awesome edits" $ git push ``` This might make dealing with collisions" caused by multiple community members trying to edit at the same time less painful to deal with. Oh, and no force pushing please! ;) ## For perfectionists If you're using the git CLI approach consider spell-checking your changes using the Kata spell checker [9] and the Kata markdown checker [10]. Get hacking y'all! Cheers, James [1] - https://github.com/kata-containers/kata-containers/blob/main/Glossary.md [2] - https://github.com/kata-containers/kata-containers/wiki/Glossary [3] - https://github.com/kata-containers/kata-containers/blob/main/docs/Documenta… [4] - https://github.com/confidential-containers/documentation/issues/13 [5] - https://github.com/kata-containers/kata-containers/tree/main/docs [6] - https://github.com/kata-containers/tests/tree/main/cmd/check-spelling/data [7] - https://github.com/kata-containers/kata-containers/blob/main/versions.yaml [8] - https://github.com/kata-containers/tests/blob/main/versions.yaml [9] - https://github.com/kata-containers/tests/tree/main/cmd/check-spelling [10] - https://github.com/kata-containers/tests/tree/main/cmd/check-markdown --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 2

[Diversity] Diversity and Inclusion WG new meeting time
by Amy Marrich 21 Jan '22

21 Jan '22

Thank you to those who responded to the Doodle for our meeting time. The day and time selected was Friday at 15:00 UTC so we will move to that in February with our first meeting being on 2/4. As usual, should we need to cancel the first Friday of the month we have the backup date of the third week. Should we end up having to do that too frequently ,as Fridays are popular for holidays and vacations, we'll readdress the meeting time again. Also chosen was to switch to a video platform and we will work on choosing one before the meeting reminder goes out Thanks, Amy (spotz)

1 0

Confidential Containers Community Meeting 2022/01/20
by Samuel Ortiz 20 Jan '22

20 Jan '22

Hey Folks, Another week, another CC community meeting tomorrow! As usual it will start at 2:00 PM UTC - 9 AM EST - 10PM CST. Tomorrow, we’ll first go through 2 (hopefully) brief rounds of updates: The CNCF one and also I’d like us to start giving CCv1 updates, for those work items that have already started. Next, we’ll have IBM folks giving us a much expected presentation about peer pods. James gave us an initial presentation a few months ago, and this is a follow up with a demo and some source code pointers. Exciting! If you have something else you want to discuss tomorrow or the upcoming weeks, please amend the agenda [1]. Cheers, Samuel. [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

1 0

OpenInfra Summit Berlin 2022 Programming Committee Nominations Now Open
by Erin Disney 20 Jan '22

20 Jan '22

Hey everyone- Programming Committee nominations <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022> for the 2022 OpenInfra Summit in Berlin (June 7-9, 2022) are now open! Programming Committees for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Full track descriptions are available here <https://etherpad.opendev.org/p/r.86088dcd62bc50a6381c19f7f26995b6>. If you’re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022>. Nominations will close on January 19, 2022. Programming Committee selections will occur before we close the Call for Presentations (CFP) so that the Committees can host office hours to consult on submissions, and help promote the event. CFP will be opening in January, registration <https://www.eventbrite.com/e/openinfra-summit-berlin-2022-tickets-211374997…> and sponsorship <https://openinfra.dev/summit/> information are already available. Please email speakersupport(a)openinfra.dev with any questions or feedback. Cheers, Erin Disney Event Marketing Open Infrastructure Foundation

1 1