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

We have said that other kinds of user interface, e.g. the CLI, are out of scope for the document (though not for OpenStack, of course!). After some discussion, we decided that Horizon being a service was more important to its categorisation than it being a user interface, so I wrote the Graphical User Interface design goal to ensure that it is covered. However, I'm sure y'all have spent much more time thinking about what Horizon contributes to OpenStack than I, so your feedback and suggestions are needed.

That is not the only way in which I think this document is relevant to the Horizon team: one of my goals with the exercise is to encourage the service projects to make sure their APIs make all of the operationally-relevant information available and legible to applications. That would include e.g. surfacing events, which I know is something that Horizon has wanted for a long time, and hopefully this will lead to easier ways to build a GUI without as much polling.

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