14:01:01 #startmeeting cloudkitty 14:01:01 Meeting started Mon Jun 23 14:01:01 2025 UTC and is due to finish in 60 minutes. The chair is rafaelweingartner. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:01 The meeting name has been set to 'cloudkitty' 14:01:03 Hello guys! 14:01:09 Roll count 14:01:14 \o 14:01:59 hello 14:02:24 :) 14:02:42 Sorry for our past meeting, I was in so many different things, and I was not able to make it. 14:06:20 I couldn't attend several time recently, apologies as well 14:06:27 No worries :) 14:06:29 I guess we can start 14:07:30 #topic vPTG OCtober/2025 14:07:40 We will have our vPTG in October. I have already signed us up for it 14:09:29 Cool 14:10:45 Moving on... 14:10:48 #topic Target reviews 14:10:55 StackHPC had internal discussion for CloudKitty recently and it would be nice to share our thoughts 14:11:20 Sure, can we do after the other topics? 14:11:29 I guess it is only us here 14:11:44 If you wish, you can share your ideas/thoughts now then 14:11:50 Yeah sure, I meant 'at the vPTG' 14:11:57 Sorry I wasn't being clear 14:12:09 sh 14:12:11 ah 14:12:11 sure 14:12:16 go ahead then about the vPTG 14:12:42 We can return to our other topics afterwards 14:13:43 Ah what I was saying is just vPTG will be a nice opportunity share our discussion with you 14:14:09 and it would be better to be shared there because it's just us for now 14:14:41 So, we can move on to target reviews 14:15:09 agreed =) 14:18:12 ok, resuming the target reviews 14:18:40 We have #link https://review.opendev.org/c/openstack/cloudkitty/+/876643, which you already reviewed! Thanks for that. 14:19:03 This patch is ready for merge, and it has been in the making for quite some time now. I hope we can get it merged for our next major release. 14:19:51 That would be really nice as it can make quoting a lot flexible 14:20:16 :) 14:20:26 yes, we for sure are eager to see that merged 14:22:49 moving on... 14:23:02 we have #link https://review.opendev.org/c/openstack/cloudkitty/+/946330, which we are waiting for the author response. 14:23:19 zigo: are you there. I guess that one is from you, right? 14:23:32 I am. How amy I help ? 14:23:42 Oh. 14:23:47 the patch #link https://review.opendev.org/c/openstack/cloudkitty/+/946330, that is from your side, right? 14:23:52 I'm lagging on that one, not sure what the error is in the CI. 14:24:04 I'll try to find time to fix, sorry. 14:24:07 Can we please get some eyes from core members on https://review.opendev.org/c/openstack/cloudkitty-specs/+/951147 ? 14:24:08 ok, thanks! 14:24:44 Oh I see we already got some, so thanks. 14:24:57 As I get everyone here ... any clue if the reprocessing API can work with a data stream rather than an index? Or should we attempt to contribute the feature ? 14:25:36 zigo: what do you mean with that? 14:26:00 The reprocessing API is broken with a data stream, it seems. 14:26:09 But never mind, sorry for disturbing the meeting ! :) 14:26:10 zigo: about #link https://review.opendev.org/c/openstack/cloudkitty/+/946330, if you have problems to update the patch, let me know. Then I can try to help you. 14:26:20 Thanks. 14:27:53 regarding the "data stream" support in the reprocessing API, I guess you can ping me in the mailing list with more data, then I can check. I do not get what you mean with "data stream". The APi takes "scope_ids", which can be a list. The HTTP method is POST. 14:28:38 data stream vs index in Elasticsearch. 14:29:11 Indeed, I need to investigate further. 14:29:15 ok 14:29:21 because for the workflow that is transparent 14:29:25 we are just using the drivers 14:29:58 I mean, if the driver for ElasticSearch/OpenSearch support, for the reprocessign workflow it would be transparent; meaning, the workflow does not need to care much about it. 14:34:03 moving on... 14:34:18 #link https://review.opendev.org/c/openstack/cloudkitty-specs/+/951147, we have a new proposal for a new storage backend for CloudKitty 14:34:56 I have reviewed it, and there are one detail regarding the features supported by the driver 14:35:08 for instance, there is the custom_usage feature in the usage report 14:35:30 and also, the support for reprocessing workflow. Looking at the code, it does not seem to support these two workflows/features 14:35:57 If that is a limitation, it would need to be properly highlighted in the spec, and then documented and a proper exception be thrown in such cases. 14:37:34 for instance, looking at the following #link https://review.opendev.org/c/openstack/cloudkitty/+/950868/5/cloudkitty/storage/v2/loki/__init__.py#141, we see the author showing that it is not possible to delete an entry. However, how would that play with the reprocessing workflow then? 14:39:01 that is what I got by the menssage in the code, but I did not check to see if it would be possible to delete the datapoint from Loki if needed (e.g. to implement the reprocessing workflow) 14:52:08 All of these points should be addressed in the spec 14:52:20 Ok noted will pass this information to Juan 14:52:22 let me know, as soon as we have an updated version of the spec 14:52:26 thanks!!! 14:52:28 ACK 14:52:48 moving on.. 14:52:52 #topic Open floor 14:53:04 if somebody else has another topics, please let us know 14:55:51 If there is nothing else, we can close for today 14:56:06 thank you all for participating. Have a nice week! 14:56:21 Thanks you too 14:57:00 #endmeeting