- kata-dev - lists.katacontainers.io

Confidential Containers Community Meeting 4/28/22
by Tobin Feldman-Fitzthum 28 Apr '22

28 Apr '22

Hello, We have our usual CC community meeting tomorrow at 2:00 PM UTC - 10 AM EDT - 10PM CST. We will cover some community updates, including progress on CNCF onboarding and the status of CCv0. We also do some housekeeping regarding these agenda emails. Does anyone read them? The big topic for tomorrow, however, is storage. If we have some time left over we might begin to discuss how/when we might start doing releases and what our versioning scheme should look like. As usual, feel free to add topics to the agenda.[1] See you tomorrow, Tobin [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

3 2

Canceled event: Kata architecture committee weekly sync @ Tue Apr 26, 2022 6pm - 7pm (IDT) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 26 Apr '22

26 Apr '22

This event has been canceled. Title: Kata architecture committee weekly sync Meeting link: https://zoom.us/j/91444082924Meeting notes: Kata Architecture Committee meetings etherpad 2022To ensure everyone can join the AC meeting smoothly in the future without waiting in the Zoom waiting room they added a passcode to join in the AC call. The passcode is kataYou can also find the dial-in link in the AC meeting etherpad When: Tue Apr 26, 2022 6pm – 7pm Israel Time Where: https://zoom.us/j/91444082924 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * fabiano(a)fidencio.org * Boeuf, Sebastien * Adams, Eric * Zhu, Peter J * fabiano.fidencio(a)intel.com * james.o.hunt(a)intel.com * Moriyoshi Ohara * kata-dev(a)lists.katacontainers.io * Boris Ostrovsky * Liam Merwick * Jakob Naucke * Vikram Darsi * 李瑞友 * Zhang Richard * Steven J Horsman 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

Weekly Kata Herders
by Hunt, James O 25 Apr '22

25 Apr '22

Hi All, # Herders This week's Kata PR and issue herders [1] are: - Binbin (https://github.com/Bevisy) - Chelsea (https://github.com/cmaf) - me (https://github.com/jodh-intel) # Statistics ## Issues Issues opened last week: 39 Issues closed last week: 30 Open issues: 599 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 31 PRs closed last week: 29 PRs merged last week: 25 Open PRs: 67 Open PRs (excluding dnm+wip): 53 # 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 Research and Development UK Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Confidential Containers Community Meeting 2022/04/21
by Samuel Ortiz 21 Apr '22

21 Apr '22

Hi All, It’s that time of the week: The Confidential Containers community meeting, tomorrow (04/21) at 2pm UTC (10am EDT - 10pm CST). We’ll start with our regular round of updates: CCv0 merge, CI/CD and the CNCF onboarding progress. The latter should take a bit more time than usual as we’re currently being blocked by a couple of issues that we’d like to discuss with the rest of the community. Then we’ll (hopefully briefly) discuss about bringing up a Confidential Containers website. Finally, I’d like to go through 2 important issues for our project: 1. The KBS repos creation: Before creating them, do we all agree this is part of the project scope? 2. The containerd fork: After Derek’s presentation a couple of weeks ago, should we continue our merging efforts or wait for the next containerd release? This meeting agenda [1], as you hopefully all know, is open. Go wild and add anything you want to bring to this community. Cheers, Samuel. [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

1 0

RFC: Streamlined process for cleanup PRs
by David Gibson 14 Apr '22

14 Apr '22

Hi everyone, I believe this idea was raised briefly at a recent AC meeting, but here's a more concrete proposal. RFC: A streamlined process for cleanup patches ============================================== Rationale --------- Currently, commiting a change to Kata generally requires both a Github issue and a linked Github pull request. This works for bugs found "in the wild" and for feature/enhancement requests: it makes sense to discuss the change that needs to happen before moving on to how to implement it. However, this process works poorly for "cleanup" patches. That includes internal refactoring without changing external behaviour, and also bugs found by inspection where it's clear that the code doesn't behave as it should, but working backwards to find user inputs which would trigger the bug can be quite difficult. It's certainly possible to write an issue for such a fix, but it often ends up just re-iterating the same information as in the PR; the issue templates also don't help with it since they assume the report is coming from observation of behaviour, rather than inspection of code. In addition cleanup patches don't work well with the procedural checks which require each PR to have a patch labelled as fixing a Github issue. A well written cleanup PR will often consist of a number of small patches which each incrementally improve the code quality, but none of which could be said specifically to "fix" a clearly delineated problem. This means that someone writing a cleanup PR has to either arbitrarily place the "fixes #" tag on the last patch (which is misleading), or place it on all of them which could lead to prematurely closing the issue if an incomplete series is merged my mistake. To reduce barriers to people addressing technical debt in Kata, I therefore propose that we introduce a shorter process for reviewing and merging cleanup patches. Guidelines ---------- We don't want to stop encouraging well written reports for externally observed bugs, or enhancement requests. So, we need some guidelines as to what constitutes a "cleanup" PR. A PR which changes the code without changing any externally visible behaviour would certainly qualify. I think limiting to *only* that would be too restrictive though: that would disallow PRs which technically change behaviour but only in an obscure / unsupported / unimportant case. Likewise it would prevent fixing of bugs found by inspection - we want to encourage people to fix bugs, not slow them down with bureaucracy. Here are some possible guidelines that admittedly leave some fuzzy room in the middle: Considered a cleanup patch: * Internal refactoring with no external behaviour change * Rewording comments or documentation for clarity * Updates to developer facing documentation to match other cleanup changes NOT considered a cleanup patch: * Added functionality * Anything requiring user facing documentation to be updated to match code changes Process ------- There are several ways we could allow for a streamline cleanup process. Here are three options, which I'm soliciting opinions on: Option 1 (no issue required) * Cleanup PRs can be submitted with no accompanying Github issue * Such a PR must be tagged with a (new) 'cleanup' label * Scripts would be adjusted to to require a "fixes" tag on a cleanup labelled PR Advantages: - Minimum of overhead for small fixes Disadvantages: - Process would need to be documented elsewhere, with no ability for Github to guide people through it Option 2 (special issue template, minimal PR) * A new issue template for Cleanup is added alongside enhancement request, bug fix etc. * PRs attached to a cleanup issue are allowed / expected to be minimal, simply linking the issue with no further description required (individual patches in the PR should still have good commit messages, of course) Advantages: - Issue template can help guide people through the processz Disadvantages: - Still requires the extra step of creating both the issue and PR Option 3 (long-lived cleanup issues) * Cleanups can be attached to a specially labelled issue which describes not a specific problem, but rather a general area where cleanup / improvement might be desirable * PRs linked to a "cleanup" issue aren't expected to "fix" it, just to make some amount of improvement * Merging multiple PRs against the same cleanup issue would be normal * Scripts would be adjusted not to require a "fixes" tag on such a PR, but maybe a "improves" tag. Processing such a PR would *not* close the issue Advantages: - Allows incremental improvements to be merged quickly, without requiring them to fully "fix" some delineated problem Disadvantages: - Unclear when the right time to (manually) close such an issue would be, because it's now "good enough" -- 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

4 6

Confidential Containers Community Meeting 4/14/22
by Tobin Feldman-Fitzthum 14 Apr '22

14 Apr '22

Hello, First of all, remember to join the CNCF Slack Workspace if you haven't yet. Tomorrow we have another CC community meeting at 2:00 PM UTC - 10 AM EDT - 10PM CST. We will discuss community updates and then we will hear from Arron and Peter regarding some recent efforts to add TDX tests to the CI. We will also hear from Dan regarding our progress towards the CII badge. As usual, please add something to the agenda if you'd like us to talk about it in a future meeting. [1] -Tobin [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

1 0

Weekly Kata Herders
by Hunt, James O 11 Apr '22

11 Apr '22

Hi All, # Herders This week's Kata PR and issue herders [1] are: - Bin (https://github.com/liubin) - Eric (https://github.com/egernst) - Greg (https://github.com/gkurz) # Statistics ## Issues Issues opened last week: 37 Issues closed last week: 26 Open issues: 580 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 30 PRs closed last week: 27 PRs merged last week: 23 Open PRs: 58 Open PRs (excluding dnm+wip): 44 # 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 Research and Development UK Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Confidential Containers Community Meeting 2022/04/07
by Samuel Ortiz 07 Apr '22

07 Apr '22

Hey Folks, Another week, another meeting. We’ll discuss Confidential Containers things tomorrow, at 2pm UTC (10am EDT - 10pm CST) on our usual Zoom [1]. We will start with our usual round of updates for the CCv0 branch, the CI progress and the CNCF on-boarding process. Then we’ll have Derek McGowan present the upcoming architectural changes for containerd. We currently depend on a non upstream (and non upstreamable) containerd feature for off-loading image management into the guest. Maintaining this containerd forks blocks us from being able to fully merge CC into Kata, and I’m hoping Derek’s presentation will help our community understand how containerd’s roadmap align with our project. As usual, feel free to amend the agenda [1] with more topics for tomorrow or the next weeks. Cheers, Samuel. [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

1 0

Canceled event: Kata architecture committee weekly sync @ Tue Apr 5, 2022 6pm - 7pm (IDT) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 05 Apr '22

05 Apr '22

This event has been canceled. Title: Kata architecture committee weekly sync Meeting link: https://zoom.us/j/91444082924Meeting notes: Kata Architecture Committee meetings etherpad 2022To ensure everyone can join the AC meeting smoothly in the future without waiting in the Zoom waiting room they added a passcode to join in the AC call. The passcode is kataYou can also find the dial-in link in the AC meeting etherpad When: Tue Apr 5, 2022 6pm – 7pm Israel Time Where: https://zoom.us/j/91444082924 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * Fabiano Fidêncio * Boeuf, Sebastien * Eric Adams * Zhu, Peter J * fabiano.fidencio(a)intel.com * James O Hunt * Moriyoshi Ohara * kata-dev(a)lists.katacontainers.io * Boris Ostrovsky * Liam Merwick * Jakob Naucke * Vikram Darsi * 李瑞友 * Zhang Richard * Steven J Horsman 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

Summary of the PR review discussion from last TC meeting
by Christophe de Dinechin 04 Apr '22

04 Apr '22

Here is a summary of the discussion we had at the last AC meeting on reviews and PRs of large, sweeping changes like runtime-rs. This is a copy of the current state of https://etherpad.opendev.org/p/Kata_Containers_2022_Architecture_Committee_…, after review and a few iterations by at least Fabiano, Peng Tao and myself. If there are some statements in there that you don't like or would like to change, now is the time to chime up. We can also archive that on the wiki or in the documentation if this is seen as important enough. Thanks Christophe • Agreement was reached as follows: • Staging (runtime-rs) branch should accept things faster than main, but the code will not be considered fully reviewed until we merge it on main • We won't merge the staging branch on main as is • As necessary, more refactoring and review may be needed • As much as possible, we will do that incrementally, with additional PRs • (c3d: original text was: "without more necessary another pass of review/refactoring, PR reorganization, patch series cleanup, and so on", which I find ambiguous) • The goal of that staging branch is to have something that runs and can be tested quickly and allow continuous improvements, even if quality or readability is not optimal (and, even if that wasn't said in the meeting, I suspect also allows the current users of runtime-rs to keep developing, like for td-shim) • It would be helpful to have multiple PRs open in parallel so that we can get a big picture view of the code • We don't need to merge on PR before merging the next one, that presents a sequential view of the code that is not really helpful for reviewers. • In that sense, we are not asking for a "slow down" but for a "dump faster" ;-) • Like for td-shim, it would be very helpful to get documentation / PDF / presentation documents merged first, so that we understand where each PR fits • It would really help if PR descriptions and commit messages were more elaborate, describing: • What the code does in some details • Where it fits in the architecture • Deviations from the existing Go implementation (Eric gave the example of replacing multiple Go packages doing similar things with a single Rust crate) • External APIs at least, ideally some of the internal flow as well (notably when it's not obvious from the code itself) • Maturity level for the code, e.g. "this is part 1 of a 3-stage development", or "this and that won't work yet" • Red Hat is currently training several engineers to become proficient with Rust, but this is likely to take ~2 months to complete • We are expecting more RedHat developers to join the force to help reviewing and refactoring the rust shim • The authors are also refactoring the code as they publish it, with the objective to give us a higher quality code based on what they learned from using it in production • Being too busy to review is not a good reason to block a PR. Please prioritise things if a reviewer thinks it is important to review. • In that sense, if a reviewer blocks a PR and then disapears, we will start to dismiss some reviews after three pings (It applies to all branches not just runtime-rs). • c3d suggestion (not discussed during meeting): Create teams for coworkers (e.g. we have "redhat" team in kata-containers, not in CoCo yet), and make a rule that ping 2 and 3 must also ping the team, with the hope that someone close to the original commenter can pick up or relay.

1 0

Weekly Kata Herders
by Hunt, James O 04 Apr '22

04 Apr '22

Hi All, # Herders This week's Kata PR and issue herders [1] are: - Archana (https://github.com/amshinde) - Tao (https://github.com/bergwolf) # Statistics ## Issues Issues opened last week: 41 Issues closed last week: 27 Open issues: 569 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 53 PRs closed last week: 43 PRs merged last week: 39 Open PRs: 57 Open PRs (excluding dnm+wip): 41 # 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 Research and Development UK Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Confidential Containers Community Meeting 3/31/22
by Tobin Feldman-Fitzthum 31 Mar '22

31 Mar '22

Hey Everyone, We have our community meeting tomorrow at 2:00 PM UTC - 10 AM EDT - 10PM CST. Note that if you live someplace that has just switched to Daylight time (like most of Europe) the meeting will appear to be an hour later than usual. This week we will pick up where we left off last week. After some community updates we will dive back into our discussion on a general Key Broker Service. Haidong and Liang did a great job presenting this last week and tomorrow should be even more interesting. Hopefully we will also have time to take another look at the CII badge. As usual, feel free to add something to the agenda.[1] -Tobin [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…

1 0

[Diversity] Meeting Cancelled and PTG
by Amy Marrich 30 Mar '22

30 Mar '22

With the PTG next week we have decided to cancel this Friday's Diversity and Inclusion WG meeting. We invite everyone to join us at the PTG on Monday at 16:00 UTC in the Mitaka room. Please add any topics you have to the PTG etherpad[0]. Hope to see everyone there! Amy 0 - https://etherpad.opendev.org/p/april2022-ptg-diversity

1 0

Updated invitation: Kata architecture committee weekly sync @ Weekly from 5pm to 6pm on Tuesday from Tue Nov 16, 2021 to Mon Mar 28 (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 29 Mar '22

29 Mar '22

This event has been changed. Title: Kata architecture committee weekly sync Meeting link: https://zoom.us/j/91444082924Meeting notes: Kata Architecture Committee meetings etherpad 2021To ensure everyone can join the AC meeting smoothly in the future without waiting in the Zoom waiting room they added a passcode to join in the AC call. The passcode is kataYou can also find the dial-in link in the AC meeting etherpad When: Weekly from 5pm to 6pm on Tuesday from Tue Nov 16, 2021 to Mon Mar 28 Israel Time (changed) Where: https://zoom.us/j/91444082924 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io * Fabiano Fidêncio * Boeuf, Sebastien * Boris Ostrovsky * Eric Adams * Zhu, Peter J * fabiano.fidencio(a)intel.com * James O Hunt Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NWpiY3I0MnN1ZnJx… 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

Updated invitation: Kata architecture committee weekly sync @ Weekly from 5pm to 6pm on Tuesday from Tue Jan 4 to Mon Mar 28 (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 29 Mar '22

29 Mar '22

This event has been changed. Title: Kata architecture committee weekly sync Meeting link: https://zoom.us/j/91444082924Meeting notes: Kata Architecture Committee meetings etherpad 2022To ensure everyone can join the AC meeting smoothly in the future without waiting in the Zoom waiting room they added a passcode to join in the AC call. The passcode is kataYou can also find the dial-in link in the AC meeting etherpad When: Weekly from 5pm to 6pm on Tuesday from Tue Jan 4 to Mon Mar 28 Israel Time (changed) Where: https://zoom.us/j/91444082924 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * Fabiano Fidêncio * Boeuf, Sebastien * Eric Adams * Zhu, Peter J * fabiano.fidencio(a)intel.com * James O Hunt * kata-dev(a)lists.katacontainers.io * Boris Ostrovsky * Liam Merwick * Jakob Naucke * Vikram Darsi * 李瑞友 * Zhang Richard Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NWpiY3I0MnN1ZnJx… 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

Updated invitation with note: Kata architecture committee weekly sync @ Weekly from 6pm to 7pm on Tuesday (IDT) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 29 Mar '22

29 Mar '22

This event has been changed with this note: "Changing the time to UTC" Title: Kata architecture committee weekly sync Meeting link: https://zoom.us/j/91444082924Meeting notes: Kata Architecture Committee meetings etherpad 2022To ensure everyone can join the AC meeting smoothly in the future without waiting in the Zoom waiting room they added a passcode to join in the AC call. The passcode is kataYou can also find the dial-in link in the AC meeting etherpad (changed) When: Weekly from 6pm to 7pm on Tuesday Israel Time (changed) Where: https://zoom.us/j/91444082924 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * Fabiano Fidêncio * Boeuf, Sebastien * Eric Adams * Zhu, Peter J * fabiano.fidencio(a)intel.com * James O Hunt * kata-dev(a)lists.katacontainers.io * Boris Ostrovsky * Liam Merwick * Jakob Naucke * Vikram Darsi * 李瑞友 * Zhang Richard Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NnE3dGgzaDJkNXFk… 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

Updated invitation: Kata containers confidential computing use case meeting @ Weekly from 4pm to 5pm on Thursday from Thu Dec 2, 2021 to Wed Mar 30 (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 28 Mar '22

28 Mar '22

This event has been changed. Title: Kata containers confidential computing use case meeting Discussing kata container confidential computing use case 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 When: Weekly from 4pm to 5pm on Thursday from Thu Dec 2, 2021 to Wed Mar 30 Israel Time (changed) Where: https://zoom.us/j/98038141932 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io * Liam Merwick * Boris Ostrovsky * Zhang Richard Attachments: * Notes - Kata containers confidential computing use case meeting - https://docs.google.com/document/d/1uLb-A45cC9XZfcCDbt6wLCt5hlzU0PTdmkfDLk-… Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=dnQwYXVvbmwzZGlh… 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

Updated invitation: Kata containers confidential computing use case meeting @ Weekly from 4pm to 5pm on Thursday from Thu Nov 11, 2021 to Wed Mar 30 (IST) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 28 Mar '22

28 Mar '22

This event has been changed. Title: Kata containers confidential computing use case meeting Discussing kata container confidential computing use case 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 When: Weekly from 4pm to 5pm on Thursday from Thu Nov 11, 2021 to Wed Mar 30 Israel Time (changed) Where: https://zoom.us/j/98038141932 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io * Liam Merwick * Boris Ostrovsky Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=dnQwYXVvbmwzZGlh… 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

Updated invitation: Kata containers confidential computing use case meeting @ Weekly from 5pm to 6pm on Thursday (IDT) (kata-dev@lists.katacontainers.io)
by aadam＠redhat.com 28 Mar '22

28 Mar '22

This event has been changed. Title: Kata containers confidential computing use case meeting Discussing kata container confidential computing use case 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 When: Weekly from 5pm to 6pm on Thursday Israel Time (changed) Where: https://zoom.us/j/98038141932 Calendar: kata-dev(a)lists.katacontainers.io Who: * aadam(a)redhat.com - organizer * kata-dev(a)lists.katacontainers.io * Liam Merwick * Boris Ostrovsky * Zhang Richard Attachments: * Notes - Kata containers confidential computing use case meeting - https://docs.google.com/document/d/1uLb-A45cC9XZfcCDbt6wLCt5hlzU0PTdmkfDLk-… Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NDRlZjhlYzdpbzMw… 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

Weekly Kata Herders
by Hunt, James O 28 Mar '22

28 Mar '22

Hi All, # Herders This week's Kata PR and issue herders [1] are: - David (https://github.com/dborquez) - Jongwu (https://github.com/jongwu) - Snir (https://github.com/snir911) # Statistics ## Issues Issues opened last week: 44 Issues closed last week: 25 Open issues: 556 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 43 PRs closed last week: 39 PRs merged last week: 28 Open PRs: 47 Open PRs (excluding dnm+wip): 32 # 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 Research and Development UK Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

Confidential Containers Community Meeting 2022/03/24
by Samuel Ortiz 24 Mar '22

24 Mar '22

Hey Everyone, Another weekly meeting for the Confidential Containers project: It’s tomorrow March 24th, at 2pm UTC (10am EDT - 10pm CST), same place as usual [1]. We have yet another busy agenda, starting with the usual opens and community/project updates. Then Dan Middleton will start the CII best practice discussion [2], something that may take us a few more sessions. But tomorrow we’d also want to leave some time for Jia to present a proposal for a KBS server [3]. We will resume the CII discussion during the next meeting(s). Remember: The agenda is yours, feel free to amend it with anything you’d like to see the community address [1]. Cheers, Samuel. [1] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh… [2] https://github.com/confidential-containers/community/issues/12 [3] https://github.com/confidential-containers/documentation/issues/26

1 0

Reviewing COCO CNCF onboarding tasks
by Ariel Adam 22 Mar '22

22 Mar '22

Hi everyone. We are working to cover all the CNCF onboarding tasks <https://github.com/orgs/confidential-containers/projects/2> and hopefully converge everything in the next 3 weeks. For Thursday's COCO meeting we'd appreciate it if you could review the tasks we have in the "Review only" column before the meeting and comment that you read/approve. This will help us focus our time on discussion topics and issues that are in progress. Thanks.

1 0

Fwd: Forum Submissions Open for Berlin Summit 2022!
by Kendall Nelson 22 Mar '22

22 Mar '22

Hello Everyone! We are now accepting Forum [1] submissions for the 2022 Open Infrastructure Summit Forum [2]. Please submit your ideas through the Summit CFP tool [3] through April 8th. Don't forget to put your brainstorming etherpad up on the Berlin Forum page [4]. This is not a classic conference track with speakers and presentations. OpenInfra community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: March 21st | Formal topic submission tool opens: https://cfp.openstack.org. April 8th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. April 15th | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. April 22nd | Forum schedule final June 20th | Forum begins! If you have questions or concerns, please reach out to speakersupport(a)openinfra.dev. Cheers, - Kendall Nelson (diablo_rojo) [1] https://wiki.openstack.org/wiki/Forum [2] https://openinfra.dev/summit [3] https://cfp.openstack.org [4] https://wiki.openstack.org/wiki/Forum/Berlin2022

1 1

Kata citizens,
by Fabiano Fidêncio 22 Mar '22

22 Mar '22

Please, join me to welcome the four students who'll spend the coming months working with us increasing unit test coverage of the Kata Containers agent. Braden Rayhorn Christopher Parks, Garret Mahin, and Jack Hance are students from North Dakota State University and have already been submitting a few patches here and there, and hopefully will become more active as they speed up with the project. For more details about the project, please, refer to https://github.com/kata-containers/community/wiki/Outreach---Internship-pro…, and let's welcome them here and Tomorrow at our Architecture Committee meeting! Have fun! :-) -- Fabiano Fidêncio

1 0

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

21 Mar '22

Hi All, # Herders This week's Kata PR and issue herders [1] are: - Binbin (https://github.com/Bevisy) - Chelsea (https://github.com/cmaf) - me (https://github.com/jodh-intel) # Statistics ## Issues Issues opened last week: 34 Issues closed last week: 41 Open issues: 539 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 37 PRs closed last week: 37 PRs merged last week: 34 Open PRs: 44 Open PRs (excluding dnm+wip): 29 # 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 | https://01.org Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0