Thursday, 2020-07-30

*** psachin has joined #openstack-telemetry03:36
*** takamatsu has quit IRC04:38
*** takamatsu has joined #openstack-telemetry04:38
*** e0ne has joined #openstack-telemetry06:40
*** bengates has joined #openstack-telemetry07:07
*** e0ne has quit IRC07:31
*** rcernin has quit IRC07:32
*** rcernin has joined #openstack-telemetry08:28
*** rcernin has quit IRC08:34
*** witek_ has joined #openstack-telemetry08:39
*** e0ne has joined #openstack-telemetry09:30
*** rcernin has joined #openstack-telemetry10:37
*** rcernin has quit IRC10:54
*** e0ne has quit IRC11:20
*** _erlon_ has joined #openstack-telemetry11:30
*** tkajinam has quit IRC12:47
*** e0ne has joined #openstack-telemetry12:59
*** psachin has quit IRC14:12
*** rcernin has joined #openstack-telemetry15:46
*** rcernin has quit IRC15:51
*** bengates has quit IRC16:04
*** witek_ has quit IRC16:24
*** tow has quit IRC16:36
*** e0ne has quit IRC17:26
*** e0ne has joined #openstack-telemetry19:48
gansomrunge: hi! Is there any page I can check the current status of the project? THe wiki at the channel topic is a bit outdated (last meeting took place in 2019 from what I could find), the most up-to-date info I was able to find was this etherpad https://etherpad.opendev.org/p/telemetry-train-roadmap20:14
*** e0ne has quit IRC20:39
mrungeganso, hi, what do you want to know?20:51
mrungemaybe it's easier that way?20:51
mrungeat the moment, I am not aware of a status overview. maybe lxkong or dtruong have it. Usually, a status update is given at summits, the last happened last year20:53
gansomrunge: are there meetings that I can participate to be involved with the direction of telemetry? I see that some key points were raised about adding back Ceilometer API, MongoDB, switch to Monasca, etc, where could I follow those decisions and also contribute to what is being or has been decided? In Gerrit I don't see storyboard links or Launchpad links on the changes, in Storyboard I don't see any Victoria set of tasks that I could follow or20:54
gansopick up to work (as the general direction seems unclear at the moment, as the info there is stale)20:54
gansomrunge: yup, the last status I found is from december on the mailing list. But development tracking seems to end there20:55
mrungeI have no insight into company policies or companies joining or leaving.20:55
mrungeyou are speaking of ceilometer?20:56
mrungeor also gnocchi?20:56
mrungeclients?20:56
mrungeaodh?20:56
mrungepanko?20:56
gansotelemetry in general. I don'20:57
mrungesince we are getting near to next release, I would suggest to test it and to file bugs20:57
gansoI was using gnocchi, but I see it is unmaintained, so I tracked down ceilometer and that ^ is what I found20:57
mrungehonestly, that'd be a great help20:57
gansoyup, but it is unclear to me how I can get involved as all source of info seems stale and there are no meetings or active bug trackers to keep track of the work or the direction the team is taking20:59
gansosince I was using gnocchi, I was initially looking for info on how to replace it. So I found Ceilometer API and MongoDB are on the roadmap, even though a lot of people diverge on this (from the mailing list)21:00
mrungeI agree, it would be a good idea to get together and come up with a plan for next development cycle21:00
mrungeright21:00
mrungeit is still to discuss how to proceed with ceilometer api, mongodb etc.21:02
mrungepersonally (not speaking for the project), I see ceilometer as a collecting agent21:02
mrungeI'd use something else for a time-series database (such as gnocchi)21:03
mrungeetc.21:03
mrungethere is still work to do on how to do autoscaling, if you want to get rid of gnocchi21:03
mrungeor step forward and support gnocchi21:04
gansomrunge: so it is up to the deployers to come up with something to consume the data ceilometer collects. What you are saying is that storing/handling the data collected is not part of the OpenStack telemetry scope?21:04
mrungeopenstack telemetry consists of several losely coupled projects21:05
mrungeand you can pick the components you like to use21:05
mrungethat is a nice way to put it21:05
mrungelooking at the "support" status, that's a different story21:06
gansoright, I'd choose the pieces that are supported and maintained though, but figuring that out has been a challenge of its own, as it seems the only piece that is consistently supported is the data collection through ceilometer21:07
mrungeyes, that's true21:08
gansoI still need to explore how integration with cloudkitty, prometheus and monasca would work. Those have been suggested by a mailing list21:08
mrungeokay, what do you want to achieve?21:09
mrungeor what do you want to collect for what reason?21:09
mrungedepending on your needs, you may be fine with just ceilometer in it's original (and now restored) state21:11
mrungeceilometer had its own database to store metrics and events. that was split out to own components gnocchi and panko for speed reasons and also because they were easier to handle that way21:12
mrungein the past more active cycle, it was decided to bring that back21:12
mrungeganso, for large deployments or fast sample rates, I'd move as much as possible from the monitored infrastructure21:15
mrungethere is e.g STF, https://infrawatch.github.io/documentation/21:15
openstackgerritGhanshyam Mann proposed openstack/telemetry-tempest-plugin master: [goal] Migrate telemetry-tempest-plugin jobs to focal  https://review.opendev.org/74405921:21
*** e0ne has joined #openstack-telemetry22:03
*** tkajinam has joined #openstack-telemetry22:05
*** e0ne has quit IRC22:25
*** e0ne has joined #openstack-telemetry22:27
*** e0ne has quit IRC22:28
*** rcernin has joined #openstack-telemetry23:13
*** rcernin has quit IRC23:14
*** rcernin has joined #openstack-telemetry23:14

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!