Adds Vagabond integration testing and setup

* Adds instructions for using Vagabond to test the
Chef repository.
* Add a new testing environment file that is specific
to Vagabond
* An ops, compute controller and compute worker node
added to the vagabond environment

Change-Id: Id15201b9b870c51d337d8d07fca5e42ca8aaf385
Remove all non-existent db recipes from roles

Right now this example repository references recipes that are no
longer present. Database configuration and table creation is not
handled by these respositories and have, therefore, been removed.

Change-Id: Iaf40343bf871a603477bea4c61e7930ac40113a3
Merge "Adds Vagabond integration testing and setup"
update roles that call db recipe

They all should be pointing to the updated openstack-ops-database::openstack-db
recipe

Change-Id: I33f243db03ac5f408bb12de788c25832e4e373aa
add metering

Change-Id: I24cde88ffc55d3a3d7066c9c5857679e01050b6b
Cleanup and consolidation of the roles to cover all-in-one installation.

There were a number of unreferenced and required recipes that needed roles.
There were also several roles that were redundant or referred to recipes that
did not exist, so they were removed.

deleted: os-block-storage-worker.rb no recipe
deleted: os-identity-api-admin.rb redundant
deleted: os-identity-api.rb unnecessarily fine-grained
deleted: os-infra-caching.rb unused

new: os-block-storage-volume.rb Cinder volume service
new: os-compute-conductor.rb Nova conductor service
new: os-compute-setup.rb Nova setup and identity registration

Change-Id: Ibdbfd8929669caa2d0771eeaad9f79f727e14867
modified: Berksfile.lock
modified: infrastructure.yml all roles captured
modified: os-block-storage.rb roll-up role now refers to the roles
modified: os-compute-api.rb added base role
modified: os-compute-single-controller.rb added openstack-ops-database::openstack-db, os-compute-setup and os-compute-conductor
modified: os-dashboard.rb removed openstack-ops-database::openstack-db, doesn't belong here
modified: os-image-api.rb removed openstack-ops-database::openstack-db, doesn't belong here
modified: os-image-registry.rb removed openstack-ops-database::openstack-db, doesn't belong here
modified: os-network.rb refer to network::common per Johannes Becker's catch
modified: os-object-storage.rb refer to the os-object-storage roles
fixed to point to openstack-compute::nova-setup recipe

Change-Id: I54de3324224576a29e7e4663a023b1050ed7cb69
Initial Vagrant testing support, using the Chef provider with Chef Zero.

The Vagrant box is the default 12.04 and 13.04 provided by Opscode's Bento
project. It uses the Vagrant plugins vagrant-berkshelf, vagrant-cachier,
vagrant-chef-zero and vagrant-omnibus. Unfortunately Chef Zero does not
understand .rb files yet, so we're using the recipes directly in the run
list. This also means that searching by roles is broken so this needs to be
fixed ASAP.

Change-Id: I5fe8b175f15c4a21c16de46bc05ec6a0c27cfdaa
Fixes to Vagrant testing support.

* Hacked around the fact that chef-zero provisioner doesn't understand .rb files by
running multiple provisioners.

* Fixed call to nova:identity_registration in os-compute-setup.rb role

note: chef run errors with 'No such file or directory - /etc/init.d/quantum-server restart', but can still start a compute instance and access via network, not a showstopper.

Change-Id: I4f9a0d10afb341b43809412e6e79d04b82b15555
remove Vagabond (for now) and update gem dependencies to fix the gating

Change-Id: I2f46c463aecaff668a4c79bac92c6a5581cb2d59
Enable all of the services required for networking.

This will probably get refactored later into more roles.

Change-Id: I303edfc8db1237acf507b0d5fe886dc66e0baeee
update dependencies to latest, including fixed mysql

Change-Id: Iee0eea99f352d29bde7cf1f5f2c48e10da6c397c
vagrant-chef-zero now supports Ruby files

Change-Id: If52514d20b01c98874244a9c3f81ad35581e20ed
add each role for each network main component

In typical openstack configuration, there may be 3 types nodes:
controller node, network node, and compute node. From the network
point, it's always supposed that: the Quantum Server is on the
controller node; and the L2 agent, DHCP agent and L3 agent are on
the network node; the L2 agent are on the compute node. We need the
each role for each OpenStack network main component. This will make
the configuration more flexible. So I add them here.

Change-Id: Ida4826c6dfe770b58790d75561bea42e9584ca89
Closes-Bug: #1240509
Removing vagrant-cachier for interfering with debugging

Vagrant-cachier works very well at caching components but should probably not be
part of the default usage because we are frequently testing changes in packages
and cookbooks, the 2 things most likely to be cached and re-used.

Change-Id: I4458bf4806e574abc20e4fb6c3fc68409cd045a0
Removing cache config option

* fixes error (Unknown configuration section 'cache')

Change-Id: I507aee9f68666d9bf296671f965ac39b90754183
Adding forwarded_ports for Vagrantfile

 * forwarding dashboard-ssl
 * forwarding nova-api
 * Converted vagrant enviroment to ruby format

Change-Id: Ic406d93ea8ab8933ce9d5dc90bcd6410c847c9f4
Merge "add each role for each network main component"
Merge "Adding forwarded_ports for Vagrantfile"
open port 4000 for Chef-Zero access

Change-Id: Ica8b0aadf6f17039399317470392650ac176847c