Open Stack

Hey Stackers,

Just a quick note from the OpenStack QA team to give folks a status
report on where we are and our attack-plan over the next couple weeks.

For details, feel free to peruse the IRC meeting log here:

http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-16-16.04.log.html

Here are the big status updates:

1) Continuous Integration

I'd like to give a quick shout out to Jesse Andrews, Vish, Anthony
Young, Dean Troyer, Chmouel Boudjnah and everyone on the RCB team
who's been helping with the devstack project. It's moving along at the
speed of light and is becoming a great way for production deployment
tooling -- like chef or puppet modules -- to understand the
oft-complex world of OpenStack deployment needs.

Monty and Jim have made significant progress on a continuous
deployment builder[1] in Jenkins that deploys OpenStack to a cluster
of machines. Currently, when finished deploying successfully the job
fires a simple script that executes the devstack exercise.sh script.

We have set a goal that by the end of this week, we want another
Jenkins builder that fires the openstack-integration-tests project
against the deployed cluster for a set of basic functional integration
tests.

Please do check out the documentation Monty and Jim have put together
on integration testing.[2]

2) Integration Test Suite

Gabe Westmaas and Daryl Walleck have made excellent progress on the
openstack-integration-tests [3] project's main integration test suite.
This main suite is known by the temporary name "storm" and is entirely
contained in the storm/ directory in the project source tree.

Gabe is putting together a list of top-priority missing test cases --
by adding bugs to the openstack-qa project on Launchpad. These bugs
will then be assigned to members of the QA team and targeted to
milestones similar to the way core OpenStack projects track things.

3) Learning How to Add Additional Functional Integration Tests

Daryl Walleck and I will be putting documentation together this week
-- to be posted on http://qa.openstack.org -- that has detailed
instructions on how the main "storm" integration test suite works, how
to add additional functional integration tests to it, and how to
contribute to the QA effort in general.

4) HP QA Cluster

Ravi and Nayna from HP are working with their engineers to bring a
4-node cluster of machines online. This cluster of machines will then
have a Jenkins slave installed on it and we will begin taking lessons
learned from the devstack deployment builder and applying those
lessons to building a chef-based deployment builder that will deploy
OpenStack via chef into the 4-node cluster and execute the same set of
integration tests against that cluster.

Feel free to provide feedback to the QA team by responding to this
email. We're happy to chat about our plans.

Cheers!
-jay

[1] https://jenkins.openstack.org/view/Gate/job/dev-gate-integration-tests-devstack-vm/
[2] http://ci.openstack.org/jenkins.html#integration-testing
[3] http://github.com/openstack/openstack-integration-tests