enabled - is boolean not text
if we push True as "True" we fill face following error:
[error] StatementError: invalid literal for int() with base 10: 'True' (original cause: ValueError: invalid literal for int() with base 10: 'True') 'INSERT INTO project (id, name, domain_id, description, enabled, extra) VALUES (%s, %s, %s, %s, %s, %s)' [{'description': '', 'extra': {}, 'enabled': u'True', 'id': '7bd58f7ad7174a709e8f794e2e477059', 'domain_id': 'default', 'name': u'admin'}]
Merge pull request #69 from MirantisDellCrowbar/bug/enables/pebbles/master

keystone unable to register anything
Zap ignore_failure.
Merge pull request #71 from VictorLowther/pull-req-release-pebbles-master-a0c8ce902ba2ff2b08a2b4fcf2938992f2e17f34

https://github.com/crowbar/barclamp-keystone/pull/71

Merged by devtool for VictorLowther
Turn down default verbosity for the keystone barclamp.
Merge pull request #72 from VictorLowther/pull-req-release-pebbles-master-898b27a701f199b0536ae0303358a67f6f08c00f

Turn down default logging verbosity for glance, ipmi, swift, and keystone. [4/4] - looks good - WA
Use correct user on SUSE
Set correct package/service names for SUSE

Conflicts:
	chef/cookbooks/keystone/recipes/server.rb
set secure permissions (bnc#771101)
Set default attributes for verbose/debug to false

This is already the case in the json file, just do it for consistency.
Remove user from bc-template-keystone

We do not want to allow end users to change this; the only reason to
have this variable is for cross-distro support.
Do not run "keystone-manage pki_setup" on SUSE

This is done by the package.
Port to database barclamp

A good part of this was made by Ralf Haferkamp <rhafer@suse.de>
Disallow SQLite setup
Don't create a proposal when no "database" proposal exists (bnc#773803)
Merge pull request #73 from vuntz/suse-port-database

Forward-port patches from SUSE, including move to database barclamp
Change display name to Keystone

This is consistent with the other barclamps.
enforcing single proposal for keystone
Make keystone test a little more verbose.
Rename signing to token_format

This is much more explicit.