Puppet Forge release 2.1.0

Updated README.md release notes.
Updated Modulefile for 2.1.0 release.

Change-Id: Idf026a2427665fdbcdc6145b3d0aa9d937326ba8
Fix some puppet lint errors.

Puppet-lint likes when the ensure's come first

Change-Id: I11b89215bb8e6d3d7c4c8fa7fe0f585efb8189ee
Disable 80chars/class_parameter_defaults checks

* Disable warnings for "line has more than 80 characters"
* Disable warnings for "parameterised class parameter without a default value"

We do not wish to track warnings for such violations.

Change-Id: I9884e2bd721d4f3e90e02a8a6fdc51219efcd819
corrected the postgresql link in .fixtures.yml

Change-Id: I0ca1df21ad25b2b5bf38317376ea58f33e641719
Clean all warnings for puppet-lint gate

Change-Id: Icd3c3098802cb075537b0d8cfb599a3b44684252
Adds Support for Managing the Token Driver Backend

Previously the keystone class did not manage the token driver.
High-Availability deployments of Keystone must use the SQL
driver so that all Keystone instances can access the same token
from a SQL database cluster.

The patch adds the token_driver parameter that is used to manage
the selection of the token driver backend in keystone.conf.
The parameter defaults to 'keystone.token.backends.kvs.Token' for
backwards compatibility and to use the KVS backend driver.

Change-Id: I4879052b7e44272c176814d048f916cb77d33581
Add syslog support to the keystone module

Change-Id: I64a1959b88f1a5d7a8ce96bd1a0dbab2e9723a00
Fail puppet-lint on warnings

Puppet-lint will now fail if there is any warnings.

Disable 'class_inherits_from_params_class' check.

Change-Id: Ia1d7fa5109178f040b00abcdb3f7d84c4bdf58b4
Merge "Fail puppet-lint on warnings"
Merge "Add syslog support to the keystone module"
Disable 80chars/class_parameter_defaults checks

* Disable warnings for "line has more than 80 characters"
* Disable warnings for "parameterised class parameter without a default value"

We do not wish to track warnings for such violations.

Change-Id: I9884e2bd721d4f3e90e02a8a6fdc51219efcd819
(cherry picked from commit 272c6063ac395a17abdf9902989bf66b49d6967c)
Adds Support for Managing the Token Driver Backend

Previously the keystone class did not manage the token driver.
High-Availability deployments of Keystone must use the SQL
driver so that all Keystone instances can access the same token
from a SQL database cluster.

The patch adds the token_driver parameter that is used to manage
the selection of the token driver backend in keystone.conf.
The parameter defaults to 'keystone.token.backends.kvs.Token' for
backwards compatibility and to use the KVS backend driver.

Change-Id: I4879052b7e44272c176814d048f916cb77d33581