Thanks Ricardo,
Eric and Fabiano have already talked about debuggability. I myself
consider this extremely crucial for wider adaptation of Kata among our customers. I have already had discussion around this with customers using Kata to identify the gaps we have today in Kata in
terms of debuggability and understand what debug features they would find beneficial while running in production scenarios. Some of this includes adding audit functionalities
in Kata, making sure logs are not lost with software crashes and logs are better managed in general. I have started work around improving our debug guides and would like to improve things further by providing a Kata image with all things required for better
debugging built in. That way a customer could simply switch to an image with necessary debug/tracing features baked in. The tremendous work done by Ant financial folks has really added value to Kata from observability point of view, I would like to
take that forward and see how we could use it for various debug scenarios.
That said, I have started looking at the shimv2 implementation for docker, and through this process I am planning to improve debuggabilty and tracing features for the shimv2 api in general.
Another aspect of crucial importance is our IO performance. I have spent some efforts measuring our virtiofs performance under various stress loads. I plan to continue those efforrts in co-ordination
with other Kata folks to make sure our IO performance improves in the long run. I also plan to include tests that stress our IO performance as part of a CI to see how well our IO performs.
Lastly, I have worked in the past on the networking aspects of Kata to make sure Kata works with various CNI plugins and with ipv6 stacks. I wish to take this work forward to make sure Kata works
well for NFV workloads by ensuring stronger support for network related features like CPU pinning and huge pages. I think this is an area where Kata could be extremely useful.
Thanks,
Archana
From: Ricardo Aravena <raravena80@gmail.com>
Date: Friday, September 18, 2020 at 10:46 AM
To: kata-dev <kata-dev@lists.katacontainers.io>
Subject: [kata-dev] Arch Committee Election: Q&A period open!
Hello Kata Citizens!
We have four candidate submissions for the Architecture Committee election, where we have three 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 (September 18th - 27th) 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 September 28th.
I'll kick it off with the first question for the candidates:
What do you think is the most important feature missing from Kata Containers that will help the project increase adoption in the next year?
Candidates (in alphabetical order):
- Archana Shinde [1]
- Eric Ernst [2]
- Fabiano Fidêncio [3]
- Justin He [4]
[1]
https://github.com/kata-containers/community/blob/master/elections/arch-committee-2020-09/ArchanaShinde.txt
[2] https://github.com/kata-containers/community/blob/master/elections/arch-committee-2020-09/EricErnst.txt
[3] https://github.com/kata-containers/community/blob/master/elections/arch-committee-2020-09/FabianoFidencio.txt
Thanks!
Ricardo