
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. Change-Id: Ibb399a0b5b96aa808b0bbb7a5a82dd4d8a948063