<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;}
/* 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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Tom,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree with you. That spread sheet is an intermediate document that allowed us to get moving.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Troy added some descriptions to <a href="https://review.openstack.org/#/c/110159/2/defcore/havanacore.json">
https://review.openstack.org/#/c/110159/2/defcore/havanacore.json</a> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That file will be the source in the future. We’re waiting for it to get +1s for review (HINT TO DEFCORE).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Rob<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin-bottom:12.0pt">> -----Original Message-----<br>
> From: Tom Fifield [mailto:tom@openstack.org]<br>
> Sent: Friday, August 22, 2014 12:58 AM<br>
> To: Hirschfeld, Rob; rochelle.grober@huawei.com; <br>
> joshua@pistoncloud.com<br>
> Cc: defcore-committee@lists.openstack.org<br>
> Subject: Re: [OpenStack-DefCore] Please review, results from <br>
> Designated Sections review w/ recommendations. +1s needed<br>
> <br>
> Hi Rob,<br>
> <br>
> Just to confirm, the 'capabilities file' is the spreadsheet at <br>
> https://wiki.openstack.org/wiki/File:DefCore_Capabilities_Scoring.pdf ?<br>
> <br>
> The names in there are a bit cryptic, don't you think?<br>
> <br>
> Is this the only place/format information about capabilities is available?<br>
> <br>
> <br>
> Regards,<br>
> <br>
> <br>
> Tom<br>
> <br>
> On 22/08/14 10:44, Rob_Hirschfeld@Dell.com wrote:<br>
> > Rocky,<br>
> ><br>
> ><br>
> ><br>
> > The capabilities file includes that information. It would be <br>
> > possible to create a tree view from the file like you suggest.<br>
> ><br>
> ><br>
> ><br>
> > Rob<br>
> ><br>
> ><br>
> ><br>
> > *From:*Rochelle.RochelleGrober [mailto:rochelle.grober@huawei.com]<br>
> > *Sent:* Wednesday, August 20, 2014 1:24 PM<br>
> > *To:* Hirschfeld, Rob; tom@openstack.org; joshua@pistoncloud.com<br>
> > *Cc:* defcore-committee@lists.openstack.org<br>
> > *Subject:* RE: [OpenStack-DefCore] Please review, results from <br>
> > Designated Sections review w/ recommendations. +1s needed<br>
> ><br>
> ><br>
> ><br>
> > Tom, Rob,<br>
> ><br>
> ><br>
> ><br>
> > Capabilities is a much longer list than projects and really gets <br>
> > into more details than some people might be able to handle.<br>
> ><br>
> ><br>
> ><br>
> > Perhaps clumping the capabilities into larger groups that are also <br>
> > contained in projects, such that you can inform the user:<br>
> ><br>
> ><br>
> ><br>
> > Capabilities:<br>
> ><br>
> > · Compute(expandable list) -- Included if you use Havana Nova<br>
> ><br>
> > o Compute capabilities expanded by clickthrough<br>
> ><br>
> > · Volume -- included if you use Nova<br>
> ><br>
> > o Nova based volume capabilities list<br>
> ><br>
> > · Object -- included if you use Swift<br>
> ><br>
> > o Object capabilities<br>
> ><br>
> > · Etc.<br>
> ><br>
> ><br>
> ><br>
> > This way, the format is capabilities based, but also calls out where <br>
> > the capabilities default from.<br>
> ><br>
> ><br>
> ><br>
> > --Rocky<br>
> ><br>
> ><br>
> ><br>
> > *From:*Rob_Hirschfeld@Dell.com <br>
> > [mailto:Rob_Hirschfeld@Dell.com]<br>
> > *Sent:* Wednesday, August 20, 2014 11:07 AM<br>
> > *To:* tom@openstack.org ; <br>
> > joshua@pistoncloud.com <br>
> > *Cc:* defcore-committee@lists.openstack.org<br>
> > <br>
> > *Subject:* Re: [OpenStack-DefCore] Please review, results from <br>
> > Designated Sections review w/ recommendations. +1s needed<br>
> ><br>
> ><br>
> ><br>
> >><br>
> >> mockups attached - very, very rough!<br>
> >><br>
> > Tom,<br>
> ><br>
> > Please look at the mockups that we created in Refstack for this:<br>
> > https://review.openstack.org/#/c/96657/ & <br>
> > https://review.openstack.org/#/c/96658/. I think any validation <br>
> > needs to focus on the capabilities instead of the projects since <br>
> > that’s the real measure of Core in the current plan.<br>
> ><br>
> > I understand that the process has been confusing to follow; however, <br>
> > I hope that we’re getting to a place where we can explain it simply.<br>
> > I’d rather have the prompt not worry about the history.<br>
> ><o:p></o:p></p>
</div>
</body>
</html>