AW: [gnocchi][telemetry][ceilometer][cloudkitty] Gnocchi unmaintained
aaronzhu1121 at gmail.com
Tue Nov 19 10:56:24 UTC 2019
I am sorry to the telemetry project happened before, but now current
telemetry core team had decided to add ceilometer api and mongodb support
and cpu_utils support back. Gnoochi will still support as the backed. All
the mentioned database (influxdb, ES....), we would happy everyone to
submit patches to support as the database backed in ceilometer.
I created a storyboard to track ceilometer Ussuri release todo things in
. Free free to add things you want to do in Ussuri release.
Due to I will have a vacation this week, I can't hold this week's meeting,
we can discuss more in the next irc meeting at 5 Dec 2:00 UTC.
Luka Peschke <luka.peschke at objectif-libre.com>于2019年11月19日 周二18:24写道：
> My two cents from my experience on cloudkitty: We had to implement
> several storage drivers, and faced more or less the same issues as the
> telemetry team did before us. We had a gnocchi driver at some point,
> which worked pretty well, but ended up being very hacky because gnocchi
> lacked flexibility for non-openstack metrics (ie. data models which
> aren't resource-based).
> We ended up implementing a driver for InfluxDB which has relatively
> good perfs. But given that the open-source version of InfluxDB does not
> support HA/clustering, we also implemented an experimental Elasticsearch
> driver (which requires ES>=6.5).
> The recent ES releases have really improved the support for timeseries,
> and it is the storage backend for elastic beats.
> Given that many openstack deployments already have an Elasticsearch
> deployment for logs, and the large adoption of ES, it'd be my choice for
> a new Ceilometer storage driver.
> However, Gnocchi is pretty stable in 4.3, and well integrated with
> Ceilometer. Wouldn't it be less effort to keep it functional for now (ie
> only bug/security fixes, no new features), instead of re-integrating
> deleted features to ceilometer ?
> Luka Peschke (peschk_l)
> Le 2019-11-19 10:51, Tobias Urdin a écrit :
> > It sure is, we as well abandoned the MongoDB backend for Gnocchi
> > which works pretty well.
> > Would be a shame if a migration back would be required, maybe we can
> > get a discussion going on a more
> > long-term solution as was discussed when talking about the future of
> > Ceilometer.
> > Supporting Gnocchi or moving to another open source project as a
> > storage backend that is stable and maintained.
> > There were (and still is? Though unofficial out-of-tree) storage
> > backends for Ceilometer that publishes to InfluxDB.
> > I were never able to follow-up on the meetings (I probably missed a
> > lot of it) regarding the Ceilometer roadmap .
> >  https://etherpad.openstack.org/p/telemetry-train-roadmap
> > On 11/19/19 10:29 AM, Blom, Merlin, NMU-OI wrote:
> >> Thanks for your work on ceilometer!
> >> The gnocchi situation is realy sad.
> >> We implemented solutions on Gnocchi and ceilometer.
> >> In my opinion you abandoned the mongodb support for performance
> >> reasons and now you are going back to it?
> >> Has mongodb made any significant performance improvements for time
> >> series data?
> >> Best regards,
> >> Merlin
> >> VON: Lingxian Kong <anlin.kong at gmail.com>
> >> GESENDET: Dienstag, 19. November 2019 10:03
> >> AN: Radosław Piliszek <radoslaw.piliszek at gmail.com>
> >> CC: openstack-discuss <openstack-discuss at lists.openstack.org>
> >> BETREFF: Re: [gnocchi][telemetry][ceilometer][cloudkitty] Gnocchi
> >> unmaintained
> >> We (ceilometer team) will probably add Ceilometer API and mongodb
> >> support back, considering the current Gnocchi project situation.
> >> However, Gnocchi will still be supported as a publisher in Ceilometer.
> >> -
> >> Best regards,
> >> Lingxian Kong
> >> Catalyst Cloud
> >> On Tue, Nov 19, 2019 at 9:54 PM Radosław Piliszek
> >> <radoslaw.piliszek at gmail.com> wrote:
> >>> Hello Folks,
> >>> It looks like gnocchi is "officially" marked as unmaintained:
> >>> https://github.com/gnocchixyz/gnocchi/issues/1049 
> >>> Has there been any discussion regarding how it affects OpenStack
> >>> projects? And/or are there any plans to amend this situation?
> >>> -yoctozepto
> > Links:
> > ------
> > 
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss