Greetings, Murano 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.

To be honest, nothing in the document we have so far really captures the scope and ambition of the original vision behind Murano. You could say that it fulfils a similar role to Heat in meeting the Customisable Integration goal by being one of the components that users can use to wire the various servies the OpenStack offers together into a coherent application, and functionally that would be a pretty accurate description. But nothing in there suggests that we want OpenStack to produce a standard packaging format for cloud application components or a marketplace where they can be published. Is that still part of the vision for Murano after the closure of the application catalog? Is it something that should be explicitly part of the vision for OpenStack clouds? If so, what should that look like?

The sections on Interoperability and Bidirectional Compatibility formalise what are already important design considerations for Murano, since one goal of its packaging format is obviously to provide interoperability across clouds.

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