December 2019 - kata-dev - lists.katacontainers.io

Gateherder(s?) for the week - **CALL FOR VOLUNTEERS**
by Whaley, Graham 09 Dec '19

09 Dec '19

Good morning, This week's Gateherder is - Carlos I will note - having a single reviewer for one of our regular rotation slots is not ideal. It has been a while since we re-visited the list and re-assessed, so please take this email as a: **CALL FOR VOLUNTEERS** To join the kata review rota: https://github.com/kata-containers/community/wiki/Review-Team-Rota As the page says, everybody is welcome - reviewing and moving along PRs can come in many forms, so don't feel that lack of specific experience or knowledge has to put you off... If you'd like to join the rota, or discuss, reach out - on this list, slack, irc, or directly to myself or any member of the architecture committee... it's a great way to get more involved and learn you way around the project. Releases: We are due a release cycle or two over the space of the next week or so: https://github.com/kata-containers/community/wiki/Release-Team-Rota#the-rota Expect activity around the v1.10(.rc0) cycles, and stable updates... Graham --------------------------------------------------------------------- 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

vsock & network namespaces in Kata
by Stefano Garzarella 05 Dec '19

05 Dec '19

Hi folks, I'm working on vsock on Linux and I'm adding the network namespace support on it[1]. The main changes are the following: - Guest: can talk with the host packets (send and receive packets) in the default init_netns (maybe we can make it configurable) - Host: can talk with the guest only in the same netns where the VMM is running (e.g. if we start qemu from ns1, all packets are received only in ns1) - Host: assign the same CID of VMs running in different network namespaces - Nested VMs (available from Linux 5.5): isolate host applications from guest applications IIUC you have a runtime running in the host that communicates using vsock with an agent in the guest. I have few questions: 1. Is the VMM (e.g. QEMU) running in a network namespace? 2. Is the host application, that use vsock to communicate with the guest, running in the same network namespace? 3. Is the agent in the guest running outside a netns (default init_netns)? If you have any other suggestions, I'd be happy to hear them. Thanks, Stefano

5 13

Status for 1.10 RC0 release
by Ernst, Eric 04 Dec '19

04 Dec '19

Hey ya’ll, I blame too much turkey for delay in discussion re: 1.10 release schedule. Per [1], Bergwolf is scheduled to drive the RC *this week* for 1.10. I took a look at the GitHub project for release 1.10, [2], and it looks like the major outstanding item still is the rust agent. It appears that it is in repo, but still has issues and is not being packaged/released yet. If this can be resolved over next few days, I’m happy to see the packaging updated to include in 1.10, but otherwise we should punt on this until next release (1.11/2.0). Carlos/Bo – where are we with respect to http API for Cloud Hypervisor? It’d be nice to have this settled before 1.10, but time is quite short now. Peng Tao, can you help with the 1.10-rc0 and 1.9.x release? We should probably sync, as much of the flow has been simplified with the introduction of GitHub actions. Carlos, can we help update docs for this? Thanks, Eric [1] - https://github.com/kata-containers/community/wiki/Release-Team-Rota [2] - https://github.com/orgs/kata-containers/projects/19

3 2

Thread on OpenDev Independence and Governance
by Clark Boylan 04 Dec '19

04 Dec '19

Hello, I wanted everyone to be aware of this thread [0] at openstack-infra(a)lists.openstack.org that I've started to formalize OpenDev's future independence and governance. Currently the infra team is formally an OpenStack project, but we think that we'll be better able to serve our non OpenStack users if the OpenDev aspects of this team become independent with its own governance. We are more than happy to hear feedback so please read this thread and respond if the topic interests you. Note, I'm using this pointer thread in an effort to avoid cross posting and losing feedback. It would be great if people can respond to the original on openstack-infra@lists. [0] http://lists.openstack.org/pipermail/openstack-infra/2019-December/006537.h… Thank you, Clark

1 0

Should we cancel the AC Meeting this week?
by Xu Wang 03 Dec '19

03 Dec '19

No new item appears on the agenda so far (the existing one was discussed last week). -- Xu Wang (@gnawux) Senior Staff Engineer at Ant Financial A Member of Kata Containers Architecture Committee

2 1

Gatekeepers this week
by Whaley, Graham 02 Dec '19

02 Dec '19

Good morning. Gatekeepers this week are: - Eric - Salvador - Ganesh https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota We have 48 open issues for review, 75 issues if we include WIP and DNM It feels like those numbers are drifting up - but - I also think that may be due to real 'activity'. We probably need a little bit of concerted effort to push some of those PRs through... According to the release rota page, Peng will be working on some releases this week: stable release 1.9.3, 1.8.6; pre-release 1.10-rc0 https://github.com/kata-containers/community/wiki/Release-Team-Rota Peng, can you confirm plans are going ahead? Graham --------------------------------------------------------------------- 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