| *** vishalmanchanda has joined #cloudkitty | 04:00 | |
| *** sboyron has joined #cloudkitty | 08:22 | |
| *** sboyron has quit IRC | 08:30 | |
| *** sboyron has joined #cloudkitty | 08:57 | |
| *** vishalmanchanda has quit IRC | 09:18 | |
| *** sboyron has quit IRC | 09:48 | |
| *** mkarpiarz has quit IRC | 10:15 | |
| *** sboyron has joined #cloudkitty | 10:26 | |
| *** Oriz has joined #cloudkitty | 12:19 | |
| *** Oriz has quit IRC | 12:20 | |
| *** rafaelweingartne has joined #cloudkitty | 13:26 | |
| *** rafaelweingartne has joined #cloudkitty | 13:27 | |
| rafaelweingartne | #startmeeting cloudkitty | 14:00 |
|---|---|---|
| openstack | Meeting started Mon Jan 11 14:00:06 2021 UTC and is due to finish in 60 minutes. The chair is rafaelweingartne. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: cloudkitty)" | 14:00 | |
| openstack | The meeting name has been set to 'cloudkitty' | 14:00 |
| rafaelweingartne | Hello guys, happy new year! | 14:00 |
| rafaelweingartne | Roll count | 14:00 |
| priteau | o/ | 14:02 |
| priteau | Happy new year rafaelweingartne! | 14:02 |
| *** mkarpiarz has joined #cloudkitty | 14:04 | |
| rafaelweingartne | priteau: it seems that it is just us today | 14:05 |
| priteau | And maybe mkarpiarz? | 14:05 |
| mkarpiarz | Hi, I'm here! | 14:06 |
| rafaelweingartne | hmm... mkarpiarz: are you going to participate in the meeting? | 14:06 |
| rafaelweingartne | ah.. cool! | 14:06 |
| rafaelweingartne | #topic Review priorities | 14:06 |
| *** openstack changes topic to "Review priorities (Meeting topic: cloudkitty)" | 14:06 | |
| rafaelweingartne | We have reviewed and merged some patches in the past week. | 14:06 |
| rafaelweingartne | Do you guys have some review priorities for us to focus on? | 14:07 |
| mkarpiarz | Nothing in the pipeline from my side. | 14:08 |
| priteau | Nothing special from me either. | 14:09 |
| mkarpiarz | But I was trying to assign priorities to tasks from our PTG meeting. | 14:09 |
| mkarpiarz | And also add tasks that could kickstartdevelopment for each section. | 14:09 |
| rafaelweingartne | I see | 14:11 |
| mkarpiarz | My idea was to try and focus on ideas we came up during the PTG. | 14:11 |
| rafaelweingartne | I agree | 14:12 |
| rafaelweingartne | I confess that I have not had time to address those issues | 14:12 |
| priteau | mkarpiarz: When you said "last 4 main points" in your email, did you mean top level items in the etherpad? | 14:12 |
| rafaelweingartne | I have been working lately on other components only; what I an able to do for now is to review patches only | 14:12 |
| mkarpiarz | 4 bottom ones | 14:12 |
| priteau | i.e. 1) Stop processing resources that have been deleted/removed and do not have data anymore, 2) Reprocessing API?, etc.? | 14:13 |
| mkarpiarz | Yep | 14:13 |
| priteau | OK | 14:13 |
| priteau | So one question, for item 3 "Cleanups of the database to remove old/legacy unwanted data objects", are we actually talking about dataframes? | 14:13 |
| rafaelweingartne | mkarplarz: I guess, you as the contributor should have the ability to choose where you want to work | 14:14 |
| rafaelweingartne | priteau: I thought that this issue refered to the that table where we have the reference for the projects to be processed | 14:14 |
| priteau | Maybe it does, that's why I am asking :) | 14:15 |
| rafaelweingartne | that table only grows, and as projects/resources get deleted, they are not cleaned up. Therefore, CloudKitty still processes projects that do not have usage data anymore | 14:15 |
| priteau | I thought it was up to fetchers to decide what projects to process | 14:17 |
| rafaelweingartne | but the problem is that they always process all of them | 14:18 |
| rafaelweingartne | them=all available in the database and that were not processed in that timeframe | 14:18 |
| rafaelweingartne | therefore, the projects/resources table to be processed only grows, and slows down the system (Cloudkitty) | 14:19 |
| priteau | Interesting, I didn't know it worked like that | 14:19 |
| rafaelweingartne | I do not know the initial design, but that is how it is working right now | 14:19 |
| priteau | So if you use the keystone fetcher, start rating on a project, then remove the cloudkitty rating role from that project, it is still processed? | 14:19 |
| rafaelweingartne | then, the fetcher fetches the usage data from the backend (e.g. gnocchi) for each project/or resource in that table | 14:19 |
| rafaelweingartne | priteau: as far as we have seen yes, because cloudkitty will collect data from gnocchi | 14:20 |
| priteau | you mean the collector | 14:20 |
| rafaelweingartne | and there is no access control there with respect to project | 14:20 |
| rafaelweingartne | I mean, that I recall that Gnocchi is doing | 14:21 |
| rafaelweingartne | I did not test removing a role, but we noticed that happening with delete/removed projects | 14:21 |
| rafaelweingartne | they are still being processed, even though there is no data in Gnocchi | 14:21 |
| priteau | I would say it depends on the fetcher being used | 14:22 |
| rafaelweingartne | We noticed this with Keystone fetcher | 14:22 |
| rafaelweingartne | oh, no, I mean Gnocchi | 14:22 |
| priteau | OK, for Gnocchi fetcher it makes less sense that it would work like this | 14:23 |
| rafaelweingartne | yes, we do use Gnocchi | 14:23 |
| rafaelweingartne | backend = gnocchi | 14:23 |
| priteau | Rather than clean up old projects via API we may want to change the fetcher to update the list? | 14:23 |
| rafaelweingartne | yes, exactly that would be even more interesting | 14:24 |
| rafaelweingartne | we just could not figure out a method to check that | 14:24 |
| rafaelweingartne | if a resource/project was deleted in Gnocchi for instance | 14:24 |
| rafaelweingartne | that is why one of the ideas was to enable this process via an API call | 14:24 |
| priteau | If the metrics are deleted you won't be able to find any data for the project in Gnocchi, but we could detect that and mark the project as inactive in CloudKitty or delete the row | 14:26 |
| rafaelweingartne | ah | 14:26 |
| rafaelweingartne | that would be a good idea | 14:26 |
| rafaelweingartne | inactive project | 14:26 |
| rafaelweingartne | We did not think that | 14:26 |
| openstackgerrit | Merged openstack/cloudkitty-tempest-plugin master: Use tempest's ServiceClients rather than Manager https://review.opendev.org/c/openstack/cloudkitty-tempest-plugin/+/767714 | 14:27 |
| rafaelweingartne | I could work on that this week | 14:28 |
| mkarpiarz | Sounds good to me! | 14:28 |
| priteau | The advantage of marking it as inactive is that you would keep the record and be able to see when it was last updated | 14:29 |
| priteau | Could be useful for debugging | 14:29 |
| rafaelweingartne | exactly | 14:29 |
| rafaelweingartne | I like this solution better | 14:29 |
| mkarpiarz | Cool, so sounds like we have a plan for this point. | 14:32 |
| rafaelweingartne | to give you an idea of the problem, we have 337 active projects, and in Cloudkitty storage states, there are 990 projects being processed | 14:32 |
| priteau | I understand, it must slow down processing quite a bit | 14:32 |
| rafaelweingartne | yes, it does | 14:32 |
| priteau | "Allow for a free USAGE consumption (e.g. First 1GB free, then 3 Cent/GB)" | 14:34 |
| priteau | Can't you do that with thresholds? | 14:34 |
| rafaelweingartne | yes, you can | 14:35 |
| rafaelweingartne | but there was a bug | 14:35 |
| rafaelweingartne | I had a patch for that | 14:35 |
| priteau | Also, remember that you can write custom pyscripts rules (although I've never tried it) | 14:35 |
| rafaelweingartne | https://review.opendev.org/c/openstack/python-cloudkittyclient/+/752956 | 14:35 |
| rafaelweingartne | exactly | 14:36 |
| priteau | "Reprocessing API?" > I think this is important. When setting up CloudKitty and tuning rating rules, it's a pain to have to clear SQL and storage backend | 14:36 |
| rafaelweingartne | yes exactly | 14:36 |
| rafaelweingartne | that is where this proposal comes from | 14:36 |
| rafaelweingartne | I do not have time for this month to work on this, but I could devote some time, maybe next month | 14:37 |
| mkarpiarz | And what do you think has to be done? Maybe someone else can pick this up? | 14:37 |
| rafaelweingartne | first, a specification needs to be written down. I have not put much thinking on this yet | 14:38 |
| mkarpiarz | I was going to start working on custom mutators as I feel this is important (especially for Prometheus) but can looks into something else instead. | 14:39 |
| priteau | Yes, design first for this as it involves new API | 14:39 |
| rafaelweingartne | that would be interesting, either one of them this reprocessing API, or the custom mutators | 14:39 |
| mkarpiarz | Ah, it sounds like reprocessing API is above my abilities, so I'll stick with mutators for now. ;) | 14:40 |
| rafaelweingartne | :) | 14:41 |
| mkarpiarz | Hopefully we will have some new reviews to discuss during the next meeting then. | 14:42 |
| rafaelweingartne | exactly | 14:43 |
| mkarpiarz | Should we move on to the next point on the agenda of this meeting? | 14:44 |
| priteau | We need to keep an eye on the release schedule | 14:45 |
| rafaelweingartne | yes | 14:46 |
| rafaelweingartne | I will ask for your help when the time comes | 14:46 |
| priteau | If we want to ship new APIs with client support, client release is March 11 | 14:46 |
| rafaelweingartne | this will be my first release | 14:46 |
| priteau | Making the release is the easy part | 14:46 |
| priteau | It's writing the code in time that's the hard part :P | 14:46 |
| mkarpiarz | xD | 14:46 |
| rafaelweingartne | :) | 14:47 |
| rafaelweingartne | I will open for general topics now | 14:47 |
| rafaelweingartne | https://review.opendev.org/c/openstack/python-cloudkittyclient/+/752956 | 14:47 |
| rafaelweingartne | ops | 14:47 |
| rafaelweingartne | wrong paste | 14:47 |
| rafaelweingartne | #topic AOB | 14:48 |
| *** openstack changes topic to "AOB (Meeting topic: cloudkitty)" | 14:48 | |
| mkarpiarz | Nothing on my side. | 14:49 |
| priteau | Nothing special from me either. | 14:50 |
| rafaelweingartne | Great | 14:50 |
| rafaelweingartne | Thank you guys for participating. Have a nice week. | 14:50 |
| rafaelweingartne | Thank you guys for participating. Have a nice week. | 14:50 |
| rafaelweingartne | #endmeeting | 14:50 |
| *** openstack changes topic to "Rating component for OpenStack https://wiki.openstack.org/wiki/CloudKitty" | 14:50 | |
| openstack | Meeting ended Mon Jan 11 14:50:57 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:51 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/cloudkitty/2021/cloudkitty.2021-01-11-14.00.html | 14:51 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cloudkitty/2021/cloudkitty.2021-01-11-14.00.txt | 14:51 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/cloudkitty/2021/cloudkitty.2021-01-11-14.00.log.html | 14:51 |
| priteau | Thanks rafaelweingartne, you too | 14:52 |
| mkarpiarz | Thanks, guys! | 15:02 |
| *** rafaelweingartne has quit IRC | 15:06 | |
| jopdorp | sorry for missing the meeting! | 16:42 |
| *** openstackgerrit has quit IRC | 17:37 | |
| *** sboyron has quit IRC | 18:18 | |
| *** sboyron has joined #cloudkitty | 18:19 | |
| *** gmann is now known as gmann_afk | 19:25 | |
| *** gmann_afk is now known as gmann | 21:13 | |
| *** fresta has quit IRC | 21:37 | |
| *** fresta has joined #cloudkitty | 21:45 | |
| *** sboyron has quit IRC | 22:11 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!