OpenStack Essex Design Summit

There has been a proliferation of custom integrated test suites and frameworks over the last year. Some of these include: * Stacktester (https://github.com/rackspace-titan/stacktester/) * Kong (https://github.com/cloudbuilders/kong) * Backfire (https://github.com/ohthree/backfire) * Proboscis (https://github.com/rackspace/python-proboscis) An effort to consolidate some of these efforts into a unified integrated test suite for OpenStack has been started and is available at https://github.com/sorenh/openstack-integration-tests. Some discussion about the effort occurred on the mailing list: https://lists.launchpad.net/openstack/msg04014.html. This session is to discuss the new, singular place to house integration tests of OpenStack and bring everyone's ideas to the table, assign some action items to interested parties, and make sure all interested parties have a clear roadmap for the integration test suite. Lets talk about a possible plan to gate commits so that things don't break quite so often. Things to consider: -Cross service? (keystone, glance, nova) -Packages or source installs? -Config management? (chef, puppet) -How to maintain? If we use packages then which packages control commits into trunk (Ubuntu, Debian, both?) -Which configurations are we gating against (libvirt, XenServer, MySQL, Postgres, etc.)