update openstack-common dependency to 0.3.x

Change-Id: Ieed3bc5194f2634a63596fcab9f2ea9a4c72f8b0
add network service_type to the register LWRP

Change-Id: I6f892654a05c3a84c5b8ada6291c2088dd0398ff
Remove Unicode characters from README.md

Unfortunately for dear ole' Ionut, Berkshelf cannot handle
uploading cookbooks with files that contain Unicode characters.
When uploading, you get the following error:

Change-Id: Id3341e1e24cf7ca468cc94cabf8920f96689e08c
STDERR: ERROR: Encoding::InvalidByteSequenceError: "\xC8" on US-ASCII
Removed the db recipe

The db recipe have been removed. It is up to the operator to
setup the database, users, and grants before deploying openstack.
It has been moved to the `openstack-db` recipe in the
`openstack-ops-database` wrapper cookbook.  Needed to converge
in the register tests, so Chef loads the provider and creates
the classes.  The db spec was previously doing that, which allowed
tests to pass.

Change-Id: I301b7fc625790960efd99d08395b91204ae18107
Removed the use of non-standard ohai plugin

We now have a helper method `#address_for` to return the
IP of a given interface. Switched out the ohai use
in favor of `#address_for`.  Also, updated berkshelf
to 2.x which handles dep resolution correctly.  I run
into problems getting berkshelf to lock to the new 0.3.0
openstack-common w/o updating berkshelf.

Change-Id: If5988dc5290ed8d5faa3950c1995f9943d9efe65
Ability to ignore db migrations

There are cases where migrations should not be executed. For example when
upgrading a zone, and the identity database is replicated across many zones.
Having the ability to toggle migration execution is useful (and a use-case
we have :))

Change-Id: I9d820e853d8afa13a55dbd49e5335d34246d97ba
Merge "Ability to ignore db migrations"
Merge "Removed the db recipe"
Added SDN neutron network endpoints

The network endpoints were missing from the catalog.

Change-Id: I2b631f8cf812e973c61231d570810e0182a205db
update to use openstack-common 0.4.0

Change-Id: Ieab0847afb074af686002a5d11a5a4694a224d16
Correct URIs in version information returned at /

The root / endpoint for Keystone returns a JSON dict
of information about the versions supported by Keystone.
This dict of information contained bad URIs, which I suspect
is preventing the v3 API from being navigated through by clients
who parse this version dictionary.

The public_endpoint and admin_endpoint configuration options
need a URI without any version path in it.

Change-Id: Ib8bf1d1f95bd86afa2a327e1cff011de8d3039f4
remove outdated comment

upstream bug was fixed long before the grizzly release

Change-Id: I23e8bbfc4f53a658717279ea2cb9add83e3db11e
make LDAP attributes configurable

Change-Id: I91b9da4cf0305e6b30e82e260533d48843332cf1
remove unused keystone_plugin.py file

Change-Id: I5aa27be1489e6def11da0a511a24a880252c6f4d
Merge "make LDAP attributes configurable"
make default blank passwords more uniform

Change-Id: Iaae27da119abf2746b94d696741d16c63c9e74ef
add (some) registration tests

Change-Id: I70a399751c51ce424481476e45c5c6411d9fada8
calculate the tenants to be registered programmatically

The tenants are now derived from the users hash. Previously the tenants
list had to be provided independently which could cause user errors.

This should also make it easier for wrapper cookbooks which don't have
to calculate the tenants themselves from the users list.

Change-Id: If3ad9840f5b224fa2938a6288df929385335ea38
derive the roles from the users hash instead of duplicating data

Change-Id: I7b4d0b2fa7722d6563b4074a45d905a093ee38db
hide .cookbooks directory

Change-Id: I832939400127519774edb1d385fcd782af17d83a