<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:微软雅黑;
panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
{font-family:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@微软雅黑";
panose-1:2 11 5 3 2 2 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks @Anne for kicking this off!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> 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?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The most important thing in next year in my mind is: ** "Making kata-containers production ready" **.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kata-Containers is becoming more and more stable in this year thanks to all contributors from our community, now we have stable branches and maintenance policy which is a good start, and this is absolutely a great achievement.<o:p></o:p></p>
<p class="MsoNormal">But I think we still have lots of works to do for making kata-containers a *product* instead of a cool *project*.<o:p></o:p></p>
<p class="MsoNormal">To achive this goal, something we need to do including(but not all):<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1. Add more features and missing APIs for better integration with K8S around container ecosystem. For example, we have some PRs for GPU/NIC pass-through, which can give us a more powerful "--device" interface(device field in OCI spec),
and help kata-containers better integrate with K8S.<o:p></o:p></p>
<p class="MsoNormal">2. Make a solid baseline of kata-containers which is stable enough and involves enough features[1], always provide stable branches and LTS support to make sure kata-containers and kata-community is trustworthy, never break backward compatibility(unless
it's inevitable) and make sure kata-containers can be upgraded smoothly("live-update" in a word)[2].<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe we can achieve this in short term with help of our great community and so many talented contributors, besides community works, what I can do is keep testing the process in our product and keep contributing codes/feedbacks back
to our community to make kata better and better!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">References:<o:p></o:p></p>
<p class="MsoNormal">[1]: https://github.com/kata-containers/packaging/issues/160<o:p></o:p></p>
<p class="MsoNormal">[2]: https://github.com/kata-containers/runtime/issues/492<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="ZH-CN" style="font-size:11.0pt;font-family:"微软雅黑",sans-serif">发件人</span></b><b><span style="font-size:11.0pt;font-family:"微软雅黑",sans-serif">:</span></b><span style="font-size:11.0pt;font-family:"微软雅黑",sans-serif"> Anne Bertucio
[mailto:anne@openstack.org] <br>
<b><span lang="ZH-CN">发送时间</span>:</b> 2018<span lang="ZH-CN">年</span>8<span lang="ZH-CN">月</span>27<span lang="ZH-CN">日</span> 23:56<br>
<b><span lang="ZH-CN">收件人</span>:</b> kata-dev@lists.katacontainers.io<br>
<b><span lang="ZH-CN">主题</span>:</b> [kata-dev] [AC] Arch Committee Election: Q&A period open!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We have four candidates for the Architecture Committee election—names and links to their ML posts below. The next week 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 the week of the 3rd. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To kick off Q&A week: <b>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?</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Candidates (in alphabetical order):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Eric Ernst [1]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Jon Olson [2]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Kaly Xin [3]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Wei Zhang [4] <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[1] <a href="http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000337.html">http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000337.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">[2] <a href="http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000341.html">http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000341.html</a> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">[3] <a href="http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000333.html">http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000333.html</a> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">[4] <a href="http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000330.html">http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000330.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Anne Bertucio<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">OpenStack Foundation<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><a href="mailto:anne@openstack.org">anne@openstack.org</a> | irc: annabelleB<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>