Fixed gate by Updating Gemfile to pin Rake to 10.1.1

The latest Rake update requires Ruby >= 1.9. Bundler in the
current gate uses 1.8.x. This update fixes the gate by pinning
Rake to the last known working version.

Change-Id: I73879680b434d62faa3ecb5cc71735dc05bab508
Release 3.1.0

Updated Modulefile and README.md for release 3.1.0

Change-Id: I48539da7148b79676ecb07e7428f921c0135e875
Use correct variable for host_access dependency

The keystone::db::mysql resource declares resources using
`$real_allowed_hosts` which is a copy of `$allowed_hosts` minus `$host`.
But then it declares dependencies using `$allowed_hosts` which includes
`$host` and will fail catalog compilation due to a missing dependency

This bug only affects users if the value of `$host` is included in the
array of `$allowed_hosts`

Change-Id: Ifdd8793bcf36178efd1a083ee35649d56dc3d768
(cherry picked from commit 7813820abd30e77c6119e11d390237c1e6978086)
Release 3.1.1

Bug fix release.

Change-Id: I83d8b3b7fa9acd235082d3a4a5309f12a83b5ebb
ensure log_file is absent when using syslog

When using syslog, we don't need to write in keystone.log file, so
log_file param should be absent to avoid any write in the file.

Example: run keystone-manage db_sync will write in ~/keystone.log
instead of /var/log/syslog.

Closes-bug #1292619
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Change-Id: I9b2613294625f3df27a70f45bd964688a425c88e
(cherry picked from commit 2f4c960a4b6970f3ba4bdf8949ae09f48884b327)
Add ability to configure any catalog driver

Add a catalog_driver parameter which can be used to bypass
the catalog_type parameter and offer finer control over
the catalog driver configuration in Keystone.

Conflicts:
  manifests/init.pp

Closes-bug: #1301592
Change-Id: If062c855c875cf06e192593181898ba0a185a91a
(cherry picked from commit cc0150532c5bc5e6498609132cc97ced3d20985b)
Release 3.2.0

Bugfix and new feature release.

Change-Id: I12dc5fbaaf0d705568449a6297205c47c694d0d5
Ensure that mysql users are created before keystone-manage db_sync.

Otherwise keystone-manage might not have rights to populate keystone DDL.
Fixes puppet re-runs on controller node. Tenant transition is not supported by puppet and will 'fail', workarounded to 'warn' and thus continues. Reason: With a keystone backend to ldap, a user's tenant id is not reported by keystone user-get (and it is a hack in sql, see extra column json blob in user SQL table); thus, transitions would happen all the time (even if they are in that tenant already).
Merge branch 'havana' of https://github.com/gwdg/puppetlabs-keystone into havana