| *** dangtrinhnt has joined #openstack-telemetry | 01:18 | |
| dangtrinhnt | 15m before the meeting | 01:45 |
|---|---|---|
| *** zhurong_phone has joined #openstack-telemetry | 01:54 | |
| dangtrinhnt | lxkong, zhurong, rafaelweingartne, engel75 are you here for the meeting? | 01:58 |
| lxkong | ^^ | 01:58 |
| dangtrinhnt | awesome | 01:59 |
| dangtrinhnt | zhurong_phone | 01:59 |
| engel75 | hi | 02:00 |
| zhurong_phone | I am here | 02:00 |
| *** rafaelweingartne has joined #openstack-telemetry | 02:00 | |
| zhurong_phone | hi | 02:00 |
| dangtrinhnt | okie | 02:00 |
| dangtrinhnt | let's start it!!! | 02:00 |
| dangtrinhnt | #startmeeting openstack telemetry | 02:00 |
| rafaelweingartne | Hello guys | 02:00 |
| openstack | Meeting started Thu May 9 02:00:19 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 |
| engel75 | hi all | 02:00 |
| dangtrinhnt | okie, we have 5 people, it's good :) | 02:00 |
| lxkong | such a big team | 02:00 |
| dangtrinhnt | So please follow the meeting agenda using this etherpad #link https://etherpad.openstack.org/p/telemetry-meeting-agenda | 02:01 |
| dangtrinhnt | #topic Finalize the core team & active contributors | 02:01 |
| *** openstack changes topic to "Finalize the core team & active contributors (Meeting topic: openstack telemetry)" | 02:01 | |
| zhurong_phone | shaoman is on our internel meeting, so he can't attend | 02:03 |
| dangtrinhnt | So now besides lxkong, zhurong_phone, we have Adrian Turjak is interested in being the core and contribute | 02:03 |
| dangtrinhnt | I may send an nomination email after this meeting. | 02:03 |
| *** adriant has joined #openstack-telemetry | 02:04 | |
| dangtrinhnt | So rafaelweingartne, engel75, I know you guys just involve in OpenStack recently (?), I may ask would you like to contribute to Telemetry? | 02:04 |
| lxkong | adrian will join shortly | 02:04 |
| adriant | o/ | 02:04 |
| dangtrinhnt | adriant hi | 02:04 |
| lxkong | ah, so quick, adriant | 02:04 |
| rafaelweingartne | dangtrinhnt: yes, we would love to | 02:05 |
| dangtrinhnt | rafaelweingartne, engel75 you don't have to take the core team but your input and code contribution would be precious for us. | 02:05 |
| rafaelweingartne | I mean, that is what we intent to, and that is why we asked about the event system deprecation | 02:05 |
| engel75 | I am not a developer at all but rafael will contribute in the near future | 02:05 |
| dangtrinhnt | That's awesome. Thanks rafaelweingartne | 02:05 |
| dangtrinhnt | engel75, np | 02:05 |
| rafaelweingartne | engel75 is an operator, so I see his inputs as very valuable providing the use cases that we design and implement | 02:06 |
| dangtrinhnt | engel75, rafaelweingartne, awesome, we absolutely need use cases!!! :) | 02:06 |
| engel75 | yes I will try to provide input from our priduction experiences | 02:07 |
| engel75 | yes I will try to provide input from our production experiences | 02:07 |
| dangtrinhnt | Thanks! | 02:07 |
| dangtrinhnt | ok, I guess we can move to the next topic, any questions/idea? | 02:08 |
| dangtrinhnt | lxkong, zhurong_phone | 02:08 |
| dangtrinhnt | ? | 02:08 |
| lxkong | go ahead | 02:08 |
| dangtrinhnt | cool | 02:08 |
| dangtrinhnt | #topic Meeting time for non-APAC contributors | 02:08 |
| *** openstack changes topic to "Meeting time for non-APAC contributors (Meeting topic: openstack telemetry)" | 02:08 | |
| dangtrinhnt | In our next poll about the time for team meeting, we missed out the non-APAC contributors. Part of it was the polling time is during the holiday and summit so those guys didnot have a chance to vote. | 02:10 |
| dangtrinhnt | So, I suggest we made a time change so the developers/operators in the US/EU region could join. | 02:10 |
| dangtrinhnt | Any suggestion? | 02:10 |
| dangtrinhnt | rafaelweingartne and engel75 are also suffered. It's 4AM their time. | 02:11 |
| zhurong_phone | ohh... | 02:11 |
| engel75 | no rafael is from Brazil | 02:11 |
| dangtrinhnt | Right, rafaelweingartne, engel75? | 02:11 |
| rafaelweingartne | actually, 23:00 PM on my time | 02:11 |
| lxkong | i am going to ask do we already know if there are people from non-APAC intereated in contributing ceilometer... | 02:11 |
| engel75 | My time zone is GMT+2 | 02:12 |
| dangtrinhnt | yes, like mrunge | 02:12 |
| engel75 | so 4:12 now :) | 02:12 |
| dangtrinhnt | a couple developers emailed me | 02:12 |
| dangtrinhnt | lxkong | 02:12 |
| lxkong | ok, that's great | 02:12 |
| dangtrinhnt | engel75, :) | 02:12 |
| dangtrinhnt | so, ok, I will send out an email asking for time change after this meeting. | 02:13 |
| engel75 | but I will not be able to attend that often anyway | 02:13 |
| zhurong_phone | can we set another poll for this | 02:13 |
| dangtrinhnt | zhurong_phone, sure | 02:13 |
| dangtrinhnt | engel75, no worries, there are still a couple US-based guys | 02:14 |
| dangtrinhnt | ok, should we move on? | 02:14 |
| zhurong_phone | I think so | 02:14 |
| dangtrinhnt | #topic Moving telemetry bug tracker to Storyboard: https://review.opendev.org/#/c/651963/ | 02:14 |
| *** openstack changes topic to "Moving telemetry bug tracker to Storyboard: https://review.opendev.org/#/c/651963/ (Meeting topic: openstack telemetry)" | 02:14 | |
| dangtrinhnt | It supposed to finish the last couple weeks but due to the summit, it's delayed. | 02:15 |
| dangtrinhnt | So I'm trying to push it. | 02:15 |
| lxkong | dangtrinhnt: thanks for that | 02:15 |
| engel75 | yes thank you | 02:15 |
| dangtrinhnt | After the migration is done, we could go through the stories and maybe set aside sometime for bug triage, I guess. | 02:16 |
| dangtrinhnt | I think there's not much to talk about this. so let's move to the next topic | 02:16 |
| engel75 | ok | 02:16 |
| dangtrinhnt | #topic Train-1 milestone targets (Jun 03 - Jun 07) | 02:16 |
| *** openstack changes topic to "Train-1 milestone targets (Jun 03 - Jun 07) (Meeting topic: openstack telemetry)" | 02:16 | |
| dangtrinhnt | #link https://releases.openstack.org/train/schedule.html | 02:17 |
| dangtrinhnt | FYI, we will reach Train-1 soon :) | 02:17 |
| dangtrinhnt | I would love to set some goals even small ones | 02:17 |
| dangtrinhnt | So what do you think you would want to accomplish at that milestone? | 02:18 |
| dangtrinhnt | lxkong, zhurong_phone, rafaelweingartne, engel75 | 02:18 |
| lxkong | dangtrinhnt: on aodh side, i will try to finish the auto-healing before T-1 | 02:18 |
| engel75 | would a statement about the event_subsystem be a valid candidate? | 02:18 |
| dangtrinhnt | lxkong, awesome. | 02:18 |
| rafaelweingartne | What about a community decision regarding the event subsystem deprecation? And maybe some new poller or something (if we decide to keep the system)? | 02:19 |
| lxkong | the last part is the notifier | 02:19 |
| dangtrinhnt | engel75, given the amount of time left, I would put that into Train-2 | 02:19 |
| lxkong | do we have other options for now to replace the event_subsystem? | 02:19 |
| engel75 | may I ask why it has to be replaced? | 02:20 |
| zhurong_phone | container metrics and switch oslo.privileps | 02:20 |
| dangtrinhnt | rafaelweingartne, but if you think you can make it on time, we could consider that | 02:20 |
| lxkong | i don't know the history of it's deprecation, if there is not good reason in the current situation, we could get it back | 02:20 |
| dangtrinhnt | engel75, I think what lxkong means is an alternative | 02:20 |
| lxkong | we are also using the notification for billing | 02:21 |
| lxkong | adriant ^^ | 02:21 |
| engel75 | as we do | 02:21 |
| engel75 | together with the pollers | 02:21 |
| dangtrinhnt | engel75, part of it was the feature is never finished | 02:21 |
| adriant | the notification samples are the only way to get accurate samples | 02:21 |
| adriant | for when a resource is created or deleted | 02:22 |
| lxkong | agree | 02:22 |
| adriant | polling is useful, but it will always be behind | 02:22 |
| engel75 | it will | 02:22 |
| adriant | and even means if a resource is only active within the polling period, we can't bill it | 02:22 |
| engel75 | a combination is the way to go imho | 02:22 |
| adriant | since the pollster will miss it | 02:22 |
| lxkong | so if there is no good candidate option, we could considering bringing that back and remove the deprecation msg. | 02:22 |
| rafaelweingartne | lxkong: the reason we got was that people wanted to shrink the code. However, there was not a clear picture of the benefits and good alternatives in place. | 02:23 |
| dangtrinhnt | engel75, rafaelweingartne, adriant, lxkong, https://github.com/openstack/ceilometer/commit/8a0245a5b3e1357d35ad6653be37ca01176577e4 | 02:23 |
| dangtrinhnt | so I guess the next topic will be discussed now | 02:23 |
| rafaelweingartne | yes | 02:23 |
| dangtrinhnt | ok, so again, I would like to set the targets for Train-1 milestone | 02:24 |
| lxkong | rafaelweingartne: does the current behavior satisfy your requirement? | 02:24 |
| lxkong | if not, could you please create a story after we have storyboard, and we could discuss how to improve there | 02:25 |
| engel75 | in our environment some nofitications are "missed" that's why we use the pollsters to make sure to get all resources | 02:25 |
| rafaelweingartne | yes it does, but we will need to add/extend a few things to fully deliver what we need. engel75 is more suitable to present the use cases. | 02:25 |
| engel75 | by "our" I mean rafaelweingartne and mine | 02:25 |
| rafaelweingartne | There are these issues for instance, but the idea is to work to fix them | 02:25 |
| dangtrinhnt | lxkong, rafaelweingartne, engel75 so you want us to have it in Train-1? | 02:26 |
| engel75 | would be great - at least a statement? | 02:26 |
| rafaelweingartne | Do you mean a statement regarding the deprecation? | 02:26 |
| lxkong | i'm not sure things will be clear before T-1, but let's be pessimistic and make it for T-2 | 02:26 |
| engel75 | to show it is maintained again | 02:26 |
| dangtrinhnt | lxkong, +1 | 02:27 |
| rafaelweingartne | statement, or a decision regarding the deprecation | 02:27 |
| engel75 | ok | 02:27 |
| dangtrinhnt | engel75, it could be right after this meeting | 02:27 |
| engel75 | ok great | 02:27 |
| dangtrinhnt | engel75, rafaelweingartne, like lxkong suggested, finish the feature in T-2, but announce it at T-1, ok? | 02:27 |
| engel75 | perfect | 02:28 |
| engel75 | +1 | 02:28 |
| dangtrinhnt | awesome, anything else?\ | 02:28 |
| dangtrinhnt | adriant, zhurong_phone, lxkong? | 02:28 |
| lxkong | dangtrinhnt: not sure if you missed the task zhurong_phone mentioned just now | 02:28 |
| dangtrinhnt | put it on the etherpad already | 02:28 |
| dangtrinhnt | https://etherpad.openstack.org/p/telemetry-meeting-agenda | 02:29 |
| lxkong | good :-) | 02:29 |
| dangtrinhnt | :) | 02:29 |
| adriant | dangtrinhnt: there was some issues around a cumulative cpu usage feature lxkong was using that is now gone | 02:29 |
| rafaelweingartne | I would just like to clarify what you mean by feature, dangtrinhnt. Do you mean a statement regarding the event system? Or, a proposal of an actual new feature in Ceilometer regarding the event system? | 02:29 |
| zhurong_phone | thanks dangtrinhnt | 02:29 |
| dangtrinhnt | adriant, cpu_util? | 02:29 |
| adriant | yeah, based on the transformer | 02:30 |
| adriant | which was removed | 02:30 |
| dangtrinhnt | rafaelweingartne, I mean making it work | 02:30 |
| lxkong | yeah, cpu_util, there are some people asking for that | 02:30 |
| adriant | it is needed for autoscaling | 02:30 |
| lxkong | or for an alternative | 02:30 |
| adriant | ^ | 02:30 |
| rafaelweingartne | dangtrinhnt, ah. Sure, got it. | 02:30 |
| dangtrinhnt | rafaelweingartne, :) | 02:30 |
| zhurong_phone | now in function test, using cpu :() | 02:30 |
| adriant | the feature was removed because it was meant to be able to be queried from gnocchi but lxkong has said he can't figure out how to get the same type of numbers/data | 02:31 |
| lxkong | and i failed to manage to get any useful suggestion from Gnocchi team. | 02:32 |
| dangtrinhnt | adriant, lxkong, zhurong_phone, gnocchi is out of our hands so I guess we can either bring it back to OpenStack and maintain it ourselves | 02:32 |
| lxkong | i have a feeling we may bring that back if there are a lot more people asking for that | 02:32 |
| lxkong | as a short term plan | 02:32 |
| engel75 | yes we should try that! | 02:32 |
| dangtrinhnt | lxkong, let's create a discussion on the ML | 02:33 |
| zhurong_phone | we also want to bring ceilometer api back | 02:33 |
| lxkong | i hope there could be some people jump out and say: it's very easy to achieve that in Gnocchi :-) | 02:33 |
| rafaelweingartne | but, this process(Gnocchi) would take some bureaucratic steps to re-introduce the project to OpenStack foundation, right? | 02:33 |
| adriant | zhurong_phone: potentially, maybe even as just a wrapper around gnocchi | 02:33 |
| dangtrinhnt | okie guys, way back into love :) | 02:34 |
| rafaelweingartne | which means that it is something for a medium/long term plan | 02:34 |
| dangtrinhnt | rafaelweingartne, sure | 02:34 |
| dangtrinhnt | that could be possible | 02:34 |
| dangtrinhnt | if we can find some champion taking care of it | 02:34 |
| dangtrinhnt | otherwise it could properly be a burden in the future | 02:35 |
| lxkong | dangtrinhnt: let's discuss in mailing list first, see if there is an easy answer | 02:35 |
| engel75 | I don't see any alternative to gnocchi right now | 02:35 |
| dangtrinhnt | lxkong, +1 | 02:36 |
| lxkong | engel75: are you using Gnocchi now? | 02:36 |
| engel75 | lxkong, +1 | 02:36 |
| engel75 | yes | 02:36 |
| lxkong | or plan to use that in the near future | 02:36 |
| lxkong | ok | 02:36 |
| engel75 | in production | 02:36 |
| dangtrinhnt | engel75, awesome | 02:36 |
| engel75 | it scales very well | 02:36 |
| engel75 | on SSDs... | 02:36 |
| dangtrinhnt | engel75, you can help lxkong on the cpu_util | 02:36 |
| dangtrinhnt | :) | 02:37 |
| engel75 | I need to get it explained but yes I can try to | 02:37 |
| engel75 | please send me an email after the meeting | 02:37 |
| lxkong | engel75: thanks, please reply the email after you see that | 02:37 |
| engel75 | sure | 02:37 |
| dangtrinhnt | engel75, if you can, please cc the openstack-discuss ML as well so others can follow | 02:38 |
| engel75 | ok will do so | 02:38 |
| dangtrinhnt | with [telemetry] prefix :) | 02:38 |
| dangtrinhnt | engel75, great thanks | 02:38 |
| dangtrinhnt | ok, anything else? | 02:38 |
| dangtrinhnt | zhurong_phone, adriant? | 02:39 |
| zhurong_phone | nup | 02:39 |
| adriant | all good :) | 02:39 |
| dangtrinhnt | ok | 02:39 |
| dangtrinhnt | #topic Telemetry roadmap cont. https://etherpad.openstack.org/p/telemetry-train-roadmap | 02:40 |
| *** openstack changes topic to "Telemetry roadmap cont. https://etherpad.openstack.org/p/telemetry-train-roadmap (Meeting topic: openstack telemetry)" | 02:40 | |
| dangtrinhnt | ok, I guess we have Train-1 targets | 02:40 |
| dangtrinhnt | but I also would love to discuss our big plan for Train, AKA, the Roadmap | 02:40 |
| adriant | dangtrinhnt: sorry just remembered, there may be some missing pollsters we can add, such as those for Magnum and I think there are some missing ones for Octavia | 02:41 |
| dangtrinhnt | ah, okie | 02:41 |
| rafaelweingartne | adriant: we have been discussing that | 02:41 |
| rafaelweingartne | and will probably implement it | 02:41 |
| adriant | would be good to do a general overview of what services are missing pollsters/event watching | 02:41 |
| dangtrinhnt | adriant, so when do you think we can have those features? | 02:41 |
| engel75 | yes we are happy to help with those pollsters | 02:41 |
| dangtrinhnt | rafaelweingartne, enge75, great | 02:41 |
| lxkong | i suggest we begin with the ones we care about, e.g. for us the Magnum and Octavia | 02:42 |
| dangtrinhnt | lxkong, +1 | 02:43 |
| rafaelweingartne | lxkong, +1 | 02:43 |
| dangtrinhnt | adriant, lxkong, what timeline do you think is doable for those? | 02:43 |
| zhurong_phone | +1 | 02:43 |
| lxkong | T-2 or T-3, adriant? | 02:43 |
| adriant | probably yeah | 02:44 |
| lxkong | should be an easy one because we already have that in our production | 02:44 |
| adriant | I don't know how much I can dedicate to telemetry for code work, but would gladly code review | 02:44 |
| dangtrinhnt | adriant, lxkong, how were those pieces of code licenced? I would avoid any commercial licenced code | 02:45 |
| dangtrinhnt | adriant, it's great as well. | 02:45 |
| rafaelweingartne | lxkong: also, do you have it in Stein or Rocky release? | 02:45 |
| lxkong | dangtrinhnt: don't worry, all apache 2.0 :-) | 02:46 |
| lxkong | rafaelweingartne: no, we are using a very old version ceilometer | 02:46 |
| dangtrinhnt | lxkong, awesome! | 02:46 |
| engel75 | lxkong, would you mind sharing your extensions regarding those pollsters? | 02:46 |
| * adriant is looking at our patch for magnum pollster now | 02:46 | |
| dangtrinhnt | rafaelweingartne, engel75, we have 14m left, I guess lxkong and adriant can propose some patches for review | 02:46 |
| engel75 | we have to introduce a Octavia pollsters the next couple of weeks | 02:46 |
| rafaelweingartne | lxkong: so there would be an effort to push forward the code (if the structure/design of the code has changed over time) | 02:47 |
| lxkong | i will see if i could submit those code in T for review | 02:47 |
| adriant | not very much code, but yes, easy to share and get working for newer versions of ceilometer | 02:47 |
| rafaelweingartne | cool | 02:47 |
| dangtrinhnt | guys, awesome! | 02:47 |
| lxkong | dangtrinhnt: please make it for T-3 and allocate magnum pollster task to me | 02:47 |
| engel75 | so regarding the roadmap in the long term - we should align with cloudkitty? | 02:48 |
| dangtrinhnt | lxkong, adriant, engel75, rafaelweingartne, \m/ rock! | 02:48 |
| engel75 | minute based billing :) | 02:48 |
| dangtrinhnt | engel75, could be possible | 02:49 |
| dangtrinhnt | for that, I would send an discussion email to the ML and let figure that out, I will put that as an option | 02:49 |
| engel75 | we just have to make sure not event is missed or if one is missed there is some sort of pollster to get it after a couple of seconds | 02:49 |
| engel75 | ok | 02:49 |
| dangtrinhnt | +1 | 02:49 |
| dangtrinhnt | ok, 10m left | 02:50 |
| dangtrinhnt | so for the roadmap, do you think puting back some features that have use cases a possible option? | 02:50 |
| rafaelweingartne | I would say so | 02:51 |
| dangtrinhnt | lxkong, zhurong_phone, adriant, rafaelweingartne, engel75 | 02:51 |
| lxkong | yep, if that's the best option we have at the moment | 02:51 |
| rafaelweingartne | I would also say that we need a clear perspective on how we handle things. For instance, what can be deprecated and removed? broken features, features with a clear and better alternatives, and so on | 02:51 |
| adriant | dangtrinhnt: yes, for cpu_util maybe, but the issue why it was removed: "Transformers cannot work correctly on multiple nodes without workload partitioning, which has been removed." | 02:52 |
| adriant | https://review.opendev.org/#/c/580709/ | 02:52 |
| adriant | so that may end up a rabbit hole | 02:52 |
| dangtrinhnt | rafaelweingartne, +1 | 02:52 |
| adriant | we need something 'like' it, but maybe bringing it back isn't the answer | 02:52 |
| dangtrinhnt | adriant, makes sense | 02:52 |
| rafaelweingartne | adriant: maybe, we could bring back the feature, but with a new design/implementation | 02:53 |
| dangtrinhnt | or alternatives. We will have to put more effort investigating that. | 02:53 |
| adriant | rafaelweingartne: that's pretty much what I mean | 02:53 |
| lxkong | i prefer we deprecate something unless we have a feature parity alternative, something like 'not work', 'covered by other projects' are not good reasons | 02:53 |
| dangtrinhnt | rafaelweingartne, agree | 02:54 |
| dangtrinhnt | lxkong, +1 | 02:54 |
| rafaelweingartne | lxkong, +1 | 02:54 |
| dangtrinhnt | ok good | 02:54 |
| dangtrinhnt | anything else? | 02:54 |
| dangtrinhnt | 5m left | 02:54 |
| lxkong | not from me | 02:54 |
| engel75 | what a bout the documentation | 02:55 |
| dangtrinhnt | engel75, what do you mean? | 02:55 |
| engel75 | it is not the most "complete" one | 02:55 |
| dangtrinhnt | missing, not correct? | 02:55 |
| dangtrinhnt | ah ok | 02:55 |
| dangtrinhnt | we absolutely need to correct and improve the documentations | 02:56 |
| dangtrinhnt | I will put it on the todos | 02:56 |
| engel75 | I will try to find missing parts | 02:56 |
| dangtrinhnt | Stories I meant :) | 02:56 |
| dangtrinhnt | thanks | 02:56 |
| dangtrinhnt | I guess we can complete it in T-1 | 02:56 |
| dangtrinhnt | 3m left | 02:57 |
| dangtrinhnt | anything else? | 02:57 |
| engel75 | I never contributed to some Openstack documentation but I could try to improve it from a operator perspective | 02:57 |
| adriant | engel75: from an operators perspective is sorely needed in the docs | 02:57 |
| engel75 | I mean the ceilometer part | 02:57 |
| dangtrinhnt | engel75, that is awesome. | 02:58 |
| lxkong | engel75: that will be very helpful | 02:58 |
| rafaelweingartne | adriant, +1 | 02:58 |
| dangtrinhnt | if you need any guideline for that, let me know | 02:58 |
| zhurong_phone | engel75: thanks | 02:58 |
| dangtrinhnt | oke, 2m left | 02:58 |
| engel75 | dangtrinhnt, ok I will send you an email to get help with it | 02:58 |
| dangtrinhnt | engel75 +1 | 02:59 |
| dangtrinhnt | Ok, I think we're good for now. Anything else you would like to discuss, please send an email to the ML | 02:59 |
| engel75 | ok | 02:59 |
| dangtrinhnt | Thanks everyone for participating in this great meeting. | 03:00 |
| dangtrinhnt | #endmeeting | 03:00 |
| *** openstack changes topic to "#openstack-telemetry is OpenStack Telemetry | http://wiki.openstack.org/Telemetry" | 03:00 | |
| openstack | Meeting ended Thu May 9 03:00:24 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 03:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-09-02.00.html | 03:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-09-02.00.txt | 03:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-09-02.00.log.html | 03:00 |
| lxkong | thank you | 03:00 |
| lxkong | have a good day/night, guys | 03:00 |
| engel75 | thank you guys | 03:00 |
| zhurong_phone | thanks, bey everyone | 03:01 |
| dangtrinhnt | bye :) | 03:01 |
| rafaelweingartne | Bye guys, have a good night/day (engel75) | 03:01 |
| dangtrinhnt | For those who cannot join the meeting today, please look at the meeting minutes http://eavesdrop.openstack.org/meetings/openstack_telemetry/2019/openstack_telemetry.2019-05-09-02.00.html | 03:01 |
| engel75 | rafaelweingartne, thank you :) | 03:01 |
| dangtrinhnt | engel75, rafaelweingartne, welcome to the team :) | 03:02 |
| engel75 | thank you :) | 03:06 |
| *** psachin has joined #openstack-telemetry | 03:34 | |
| *** lpetrut has joined #openstack-telemetry | 03:53 | |
| openstackgerrit | Jake Yip proposed openstack/python-aodhclient master: allow an empty string to unset options https://review.opendev.org/656613 | 04:06 |
| *** lpetrut has quit IRC | 04:18 | |
| *** ivve has quit IRC | 04:45 | |
| *** zhurong_phone has quit IRC | 05:21 | |
| joadavis | engel75: "I don't see any alternative to gnocchi right now" There are alternatives, such as https://wiki.openstack.org/wiki/Ceilosca | 05:29 |
| openstackgerrit | Merged openstack/python-aodhclient master: allow an empty string to unset options https://review.opendev.org/656613 | 05:44 |
| *** ivve has joined #openstack-telemetry | 05:49 | |
| dangtrinhnt | joadavis, thanks for the information. | 05:50 |
| dangtrinhnt | we will put it to the discussioni | 05:50 |
| dangtrinhnt | @all, I just updated the contributors list on #link https://wiki.openstack.org/wiki/Telemetry | 05:50 |
| dangtrinhnt | let me know if I'm missing someone. | 05:50 |
| dangtrinhnt | Thanks. | 05:50 |
| openstackgerrit | zhongshengping proposed openstack/ceilometer master: Update Python 3 test runtimes for Train https://review.opendev.org/657932 | 06:27 |
| *** witek has joined #openstack-telemetry | 06:55 | |
| *** tesseract has joined #openstack-telemetry | 07:09 | |
| *** dougsz has joined #openstack-telemetry | 08:13 | |
| *** gmann_pto has joined #openstack-telemetry | 08:59 | |
| openstackgerrit | zhongshengping proposed openstack/ceilometer master: Update Python 3 test runtimes for Train https://review.opendev.org/657932 | 09:36 |
| *** tesseract has quit IRC | 10:40 | |
| *** tesseract has joined #openstack-telemetry | 10:41 | |
| *** tesseract has quit IRC | 10:45 | |
| *** tesseract has joined #openstack-telemetry | 10:45 | |
| *** shardy has quit IRC | 11:27 | |
| *** shardy has joined #openstack-telemetry | 11:27 | |
| *** gmann_pto has quit IRC | 11:50 | |
| *** zigo has quit IRC | 11:59 | |
| *** rafaelweingartne has quit IRC | 12:00 | |
| *** zigo has joined #openstack-telemetry | 12:24 | |
| *** Dantalion has joined #openstack-telemetry | 12:40 | |
| Dantalion | hello I was wondering how to get cpu utilization for instances now that cpu_util metric has been deprecated? | 12:40 |
| openstackgerrit | Merged openstack/python-aodhclient stable/queens: Fixup README https://review.opendev.org/653294 | 13:24 |
| *** tesseract has quit IRC | 13:35 | |
| *** tesseract has joined #openstack-telemetry | 13:35 | |
| *** altlogbot_2 has quit IRC | 13:43 | |
| *** altlogbot_2 has joined #openstack-telemetry | 13:45 | |
| *** psachin has quit IRC | 13:51 | |
| *** tesseract has quit IRC | 14:24 | |
| *** tesseract has joined #openstack-telemetry | 14:50 | |
| *** tesseract has quit IRC | 14:51 | |
| *** tesseract has joined #openstack-telemetry | 14:51 | |
| *** tesseract has quit IRC | 15:01 | |
| *** tesseract has joined #openstack-telemetry | 15:03 | |
| joadavis | Dantalion: For a discussion of cpu_util, check in the meeting minutes from the meeting yesterday - http://eavesdrop.openstack.org/irclogs/%23openstack-telemetry/%23openstack-telemetry.2019-05-09.log.html | 15:06 |
| joadavis | Dantalion: briefly, you currently have a few options - use an older version of Ceilometer, use Gnocchi to aggregate the metric for you, use a different storage backend that will generate the metric for you (such as Ceilosca and Monasca), or pull the data into your own application and do the calculation there. | 15:07 |
| *** tesseract has quit IRC | 15:11 | |
| Dantalion | joadavis: is there any documentation on how to setup Gnocchi to aggregate this metric because when I install devstack with CEILOMETER_BACKEND=gnocchi it is not there | 15:13 |
| *** tesseract has joined #openstack-telemetry | 15:16 | |
| *** tesseract has quit IRC | 15:18 | |
| *** tesseract has joined #openstack-telemetry | 15:20 | |
| Dantalion | joadavis: Or information on how to calculate cpu_util from other ceilometer data would also work | 15:29 |
| joadavis | Dantilion: unfortunately, I don't know (I don't use Gnocchi). Its been a while since I looked at it in Ceilometer, but over in Monasca we can use the cpu.utilization_perc metric we pull from the libvirt plugin. | 15:36 |
| *** ivve has quit IRC | 15:40 | |
| Dantalion | joadavis: Cool yeah I am trying to setup a devstack with Monasca to, I work on Watcher and we would like to have 'known good' devstack setups that help developers verify patches | 15:52 |
| *** tesseract has quit IRC | 16:01 | |
| *** irclogbot_0 has quit IRC | 16:46 | |
| *** irclogbot_1 has joined #openstack-telemetry | 16:47 | |
| *** dougsz has quit IRC | 17:02 | |
| *** shardy has quit IRC | 17:03 | |
| *** ivve has joined #openstack-telemetry | 17:42 | |
| *** jobewan has joined #openstack-telemetry | 19:22 | |
| *** engel75 has quit IRC | 19:26 | |
| *** my_nd has joined #openstack-telemetry | 19:43 | |
| my_nd | hi there! I'm working with gnocchi for metrics of instances and volumes and I have to estimate the amount of disk capacity for storing those metrics in a period of 3 months. Do you have some formula for this? | 19:46 |
| *** witek has quit IRC | 19:57 | |
| *** dasp has quit IRC | 21:52 | |
| *** my_nd has quit IRC | 23:19 | |
| *** jobewan has quit IRC | 23:36 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!