14:00:17 #startmeeting cloudkitty 14:00:17 Meeting started Mon Oct 31 14:00:17 2022 UTC and is due to finish in 60 minutes. The chair is rafaelweingartner. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:17 The meeting name has been set to 'cloudkitty' 14:00:21 Roll count 14:00:45 Hi! 14:01:08 Hello Mariusz 14:01:14 Is Etherpad offline for you too? 14:01:37 Hello. 14:01:39 I am in another meeting, I may be slow to reply today. 14:01:45 Service Unavailable 14:01:53 :( same here then 14:02:55 Same here. 14:04:47 I do not have the topics for the meeting :( 14:05:05 they were already organized in etherpad, but I do not have them here with me... 14:05:10 shall we postpone this meeting then? 14:05:56 rafaelweingartner: You have your summary email 14:06:02 That could be enough to review 14:06:24 Yes, it might be. Let me grab it 14:06:51 It is not the same though 14:07:04 So, to start the discussions. About the ES support. 14:07:29 Kolla-ansible is moving from ElasticSearch to OpenSearch. Therefore, we need to evaluate if this can have an impact in CloudKitty. Most certainly it will impact people using ES as the backend 14:07:57 We are not using ES for CloudKitty. Therefore, we might not be the best one to comment on this. What do you guys think? 14:08:12 When I say "we", I mean, my side here, and not the community itself 14:09:44 I only now started testing with ES 7 as a backend, so there is not much I can add to the discussion yet. 14:10:56 I'm guessing users will want a way to move their data from ElasticSearch to OpenSearch. 14:11:29 But maybe we should simply tell them to use the reprocessing API. 14:12:37 rafaelweingartner: Have you tested reprocessing with the ES backend? 14:13:26 If not, my test environemnt is pretty much set for this. 14:13:51 (so I can do this) 14:16:26 Hopefully OpenSearch APIs remain compatible with ES 7 (at least for a while). 14:20:17 mkarpiarz: No, I have not tested with ES 14:20:59 I would say that the migration path is going to be provided by Kolla-ansbile already, isn't it? 14:21:12 Yes, it will 14:21:21 Ah, nice! 14:21:32 The data will be copied from ES to OS 14:22:29 So, we do not need to worry about that. However, we need to think about the support message we want to have 14:22:47 if we want to support only OS, we need to have a deprecation warning this release, I guess 14:25:08 Well, Kolla Ansible will drop Elasticsearch in Zed, so we won't really be aligned with them 14:25:15 The sooner the better really. 14:25:35 That is why it would be interesting to have a message as soon as possible 14:25:54 we cannot/should not remove support in Antelope, as we should provide at least one release of warning 14:26:22 Merged openstack/cloudkitty master: Validates the period compatibility of reprocessing dates https://review.opendev.org/c/openstack/cloudkitty/+/861807 14:27:27 Do you want one of us to take action for adding deprecation notice? 14:27:56 I can do so. We just need to agree on the matter, I guess 14:28:42 If we agree, I think that the next steps is (i) add the deprecation noticed, (ii) rename the drivers (or change them to OS), (iii) remove support to ES 14:28:48 Or something similar 14:30:12 If the API is the same, is it really needed to formally drop support? Or just say that it isn't actively tested anymore (though it may still work) 14:31:17 Because, if we have a library, we could replace the in-house client that we have for the library, which can in turn make it incompatible with ES 14:31:53 I understand, but is that really needed? I thought we agreed during PTG that we would keep using HTTP requests 14:32:08 To avoid compatibility issues with the library 14:32:48 I see, we agreed if the library would not bring much benefits. However, I thought that we wuld first evaluate what is the difference between using the library or not 14:36:28 Should I draft something about deprecating (but keeping unofficial support for) ES7? 14:36:43 I guess so 14:36:53 If you can, that would help a lot :) 14:37:50 Yes, I think it makes sense to stick to requests for now. We can introduce the OS client later on if we want to. 14:44:23 +1 14:45:46 So, moving on 14:45:54 what about Monasca? Should we do the same for Monasca? 14:46:38 I think so. Unless someone opposes. 14:46:50 I agree with this movemente 14:47:01 I mean, with this process 14:47:34 Do we know whether there are people using CloudKitty with Monasca? 14:47:55 I do not know anybody 14:48:05 I think we should email the mailing list to ask for feedback 14:48:13 That's the usual approach done by Kolla 14:48:17 Ah, goos idea! 14:48:23 *good 14:48:44 ok 14:48:47 I will do so 14:50:33 I would like to discuss Gnocchi, but that might be a longer discussion. Therefore, I will add it to our next meeting 14:50:45 So, before we close it for today. Do you guys have something to add? 14:51:18 Nothing special from me. I was away all last week so still catching up on things. 14:52:33 I think I know what is required to add the CloudKitty API reference to the landing page for OpenStack APIs. 14:53:26 Ah, that is cool 14:53:33 can you execute/conduct that process? 14:53:37 The TODO list is a bit more involved than I thought it would be but I still think it's worth doing. 14:54:18 Yes, I'm currently working on a patch which should execute the first step. :) 14:54:25 awesome! 14:54:27 thanks!!!! 14:55:04 Basically, the end goal is to add a link to CloudKitty APIs here: https://docs.openstack.org/api/ 14:55:11 exactly 14:55:37 If that is all guys, I will close it for today 14:55:47 That's all from my side. 14:55:58 Thank you guys for participating. Have a nice week. 14:56:06 #endmeeting