Thanks Ricardo.
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?
Similar to Fabiano's reply, I have a hard time picking one. Also similarly, I will point out things that aren't really 'features' :) I am currently looking at IO performance for storage, manageability/observability, and performance isolation (cpusets, etc). Of these, I think the manageability part is most interesting/important part that will be common among all end users.
Administrators, security teams and end-users assume a certain level of visibility into the container workload that is running, which is much more challenging when leveraging the Kata Containers runtime. As a result, we need to be proactive to assure that it is easy to assess "how much is this costing?", "can I trace malicious behavior of the workload even though its in a VM?' and "how can I determine the performance profile of my application and how it is using host/guest resources." We are quite lucky that our friends at AntFinancial have done a good job pushing this forward with some of the observability APIs introduced in 2.0, but we will likely need to continue to develop this going forward, providing the right hooks for key container management tools to operate well with the Kata runtime.
Of course, if our footprint and IO performance aren't kept competitive enough, then observability doesn't matter as much, so .. yeah, that's very important still too :)
Candidates (in alphabetical order):
- Archana Shinde [1]
- Eric Ernst [2]
- Fabiano Fidêncio [3]
Thanks!
Ricardo
kata-dev mailing list
kata-dev@lists.katacontainers.io
http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev