Add python-virtualenv to the python dependencies

Sometimes it would be advantageous to run python services/scripts
inside of a virtualenv so that we do not pollute the standard
python sysem library paths.
Adding barbican/python-barbicanclient support

This change creates a new barbican role. As Barbican is still in
Stackforge, this change configures it to run from within its own
virtualenv. The service runs under uwsgi which is also part of the
specified virtualenv. Haproxy fronts this service as it would with
any other OpenStack service that we have.  The port has been moved
from 9311 to 9322 accordingly.

In addition to configuring Barbican, this change also installs
python-barbicanclient. We specifically pull directly from github due
to the fact that we have recently pushed changes upstream. These are
not yet in any of the Pypi repositories yet. Regardless, this is how
we manage the other python-*clients, so it will likely stay this way.
This client is installed into the system's python path - no
virtualenv wrangling required.
Moving configuration to proper section

enabled_crypto_plugins belongs under the configuration group "crypto"
not "DEFAULT"
Add python-virtualenv to the python dependencies

Sometimes it would be advantageous to run python services/scripts
inside of a virtualenv so that we do not pollute the standard
python sysem library paths.
Adding barbican/python-barbicanclient support

This change creates a new barbican role. As Barbican is still in
Stackforge, this change configures it to run from within its own
virtualenv. The service runs under uwsgi which is also part of the
specified virtualenv. Haproxy fronts this service as it would with
any other OpenStack service that we have.  The port has been moved
from 9311 to 9322 accordingly.

In addition to configuring Barbican, this change also installs
python-barbicanclient. We specifically pull directly from github due
to the fact that we have recently pushed changes upstream. These are
not yet in any of the Pypi repositories yet. Regardless, this is how
we manage the other python-*clients, so it will likely stay this way.
This client is installed into the system's python path - no
virtualenv wrangling required.
Moving configuration to proper section

enabled_crypto_plugins belongs under the configuration group "crypto"
not "DEFAULT"
Adding barbican support for additional modules

Barbican uses stevedore in order to provide a simple mechanism for
crypto plugins.  Therefore provide an ansible task to pull python
modules from some external source - whether it be a URL or pyi
itself.
Merge branch 'barbican' of github.com:craigtracey/ursula into barbican

Conflicts:
	roles/barbican/defaults/main.yml
	roles/barbican/handlers/main.yml
	roles/barbican/tasks/main.yml
Updating barbican-api & barbican-api-paste config

Based upon some feedback received from John, I have updated both of
these config files to reflect our ursula environment. Similarly, as
it is no longer necessary to fork barbican, move back to using
stackforge git_mirror.
Merge pull request #152 from craigtracey/barbican

Support for Barbican and python-barbicanclient