Adam Harwell 2228ef86ab Refactor BarbicanAuth to allow for configurable auth method ... There is now a new configuration option "barbican_auth" in the certificates section, to specify which auth plugin to use when communicating with Barbican. This is because the default option (using ACLs inside Barbican to control access) should be ok as a default workflow, but it might be required to use other methods depending on your deployment. For example, another possible auth method would be BarbicanTrustAuth, utilizing Keystone Trusts. While we're in this file, prune the unused (and really bad) method that would *actually* delete certs from Barbican (not in our scope). This is (nearly) a direct port of the work done in: https://review.openstack.org/#/c/216140/ Change-Id: Id8386c36c7acfd954bc2309947345dfe31124b16		2016-01-18 17:41:34 -06:00
..
__init__.py	VMWare NSXv LBaaSv2 driver	2016-01-15 20:45:39 +00:00
edge_driver_v2.py	Refactor BarbicanAuth to allow for configurable auth method	2016-01-18 17:41:34 -06:00