Greetings, Cinder team!
As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide decisions. You can read the latest draft here:

We're trying to get feedback from as many people as possible - in many ways the value is in the process of coming together to figure out what we're trying to achieve as a community with OpenStack and how we can work together to build it. The document is there to help us remember what we decided so we don't have to do it all again over and over.

The vision is structured with two sections that apply broadly to every project in OpenStack - describing the principles that we believe are essential to every cloud, and the ones that make OpenStack different from some other clouds. The third section is a list of design goals that we want OpenStack as a whole to be able to meet - ideally each project would be contributing toward one or more of these design goals.

Clearly Cinder is an integral part of meeting the 'Basic Physical Data Center Management' design goal, and also contributes to the 'Hardware Virtualisation' goal.

The last paragraph in the 'Plays Well With Others' goal, about providing a standalone backend abstraction layer independently of the higher-level API (that might include e.g. scheduling and integration with other OpenStack services) was added with Cinder in mind, as I know that this is something the Cinder community has discussed, and it might also be applicable to other projects. Of course this is by no means mandatory, but it might be an interesting are to continue exploring.

The Partitioning section highlights the known mismatch between the concept of Availability Zones as borrowed from other clouds and the way operators use OpenStack, and offers a long-term design direction that Cinder might want to pursue in conjunction with Nova.

If you would like me or another TC member to join one of your team IRC meetings to discuss further what the vision means for your team, please reply to this thread to set it up. You are also welcome to bring up any questions in the TC IRC channel, #openstack-tc - there's more of us around during Office Hours (, but you can talk to us at any time.

Feedback can also happen either in this thread or on the review

If the team is generally happy with the vision as it is and doesn't have any specific feedback, that's cool but I'd like to request that at least the PTL leave a vote on the review. It's important to know whether we are actually developing a consensus in the community or just talking to ourselves :)

many thanks,

OpenStack Development Mailing List (not for usage questions)

Reply via email to