| *** chaconpiza has joined #openstack-monasca | 07:16 | |
| *** witek has joined #openstack-monasca | 07:53 | |
| *** dougsz has joined #openstack-monasca | 08:08 | |
| *** chaconpiza has quit IRC | 08:34 | |
| *** chaconpiza has joined #openstack-monasca | 08:38 | |
| *** chaconpiza has quit IRC | 08:49 | |
| openstackgerrit | Arseni Lipinski proposed openstack/monasca-persister master: Minor refactoring for utils.py https://review.opendev.org/652026 | 11:33 |
|---|---|---|
| openstackgerrit | Arseni Lipinski proposed openstack/monasca-persister master: Minor refactoring for utils.py https://review.opendev.org/652026 | 11:36 |
| *** bobh has joined #openstack-monasca | 11:57 | |
| *** bobh has quit IRC | 12:02 | |
| *** witek has quit IRC | 12:13 | |
| openstackgerrit | Dobroslaw Zybort proposed openstack/monasca-persister master: Add tests for cassandra/token_range_query_manager.py https://review.opendev.org/652653 | 12:16 |
| openstackgerrit | Dobroslaw Zybort proposed openstack/monasca-persister master: Add tests for cassandra/retry_policy.py https://review.opendev.org/652974 | 12:18 |
| openstackgerrit | Dobroslaw Zybort proposed openstack/monasca-persister master: Add tests for cassandra/alarm_state_history_repository.py https://review.opendev.org/653703 | 12:26 |
| openstackgerrit | Arseni Lipinski proposed openstack/monasca-persister master: Add tests for cassandra/token_range_query_manager.py https://review.opendev.org/652653 | 12:57 |
| *** witek has joined #openstack-monasca | 14:30 | |
| *** witek has left #openstack-monasca | 14:30 | |
| *** witek has joined #openstack-monasca | 14:30 | |
| joadavis | Reminder: team meeting at 1500 UTC, agenda at https://etherpad.openstack.org/p/monasca-team-meeting-agenda | 14:43 |
| openstackgerrit | Joseph Davis proposed openstack/monasca-agent master: WIP Enable unit tests for py36 https://review.opendev.org/657829 | 14:54 |
| *** halbbalda has quit IRC | 14:57 | |
| *** koji_n has joined #openstack-monasca | 15:00 | |
| witek | #startmeeting monasca | 15:00 |
| openstack | Meeting started Wed May 8 15:00:23 2019 UTC and is due to finish in 60 minutes. The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: monasca)" | 15:00 | |
| openstack | The meeting name has been set to 'monasca' | 15:00 |
| witek | hello everyone | 15:00 |
| koji_n | hi | 15:00 |
| witek | agenda for today: | 15:01 |
| witek | https://etherpad.openstack.org/p/monasca-team-meeting-agenda | 15:01 |
| dougsz | hello all - apologies for not making Saturday at PTG, the honest answer was that I totally forgot :( | 15:01 |
| joadavis | :) | 15:02 |
| witek | :) no worries, we covered most of the topics on Friday already | 15:02 |
| joadavis | good to know you are human | 15:02 |
| dougsz | :-D | 15:02 |
| witek | #topic Train tasks prioritization | 15:03 |
| *** openstack changes topic to "Train tasks prioritization (Meeting topic: monasca)" | 15:03 | |
| witek | I think the list should be complete now | 15:04 |
| witek | I've created new or linked to existing Stories | 15:04 |
| witek | there is also a link to meeting minutes, I haven't managed to write a summary yet | 15:04 |
| witek | please also let me know or just add to the list if something is missing or should be differently handled | 15:06 |
| witek | I would like to evaluate the results in one week | 15:07 |
| dougsz | ok, thanks witek | 15:07 |
| witek | any comments right now to list items? | 15:08 |
| witek | or anything related? | 15:08 |
| joadavis | its a good list | 15:09 |
| dougsz | Should merge APIs task be on there, I guess that should make Train? | 15:09 |
| witek | oh yes, forgot to comment on that one | 15:09 |
| dougsz | (just thinking about the log-query API which will come after) | 15:10 |
| joadavis | right, we discussed if tasks in progress should be on the list | 15:10 |
| witek | I assumed we will continue the work on merging APIs and Kafka upgrade | 15:10 |
| witek | so these will automatically make it to the priorities list | 15:10 |
| dougsz | sounds good, thanks | 15:10 |
| witek | joadavis, dougsz: I don't remember if we decided how we should handle these, is it OK to skip them from the game or you prefer to have them as well? | 15:12 |
| Dobroslaw | I would prefer them in game so we see all "big" tasks | 15:13 |
| dougsz | I guess Kafka upgrade is already part of Middleware upgrade | 15:13 |
| Dobroslaw | that are worked on/considered | 15:13 |
| joadavis | I'd add a second section below the table for voting and list them there for context | 15:13 |
| witek | dougsz: no, client upgrade is meant, it includes code changes | 15:13 |
| joadavis | or make them a different color so they stand out as in-progress | 15:13 |
| witek | OK, I'll add the two to the list and mark as in progress, we have stories for them already | 15:15 |
| dougsz | I suppose from a reviewing perspective, it would be nice to have them all there, to make it clear where review time should be targetted. | 15:16 |
| witek | will update after the meeting | 15:16 |
| witek | any other comments? | 15:16 |
| witek | #topic TimescaleDB | 15:17 |
| *** openstack changes topic to "TimescaleDB (Meeting topic: monasca)" | 15:17 | |
| Dobroslaw | that's from me | 15:17 |
| Dobroslaw | I found it few days ago | 15:17 |
| Dobroslaw | and it looks promising as a alternative for influx/cassandra | 15:18 |
| Dobroslaw | I added more links in etherpad | 15:18 |
| Dobroslaw | in short: extension to PostgreSQL | 15:18 |
| Dobroslaw | a lot faster than PostgreSQL for storing and handling metrics (use something called hypertable on top of Postgres) | 15:19 |
| Dobroslaw | apparently also a lot faster than cassandra | 15:19 |
| Dobroslaw | slower than influx if we send few metrics from every node | 15:20 |
| Dobroslaw | but if number of metrics from one node increase it's starting to be faster than inflax | 15:20 |
| Dobroslaw | big point: we can use most tools for Postgres for HA | 15:21 |
| *** altlogbot_0 has quit IRC | 15:21 | |
| Dobroslaw | https://blog.timescale.com/high-availability-timescaledb-postgresql-patroni-a4572264a831/ | 15:21 |
| Dobroslaw | There are also cons like much higher disk usage than Influx in exchange for less memory and CPU use. They recomend to run TimescaleDB on top of ZFS as users often see 3-9x compression. | 15:21 |
| witek | do they have any dedicated clients, or standard mysql should be used? | 15:21 |
| dougsz | I suppose for me, it's an interesting thing to keep an eye on for the future. | 15:22 |
| Dobroslaw | as far as I understand standard sql | 15:22 |
| *** altlogbot_0 has joined #openstack-monasca | 15:22 | |
| *** irclogbot_2 has quit IRC | 15:22 | |
| witek | how does it scale horizontally, any limitations? | 15:23 |
| Dobroslaw | ^ link have more info | 15:23 |
| Dobroslaw | using etcd or zookeeper or anything similar for choosing master | 15:24 |
| *** irclogbot_2 has joined #openstack-monasca | 15:24 | |
| Dobroslaw | limitations I would say similar to Postgres | 15:24 |
| Dobroslaw | need streaming replication from HA tools | 15:25 |
| witek | https://docs.timescale.com/v1.3/faq#clustered | 15:25 |
| witek | "Full, scale-out clustering (i.e., for data volumes > 500 billion rows and ingest rates > 300K row inserts / second) is in the works and will leverage the automated partitioning capabilities already available in single-node TimescaleDB today." | 15:26 |
| witek | not sure, if that's up to date | 15:26 |
| *** altlogbot_0 has quit IRC | 15:27 | |
| Dobroslaw | well, it's just another tool on Apache 2.0 to check from time to time | 15:27 |
| *** altlogbot_2 has joined #openstack-monasca | 15:28 | |
| witek | I've heard of TimescaleDB before and it seems they are actively developing it | 15:28 |
| *** irclogbot_2 has quit IRC | 15:28 | |
| dougsz | I suppose the other question is how well does it handle high cardinality | 15:29 |
| Dobroslaw | they raised 15M $ in January | 15:29 |
| joadavis | it is appealing that it supports "all of SQL" | 15:29 |
| Dobroslaw | https://blog.timescale.com/what-is-high-cardinality-how-do-time-series-databases-influxdb-timescaledb-compare/ | 15:29 |
| dougsz | :) | 15:29 |
| Dobroslaw | dougsz: newest post on they blog :) | 15:29 |
| *** irclogbot_2 has joined #openstack-monasca | 15:30 | |
| dougsz | I wonder what their business model is | 15:30 |
| witek | they also have Prometheus remote read/write adapter | 15:30 |
| witek | https://github.com/timescale/prometheus-postgresql-adapter | 15:30 |
| Dobroslaw | https://www.timescale.com/pricing | 15:30 |
| Dobroslaw | Timescale License basically block Amazon and similar from providing it as a SaaS | 15:31 |
| Dobroslaw | DBaaS | 15:31 |
| Dobroslaw | dougsz: https://blog.timescale.com/how-we-are-building-an-open-source-business-a7701516a480/ | 15:32 |
| witek | hm, could licensing also be an issue for us? | 15:33 |
| Dobroslaw | Community features (free): Will be licensed under the TSL, but will be made available at no charge. There are two exceptions that are prohibited from using these features (without a commercial agreement): (1) cloud and SaaS providers who just offer a hosted “database-as-a-service” version of TimescaleDB, and (2) OEMs that don’t provide any other value on top of the database. This tier enables us to continue | 15:33 |
| Dobroslaw | to provide free features to and invest in our community, while protecting from open-source strip mining. | 15:33 |
| Dobroslaw | Base is Apache 2.0 | 15:33 |
| Dobroslaw | Differences in functionality here: https://www.timescale.com/pricing | 15:34 |
| witek | I see some functionality is not included in Apache license | 15:34 |
| Dobroslaw | I did not read this license but Monasca IS providing value on top of the database | 15:35 |
| witek | I understand that implementing support for TimescaleDB addresses the same problems as `Sharding model for InfluxDB` on our priorities list | 15:36 |
| Dobroslaw | but I'm not lawyer | 15:36 |
| witek | Dobroslaw: correct, wanted to comment with the same sentence | 15:36 |
| witek | I guess we would need one to clarify | 15:36 |
| Dobroslaw | yea... I hate this license wars... | 15:36 |
| witek | or check if Apache is enough for us | 15:36 |
| witek | should we be adding Timescale to our game list? | 15:37 |
| Dobroslaw | don't know, up to you all | 15:38 |
| witek | have you discussed it in your team? | 15:38 |
| Dobroslaw | I just showed it today to Adrian but he did not look much into this | 15:39 |
| Dobroslaw | just said it's nice that we can connect to it like to any SQL db | 15:39 |
| witek | I'd be interested in Matthias' opinion | 15:40 |
| Dobroslaw | he is sick this week | 15:40 |
| witek | for now, I would say we can keep an eye on it and can evaluate, but don't include in the list yet | 15:41 |
| Dobroslaw | fine by me | 15:41 |
| witek | let's move on | 15:41 |
| dougsz | thanks Dobroslaw | 15:42 |
| Dobroslaw | :) | 15:42 |
| witek | #topic new tag for monasca-log-api Pike | 15:42 |
| *** openstack changes topic to "new tag for monasca-log-api Pike (Meeting topic: monasca)" | 15:42 | |
| witek | dougsz: thanks for the heads-up | 15:42 |
| witek | I've given +1 today | 15:43 |
| dougsz | Thanks witek, I've been trying to gets someone to W+1 in reviews | 15:43 |
| witek | everyone busy after Summit I assume | 15:43 |
| dougsz | yeah | 15:43 |
| dougsz | I guess that is it for this | 15:44 |
| joadavis | Looks ok to me, should I give it the W+!? | 15:44 |
| witek | joadavis: it | 15:44 |
| dougsz | Can you do it in releases? | 15:44 |
| joadavis | oh, good point. :( | 15:45 |
| witek | I can ping in #openstack-release | 15:45 |
| witek | #topic Readme formating errors in Pike | 15:46 |
| *** openstack changes topic to "Readme formating errors in Pike (Meeting topic: monasca)" | 15:46 | |
| witek | https://review.opendev.org/652854 | 15:46 |
| witek | reminder from last time | 15:46 |
| witek | we cannot tag on Pike because of formatting errors in Readmes | 15:46 |
| witek | http://logs.openstack.org/54/652854/3/check/openstack-tox-validate/14a09ef/job-output.txt.gz#_2019-04-18_05_37_47_484135 | 15:47 |
| witek | it would be great if someone could pick it up | 15:48 |
| witek | I can help as well | 15:48 |
| witek | #topic Python 3 support in monasca-agent | 15:49 |
| *** openstack changes topic to "Python 3 support in monasca-agent (Meeting topic: monasca)" | 15:49 | |
| joadavis | I posted a WIP patch for py36 environment enabling in mon-agent | 15:49 |
| witek | nice, thanks | 15:49 |
| witek | still a lot of work to turn it green, right? | 15:50 |
| joadavis | There are still a number of errors that result from the patch, and will need to track them down | 15:50 |
| joadavis | zuul says 86, which is more than I saw locally. :) | 15:51 |
| witek | do you want to work on this? | 15:51 |
| joadavis | I did when I thought the list of errors would be shorter. ;) | 15:52 |
| witek | haha | 15:52 |
| witek | perhaps it could be split | 15:52 |
| joadavis | I will take another pass at it today, and will ask for help where I can't find an easy fix | 15:52 |
| witek | cool, thanks | 15:53 |
| joadavis | I suspect there are many repeated errors, and most can be solved by a quick google for the equivalent call, or importing six | 15:53 |
| joadavis | We should check all the other monasca-* projects are properly invoking the py36 unit tests | 15:53 |
| dougsz | Will try and take a look sometime | 15:53 |
| witek | I think monasca-agent is the only one not executing tests | 15:54 |
| joadavis | thanks | 15:54 |
| witek | btw., I've added the story to the new board | 15:54 |
| joadavis | and I would appreciate anyone with a bit more tox expertise reviewing the tox.ini change to make sure I didn't miss something. :) | 15:54 |
| witek | https://storyboard.openstack.org/#!/board/141 | 15:54 |
| witek | #topic Telemetry meeting | 15:55 |
| *** openstack changes topic to "Telemetry meeting (Meeting topic: monasca)" | 15:55 | |
| witek | Telemetry team has scheduled a bi-weekly meeting | 15:56 |
| witek | on Thursdays 2am UTC | 15:56 |
| witek | http://eavesdrop.openstack.org/#Telemetry_Team_Meeting | 15:56 |
| witek | middle of the night for me | 15:57 |
| joadavis | 7pm here, but I have a conflict tonight | 15:57 |
| witek | we've seen a lot of interest during the Summit from people asking how to migrate from Ceilometer/Aodh to Monasca | 15:58 |
| joadavis | I may have to just review the logs. I do want to get a conversation with the telemetry team about publishers | 15:58 |
| dougsz | +1 People have been showing up in Kolla-Ansible asking for help with Monasca for this purpose | 15:58 |
| joadavis | yes, it might be good to write a quick article about how to migrate and what are some differences | 15:59 |
| witek | volunteers? :) | 15:59 |
| dougsz | What is the reference design for Monasca? | 15:59 |
| joadavis | hah, are you looking at me? | 15:59 |
| joadavis | dougsz: good question. should we be steering users to kolla or docker or a distribution? | 16:00 |
| joadavis | or just give a simple devstack based example | 16:00 |
| witek | dougsz: what do you mean by reference? | 16:00 |
| dougsz | Ceilometer replacement | 16:01 |
| witek | don't understadn | 16:01 |
| dougsz | I suppose these people want to do billing? | 16:02 |
| joadavis | some will, some just want monitoring | 16:02 |
| witek | I think Monasca publisher is important, we should also describe installation methods (or link) in the central place (d.o.o) | 16:04 |
| joadavis | I do wish we had a recent user who had moved so we could reference their experience. | 16:04 |
| witek | article is a great idea | 16:04 |
| witek | we could also reach out to Telemetry team and ask if they are interested in migrating | 16:05 |
| joadavis | It might be easiest to start hacking out the article as a page on the wiki, then when ready we can try submitting it to the Superuser magazine | 16:05 |
| witek | and provide use cases which have to be supported | 16:05 |
| witek | OK, I think we can wrap up now, we're over time anyway | 16:06 |
| witek | but we should definitely follow up on this | 16:06 |
| witek | thanks for joining | 16:06 |
| joadavis | yes. I'll start an outline and will post the link to this channel | 16:07 |
| dougsz | Thanks all | 16:07 |
| witek | please remember about priorities | 16:07 |
| witek | thanks joadavis | 16:07 |
| koji_n | thanks | 16:07 |
| witek | thanks everyone | 16:07 |
| witek | bye | 16:07 |
| witek | #endmeeting | 16:07 |
| *** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca" | 16:07 | |
| Dobroslaw | bye | 16:07 |
| openstack | Meeting ended Wed May 8 16:07:31 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:07 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-05-08-15.00.html | 16:07 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-05-08-15.00.txt | 16:07 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-05-08-15.00.log.html | 16:07 |
| *** koji_n has quit IRC | 16:07 | |
| *** witek has quit IRC | 16:16 | |
| *** dougsz has quit IRC | 16:58 | |
| joadavis | It still kills me that when you go to https://docs.openstack.org/stein/ and search for "monasca" you get no results | 17:16 |
| joadavis | Quick start - https://wiki.openstack.org/wiki/Monasca/Migration_from_Ceilometer | 17:43 |
| *** guimaluf has quit IRC | 20:44 | |
| *** bobh has joined #openstack-monasca | 20:44 | |
| *** bobh has quit IRC | 20:45 | |
| *** bobh has joined #openstack-monasca | 21:22 | |
| *** bobh has quit IRC | 21:26 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!