02:00:32 #startmeeting openstack telemetry 02:00:33 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:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:00:36 The meeting name has been set to 'openstack_telemetry' 02:00:59 zhurong, lxkong, are you here? 02:01:13 hey 02:01:24 shaoman, adriant 02:01:27 lxkong hi 02:01:41 o/ 02:01:47 Let's look at the meeting agenda today #link https://etherpad.openstack.org/p/telemetry-meeting-agenda 02:01:51 adriant hi :) 02:01:58 Hi dangtrinhnt 02:02:05 zhurong hi 02:02:51 okie, our focus today is the Train-1 goals and Telemetry roadmap 02:03:20 #topic Telemetry roadmap (cont.) 02:03:34 #link https://etherpad.openstack.org/p/telemetry-train-roadmap 02:04:24 After the last meeting, joadavis helped us to gather some options for Telemetry in Train 02:05:18 I would like to discuss a little bit about them before moving forward 02:05:40 +Proposal A: Try to maintain current course, Increase community involvement and communication 02:05:50 +Proposal B: Gather new feature requirements, dedicate a team to implementing them 02:06:01 +Proposal C: Work with each OpenStack project to provide its own telemetry data 02:06:10 +Proposal D: Define an end of life for the Telemetry project, tell the community to switch to Prometheus 02:06:25 +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:26 What do you think? 02:06:38 lxkong, zhurong, adriant? 02:07:49 the pA and pB are more realistic 02:07:51 I vote for Proposal B 02:07:59 part of me wonders if a mix of ABC is possible 02:08:11 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:49 lxkong, +1 02:09:05 adriant, I have the same thought with you. 02:09:15 in theory, would prometheus be able to give us all the same metrics? 02:09:32 and it would act as a datastore too, so no gnocchi 02:10:05 the problem is no keystone integration 02:10:16 and within that per project multi-tenancy 02:10:44 and a lot of of useful features of telemetry rely on the concept of per project metrics 02:11:07 * adriant isn't 100% sure he's making sense 02:11:46 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:54 am I right lxkong? 02:12:16 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:30 otherwise, i'm not considering that as an option 02:12:40 I am agree with lxkong 02:12:47 sorry, should be "i'm only convinced unless" 02:13:50 So am I. 02:13:59 maybe prometheus is much more promising than ceilometer, i don't know. So, show me something 02:14:57 Okie, so I think we can put Proposal D aside. How about E? 02:15:17 Monasca? 02:16:27 does it do polling of resource data? 02:16:36 I don't actually know enough about it 02:17:00 https://github.com/openstack/monasca-agent so I guess it does collection of a sort 02:17:18 I think so #link https://wiki.openstack.org/wiki/Monasca 02:18:02 hmm...it replies on Apache Spark and kafaka? 02:18:13 It is an agent-based monitoring system. Ah, yes 02:18:19 it sounds like it can be used for telemetry, but it does a lot more than just that 02:18:41 adriant: i don't think our ops will like it :-) 02:18:55 folding telemetry for billing into monitoring sounds like a potential nightmare 02:19:12 and yeah... even more complex dependencies :( 02:19:57 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:20:15 I don't think it's a good idea for this cycle or the next one. 02:20:32 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:43 +1 02:20:59 at least for us, we won't consider using it in the next 1 or 1.5 years 02:21:30 it makes sense considering the amount of resource and effort you have put into Telemetry 02:21:42 but i'm not against that idea 02:22:40 okie, I think we need to work with joadavis and the monasca team over the next several cycles I guess :) 02:23:08 I guess for Train, we will do something like a mix of A,B, and C. 02:23:18 any comments? 02:25:00 I will draft a proposal roadmap for Telemetry patch on gerrit in the next couple days. 02:25:07 Okie, next topic 02:25:27 #topic Train-1 progress update 02:26:37 self-healing with AODH is done, isn't it? lxkong? 02:26:48 dangtrinhnt: yes 02:26:49 #link https://review.opendev.org/#/c/659046/ 02:26:54 great, thanks 02:26:58 we are working on the Heat support internally 02:27:17 that's cool 02:27:21 dangtrinhnt: you may notice i was still creating the alarm manually in the demo 02:27:37 after heat support, we could define the alarm in heat template 02:27:50 awesome 02:28:01 It is a great job lxkong 02:28:04 Please keep us updated with that, thanks 02:28:22 sure 02:29:40 zhurong "switch to oslo.privileps" is merged 02:30:25 yeah, next part we want to add container metrics 02:30:27 #link https://review.opendev.org/#/c/656098/ 02:30:42 Great, thanks. 02:31:00 zhurong: container metrics, you mean Magnum or Zun? 02:31:23 with Zun 02:31:27 ah, ok 02:31:37 zhurong: have you deployed Zun in production? 02:32:03 yeah, we have Zun in our production 02:32:12 That's cool 02:33:12 cool, good to know 02:33:55 we did a lot of work in Zun 02:34:46 okie, next feature, the "event subsystem": I would want to wait for rafaelweingartne to update on this. He cannot attend today meeting. 02:35:42 In the last meeting, we're thinking about bringing back cpu_util to telemetry. Do we have resource to do that? 02:36:14 unfortunately, i don't have time to do that currently 02:36:53 but we definitely need that after upgrading Ceilometer 02:37:06 Okie, I guess we can put that on hold and maybe re-open it at Train-2 or 3 02:37:17 yeah 02:38:10 I will trying to spend something fix/update the docs in the next couple days. 02:38:39 Anything you want to discuss about Train-1 milestone? 02:39:34 nothing from me 02:39:56 me too 02:40:08 okie, next topic 02:40:21 #topic Shanghai summit 02:40:42 Anyone want to attend the next OpenInfra Summit in Shanghai? 02:40:59 haha lxkong welcome back, come on, 加西亚 02:41:07 :) 02:41:13 dangtrinhnt: we don't know yet. 02:41:24 but i will be kubecon Shanghai in June 02:41:38 We need to show the world what we're doing this cycle :) 02:41:47 zhurong, will you? :) 02:42:17 btw, i'm in the Programming Committee for the Container Infrastructure Track for Shanghai Openinfra Summit 02:42:18 I will be there, this time I don't need the visa, haha 02:42:30 cool lxkong 02:43:03 zhurong: would much appreciate if you could share the work you've done in Zun 02:44:07 we have a lighter topic about zun in Denver summit, but due to the visa, we can not attend. 02:44:19 lxkong yeah, that's cool 02:44:44 zhurong, same with me, I could not attend Denver because of VISAAA 02:44:46 :) 02:44:59 We did miss telemetry at Denver summit. 02:45:17 sure, we will have topic about zun in shanghai lxkong 02:45:18 joadavis_ hi :) 02:45:41 Dont mind me, I'm only partly here 02:46:28 I would like to come to Shanghai summit and meet you all, but budget constraints... 02:47:24 okie, np. Neither do I, I just changed job and don't think I can go there. 02:47:53 Do you have anything else to discuss? 02:48:04 we have 12m left. 02:48:38 i have to leave now, has an appointment later on 02:48:48 As a late attendee, I will say proposal E is somewhat already done/doable 02:49:10 Witek can talk about it in the meeting at 0800 too 02:49:12 lxkong, np. Take your time. 02:49:32 joadavis_ , so let do it in the next meeting session today. Thanks 02:49:46 bye lxkong 02:49:49 zhurong, adriant, do you have anything to add? 02:51:00 dangtrinhnt: nothing from my side today 02:51:17 no, mostly just a fly on the wall today. 02:51:39 btw, zhurong, could you and shaoman attend the next meeting today? 02:51:51 with the other guys 02:52:03 I guess it's too much for you. 02:52:31 adriant, your inputs/questions are valuable :) 02:52:32 yeah, we will, today shaoman have a internal meeting this time 02:53:07 dangtrinhnt: ty! Just busy running around between a lot of tasks, so mostly writing/testing code while watching IRC a bit today. 02:53:39 zhurong: great, thanks :) see you then. 02:54:02 adriant, so do I :) haha 02:54:11 okie, I guess we can end the meeting now 02:54:19 Thanks everyone for joining. 02:54:41 thanks, bye all 02:54:53 #endmeeting