<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:#1F497D;}
.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"><span style="color:#1F497D">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I would like to announce my candidacy for the PTL position of Magnum.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">To introduce myself, my involvement in Magnum began in December 2014, in which the project was at a very early stage. Since then, I have been working with the team to explore the roadmap, implement and refine
individual components, and gradually grow the feature set. Along the way, I’ve developed comprehensive knowledge of the architecture and has led me to take more leadership responsibilities. In the past release cycle, I started taking some of the PTL responsibilities
when the current PTL was unavailable. I believe my past experience shows that I am qualified for the Magnum PTL position.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In my opinion, Magnum's key objective is to pursue tight integration between OpenStack and the various Container Orchestration Engines (COE) such as Kubernetes, Docker Swarm, and Apache Mesos. Therefore, I would
suggest to give priority to the features that will improve the integration in this regard. In particular, I would emphasize the following features:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Neutron integration: Currently, Flannel is the only supported network driver for providing connectivity between containers in different hosts. Flannel is mostly used for overlay networking, and it has significant
performance overhead. In the Newton cycle, I would suggest we collaborate with the Kuryr team to develop a non-overlay network driver.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Cinder integration: Magnum supports using Cinder volume for storing container images. We should add support for mounting Cinder volumes to containers as data volumes as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Ironic integration: Add support for Ironic virt-driver to enable support for high-performance containers on baremetal servers. We identified this feature as a key feature in a few release cycles previously
but unfortunately it hasn't been fully implemented yet.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In addition, I believe the items below are important and need attention in the Newton cycle:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Pluggable architecture: Refine the architecture to make it extensible. As a result, third-party vendors can plugin their own flavor of COEs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Quality assurance: Improve coverage of integration and unit tests.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Documentation: Add missing documents and enhance existing documents.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Remove hard dependency: Eliminate hard dependency on Barbican by implementing a functional equivalent replacement. Note that this is a technical debt [1] and should be clean up in Newton cycle.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Horizon UI: Enhance our Horizon plugin.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Grow the community: Attract new contributors to Magnum.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In the long term, I hope to work towards the goal of making OpenStack become a compelling platform for hosting containerized applications. To achieve this goal, we need to identify and develop unique capabilities
that could differentiate Magnum from its competitors, thus attracting users to move their container workloads to OpenStack. As an initial start, below is a list features that I believe we could explore. Please don't consider it as final decisions and we will
definitely debate each of them. Also, you are always welcome to contribute your own list of requirements:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Resource interconnection and orchestration: Support dynamically connecting COE-managed resources (i.e. a container) to OpenStack-managed resources (i.e. a Neutron network), thus providing the capabilities to
link containerized applications to existing OpenStack infrastructure. By doing that, we enable orchestrations across COE-managed resources and OpenStack-managed resources through a Heat template.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Integrated authentication system: Integrate COE authentication system with Keystone, thus eliminating the pain of handling multiple authentication mechanism.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">* Standard APIs: Hide the heterogeneity of various COEs and expose a unified interface to manage resources of various kinds.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for considering my PTL candidacy.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-July/069130.html">
http://lists.openstack.org/pipermail/openstack-dev/2015-July/069130.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Hongbin<o:p></o:p></span></p>
</div>
</body>
</html>