September 2018 - kata-dev - lists.katacontainers.io

[Community] KubeCon NA attendance?
by Anne Bertucio 03 Oct '18

03 Oct '18

Hey all, One of the things we will talk about tomorrow in the Working Committee meeting (1500 UTC) is our plans for KubeCon North America in December, where Kata Containers will have a booth. We’ve tossed around ideas about office hours, live demos, etc., but it’d be helpful to get an idea of who is attending and who is interested in helping out with community activities like that. Who’s planning to be there? Cheers, Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

6 13

Kata PR review rota
by Hunt, James O 29 Sep '18

29 Sep '18

We have a couple of free slots for next week if anyone would like to join Graham? - https://github.com/kata-containers/community/wiki/Review-Team-Rota (Don't worry - if you're in EMEA too, you can still help! :) A reminder - you *don't* need to be an expert in Kata / reviewing / golang / stuff: - http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000357.html Cheers, James --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

OpenStack Summit Forum Submission Process Extended
by Jimmy McArthur 28 Sep '18

28 Sep '18

Hello Everyone We are extended the Forum Submission process through September 30, 11:59pm Pacific (6:59am GMT). We've already gotten a ton of great submissions, but we want to leave the door open through the weekend in case we have any stragglers. Please submit your topics here: https://www.openstack.org/summit/berlin-2018/call-for-presentations If you'd like to review the submissions to date, you can go to https://www.openstack.org/summit/berlin-2018/vote-for-speakers. There is no voting period, this is just so Forum attendees can review the submissions to date. Thank you! Jimmy

1 0

Namespaces in the host
by Montes, Julio 28 Sep '18

28 Sep '18

Hi All Currently Kata Containers only supports network namespaces in the host, other namespaces are not supported. This week I started to work on this but I faced some issues with the mount namespace in Go, the main issue is that a multithread process can't be reassociated with a new mount namespace [1] as it's reported here [2]. A solution for this might be to write a new binary in C to create and join namespaces and start the kata components (shim, qemu, etc) inside it, also this binary would be used to clean up (unmount, etc) the containers. Another solution might be to use a C constructor in Go (cgo) to create and join the namespace, but that means kata-runtime will run inside the namespace. If you are already working on this or know how to deal with this issue, please let me know. In the meantime I'll try to figure out how. Thank you! -- Julio [1] - http://man7.org/linux/man-pages/man2/setns.2.html [2] - https://github.com/golang/go/issues/8676

4 3

[ANNOUNCEMENT] Kata Containers 1.3.0 release and 1.2.2 stable release
by Tao Peng 28 Sep '18

28 Sep '18

Hello Kata Kats, I'm proud to announce that we have reached another milestone for Kata Containers by releasing the 1.3.0 release and 1.2.2 stable release. All users are recommended to upgrade. The 1.3.0 release highlights following features: - Network hotplug: Sandbox network can now be dynamically changed by the "kata-runtime network" subcommand. This allows customized CNI plugins to create more Kata-native network endpoints. - Network monitoring: a new kata component (kata-netmon) is added to monitor container netns on the host. Now CNI hooks to dynamically change the network setup of a running container, and "docker network connect" works with Kata Containers. - Network multiqueue support: Network cards are added to to the guest with multiqueue support. It allows Kata Containers to gain better network performance. - Memory hotplug: "kata-runtime update" subcommand can now add extra memory to a running container. - Better container memory constraint support: containers in the same sandbox can be constrained by memcg inside the guest. - GPU support: both GVT-g and GVT-d GPU devices can now be used by Kata Containers. - Architecture/arm64: add GICv4 or higher support. For full details, please see https://github.com/kata-containers/runtime/releases/tag/1.3.0 The 1.2.2 stable release also sees several important fixes and users who want to stick with stable-1.2 branch are recommended to update. For full details, please see https://github.com/kata-containers/runtime/releases/tag/1.2.2 Thanks to all contributors who have helped to make it happen! Cheers, Tao -- bergwolf(a)hyper.sh

4 3

About the future kata rootfs, qcow2 or nfs/vsock
by Qixuan Wu 28 Sep '18

28 Sep '18

Hi Stefan, Now we found 9pfs performance is poor, we are thinking of other solution for the rootfs of kata container. As per the link, https://github.com/kata-containers/runtime/issues/279. Seem you are doing about nfs/vsock optimization, and nfs/vsock seems that can possible be the future default rootfs of kata container. And I heard about qcow2+snapshot+virtio_scsi also. And how do you think about it as the rootfs of kata container? And do you know how the kata commumity think about this solution also and compare it with nfs/vsock ? Anything is welcome and helpful. Thanks & Regards Qixuan Wu.

7 24

/dev/urandom or /dev/random
by Boeuf, Sebastien 27 Sep '18

27 Sep '18

Hi folks, Following the discussion from this morning during the Arch committee meeting, I have investigated the sporadic issue https://github.com/kata-containers/runtime/issues/702 preventing from starting some Kata containers. I have been able to reproduce it pretty easily and I have identified it is related to the entropy of the host being almost entirely consumed by the first containers, leaving no time for the host to regenerate new entropy for the next containers. Currently, the virtio-rng device exposed by Qemu relies on /dev/random on the host, and because this device will block any access to it until some more entropy is ready, that's why we end up getting the timeout from the gRPC client as the agent is not ready, hence the gRPC server does not run yet (the guest is blocked on getting new entropy from /dev/random). One way to workaround this issue is to tweak the parameters of the virtio-rng device such as max-bytes=10, limiting the amount of entropy that can be consumed by the guest each period. This means that starting one container will not consume all host's entropy, but eventually, if we run a lot of containers, we'll be very likely to hit this same issue. The long term solution seems to rely on /dev/urandom device as this one will not block if no entropy is ready yet. But from what we can read online, it seems that some people have some security concerns about it. I'd like to understand if those worries are valid or not, and if we should keep thinking about another way to fix this issue. Thanks, Sebastien

13 17

Documentation for stable branch releases
by Hunt, James O 27 Sep '18

27 Sep '18

Hi all, We're having some discussion on how best to handle documentation for stable branch releases over on [1]. I don't want to repeat it all here, but the main question is whether we branch the doc repo [2] where we keep the installation guides and architecture doc. Currently, we only have a single doc repo branch so the existing install docs would need to handle all the releases we create going forward. Branching would be in line with our strategy for the other repos and would allow the release docs in each branch to only need to document how to install Kata for that particular release. There are of course costs associated with branching and there may be gotchas we haven't considered yet. Please feel free to join the conversation, particularly if you have experience with maintaining documentation for multiple release branches [3]. Cheers, James [1] - https://github.com/kata-containers/documentation/issues/234 [2] - https://github.com/kata-containers/documentation [3] - please, no pictures of your battle scars though! :) --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

I nominate user `marcov` to be a Kata Containers github maintainer
by Whaley, Graham 25 Sep '18

25 Sep '18

Hi all current maintainers. I know we discussed improving/defining the process we will use for officially adding maintainers to the Kata Containers github org recently. I forget the details we decided on (I know, they should be in the meeting minutes, and it is probably down for me to define and update the process on our documentation). However, for now we have a simple process defined at: https://github.com/kata-containers/community#maintainer Following that, I would like to nominate github user 'marcov' https://github.com/marcov to become a member of our org. I hereby present some supporting evidence: Marcov has been active in our Kat Herding review cycle: https://github.com/kata-containers/community/wiki/Review-Team-Rota Marcov has been active on contributing commits https://github.com/search?q=org%3Akata-containers+marcov&type=Commits As well as active in review and contribution to Issues and PRs: https://github.com/search?q=org%3Akata-containers+marcov&type=Issues Marcov is our SuSe package maintainer https://github.com/kata-containers/osbuilder/pull/161 And has been actively improving osbuilder. I will submit my +1 here :-) 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.

10 9

[Forum] Forum Topic Submission Period - Time Running out!
by Jimmy McArthur 25 Sep '18

25 Sep '18

Just a reminder that there is a little more than 60 hours left to submit your forum topics. Please make haste to the Forum submission tool: https://www.openstack.org/summit/berlin-2018/call-for-presentations Cheers, Jimmy > Jimmy McArthur <mailto:jimmy@openstack.org> > September 17, 2018 at 11:13 AM > Hello Everyone! > > The Forum Topic Submission session started September 12 and will run > through September 26th. Now is the time to wrangle the topics you > gathered during your Brainstorming Phase and start pushing forum > topics through. Don't rely only on a PTL to make the agenda... step on > up and place the items you consider important front and center. > > As you may have noticed on the Forum Wiki > (https://wiki.openstack.org/wiki/Forum) we're reusing the normal CFP > tool this year. We did our best to remove Summit specific language, > but if you notice something, just know that you are submitting to the > Forum. URL is here: > > https://www.openstack.org/summit/berlin-2018/call-for-presentations > > Looking forward to seeing everyone's submissions! > > If you have questions or concerns about the process, please don't > hesitate to reach out. > > Cheers, > Jimmy > > _______________________________________________ > Openstack-track-chairs mailing list > Openstack-track-chairs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs

1 0