<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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"><span style="color:#1F497D">Would just like to point out .. assigning a machine to a single tenant – with Docker, would not be very different from assigning bare metal to a tenant who does not want the overhead of virtualization and that
is an use case we would like to support in the cloud too.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Malini<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Rob_Hirschfeld@Dell.com [mailto:Rob_Hirschfeld@Dell.com]
<br>
<b>Sent:</b> Friday, May 23, 2014 5:02 PM<br>
<b>To:</b> Auld, Will; aclark@suse.com; Defcore-committee@lists.openstack.org<br>
<b>Subject:</b> Re: [OpenStack-DefCore] Seeking DefCore Feedback from Summit (you can just +1 if you think community supports DefCore)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Will,<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 want to make sure I understand. You agree that the issue does not change DefCore approach? We’re going to wait and see what happens with Docker.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Auld, Will [<a href="mailto:will.auld@intel.com">mailto:will.auld@intel.com</a>]
<br>
<b>Sent:</b> Friday, May 23, 2014 11:19 AM<br>
<b>To:</b> Hirschfeld, Rob; <a href="mailto:aclark@suse.com">aclark@suse.com</a>;
<a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
<b>Cc:</b> Auld, Will<br>
<b>Subject:</b> RE: [OpenStack-DefCore] Seeking DefCore Feedback from Summit (you can just +1 if you think community supports DefCore)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">The issue here is as much paradigm as much as function. Docker with OpenStack is kinda like a PaaS and kinda like a IaaS. We would like to be able to deliver it in the cloud as an option alongside our various
hypervisors as well as bare metal. Delivered on a Nova compute host means the host should be restricted to a single tenant which is unusual. Docker is just a different beast for our environment and will need to evolve before it could be a part of core.
<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">Thanks,<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">Will<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:Rob_Hirschfeld@Dell.com">Rob_Hirschfeld@Dell.com</a> [<a href="mailto:Rob_Hirschfeld@Dell.com">mailto:Rob_Hirschfeld@Dell.com</a>]
<br>
<b>Sent:</b> Tuesday, May 20, 2014 1:52 PM<br>
<b>To:</b> <a href="mailto:aclark@suse.com">aclark@suse.com</a>; <a href="mailto:Defcore-committee@lists.openstack.org">
Defcore-committee@lists.openstack.org</a><br>
<b>Subject:</b> Re: [OpenStack-DefCore] Seeking DefCore Feedback from Summit (you can just +1 if you think community supports DefCore)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin-bottom:12.0pt">> > 2. Nova Docker is an interesting use case because Docker does not use<br>
> > Glance or Cinder in the same way as libvirt Nova does. This means <br>
> > that a Docker cloud would not pass the core tests for Glance or <br>
> > Cinder as currently structured.<br>
> <br>
> <br>
> ok a naive question on my part. Is this a question for the first <br>
> release or something to address for Juno? I ask the question because <br>
> I'm not sure what the stated Docker support was for Havana and Icehouse.<br>
> <o:p></o:p></p>
<p style="margin-bottom:12.0pt">I don’t think we have to make changes in response, but it does raise questions that we should consider.<o:p></o:p></p>
<p style="margin-bottom:12.0pt">If someone wanted a “Docker Only” OpenStack then there would be compatibly issues with Glance and Cinder because they don’t work the same way for Docker as other approaches. We could fake the responses to pass the tests but
that would cause other issues. At some point, we may have to resolve if Nova+Docker is a new type of IaaS and thus a different set of capabilities. There’s no simple answer.<o:p></o:p></p>
<p style="margin-bottom:12.0pt">Since our goal is interop, I suspect there’s little room for APIs that behave in different ways. Consequently, the Docker question is an excellent test of DefCore.<o:p></o:p></p>
<p style="margin-bottom:12.0pt">I hope that helps.<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>