| *** dangtrinhnt has joined #openstack-telemetry | 01:43 | |
| *** zhurong has joined #openstack-telemetry | 01:50 | |
| dangtrinhnt | Meeting in 1m :) | 01:59 |
|---|---|---|
| dangtrinhnt | okie | 02:00 |
| dangtrinhnt | #startmeeting openstack telemetry | 02:00 |
| openstack | Meeting started Thu May 23 02:00:32 2019 UTC and is due to finish in 60 minutes. The chair is dangtrinhnt. Information about MeetBot at http://wiki.debian.org/MeetBot. | 02:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 02:00 |
| *** openstack changes topic to " (Meeting topic: openstack telemetry)" | 02:00 | |
| openstack | The meeting name has been set to 'openstack_telemetry' | 02:00 |
| dangtrinhnt | zhurong, lxkong, are you here? | 02:00 |
| lxkong | hey | 02:01 |
| dangtrinhnt | shaoman, adriant | 02:01 |
| dangtrinhnt | lxkong hi | 02:01 |
| adriant | o/ | 02:01 |
| dangtrinhnt | Let's look at the meeting agenda today #link https://etherpad.openstack.org/p/telemetry-meeting-agenda | 02:01 |
| dangtrinhnt | adriant hi :) | 02:01 |
| zhurong | Hi dangtrinhnt | 02:01 |
| dangtrinhnt | zhurong hi | 02:02 |
| dangtrinhnt | okie, our focus today is the Train-1 goals and Telemetry roadmap | 02:02 |
| dangtrinhnt | #topic Telemetry roadmap (cont.) | 02:03 |
| *** openstack changes topic to "Telemetry roadmap (cont.) (Meeting topic: openstack telemetry)" | 02:03 | |
| dangtrinhnt | #link https://etherpad.openstack.org/p/telemetry-train-roadmap | 02:03 |
| dangtrinhnt | After the last meeting, joadavis helped us to gather some options for Telemetry in Train | 02:04 |
| dangtrinhnt | I would like to discuss a little bit about them before moving forward | 02:05 |
| dangtrinhnt | +Proposal A: Try to maintain current course, Increase community involvement and communication | 02:05 |
| dangtrinhnt | +Proposal B: Gather new feature requirements, dedicate a team to implementing them | 02:05 |
| dangtrinhnt | +Proposal C: Work with each OpenStack project to provide its own telemetry data | 02:06 |
| dangtrinhnt | +Proposal D: Define an end of life for the Telemetry project, tell the community to switch to Prometheus | 02:06 |
| dangtrinhnt | +Proposal E: Fold Telemetry in to the Monasca project => I could expect an optimistic future for this proposal but after 2-3 more cycles | 02:06 |
| dangtrinhnt | What do you think? | 02:06 |
| dangtrinhnt | lxkong, zhurong, adriant? | 02:06 |
| lxkong | the pA and pB are more realistic | 02:07 |
| zhurong | I vote for Proposal B | 02:07 |
| adriant | part of me wonders if a mix of ABC is possible | 02:07 |
| dangtrinhnt | I'm ok with A,B,C. But, D, E I guess are hard to choose because there are too many people still rely on Telemetry. | 02:08 |
| dangtrinhnt | lxkong, +1 | 02:08 |
| dangtrinhnt | adriant, I have the same thought with you. | 02:09 |
| adriant | in theory, would prometheus be able to give us all the same metrics? | 02:09 |
| adriant | and it would act as a datastore too, so no gnocchi | 02:09 |
| adriant | the problem is no keystone integration | 02:10 |
| adriant | and within that per project multi-tenancy | 02:10 |
| adriant | and a lot of of useful features of telemetry rely on the concept of per project metrics | 02:10 |
| * adriant isn't 100% sure he's making sense | 02:11 | |
| dangtrinhnt | like lxkong and joadavis has pointed out, there are some issues with timestamp in Prometheus that will not provide reliable data for billing | 02:11 |
| dangtrinhnt | am I right lxkong? | 02:11 |
| lxkong | i'm only convinced if the person who recommends prometheus could provide some PoC demos, or at least do some actual work to compare those two | 02:12 |
| lxkong | otherwise, i'm not considering that as an option | 02:12 |
| zhurong | I am agree with lxkong | 02:12 |
| lxkong | sorry, should be "i'm only convinced unless" | 02:12 |
| dangtrinhnt | So am I. | 02:13 |
| lxkong | maybe prometheus is much more promising than ceilometer, i don't know. So, show me something | 02:13 |
| dangtrinhnt | Okie, so I think we can put Proposal D aside. How about E? | 02:14 |
| dangtrinhnt | Monasca? | 02:15 |
| adriant | does it do polling of resource data? | 02:16 |
| adriant | I don't actually know enough about it | 02:16 |
| adriant | https://github.com/openstack/monasca-agent so I guess it does collection of a sort | 02:17 |
| dangtrinhnt | I think so #link https://wiki.openstack.org/wiki/Monasca | 02:17 |
| lxkong | hmm...it replies on Apache Spark and kafaka? | 02:18 |
| dangtrinhnt | It is an agent-based monitoring system. Ah, yes | 02:18 |
| adriant | it sounds like it can be used for telemetry, but it does a lot more than just that | 02:18 |
| lxkong | adriant: i don't think our ops will like it :-) | 02:18 |
| adriant | folding telemetry for billing into monitoring sounds like a potential nightmare | 02:18 |
| adriant | and yeah... even more complex dependencies :( | 02:19 |
| dangtrinhnt | What they are trying to do is to add scalability to monitoring. And, considering the architecture, I guess It would be a huge change if people want to replace telemetry with monasca | 02:19 |
| dangtrinhnt | I don't think it's a good idea for this cycle or the next one. | 02:20 |
| lxkong | i don't know much about Monasca either, i'll leave it to the Mosasca team. Hopefully after several dev cycles, there are more and more users deploy Monasca. We will see. | 02:20 |
| dangtrinhnt | +1 | 02:20 |
| lxkong | at least for us, we won't consider using it in the next 1 or 1.5 years | 02:20 |
| dangtrinhnt | it makes sense considering the amount of resource and effort you have put into Telemetry | 02:21 |
| lxkong | but i'm not against that idea | 02:21 |
| dangtrinhnt | okie, I think we need to work with joadavis and the monasca team over the next several cycles I guess :) | 02:22 |
| dangtrinhnt | I guess for Train, we will do something like a mix of A,B, and C. | 02:23 |
| dangtrinhnt | any comments? | 02:23 |
| dangtrinhnt | I will draft a proposal roadmap for Telemetry patch on gerrit in the next couple days. | 02:25 |
| dangtrinhnt | Okie, next topic | 02:25 |
| dangtrinhnt | #topic Train-1 progress update | 02:25 |
| *** openstack changes topic to "Train-1 progress update (Meeting topic: openstack telemetry)" | 02:25 | |
| *** irclogbot_1 has quit IRC | 02:26 | |
| dangtrinhnt | self-healing with AODH is done, isn't it? lxkong? | 02:26 |
| lxkong | dangtrinhnt: yes | 02:26 |
| dangtrinhnt | #link https://review.opendev.org/#/c/659046/ | 02:26 |
| dangtrinhnt | great, thanks | 02:26 |
| lxkong | we are working on the Heat support internally | 02:26 |
| dangtrinhnt | that's cool | 02:27 |
| lxkong | dangtrinhnt: you may notice i was still creating the alarm manually in the demo | 02:27 |
| lxkong | after heat support, we could define the alarm in heat template | 02:27 |
| dangtrinhnt | awesome | 02:27 |
| zhurong | It is a great job lxkong | 02:28 |
| dangtrinhnt | Please keep us updated with that, thanks | 02:28 |
| lxkong | sure | 02:28 |
| dangtrinhnt | zhurong "switch to oslo.privileps" is merged | 02:29 |
| *** irclogbot_0 has joined #openstack-telemetry | 02:30 | |
| zhurong | yeah, next part we want to add container metrics | 02:30 |
| dangtrinhnt | #link https://review.opendev.org/#/c/656098/ | 02:30 |
| dangtrinhnt | Great, thanks. | 02:30 |
| lxkong | zhurong: container metrics, you mean Magnum or Zun? | 02:31 |
| zhurong | with Zun | 02:31 |
| lxkong | ah, ok | 02:31 |
| lxkong | zhurong: have you deployed Zun in production? | 02:31 |
| zhurong | yeah, we have Zun in our production | 02:32 |
| dangtrinhnt | That's cool | 02:32 |
| lxkong | cool, good to know | 02:33 |
| zhurong | we did a lot of work in Zun | 02:33 |
| dangtrinhnt | okie, next feature, the "event subsystem": I would want to wait for rafaelweingartne to update on this. He cannot attend today meeting. | 02:34 |
| *** joadavis_ has joined #openstack-telemetry | 02:35 | |
| dangtrinhnt | In the last meeting, we're thinking about bringing back cpu_util to telemetry. Do we have resource to do that? | 02:35 |
| lxkong | unfortunately, i don't have time to do that currently | 02:36 |
| lxkong | but we definitely need that after upgrading Ceilometer | 02:36 |
| dangtrinhnt | Okie, I guess we can put that on hold and maybe re-open it at Train-2 or 3 | 02:37 |
| dangtrinhnt | yeah | 02:37 |
| dangtrinhnt | I will trying to spend something fix/update the docs in the next couple days. | 02:38 |
| dangtrinhnt | Anything you want to discuss about Train-1 milestone? | 02:38 |
| lxkong | nothing from me | 02:39 |
| zhurong | me too | 02:39 |
| dangtrinhnt | okie, next topic | 02:40 |
| dangtrinhnt | #topic Shanghai summit | 02:40 |
| *** openstack changes topic to "Shanghai summit (Meeting topic: openstack telemetry)" | 02:40 | |
| dangtrinhnt | Anyone want to attend the next OpenInfra Summit in Shanghai? | 02:40 |
| zhurong | haha lxkong welcome back, come on, 加西亚 | 02:40 |
| dangtrinhnt | :) | 02:41 |
| lxkong | dangtrinhnt: we don't know yet. | 02:41 |
| lxkong | but i will be kubecon Shanghai in June | 02:41 |
| dangtrinhnt | We need to show the world what we're doing this cycle :) | 02:41 |
| dangtrinhnt | zhurong, will you? :) | 02:41 |
| lxkong | btw, i'm in the Programming Committee for the Container Infrastructure Track for Shanghai Openinfra Summit | 02:42 |
| zhurong | I will be there, this time I don't need the visa, haha | 02:42 |
| zhurong | cool lxkong | 02:42 |
| lxkong | zhurong: would much appreciate if you could share the work you've done in Zun | 02:43 |
| zhurong | we have a lighter topic about zun in Denver summit, but due to the visa, we can not attend. | 02:44 |
| dangtrinhnt | lxkong yeah, that's cool | 02:44 |
| dangtrinhnt | zhurong, same with me, I could not attend Denver because of VISAAA | 02:44 |
| dangtrinhnt | :) | 02:44 |
| joadavis_ | We did miss telemetry at Denver summit. | 02:44 |
| zhurong | sure, we will have topic about zun in shanghai lxkong | 02:45 |
| dangtrinhnt | joadavis_ hi :) | 02:45 |
| joadavis_ | Dont mind me, I'm only partly here | 02:45 |
| joadavis_ | I would like to come to Shanghai summit and meet you all, but budget constraints... | 02:46 |
| dangtrinhnt | okie, np. Neither do I, I just changed job and don't think I can go there. | 02:47 |
| dangtrinhnt | Do you have anything else to discuss? | 02:47 |
| dangtrinhnt | we have 12m left. | 02:48 |
| lxkong | i have to leave now, has an appointment later on | 02:48 |
| joadavis_ | As a late attendee, I will say proposal E is somewhat already done/doable | 02:48 |
| joadavis_ | Witek can talk about it in the meeting at 0800 too | 02:49 |
| dangtrinhnt | lxkong, np. Take your time. | 02:49 |
| dangtrinhnt | joadavis_ , so let do it in the next meeting session today. Thanks | 02:49 |
| zhurong | bye lxkong | 02:49 |
| dangtrinhnt | zhurong, adriant, do you have anything to add? | 02:49 |
| zhurong | dangtrinhnt: nothing from my side today | 02:51 |
| adriant | no, mostly just a fly on the wall today. | 02:51 |
| dangtrinhnt | btw, zhurong, could you and shaoman attend the next meeting today? | 02:51 |
| dangtrinhnt | with the other guys | 02:51 |
| dangtrinhnt | I guess it's too much for you. | 02:52 |
| dangtrinhnt | adriant, your inputs/questions are valuable :) | 02:52 |
| zhurong | yeah, we will, today shaoman have a internal meeting this time | 02:52 |
| adriant | dangtrinhnt: ty! Just busy running around between a lot of tasks, so mostly writing/testing code while watching IRC a bit today. | 02:53 |
| dangtrinhnt | zhurong: great, thanks :) see you then. | 02:53 |
| dangtrinhnt | adriant, so do I :) haha | 02:54 |
| dangtrinhnt | okie, I guess we can end the meeting now | 02:54 |
| dangtrinhnt | Thanks everyone for joining. | 02:54 |
| zhurong | thanks, bye all | 02:54 |
| dangtrinhnt | #endmeeting | 02:54 |
| *** openstack changes topic to "#openstack-telemetry is OpenStack Telemetry | http://wiki.openstack.org/Telemetry" | 02:54 | |
| openstack | Meeting ended Thu May 23 02:54:53 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 02:54 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-23-02.00.html | 02:54 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-23-02.00.txt | 02:54 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-23-02.00.log.html | 02:54 |
| *** joadavis_ has quit IRC | 02:58 | |
| *** dangtrinhnt has quit IRC | 03:12 | |
| *** dangtrinhnt has joined #openstack-telemetry | 03:15 | |
| *** tojuvone has joined #openstack-telemetry | 03:18 | |
| *** lpetrut has joined #openstack-telemetry | 05:11 | |
| *** tesseract has joined #openstack-telemetry | 06:41 | |
| *** witek has joined #openstack-telemetry | 06:53 | |
| *** witek has quit IRC | 06:55 | |
| *** witek has joined #openstack-telemetry | 06:56 | |
| *** rcernin has quit IRC | 07:00 | |
| *** pcaruana has joined #openstack-telemetry | 07:07 | |
| *** mrunge_ has quit IRC | 07:27 | |
| *** mrunge has joined #openstack-telemetry | 07:27 | |
| *** ivve has joined #openstack-telemetry | 07:42 | |
| dangtrinhnt | 14m before the 2nd meeting today :) | 07:46 |
| *** m0zart89 has joined #openstack-telemetry | 07:55 | |
| dangtrinhnt | Okie, let's start the meeting | 08:00 |
| dangtrinhnt | #startmeeting openstack telemetry | 08:00 |
| openstack | Meeting started Thu May 23 08:00:31 2019 UTC and is due to finish in 60 minutes. The chair is dangtrinhnt. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| *** openstack changes topic to " (Meeting topic: openstack telemetry)" | 08:00 | |
| openstack | The meeting name has been set to 'openstack_telemetry' | 08:00 |
| dangtrinhnt | mrunge, zhurong, joedavis, hyang, witek, shaoman are you here for the meeting? | 08:01 |
| witek | morning | 08:01 |
| dangtrinhnt | witek, hi :) | 08:02 |
| mrunge | hi | 08:02 |
| witek | hi | 08:02 |
| dangtrinhnt | I'm looking for Tobias Urdin's IRC handle | 08:02 |
| dangtrinhnt | anyone know it? | 08:02 |
| mrunge | good question, I may remember it, when I see it | 08:03 |
| witek | tobiao? | 08:03 |
| dangtrinhnt | I guess, tobias-urdin | 08:04 |
| dangtrinhnt | anyway | 08:04 |
| m0zart89 | Hello.Is this channel strictly for meetings and discussions ? | 08:04 |
| mrunge | https://launchpad.net/~tobias-urdin | 08:04 |
| mrunge | tobias-urdin, as already said | 08:04 |
| mrunge | m0zart89: it's not. but we're having a meeting right now. if you have a question, can that wait till after the meeting? | 08:05 |
| dangtrinhnt | anyway, the focus of this meeting is "Cross-project discussion (e.g., monasca merged/integration/replacement) + roadmap of Telemetry in Train" | 08:05 |
| m0zart89 | mrunge: of course ;) | 08:05 |
| dangtrinhnt | m0zart89, :) in about 1 hour, we're free :) | 08:06 |
| dangtrinhnt | Please look at the meeting agenda #link https://etherpad.openstack.org/p/telemetry-meeting-agenda | 08:06 |
| *** dougsz has joined #openstack-telemetry | 08:07 | |
| witek | I have added a URL to Monasca publisher review to the agenda | 08:07 |
| witek | oh, you moved it, it's OK | 08:07 |
| dangtrinhnt | witek, yes, I would like to discuss a little bit about our roadmap before moving forward | 08:07 |
| dangtrinhnt | #topic Telemetry roadmap | 08:08 |
| *** openstack changes topic to "Telemetry roadmap (Meeting topic: openstack telemetry)" | 08:08 | |
| dangtrinhnt | #link https://etherpad.openstack.org/p/telemetry-train-roadmap | 08:08 |
| dangtrinhnt | joadavis had helped us put together several options | 08:08 |
| dangtrinhnt | A: Try to maintain current course, Increase community involvement and communication | 08:09 |
| dangtrinhnt | B: Gather new feature requirements, dedicate a team to implementing them | 08:09 |
| dangtrinhnt | C: Work with each OpenStack project to provide its own telemetry data | 08:09 |
| dangtrinhnt | D: Define an end of life for the Telemetry project, tell the community to switch to Prometheus | 08:09 |
| dangtrinhnt | E: Fold Telemetry in to the Monasca project => I could expect an optimistic future for this proposal but after 2-3 more cycles | 08:10 |
| witek | I think C adds real value to OpenStack | 08:11 |
| dangtrinhnt | In this morning session, we agreed that a mix of A,B,C could be a doable solution. D would need a solid proof that Prometheus can replace Telemetry. E. Is also a good option but would be in 2-3 cycles since many people depends on Telemetry | 08:11 |
| dangtrinhnt | witek, I think so too | 08:12 |
| dangtrinhnt | Any comments? | 08:12 |
| witek | regarding E, I think it should be a free choice for companies to decide which approach they want to choose | 08:13 |
| mrunge | I'd think, we should keep the community honest and talk about deprecation | 08:13 |
| mrunge | regarding to D: I don't see a feature parity there yet | 08:14 |
| dangtrinhnt | +1 | 08:15 |
| mrunge | other thoughts? | 08:16 |
| witek | what is your opinion dangtrinhnt ? | 08:17 |
| dangtrinhnt | witek, monasca seems more flexible and give users more choice so I think it's inevitable to use monasca. | 08:17 |
| dangtrinhnt | Looking at what Monasca offers so far, I would want to design a future for Billing and Monitoring. | 08:17 |
| mrunge | do you really want to dive into billing? | 08:18 |
| mrunge | there used to be a project for that | 08:18 |
| mrunge | and everyone else tried to avoid it like hell | 08:18 |
| dangtrinhnt | Cloud Kitty you mean? | 08:19 |
| mrunge | right | 08:19 |
| mrunge | there was a single company behind it, iirc | 08:19 |
| *** tobias-urdin has joined #openstack-telemetry | 08:19 | |
| dangtrinhnt | lxkong and adriant are mostly use ceilometer for their billing system | 08:19 |
| dangtrinhnt | tobias-urdin, hi | 08:19 |
| mrunge | with regards to merging monasca and telemetry: which community is larger? | 08:20 |
| tobias-urdin | hi o/ sorry if i missed the beginning, been working nightshift | 08:20 |
| mrunge | i.e. maybe it'd make sense to merge monasca into telemetry? | 08:20 |
| dangtrinhnt | mrunge, I would love to here some stats of monasca from witek | 08:21 |
| witek | stats are all public, you can look them up at stackalytics | 08:21 |
| dangtrinhnt | But like I said, It would be in 2-3 more cycles. | 08:21 |
| witek | we have Fujitsu, SUSE, StackHPC and NEC on board | 08:21 |
| dangtrinhnt | so currently, they are all active contributors? | 08:22 |
| witek | yes, these are companies actively contributing | 08:23 |
| dangtrinhnt | great | 08:23 |
| mrunge | looking at the stats, telemetry is about twice as big? | 08:23 |
| mrunge | hmm, that is derailing here and doesn't lead anywhere, let's table that | 08:24 |
| witek | mrunge: I think Telemetry's mission never had been to provide operational monitoring | 08:24 |
| witek | with sampling rates of 15s and below | 08:25 |
| dangtrinhnt | but right now Telemetry only has a couple active contributors like shaoman, lxkong, zhurong and myself (mostly review and merge code) | 08:25 |
| dangtrinhnt | witek, true | 08:25 |
| mrunge | right witek. /me is looking more for sampling rates in 1s intervals | 08:25 |
| mrunge | or below | 08:26 |
| dangtrinhnt | okie, regarding the merge, how about wait until the end of Train? | 08:27 |
| tobias-urdin | im somewhat conflated on treating monitoring and metrics collection as the same thing, we explicitly kept away from monasca to not provide monitoring and only collect metrics | 08:27 |
| tobias-urdin | to skip deploying eight more services, and skipping java | 08:27 |
| witek | dangtrinhnt: coming back to your idea, I'd be happy to help working on such design | 08:28 |
| mrunge | right. we don't do monasca either | 08:28 |
| dangtrinhnt | witek, great thanks, let's start an etherpad and see what could be done. | 08:29 |
| dangtrinhnt | tobias-urdin, makes sense, I would skip java | 08:29 |
| witek | on Java topic, we planned for this cycle to work on removing the last Java component | 08:30 |
| witek | thresholding engine | 08:30 |
| dangtrinhnt | Let's put together a draft design if the two (telemetry, monasca) could be matched. | 08:30 |
| dangtrinhnt | okie, anything else on this? | 08:32 |
| mrunge | not from my side | 08:32 |
| witek | not from me either | 08:33 |
| dangtrinhnt | okie | 08:34 |
| dangtrinhnt | That's great. I will draft a vision for Telemetry in Train (published to the docs) based on what we discussed here including mention the possibility or merging with Monasca | 08:35 |
| dangtrinhnt | in the next couple days | 08:35 |
| dangtrinhnt | next topic | 08:35 |
| mrunge | ok, thank you dangtrinhnt | 08:35 |
| dangtrinhnt | #topic Monasca publisher | 08:36 |
| *** openstack changes topic to "Monasca publisher (Meeting topic: openstack telemetry)" | 08:36 | |
| dangtrinhnt | #link https://review.opendev.org/#/c/562400/ | 08:36 |
| dangtrinhnt | It has been a while | 08:36 |
| witek | this is an old review we have tried to contribute over one year ago | 08:36 |
| witek | it adds Monasca publisher to Ceilometer | 08:36 |
| witek | and allows pushing Ceilometer measurements to Monasca API | 08:37 |
| dangtrinhnt | I don't see any reason not to merge it. | 08:37 |
| witek | great, that's what I wanted to check on | 08:37 |
| dangtrinhnt | So please resolve the merge conflicts and let us review it again. | 08:38 |
| witek | the last PS is from October, so I think it should be revisited again | 08:38 |
| witek | great, we'll update you on this | 08:38 |
| dangtrinhnt | Okie, thanks. | 08:38 |
| dangtrinhnt | mrunge, any comment? | 08:39 |
| mrunge | uhm, regarding the publisher? nope | 08:40 |
| dangtrinhnt | okie | 08:40 |
| dangtrinhnt | Do you have anything else to discuss today? | 08:41 |
| mrunge | uhm, I still have a pile of openstack emails to read, so I probably skipped the announcement for this meeting so far | 08:41 |
| mrunge | are we going to have this meeting in this time slot regularly? | 08:42 |
| witek | what about the idea of new instrumentation code for OpenStack projects? | 08:42 |
| dangtrinhnt | Yes, for now | 08:42 |
| witek | Idea C from your list | 08:42 |
| mrunge | dangtrinhnt: thank you, sounds good to me. | 08:43 |
| mrunge | I would rather document integration or exposing of metrics for other projects | 08:43 |
| mrunge | i.e. document, how to send metrics to the metrics subsystem | 08:44 |
| dangtrinhnt | witek, I'm ok with that and would combine it with A and B. | 08:44 |
| dangtrinhnt | #topic Any other things | 08:44 |
| *** openstack changes topic to "Any other things (Meeting topic: openstack telemetry)" | 08:44 | |
| dangtrinhnt | mrunge, +1 | 08:44 |
| tobias-urdin | mrunge: +1 from what i understood it telemetry never wanted to build ceilometer with this polling mechanism to work around projects not exposing metrics | 08:45 |
| * mrunge nods | 08:45 | |
| tobias-urdin | when it first started, would be interesting to know the optimal end result if it started from the beginning now | 08:45 |
| mrunge | I've been contacted e.g by the manila team on exactly that question | 08:46 |
| mrunge | ceilometer has a bad name for being slooooow | 08:46 |
| tobias-urdin | any idea how one reliably would solve the push of metrics instead of polling? while polling is resource intensive it somewhat reliable on what it does | 08:46 |
| dangtrinhnt | :) | 08:46 |
| mrunge | I'd have ideas :) | 08:47 |
| tobias-urdin | please don't say use existing message buss (rabbitmq) :D | 08:47 |
| * mrunge nods | 08:47 | |
| mrunge | nope. do not use rabbit | 08:47 |
| mrunge | I would also like to see a message mesh instead of a single bus | 08:48 |
| witek | shouldn't every service instrument their own code and expose it in the standardized way? | 08:48 |
| mrunge | witek we're talking about different things | 08:48 |
| tobias-urdin | i'll just out; im for any A,B,C approach, we use it primaryly for billing and autoscaling, gnocchi for storage and have invested a lot of time to have a third party integrate their billing engine with gnocchi API | 08:48 |
| tobias-urdin | i heard some mention on octavia metrics, we have a simple one that collects usage, i can clean that up and push upstream | 08:49 |
| mrunge | that sounds like you invested some effort, tobias-urdin | 08:49 |
| mrunge | kudos! | 08:50 |
| dangtrinhnt | tobias-urdin, great | 08:50 |
| dangtrinhnt | Since we only have less than 10m left, I will put your question on the agenda for the next meeting and maybe open a discussion on the ML | 08:52 |
| mrunge | so, any immediate actions for now? | 08:52 |
| mrunge | or a plan what to do next wrt telemetry here? | 08:52 |
| dangtrinhnt | I don't have any idea for now. So let bring that up to the ML. | 08:53 |
| dangtrinhnt | if you talking about what tobias-urdin just asked | 08:53 |
| mrunge | I haven't seen any question from tobias-urdin, did I miss that? | 08:55 |
| dangtrinhnt | ah, about the metric polling/pushing | 08:55 |
| mrunge | No I meant next steps for us to move forward here (with train) | 08:55 |
| mrunge | ah! got you | 08:55 |
| mrunge | what about pushing metrics via amqp to something presenting it to a component to pick it up? | 08:56 |
| mrunge | i.e. you'd be moving the load off the collectors | 08:57 |
| witek | isn't this what Monasca is doing right now? | 08:57 |
| witek | s/amqp/kafka | 08:57 |
| dangtrinhnt | Okie, for Train I wouldn't expect big design/architecture or changes. | 08:58 |
| dangtrinhnt | So next steps are: | 08:59 |
| tobias-urdin | the C approach is interesting to say the least, A and B more realistic. Then there is probably a lot of things that Monasca and Telemetry could work togther on | 08:59 |
| tobias-urdin | sorry dangtrinhnt, go on :) | 08:59 |
| dangtrinhnt | 1. Focus on community engament via ML, meeting, events | 09:00 |
| dangtrinhnt | 2. Fix existing bugs, documents | 09:00 |
| dangtrinhnt | 3. Designing the vision for Telemetry for the next 2-3 cycles (e.g., monasca work together) | 09:01 |
| dangtrinhnt | Yeah, basically what tobias-urdin said. | 09:01 |
| dangtrinhnt | Is that clear enought? | 09:01 |
| dangtrinhnt | okie, time up | 09:01 |
| mrunge | yupp | 09:02 |
| mrunge | thank you, dangtrinhnt | 09:02 |
| witek | thanks dangtrinhnt | 09:02 |
| tobias-urdin | yes, thanks for clearing everything up dangtrinhnt! | 09:02 |
| dangtrinhnt | okie, thanks everyone for the meeting | 09:03 |
| dangtrinhnt | #endmeeting | 09:03 |
| *** openstack changes topic to "#openstack-telemetry is OpenStack Telemetry | http://wiki.openstack.org/Telemetry" | 09:03 | |
| openstack | Meeting ended Thu May 23 09:03:13 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:03 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-23-08.00.html | 09:03 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-23-08.00.txt | 09:03 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-23-08.00.log.html | 09:03 |
| dangtrinhnt | Okie, I will try to keep the meeting time balance between the APAC, US, and or EU timezone :) | 09:04 |
| m0zart89 | Hello, community. I have openstack with several regions: US1, EU1. I have resource "instance_network_interface" with my custom attribute "region_id". My goal is to do "gnocchi measures aggregation ... --groupby project_id --groupby region_id". What is the correct way to put constant attribute "region_id" to my resource. | 09:09 |
| *** tojuvone has quit IRC | 10:30 | |
| *** tojuvone has joined #openstack-telemetry | 10:30 | |
| *** m0zart89 has quit IRC | 10:57 | |
| *** m0zart89 has joined #openstack-telemetry | 11:10 | |
| dangtrinhnt | m0zart89, the command you posted must be from an older version of gnocchi | 11:19 |
| dangtrinhnt | Correct one as far as I know is `gnocchi aggregates --groupby region_id` #link https://gnocchi.xyz/gnocchiclient/shell.html | 11:20 |
| m0zart89 | dangtrinhnt: Yes, this is deprecated function (gnocchi 4.2.5). But I have problem with resource attributes. I want to set attribute: 'US1' for ceilometer in US and 'EU1' in Europe. | 11:29 |
| openstackgerrit | Merged openstack/ceilometer master: Windows: avoid passing conf objects to subprocesses https://review.opendev.org/624380 | 11:33 |
| m0zart89 | dangtrinhnt: In general I will be using rest api. | 11:44 |
| *** dave-mccowan has joined #openstack-telemetry | 13:14 | |
| *** mrunge has quit IRC | 13:37 | |
| *** mrunge has joined #openstack-telemetry | 13:42 | |
| *** pcaruana has quit IRC | 14:10 | |
| *** pcaruana has joined #openstack-telemetry | 14:29 | |
| *** dave-mccowan has quit IRC | 14:52 | |
| *** joadavis has quit IRC | 14:57 | |
| *** joadavis has joined #openstack-telemetry | 14:59 | |
| *** ivve has quit IRC | 15:06 | |
| *** lpetrut has quit IRC | 15:08 | |
| *** m0zart89 has quit IRC | 15:28 | |
| *** pcaruana has quit IRC | 16:09 | |
| *** ivve has joined #openstack-telemetry | 16:23 | |
| *** witek has quit IRC | 16:24 | |
| *** pcaruana has joined #openstack-telemetry | 17:00 | |
| *** dougsz has quit IRC | 17:03 | |
| *** lpetrut has joined #openstack-telemetry | 18:03 | |
| *** lpetrut has quit IRC | 18:07 | |
| *** tesseract has quit IRC | 19:05 | |
| *** pcaruana has quit IRC | 20:47 | |
| *** ivve has quit IRC | 21:59 | |
| *** joadavis has quit IRC | 22:34 | |
| *** rcernin has joined #openstack-telemetry | 23:18 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!