Pavlo Shchelokovskyy wrote:
[...]
We do better bump the requirements. The only projects I know of using
ceilometerclient are Heat, Horizon and Ceilometer itself.
No packager reported pain, so exception is granted and I approved the patch.
--
Thierry Carrez (ttx)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/2015 01:58 PM, Eoghan Glynn wrote:
Pavlo Shchelokovskyy wrote:
unfortunately, in Heat we do not have yet integration tests for
all the Heat resources (creating them in real OpenStack), and
Ceilometer alarms are in those not covered. In
Pavlo Shchelokovskyy wrote:
unfortunately, in Heat we do not have yet integration tests for all the
Heat resources (creating them in real OpenStack), and Ceilometer alarms
are in those not covered. In unit tests the real client is of course
mocked out. When we stumbled on this issue during
Pavlo Shchelokovskyy wrote:
unfortunately, in Heat we do not have yet integration tests for all the
Heat resources (creating them in real OpenStack), and Ceilometer alarms
are in those not covered. In unit tests the real client is of course
mocked out. When we stumbled on this issue
Hi all,
my previous update was a bit too hasty indeed - the problem is still there.
Steps I took:
in two empty virtualenvs I installed cilometerclient 1.0.12 and 1.0.13 and
compared pip freeze outputs - everything is the same except the
ceilometerclient itself.
Then I re-installed my DevStack
