Thank you, Graham.
Q. What is the most important thing (be it an integration, a particular feature, adopting a policy, etc) Kata Containers needs to achieve in the next year and how should we get there?
As a community, we need more participants from end-users. To get there, we should work on three aspects: reducing overhead, improving isolation, and helping new users: More and more people agree with isolation is important, however, they still need to pay too much to migrate to kata containers. I think we should work on the following aspects: - Reducing memory overhead. People like isolation, but they don't want to pay for it. - `rust-agent` is a good starting point, and we could reduce the heap memory consumption down to less than 800KB in our initial tests with rust-agent+ttrpc. - `cloud-hypervisor` has been integrated with kata, and it is a lightweight, modularized, and more open project for contributors. We shall work with it and have a kata profile of it. - Being more flexible. One critique on Kata is that we are not as flexible as a "real" container. - We are working on virtio-mem, @teawater from our team has prepared patches and documents for it, and he is working on virtio-mem for cloud-hypervisor as well. I am looking forward to landing it in kata in months. On the other hand, we should enhance the isolation of Kata, which is our initial goal. - Enable users to move all the image operations in the guest sandbox for better isolation. In a discussion during the last PTG, the developers from Alibaba and IBM are all working on it. - It is possible to introduce TEE technologies from Intel/AMD/IBM/ARM chips, which provide "bi-direction isolation", i.e. protecting workloads from the infra providers. Another important thing is providing more user practice in the community, which may help new adopters. - Baidu's Kata deployment won the Superuser Award in the last summit and has a whitepaper published. We are working on Alibaba and Ant Financial Kata clusters and will publish more document and testing data about them. And we still need more from all the contributors. - The marketing team of Kata is planning on setting up neutral and open performance metrics test for Kata, which will help the users to know whether or when Kata is fit for them. - And we shall attend conferences and meetups on infra and cloud-native to promote Kata as well. Thank you guys for the contributions, and let's work together for a better year. Cheers! Xu ------------------------------------------------------------------ From:Whaley, Graham <graham.whaley@intel.com> Send Time:2020年2月13日(星期四) 18:25 To:kata-dev@lists.katacontainers.io <kata-dev@lists.katacontainers.io> Subject:[kata-dev] Arch Committee Election: Q&A period open! Hello all, We have three candidate submissions for the Architecture Committee election, where we have two seats available. Thus, we shall enter the Q&A and subsequently the voting phases. Candidates names and links to their github submissions are below. The next period (Feb13-23rd) is for asking questions to candidates via this mailing list; it's an opportunity to get familiar with the perspective they would bring as an Arch Committee member before voting opens on the 24th. To kick off the Q&A, I shall ask to the candidates: Q. What is the most important thing (be it an integration, a particular feature, adopting a policy, etc) Kata Containers needs to achieve in the next year and how should we get there? Candidates (in alphabetical order): -David Alan Gilbert [1] -Samuel Ortiz [2] -Xu Wang [3] [1] https://github.com/kata-containers/community/blob/master/elections/arch-comm... [2] https://github.com/kata-containers/community/blob/master/elections/arch-comm... [3] https://github.com/kata-containers/community/blob/master/elections/arch-comm... --------------------------------------------------------------------- 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. _______________________________________________ kata-dev mailing list kata-dev@lists.katacontainers.io http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev