Hi Giuseppe
On Wed, 21 Feb 2018 at 11:15 Giuseppe Attardi
wrote:
> The latest Ceilometer non longer uses a DB to store its data, but rather
> it sends it in a pipeline to Gnocchi.
> In order to use Ceilometer with Gnocchi, I had to patch the ceilometer
> bundle not to wait for
The latest Ceilometer non longer uses a DB to store its data, but rather it
sends it in a pipeline to Gnocchi.
In order to use Ceilometer with Gnocchi, I had to patch the ceilometer bundle
not to wait for a shared-db relation.
In fact, I removed completely any mention of the database in the code
Giuseppe,
The bug is still there
https://bugs.launchpad.net/charm-ceilometer/+bug/1717337
So if you have a missing database relation, this is expected until there
will be a workaround in-place.
ceilometer-ba1-cl2/5* blocked idle 5/lxd/25 90.147.161.27 8777/tcp
Missing relations
This is what I have:
$ juju status ceilometer-ba1-cl2|head -40
Model ControllerCloud/Region Version SLA
cloudbase garr-maas-ctrl-2 garrMAAS/Bari 2.2.3unsupported
App Version Status Scale Charm Store Rev OS
Notes
ceilometer-ba1-cl2
Giuseppe,
Just in case:
juju status
ModelController Cloud/Region Version SLA
default localhost-localhost localhost/localhost 2.2.4unsupported
App Version Status Scale CharmStore
Rev OS Notes
ceilometer 9.0.0
ba...@canonical.com>> wrote:
>>
>> Giuseppe,
>>
>> Unfortunately, it's this way now and it is a known problem. I made a
>> write-up in this bug
>> https://bugs.launchpad.net/charm-ceilometer/+bug/1717337
>> <https://bugs.launchpad.net/charm-cei
> On 14 set 2017, at 20:35, Dmitrii Shcherbakov
> wrote:
>
> Giuseppe,
>
> Unfortunately, it's this way now and it is a known problem. I made a write-up
> in this bug https://bugs.launchpad.net/charm-ceilometer/+bug/1717337
> <https://bugs.launchpad.n
Giuseppe,
Unfortunately, it's this way now and it is a known problem. I made a
write-up in this bug
https://bugs.launchpad.net/charm-ceilometer/+bug/1717337
In short: ceilometer-upgrade in the ceilometer package itself uses a
database (mongodb) connection url unconditionally and blocks if
I have upgraded ceilometer to release 17.08 for use with the new gnocchi charm.
ceilometer should no longer need a DB, but it still waits for the DB relation:
ceilometer-ba1-cl2/1*waiting idle5/lxd/0
90.147.161.27 8777/tcp
Hi Dmitrii
On Sun, 9 Jul 2017 at 12:10 Dmitrii Shcherbakov <
dmitrii.shcherba...@canonical.com> wrote:
Hi Giuseppe,
>
> First of all, thank you for looking into writing a gnocchi charm!
>
> There is already an ongoing effort from James Page on charming gnocchi:
> https://github.com/openstack-char
ys, patches are welcome :^)
Best Regards,
Dmitrii Shcherbakov
Field Software Engineer
IRC (freenode): Dmitrii-Sh
On Thu, Jul 6, 2017 at 6:46 PM, Giuseppe Attardi
wrote:
> The ceilometer service has gone through a major overhaul, where some of
> its parts have been removed and assigned to gno
The ceilometer service has gone through a major overhaul, where some of its
parts have been removed and assigned to gnocchi.
https://docs.openstack.org/ceilometer/latest/architecture.html
In particular the ceilometer api has been discontinued and the ceilometer
collector is superseded by
Hi Drew
On Wed, 8 Mar 2017 at 16:03 Drew Freiberger
wrote:
[...]
> Unfortunately, nothing in ceilometer is picking up the
>
oslo_message_notifications on the unit where cinder is running. I went
> to add the ceilometer-agent-charm to the unit, but found it's only
> written
Hello all,
I recently came across the need to add cinder's volume telemetry data
into a client's ceilometer environment.
I've found that there was a patch for charm-cinder that enables the
cron-tick for cinder-volume-usage-audit and implemented it in a
cherry-picked fashion
I originally opened a bug for not having a 5.0.3 version.
https://bugs.launchpad.net/charms/+source/ceilometer/+bug/1590257
<https://bugs.launchpad.net/charms/+source/ceilometer/+bug/1590257>
However it was recommended for me to use the proposed branch to test it out.
It doesn’t work
15 matches
Mail list logo
