[OpenStack-DefCore] Please review, results from Designated Sections review w/ recommendations. +1s needed

Tom Fifield tom at openstack.org
Fri Aug 22 05:57:40 UTC 2014


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>
> [mailto:Rob_Hirschfeld at Dell.com]
> *Sent:* Wednesday, August 20, 2014 11:07 AM
> *To:* tom at openstack.org <mailto:tom at openstack.org>;
> joshua at pistoncloud.com <mailto:joshua at pistoncloud.com>
> *Cc:* defcore-committee at lists.openstack.org
> <mailto: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.
> 




More information about the Defcore-committee mailing list