Open Stack

Tom,

I agree with you.  That spread sheet is an intermediate document that allowed us to get moving.

Troy added some descriptions to https://review.openstack.org/#/c/110159/2/defcore/havanacore.json

That file will be the source in the future.  We're waiting for it to get +1s for review (HINT TO DEFCORE).

Rob


> -----Original Message-----
> From: Tom Fifield [mailto:tom at openstack.org]
> Sent: Friday, August 22, 2014 12:58 AM
> To: Hirschfeld, Rob; rochelle.grober at huawei.com;
> joshua at pistoncloud.com
> Cc: defcore-committee at lists.openstack.org
> Subject: Re: [OpenStack-DefCore] Please review, results from
> Designated Sections review w/ recommendations. +1s needed
>
> Hi Rob,
>
> Just to confirm, the 'capabilities file' is the spreadsheet at
> https://wiki.openstack.org/wiki/File:DefCore_Capabilities_Scoring.pdf ?
>
> The names in there are a bit cryptic, don't you think?
>
> Is this the only place/format information about capabilities is available?
>
>
> Regards,
>
>
> Tom
>
> On 22/08/14 10:44, Rob_Hirschfeld at Dell.com wrote:
> > Rocky,
> >
> >
> >
> > The capabilities file includes that information. It would be
> > possible to create a tree view from the file like you suggest.
> >
> >
> >
> > Rob
> >
> >
> >
> > *From:*Rochelle.RochelleGrober [mailto:rochelle.grober at huawei.com]
> > *Sent:* Wednesday, August 20, 2014 1:24 PM
> > *To:* Hirschfeld, Rob; tom at openstack.org; joshua at pistoncloud.com
> > *Cc:* defcore-committee at lists.openstack.org
> > *Subject:* RE: [OpenStack-DefCore] Please review, results from
> > Designated Sections review w/ recommendations. +1s needed
> >
> >
> >
> > Tom, Rob,
> >
> >
> >
> > Capabilities is a much longer list than projects and really gets
> > into more details than some people might be able to handle.
> >
> >
> >
> > Perhaps clumping the capabilities into larger groups that are also
> > contained in projects, such that you can inform the user:
> >
> >
> >
> > Capabilities:
> >
> > * Compute(expandable list) -- Included if you use Havana Nova
> >
> > o Compute capabilities expanded by clickthrough
> >
> > * Volume -- included if you use Nova
> >
> > o Nova based volume capabilities list
> >
> > * Object -- included if you use Swift
> >
> > o Object capabilities
> >
> > * Etc.
> >
> >
> >
> > This way, the format is capabilities based, but also calls out where
> > the capabilities default from.
> >
> >
> >
> > --Rocky
> >
> >
> >
> > *From:*Rob_Hirschfeld at Dell.com
> > [mailto:Rob_Hirschfeld at Dell.com]
> > *Sent:* Wednesday, August 20, 2014 11:07 AM
> > *To:* tom at openstack.org ;
> > joshua at pistoncloud.com
> > *Cc:* defcore-committee at lists.openstack.org
> >
> > *Subject:* Re: [OpenStack-DefCore] Please review, results from
> > Designated Sections review w/ recommendations. +1s needed
> >
> >
> >
> >>
> >> mockups attached - very, very rough!
> >>
> > Tom,
> >
> > Please look at the mockups that we created in Refstack for this:
> > https://review.openstack.org/#/c/96657/ &
> > https://review.openstack.org/#/c/96658/. I think any validation
> > needs to focus on the capabilities instead of the projects since
> > that's the real measure of Core in the current plan.
> >
> > I understand that the process has been confusing to follow; however,
> > I hope that we're getting to a place where we can explain it simply.
> > I'd rather have the prompt not worry about the history.
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140822/c740bcec/attachment.html>