Evaluate Integration testing options for StackForge

For the Havana release we need to establish a base level of integration gating tests for the cookbooks. OpenStack-Infra has resources available for performing functional and integration tsts, we need to find what those are and how we can use them. Ideally we will be able to add Test Kitchen and/or Vagrant support to each cookbook for spinning up VMs to at least test single-node deployments of the recipes. If multi-node testing is available, that would be a worth pursuing eventually.

Start here and follow up with questions in #openstack-infra without bugging them too much.
  http://ci.openstack.org/project.html

Goals:
* Functional testing of each component cookbook upon change request of a component cookbook
* Functional testing of entire stack (All-In-One) upon change request of a component cookbook or top-level repo
* Functional testing of a multi-node deployment upon change request of a component cookbook or top-level repo

-- 07/17/2014 --
Looking to kill this blueprint and re-open a discussion about how to implement integration testing. (j^2, markvan, galstrom)