Hi all,
we have a problem with dependencies for the kilo-rc1 release of Heat - see
bug [1]. Root cause is ceilometerclient was not updated for a long time and
just got an update recently. We are sure that Heat in Kilo would not work
with ceilometerclient =1.0.12 (users would not be able to create
Hi all,
we have a problem with dependencies for the kilo-rc1 release of Heat - see
bug [1]. Root cause is ceilometerclient was not updated for a long time and
just got an update recently. We are sure that Heat in Kilo would not work
with ceilometerclient =1.0.12 (users would not be able
Hi Guys.
A couple of concerns:
#1 - would have been really nice if the commit message for the review
included the above block of text. The current commit message is not
clear that Heat *can not* work.
I will update commit message regarding info mentioned in this thread.
#2 - why
On 04/02/2015 05:42 AM, Eoghan Glynn wrote:
Hi all,
we have a problem with dependencies for the kilo-rc1 release of Heat - see
bug [1]. Root cause is ceilometerclient was not updated for a long time and
just got an update recently. We are sure that Heat in Kilo would not work
with
Sean,
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 normal Heat usage, we
Hi all,
a (may be hasty) update.
I just tried using a quite fresh devstack master that somehow still
(PIP_UPGRADE=False?) has ceilometerclient as 1.0.12,
and ceilometer alarms do work as expected, template is [1]. May be the
actual bug/backward incompatibility was somewhere in oslo-incubator and
