[openstack-dev] Openstack Cinder - Wishlist
scott.dangelo at hpe.com
Tue Mar 1 13:15:56 UTC 2016
I like the idea of a Cinder Wishlist or perhaps titled: Cinder Future Design and Architecture list. I think the Cinder community could benefit if we continued to refine the work we did on this Wishlist at the Mitaka midcycle and spent a few minutes each cycle going over the list, prioritizing, and commenting.
This seems useful for new contributors, such as Mohammed and his team, as well as others who wish to plan work.
Note: Future work for Cinder <-> Nova API changes are tracked and discussed here:
Scott D'Angelo (scottda)
From: Michał Dulko [michal.dulko at intel.com]
Sent: Tuesday, March 01, 2016 5:48 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Openstack Cinder - Wishlist
On 03/01/2016 11:31 AM, mohammed.asharaf at wipro.com wrote:
> Would like to know if there’s feature wish list/enhancement request
> for Open stack Cinder I.e. a list of features that we would like to
> add to Cinder Block Storage ; but hasn’t been taken up for development
> We have couple developers who are interested to work on OpenStack
> Cinder... Hence would like to take a look at those wish list…
> Thanks ,
At the Cinder Midcycle Meetup in January we've created a list of
developers answers to "if you would have time what would you want to
sort out in Cinder?". The list can be find at the bottom of etherpad
. It may seem a little vague for someone not into Cinder's internals,
so I can provide some highlights:
* Quotas - Cinder have issues with quota management. Right now there are
efforts to sort this out.
* Notifications - we do not version or standardize notifications sent
over RPC. That's a problem if someone relies on them.
* A/A HA - there are ongoing efforts to make cinder-volume service
scalable in A/A manner.
* Cinder/Nova API - the way Nova talks with Cinder needs revisiting as
the limitations of current design are blocking us.
* State management - the way Cinder resources states are handled isn't
strongly defined. We may need some kind of state machine for that? (this
one is controversial ;)).
* Objectification - we've started converting Cinder to use
oslo.versionedobjects back in Kilo cycle. This still needs to be finished.
* Adding CI that tests rolling upgrades - starting from Mitaka we have
tech preview of upgrades without downtime. To get this feature out of
experimental stage we need a CI that will test it in gate.
* Tempest testing - we should increase our integration tests coverage.
If you're interested in any of these items feel free to ask me on IRC
(dulek on freenode) so I can point you to correct people for details.
Apart from that you can look through the blueprint list . Note that a
lot of items there may be outdated and not fitting well into current
state of Cinder.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev