Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
One of the big pressures on Devstack is everyone wanting to be included. The laundry list of distros supported is big, and is only prevented in growing by nacking patches for new ones. All kinds of projects want in, and it's still not clear where a project moves to "official enough" to get landed.
All of this means most of what's in devstack isn't tested at all in our CI system (we only run on precise, and only in a small number of configs). That makes the complexity of landing or changing things in devstack, and knowing we didn't break something important, pretty hard.
I'd like to drive some discussion around what it means to be supported. I think requiring distros to be part of the devstack/tempest gate should be required for icehouse, and those that aren't, are either removed or pulled from the documentation. I think for projects and plugins to projects we also need to think about validation requirements. But this should be a lively discussion to try to sort out those boundaries so that we can have an even more solid icehouse version of Devstack.
