Direct `from novaclient.v2 import client` became source of problems
since the introduction of microversions in Nova. According to
novaclient docs, `from novaclient import client` (with the following
specification of version 2 in Client constructor) is a proper way of
using it. It should safeguard Horizon against the backward
incompatibility issues, such as in bug 1493205.
Reviewed: https:/ /review. openstack. org/221711 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=27ceba6035c 22b7f11e529ddbc 287f27568bb8e8
Committed: https:/
Submitter: Jenkins
Branch: master
commit 27ceba6035c22b7 f11e529ddbc287f 27568bb8e8
Author: Timur Sufiev <email address hidden>
Date: Wed Sep 9 14:27:34 2015 +0300
Fix usage of python-novaclient in Horizon
Direct `from novaclient.v2 import client` became source of problems
since the introduction of microversions in Nova. According to
novaclient docs, `from novaclient import client` (with the following
specification of version 2 in Client constructor) is a proper way of
using it. It should safeguard Horizon against the backward
incompatibility issues, such as in bug 1493205.
Change-Id: Ifedd47e8ad6a7a ac52549f6e1742d d73fed48da1
Closes-Bug: #1493576
Closes-Bug: #1493205