Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
At present, automated testing only tests a single configuration. We are facing an explosion of configurations that we expect will actually be used:
* Hypervisor * Quantum vs. nova-network * Cinder vs. nova-volume * mysql vs. postgres
In addition, some of these components have important sub-configurations. We need to be testing more configurations but can't possibly test them all. Some of these need real hardware configurations to be properly tested.
We need to choose a set of configurations to include and marshal the hardware resources. At the same time, it should be possible for any one that wants to add another configuration to the test be able to do so by providing the hardware resources.
Pruning the configuration tree requires the input of those with deep architectural knowledge of the component interactions. Only they can say which configurations are "different" enough that they should be included.