The CloudKitty dashboard now inherits the interface type from Horizon.
This allows for easier testing, like in an all-in-one to use the
(cherry picked from commit 19ead1f072)
Until now, the region_name was not specified when instanciating
cloudkittyclient from the horizon dashboard. This caused the
client to use systematically use the default region. That
behavior was problematic in multi-region setups, as only the
cloudkitty API of the default region could be reached.
This adds support for the both options mentionned in the title. The ca
certificate was wrongfully passed to keystoneauth through the 'cert' parameter,
which is meant for the client certificate.