[openstack-dev] [cinder] Custom fields for versioned objects

Gorka Eguileor geguileo at redhat.com
Fri Dec 18 08:46:46 UTC 2015

On 15/12, Ryan Rossiter wrote:
> Thanks for the review Michal! As for the bp/bug report, there’s four options:
> 1. Tack the work on as part of bp cinder-objects
> 2. Make a new blueprint (bp cinder—object-fields)

I think #2 would be the best option, as this is not part of the effort
to move to VOs but to improve them and the code in general.

Thanks for working on this, as I've been meaning to tackle the issue of
having literal strings all over the code for the status for quite a

> 3. Open a bug to handle all changes for enums/fields
> 4. Open a bug for each changed enum/field
> Personally, I’m partial to #1, but #2 is better if you want to track this work separately from the other objects work. I don’t think we should go with bug reports because #3 will be a lot of Partial-Bug and #4 will be kinda spammy. I don’t know what the spec process is in Cinder compared to Nova, but this is nowhere near enough work to be spec-worthy.
> If this is something you or others think should be discussed in a meeting, I can tack it on to the agenda for tomorrow.

More information about the OpenStack-dev mailing list