<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Sep 12, 2014, at 2:37 PM, Joshua McKenty <<a href="mailto:joshua@pistoncloud.com">joshua@pistoncloud.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Just so I’m clear, Doug - you would therefore also like to propose some designated sections for Keystone?</div></blockquote><div><br></div><div>Based on comments from the meeting yesterday, I thought we had no keystone tests, and so there wouldn’t be a need for any designated sections. That’s not optimal, in my mind, because the community did *build* a version of keystone for havana, but if we don’t have the tests or have not required capabilities for some other reason, then I am OK with ignoring the designated sections question for havana. </div><div><br></div><div>If I misheard or that information about the tests was incorrect, then we should apply the same criteria to keystone that I’m proposing for Swift and either have some designated sections or reconsider whether we include the capabilities. In the keystone case, dropping the capabilities would seriously hinder our ability to say that DefCore is describing an interoperable set of features, since authentication is so pervasive, and so the resolution would need to be thought through very carefully.</div><div><br></div><div>Doug</div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br><div apple-content-edited="true">
<div style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--</div><div><br></div><div>Joshua McKenty</div><div>Chief Technology Officer</div><div>Piston Cloud Computing, Inc.</div><div>+1 (650) 242-5683</div><div>+1 (650) 283-6846</div><div><a href="http://www.pistoncloud.com/">http://www.pistoncloud.com</a></div><div><br></div><div>"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."</div></div></div>
</div>
<br><div><div>On Sep 12, 2014, at 11:35 AM, <<a href="mailto:Rob_Hirschfeld@Dell.com">Rob_Hirschfeld@Dell.com</a>> <<a href="mailto:Rob_Hirschfeld@Dell.com">Rob_Hirschfeld@Dell.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<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;}
/* 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";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1"><p>> -----Original Message-----<br>
> From: Doug Hellmann [<a href="mailto:doug@doughellmann.com">mailto:doug@doughellmann.com</a>]<br>
> The actual current proposal, if I understand correctly, is to require <br>
> the Swift APIs be provided, but not require the use of Swift’s code to <br>
> do so. We may be converging on dropping the requirement of the APIs, <br>
> but I don’t think that’s settled.<br>
<br>
<o:p></o:p></p><p>The current Havana recommendation includes some Swift APIs; however, I believe we should (and will ask the Board to) reconsider that based on feedback I have been getting.<o:p></o:p></p><p><br>
> I believe, and Rob please correct me if I misunderstood, that some <br>
> distros would also like to provide an OpenStack product that doesn’t <br>
> include object storage in any way (neither Swift nor Ceph). I’m not <br>
> especially inclined to care about that use case, but it’s out there.<br>
<br>
<o:p></o:p></p><p>I don’t see distros doing omitting whole projects; however, more integrated products or services have already proven that they will be more selective. IMHO, that’s the market giving us critical feedback and we should be careful in over fencing the market.
<o:p></o:p></p>
</div>
</div>
_______________________________________________<br>Defcore-committee mailing list<br><a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a><br></blockquote></div><br></div></div></blockquote></div><br></body></html>