<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
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.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.b
{mso-style-name:b;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For instance: Open DayLight, OpenStack™ compatible<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--rocky<o:p></o:p></span></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 #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""> Bhandaru, Malini K [mailto:malini.k.bhandaru@intel.com]
<br>
<b>Sent:</b> Thursday, May 01, 2014 12:32 PM<br>
<b>To:</b> Auld, Will; Mark Collier<br>
<b>Cc:</b> Defcore-committee@lists.openstack.org<br>
<b>Subject:</b> Re: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Non commercial product -- Say there is some new open source switch or management framework .. if it wants to earn the OpenStack seal it should meet some agreed
upon interface and pass some functionality tests. That would reduce the guess work on the part of the cloud provider on what they can mix and match. Certification would also be tied to a version number.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Malini<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"></a><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 #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""> Auld, Will [mailto:will.auld@intel.com]
<br>
<b>Sent:</b> Thursday, May 01, 2014 11:57 AM<br>
<b>To:</b> Mark Collier<br>
<b>Cc:</b> Defcore-committee@lists.openstack.org<br>
<b>Subject:</b> Re: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I don’t really have anything in mind. However, anything and everything that might be considered as a candidate for a granted a license should be included.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Will<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";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""> Mark Collier [<a href="mailto:mark@openstack.org">mailto:mark@openstack.org</a>]
<br>
<b>Sent:</b> Thursday, May 01, 2014 11:44 AM<br>
<b>To:</b> Auld, Will<br>
<b>Cc:</b> <a href="mailto:Rob_Hirschfeld@Dell.com">Rob_Hirschfeld@Dell.com</a>; <a href="mailto:Defcore-committee@lists.openstack.org">
Defcore-committee@lists.openstack.org</a><br>
<b>Subject:</b> Re: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What would be an example of a non commercial product?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On May 1, 2014, at 1:31 PM, Auld, Will <<a href="mailto:will.auld@intel.com">will.auld@intel.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I’m having a little trouble with “Core Capability” and “Capability.”<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I like Mark’s definition but want it to also say how we know whether specific items are part of the “core capability.” For example we might modify Mark’s definition as:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Core Capability</b>: A capability all<span class="apple-converted-space"> </span><s>commercial</s><span class="apple-converted-space"> </span>products are expected to include when marketed as “OpenStack”, to ensure interoperability
between such products, which will be implemented via requirements in trademark licenses granted by the foundation.<span class="apple-converted-space"> </span><span style="color:red">The requirements will include both “Designated Sections” and “Capabilities”
defined by the technical committee.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I think this should apply to any product, commercial or otherwise, for which we grant a license.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">As for my problem with “Capability,” I think it should be more about the functionality than the tests:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Capability</b><span class="apple-converted-space"> </span>–<span class="apple-converted-space"> </span><span style="color:red">the functionality ensured by</span><span class="apple-converted-space"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">a
set of tests collected into a group as defined by the technical community (the DefCore committee has made preliminary assignments to start the process)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Will</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
</div>
<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">
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span class="apple-converted-space"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Mark
Collier [<a href="mailto:mark@openstack.org">mailto:mark@openstack.org</a>]<span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Thursday, May 01, 2014 10:33 AM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:Rob_Hirschfeld@Dell.com">Rob_Hirschfeld@Dell.com</a><br>
<b>Cc:</b><span class="apple-converted-space"> </span><a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I think “Core Capability” works, provided we have a good clear definition for the word that makes it clear this is meant to be used in the context of technical capabilities commercial products are expected to include if they wish to license
the OpenStack marks. Maybe it’s that simple:<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b>Core Capability</b>: A capability all commercial products are expected to include when marketed as “OpenStack”, to ensure interoperability between such products, which will be implemented via requirements in trademark licenses granted
by the foundation.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">This should make it clear that the new use of “core” is all about commercial implementations/products nothing else, superseding the old concept of “core” which was more associated with projects and how they are managed in the community.
Is that a fair statement?<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On Apr 30, 2014, at 10:22 PM, <<a href="mailto:Rob_Hirschfeld@Dell.com"><span style="color:purple">Rob_Hirschfeld@Dell.com</span></a>> <<a href="mailto:Rob_Hirschfeld@Dell.com"><span style="color:purple">Rob_Hirschfeld@Dell.com</span></a>>
wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">All,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">We’re getting into crunch time for DefCore! We need to get the TC & PTLs engaged to help score the last criteria. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">At the last meeting, we put that on hold to figure out some lexicon. Please review and raise issues if you have any:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Lexicon:</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></b><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Core
Capability –<span class="apple-converted-space"> </span></span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">this is THE REAL DEAL – core capabilities are the definition of core. OpenStack products demonstration that they work for
the core capabilities.<span class="apple-converted-space"><b> </b></span><b> </b> We believe it’s important to use the word “core” here and not introduce new terms like “required” “baseline” or “essential.”</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Capability
Selection Matrix</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">– this is how we pick core capabilities by scoring
them with the selection criteria</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Selection
Criteria</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">– this is one of 12 factors considered in selecting core
capabilities. (see text below)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Designated
Section –<span class="apple-converted-space"> </span></span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">a part of the code that the OpenStack technical community has identified as required to be implemented. </span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Capability</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">–
a set of tests collected into a group as defined by the technical community (the DefCore committee has made preliminary assignments to start the process)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:.5in">
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:11.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">DefCore</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">–
the board committee that oversees that core capability selection process for each release and other items related to the commercial brand.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Also, I’d like to made a quick decision > PUBLIC APIs ONLY. I was looking at the criteria and realized that non-admin trumps everything. I believe that we just need to
accept that Core is Public API only because that’s required for interop. Admin tests are great but will not be core.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Finally, here’s an updated description of the Capabilities Scoring that Josh and I have worked out (WITH GRAPHICS!)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<h1 style="margin:0in;margin-bottom:.0001pt;line-height:36.0pt;vertical-align:baseline">
<span style="font-size:27.0pt">DefCore Core Capabilities Selection Criteria SIMPLIFIED -> how we are picking Core</span><o:p></o:p></h1>
<div>
<div>
<p class="MsoNormal" style="line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;color:#373737"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;color:#373737">I’ve posted about the<span class="apple-converted-space"> </span><a href="http://robhirschfeld.com/2014/01/07/defcore-critieria/" title="How are we picking the OpenStack DefCore “must pass” tests?"><span style="color:#1982D1;border:none windowtext 1.0pt;padding:0in">early
DefCore core capabilities selection</span></a><span class="apple-converted-space"> </span>process before and we’ve put them into application and<span class="apple-converted-space"> </span><a href="http://robhirschfeld.com/2014/04/11/defcore-road-show/" title="Running with scissors > DefCore “must-pass” Road Show Starts [VIDEOS]"><span style="color:#1982D1;border:none windowtext 1.0pt;padding:0in">discussed
them with the community</span></a>. The feedback was simple:<span class="apple-converted-space"> </span><a href="http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read"><span style="color:#1982D1;border:none windowtext 1.0pt;padding:0in">tl;dr</span></a>.
<em><span style="border:none windowtext 1.0pt;padding:0in">You’ve got the right direction but make it simpler</span></em>!</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="line-height:20.3pt;background:white;vertical-align:baseline">
<a href="http://robhirschfeld.files.wordpress.com/2014/04/capabilities_selection2.png"><span style="font-size:11.5pt;color:#1982D1;border:none windowtext 1.0pt;padding:0in;text-decoration:none"><image001.png></span></a><o:p></o:p></p>
</div>
</div>
<p style="margin-bottom:19.5pt;line-height:20.3pt;background:white;vertical-align:baseline;font-style:inherit;font-weight:inherit;outline: 0px">
<span style="font-size:11.5pt;color:#373737">So we pulled the 12 criteria into four primary categories:</span><o:p></o:p></p>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;color:#373737">1.</span><span style="font-size:7.0pt;color:#373737"> <span class="apple-converted-space"> </span></span><strong><span style="font-size:11.5pt;color:#373737;border:none windowtext 1.0pt;padding:0in">Usage:</span></strong><span class="apple-converted-space"><b><span style="font-size:11.5pt;color:#373737;border:none windowtext 1.0pt;padding:0in"> </span></b></span><span style="font-size:11.5pt;color:#373737">the
capabilitiy is widely used (Refstack will collect data)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;color:#373737">2.</span><span style="font-size:7.0pt;color:#373737"> <span class="apple-converted-space"> </span></span><strong><span style="font-size:11.5pt;color:#373737;border:none windowtext 1.0pt;padding:0in">Direction</span></strong><span style="font-size:11.5pt;color:#373737">:
the capability advances OpenStack technically</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;color:#373737">3.</span><span style="font-size:7.0pt;color:#373737"> <span class="apple-converted-space"> </span></span><strong><span style="font-size:11.5pt;color:#373737;border:none windowtext 1.0pt;padding:0in">Community</span></strong><span style="font-size:11.5pt;color:#373737">:
the capability builds the OpenStack community experience</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;color:#373737">4.</span><span style="font-size:7.0pt;color:#373737"> <span class="apple-converted-space"> </span></span><strong><span style="font-size:11.5pt;color:#373737;border:none windowtext 1.0pt;padding:0in">System</span></strong><span style="font-size:11.5pt;color:#373737">:
the capability integrates with other parts of OpenStack</span><o:p></o:p></p>
</div>
</div>
<p style="margin-bottom:19.5pt;line-height:20.3pt;background:white;vertical-align:baseline;font-style:inherit;font-weight:inherit;outline: 0px">
<span style="font-size:11.5pt;color:#373737">These categories summarize critical values that we want in OpenStack and so make sense to be the primary factors used when we select core capabilies. While we strive to make the DefCore process objective and quantative,
we must recognize that these choices drive community behavior.</span><o:p></o:p></p>
<p style="margin-bottom:19.5pt;line-height:20.3pt;background:white;vertical-align:baseline;font-style:inherit;font-weight:inherit;outline: 0px">
<span style="font-size:11.5pt;color:#373737">With this prespective, let’s review the thirteen selection criteria. To make it easier to cross reference, we’ve given each criteria a shortened name:</span><o:p></o:p></p>
<h3 style="margin:0in;margin-bottom:.0001pt;line-height:31.2pt;background:white;vertical-align:baseline;font-weight:inherit;font-style:inherit;outline: 0px" id="magicdomid240">
<span style="font-size:7.5pt;text-transform:uppercase;letter-spacing:1.2pt">SHOWS PROVEN USAGE</span><o:p></o:p></h3>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">“<span class="b"><b><span style="border:none windowtext 1.0pt;padding:0in">Widely
Deployed</span></b></span>” Candidates are widely deployed capabilities. We favor capabilities that are supported by multiple public cloud providers and private cloud products</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Used
by Tools”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> Candidates are widely used capabilities:Should be included if supported by common tools (RightScale, Scalr)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">“</span><strong><span style="font-size:11.5pt;border:none windowtext 1.0pt;padding:0in">Used
by </span></strong><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">Clients”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> Candidates are widely
used capabilities: Should be included if part of common libraries (Fog, Apache jclouds, etc)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">Aligns with Technical Direction</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">“<span class="b"><b><span style="border:none windowtext 1.0pt;padding:0in">Future
Direction”</span></b></span> Should reflect future technical direction (from the project technical teams and the TC)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Stable” </span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">Test
is required stable for >2 releases (because things leaving Core are bad)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Complete”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> Where
the code being tested has an designed area of alternate implementation (extension framework) as per the Core Principles, there should be parity in capability tested across extension implementations</span><o:p></o:p></p>
</div>
</div>
<h3 style="margin:0in;margin-bottom:.0001pt;line-height:31.2pt;background:white;vertical-align:baseline;font-weight:inherit;font-style:inherit;outline: 0px" id="magicdomid265">
<span style="font-size:7.5pt;text-transform:uppercase;letter-spacing:1.2pt">PLAYS WELL WITH OTHERS</span><o:p></o:p></h3>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Discoverable”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> Capability
being tested is Service Discoverable (can be found in Keystone and via service introspection)</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Doc’d”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> Should
be well documented, particularly the expected behavior.</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Core
in Last Release”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> A test that is a must-pass test should stay a must-pass test (makes must-pass tests sticky release per release)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">Takes a System View</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif"">“<span class="b"><b><span style="border:none windowtext 1.0pt;padding:0in">Foundation”</span></b></span> Test
capabilities that are required by other must-pass tests and/or depended on by many other capabilities</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Atomic”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> Capabilities
is unique and cannot be build out of other must-pass capabiliies</span><o:p></o:p></p>
</div>
</div>
<div style="margin-left:30.0pt">
<div>
<p class="MsoNormal" style="text-indent:-.25in;line-height:20.3pt;background:white;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:Wingdings">§</span><span style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span class="b"><b><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";border:none windowtext 1.0pt;padding:0in">“Proximity”</span></b></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif""> (sometimes
called a Test Cluster) selects for Capabilities that are related to Core Capabilities. This helps ensure that related capabilities are managed together.</span><o:p></o:p></p>
</div>
</div>
<p style="margin-bottom:19.5pt;line-height:20.3pt;background:white;vertical-align:baseline;font-style:inherit;font-weight:inherit;outline: 0px">
<span style="font-size:11.5pt">Note: The 13th “non-admin” criteria has been removed because Admin APIs cannot be used for interoperability and cannot be considered Core.</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Rob</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">______________________________</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Rob Hirschfeld</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Sr. Distinguished Cloud Solution Architect</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#0085C3">Dell</span></b><span class="apple-converted-space"><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444"> </span></span><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">|
Cloud Edge, Data Center Solutions</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">cell</span></b><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#AAAAAA"> </span><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">+1
512 909-7219<span class="apple-converted-space"> </span><b>blog</b><span class="apple-converted-space"> </span><a href="http://robhirschfeld.com/"><span style="color:purple">robhirschfeld.com</span></a>,<span class="apple-converted-space"> </span><b>twitter</b><span class="apple-converted-space"> </span>@zehicle</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Please note, I am based in the CENTRAL (-6) time zone</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>