Even in case of DEBUG level logging credentials (especially those that
give admin level access) should not be saved into log files.

This way of handling it has the side effect that if someone uses
password "password", it will be replaced in another place too... but
password "password" or some other keyword that can be found in the
request itself was a pretty bad idea to begin with.

Shell utilities are not affected and the verbose mode will still
display the passwords to make debugging easy.

Implements: blueprint limit-credentials-logging
Change-Id: I50d0ebbfbd44c7a5b162d9334b4fdbda67e5c28d

Change-Id: Ie7faeb604e0813401e5d1816a8f7c6791a16b001
Implements: blueprint fwaas-client-cli

implements blueprint service-types-cli

Add command service-provider-list - lists service providers available
in neutron configuration

Change-Id: I2ea25abc6d54b93fd9d11e8c494d7e3f77f25c53

Due to the mox object being created twice, anything that was mocked
by the original instance only will never be unset. Remove the repeated
self.mox creation to allow new tests to run properly.

Change-Id: Icf644178f5a8270f913997e7e3f10dade412b321

blueprint lbaas-agent-scheduler

Change-Id: Iba1682b122d5ae411f67ab535aecbfc4696aa925

 - add --os-cacert option which allows to set a file containing
   certificates of root CAs (certificate authorities) that are
   required for validation of HTTPS servers SSL certificates

 - wrap httplib2 SSL certificates validation errors with a
   custom quantumclient exception

Blueprint: quantum-client-ssl

Change-Id: I4e6a7d177ba14314ba9bed613ec2684bffc35222