<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=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
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:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.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-CA" 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">I nominated myself to be a candidate of Zun PTL for Queens. As the founder of this<o:p></o:p></p>
<p class="MsoNormal">project, it is my honor to work with all of you to build an innovative<o:p></o:p></p>
<p class="MsoNormal">OpenStack container service.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OpenStack provides a full-featured data center management solution which<o:p></o:p></p>
<p class="MsoNormal">includes multi-tenant security, networking, storage, management and monitoring,<o:p></o:p></p>
<p class="MsoNormal">and more. All theses services are needed regardless of whether containers,<o:p></o:p></p>
<p class="MsoNormal">virtual machines, or baremetal servers are being used [1]. In this context,<o:p></o:p></p>
<p class="MsoNormal">Zun's role is to bring prevailing container technologies to OpenStack and<o:p></o:p></p>
<p class="MsoNormal">enable the reuse of existing infrastructure services for containers.<o:p></o:p></p>
<p class="MsoNormal">Eventually, different container technologies should be easily accessible by<o:p></o:p></p>
<p class="MsoNormal">cloud consumers, which is a goal Zun is contributing to.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Since April 2016, in which the project was founded, the Zun team has been<o:p></o:p></p>
<p class="MsoNormal">working hard to achieve its mission. We managed to delivere most of the<o:p></o:p></p>
<p class="MsoNormal">important features includes:<o:p></o:p></p>
<p class="MsoNormal">* A full-featured container API.<o:p></o:p></p>
<p class="MsoNormal">* A docker driver that serves as reference implementation.<o:p></o:p></p>
<p class="MsoNormal">* Neutron integration via Kuryr-libnetwork.<o:p></o:p></p>
<p class="MsoNormal">* Two image drivers: Docker Registry (i.e. Docker Hub) and Glance.<o:p></o:p></p>
<p class="MsoNormal">* Multi-tenancy: Containers are isolated by Keystone projects.<o:p></o:p></p>
<p class="MsoNormal">* Horizon integration.<o:p></o:p></p>
<p class="MsoNormal">* OpenStack Client integration.<o:p></o:p></p>
<p class="MsoNormal">* Heat integration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">By looking ahead to Queens, I would suggest the Zun team to focus on the<o:p></o:p></p>
<p class="MsoNormal">followings:<o:p></o:p></p>
<p class="MsoNormal">* NFV: Containerized NFV workload is emerging and we wants to adapt this trend.<o:p></o:p></p>
<p class="MsoNormal">* Containers-on-VMs: Provide an option to auto-provision VMs for containers.<o:p></o:p></p>
<p class="MsoNormal"> This is for use cases that containers need to be strongly isolated by VMs.<o:p></o:p></p>
<p class="MsoNormal">* Cinder integration: Leverage Cinder for providing data volume for containers.<o:p></o:p></p>
<p class="MsoNormal">* Alternative container runtime: Introduce a second container runtime as a<o:p></o:p></p>
<p class="MsoNormal"> Docker alternative.<o:p></o:p></p>
<p class="MsoNormal">* Capsule API: Pack multiple containers into a managed unit.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Beyond Pike, I would estimate Zun to move toward the following directions:<o:p></o:p></p>
<p class="MsoNormal">* Kubernetes: Kubernetes is probably the most popluar containers orchestration<o:p></o:p></p>
<p class="MsoNormal"> tool, but there are still some gaps that prevent Kubernetes to work well with<o:p></o:p></p>
<p class="MsoNormal"> OpenStack. I think Zun might be able to help to reduce the gaps. We could<o:p></o:p></p>
<p class="MsoNormal"> explore integration options for Kubernetes to make OpenStack more appealing<o:p></o:p></p>
<p class="MsoNormal"> for cloud-native users.<o:p></o:p></p>
<p class="MsoNormal">* Placement API: Nova team is working to split its scheduler out and Zun would<o:p></o:p></p>
<p class="MsoNormal"> like to leverage this new service if appropriate.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[1] https://www.openstack.org/assets/pdf-downloads/Containers-and-OpenStack.pdf<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Hongbin<o:p></o:p></p>
</div>
</body>
</html>