Allow newer versions of pylint

The .pylintrc used for neutron refers to checks added in pylint 1.3.0,
and aborts on earlier versions (from a quick experiment).

This change moves from a strict pylint==0.25.2 pin to allow newer
versions, as a first step to moving to pylint>=1.3.0.

Change-Id: Ia293eb1329f2c1c2894ab7d8d2142951e670fbaf
Update redis library to >=2.10.0

Tooz is using this library and is depending on a version that
has exceptions added in 2.10.0 so in order to avoid conflicts
we should bump up the redis to be at least that version. This
avoids mishaps later with other users that could be depending
on versions <2.10.0

Change-Id: Ia8e58f8cb6a19d2a12846a6a8f0e2e313d48f9a0
Bump testtools version to support message parameter in assertIn

Commit aa67a51299faa5e51da2e96fcf3b0ba3fc2ddc86 introduced usage of the
`message` parameter to `assertIn`.

The current minimium version of `testtools` doesn't support it, so we need to
bump up to at least version 0.3.6.

Change-Id: I6985bd1daa373348f2f37e26fb5597ac3e46f316
Closes-Bug: 1387870
Disable python-barbicanclient 3.0.0 version

python-barbicanclient 3.0.0 has introduced cliff module, but pins it
to 1.6.1, while global-requirements set it to >=1.7.0, now the whole
OpenStack projects depends on higher version of cliff, but
python-barbicanclient is needed by cinder, then grenade test will
fail because: pkg_resources.DistributionNotFound: cliff==1.6.1

As long as python-barbicanclient maintainers don't provide a patch
for 3.0.0 (which seems not happen FMPOV), we need to disbable this
version.

Change-Id: Idd519fc3aa6e004aa75b56b36ffd125dde20f70e
Related-Bug: #1388414
Add barbican and python-barbicanclient to projects

These projects are part of the integrated gates, we need to test
them.

Related-Bug: #1388414

Change-Id: I8024086cedb1d70e0586d681d0cbda851107c6b9
Merge "Update redis library to >=2.10.0"
Merge "Add barbican and python-barbicanclient to projects"
Upgrade to avoid vulnerable requests-kerberos versions

All versions of requests-kerberos prior to 0.6 do not properly handle
mutual authentication. In short this means that the server was never
properly verified and a client could potentially send sensitive data to
an untrusted server.

Change-Id: I1e9a3b1af15e69ae5c155a146638774cf472ef33
Merge "Bump testtools version to support message parameter in assertIn"
Add cassandra-driver>=2.1.1 requirement

Apache 2 licensed; needed for Cassandra support in Ceilometer

> Is the library actively maintained?

This is the official DataStax library and they actively maintain it.
https://github.com/datastax/python-driver

> Is the library good code?

Yes.

> Is the library python 3 compatible?

Yes.

> Is the library license compatible?

Yes: Apache2

> Is the library already packaged in the distros we target (Ubuntu latest /
> Fedora latest)?

Packaged by DataStax, and in PyPi.  Not yet in Ubuntu / Fedora.

However, this is only going to be an _optional_ requirement.  If users do not
enable the Cassandra backend for Ceilometer, they will not use it.  As such,
this is a weaker requirement for packaging OpenStack.

Indeed, it would likely be inappropriate to install the Cassandra driver as part
of a default OpenStack distro, as Cassandra is not a primary datastore for any
OpenStack project.

As such, I do not believe we are requiring the distros to package it.  They may
choose to do so for the convenience of their users, but that is their choice.

> Is the function of this library already covered by other libraries in
> global-requirements.txt?

No

Change-Id: I5803f93be601b875fdfb8276c04e7ecebab8d08e
Merge "Allow newer versions of pylint"
Merge "Add cassandra-driver>=2.1.1 requirement"