Merge pull request #96 from puppetlabs/master

working folsom code
Merge pull request #98 from bodepd/1_release

Release 1.0.0
Ensure that mysql users are created before keystone-manage db_sync.

Otherwise keystone-manage might not have rights to populate keystone DDL.
Merge pull request #102 from Mirantis/allowed-hosts-before-db-sync

Ensure that mysql users are created before keystone-manage db_sync.
release 1.1.0
Merge pull request #125 from bodepd/1_1_0

release 1.1.0
Merge remote-tracking branch 'origin/folsom'
Merge pull request #127 from bodepd/merge_folsom_changes

Merge folsom changes
update 1.1.1 release
Merge pull request #129 from bodepd/1_1_1

update 1.1.1 release
Removed quotes in allowed_hosts as it was causing a failure when allowed_hosts is an array of hosts
Merge pull request #134 from jtopjian/jtopjian-allowed-hosts-fix

Removed quotes in allowed_hosts
Update test for a keystone server that isn't ready

Older versions of keystone client returned
Unable to communicate with identity service: [Errno 111] Connection refused. (HTTP 400)
this has changed to
[Errno 111] Connection refused
update keystone ready test for grizzly

The keystone server is not guarenteed to be ready when
its service start exits. It is possible that puppet can
attempt to make calls against keystone before it is ready.

The message returned when keystone is not ready has changed
between folsom and grizzly. This commit updates the internal
retry code to ensure that the keystone types will sleep and
rety as expected on both grizzly and folsom.

It also adds a retry method to help clean up the internal
state for testing.

This is an adaptation of a patch submitted by Derek Higgins
(and Nick Lewis helped with the tests a bit)
Merge pull request #135 from bodepd/keystone_not_ready_grizzly

Keystone not ready grizzly
Add keystone code to capture and ignore warning

When upgrading to grizzly, I found many errors
in the keystone command line output.The provider
was unfortunately not robust enough to still
parse STDOUT when these error appeared.

This commit wraps all keystone CLI invocations
in something that filters out warnings.

This patch is intended to resolve the issue in a way
that still maintains backards compatibility with folsom.
explicitly set token_format

the default setting for token_format in grizzly
changes from UUID to PKI.

This adds explicit configuration to ensure that
it is set as UUID to ease the process of upgrades
and allow the same puppet code to work with both
versions.
Ensure _member_ role is present
Merge pull request #139 from jtopjian/jtopjian-grizzly-keystone-member

Ensure _member_ role is present
Merge pull request #137 from bodepd/grizly_strip_keystone_warnings

Add keystone code to capture and ignore warning