Hey team, Isn’t it correct that OpenSearch and ES drivers should be generically compatible with each other? --Karl. From: thomas@goirand.fr <thomas@goirand.fr> Date: Friday, 21 June 2024 at 8:05 am To: Rafael Weingärtner <rafaelweingartner@gmail.com>, openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: [CloudKitty] query regarding ElasticSearch usage Hi, We are using ES, and as much as I know, the team maintaining the cluster has no intention switching to something else. Please, keep the driver alive. Cheers, Thomas Goirand Sent from Workspace ONE Boxer On Jun 20, 2024 9:55 PM, Rafael Weingärtner <rafaelweingartner@gmail.com> wrote: Hello OpenStack community and users of CloudKitty! There have been some discussions in our bi-weekly meetings and vPTG meetings regarding the deprecation and removal of ElasticSearch support as a storage backend. Therefore, this e-mail is to consult/query users regarding ElasticSearch users. If there are no people using it anymore with CloudKitty, we are considering the alternative of removing it and maintaining only the OpenSearch support. We would like to hear back from you guys. Let me know if you are using ElasticSearch, and if you intend to stick with it. Also, do you guys feel the need to improve something in its support in CloudKitty. Thanks in advance for your feedback! -- Rafael Weingärtner

Hello guys, Thank you for your valuable feedback. So far, the ElasticSearch driver is only deprecated, and before we move towards a removal process, we wanted to check with you guys (CloudKitty users). They (ElasticSearch and OpenSearch) are diverging in terms of some APIs and new workflows. Therefore, we (CloudKitty developers) started this discussion, to see if we need to work to maintain both or not. Also, further opinions and ideas are welcome to improve and add more differential between these two drivers. On Fri, Jun 21, 2024 at 12:22 PM Thomas Goirand <zigo@debian.org> wrote:

Hi,

Putting the quoting in order, and stopping the top-post... :)

My follow-up below...

...

On Jun 20, 2024 9:55 PM, Rafael Weingärtner <rafaelweingartner@gmail.com> wrote:

Hello OpenStack community and users of CloudKitty!

There have been some discussions in our bi-weekly meetings and vPTG meetings regarding the deprecation and removal of ElasticSearch support as a storage backend. Therefore, this e-mail is to consult/query users regarding ElasticSearch users. If there are no people using it anymore with CloudKitty, we are considering the alternative of removing it and maintaining only the OpenSearch support.

We would like to hear back from you guys. Let me know if you are using ElasticSearch, and if you intend to stick with it. Also, do you guys feel the need to improve something in its support in CloudKitty.

Thanks in advance for your feedback!

--

Rafael Weingärtner

*From: *thomas@goirand.fr <thomas@goirand.fr> *Date: *Friday, 21 June 2024 at 8:05 am *To: *Rafael Weingärtner <rafaelweingartner@gmail.com>, openstack-discuss <openstack-discuss@lists.openstack.org> *Subject: *Re: [CloudKitty] query regarding ElasticSearch usage

Hi,

We are using ES, and as much as I know, the team maintaining the cluster has no intention switching to something else.

Please, keep the driver alive.

Cheers,

Thomas Goirand On 6/21/24 00:22, Karl Kloppenborg wrote: Hey team,

Isn’t it correct that OpenSearch and ES drivers should be generically compatible with each other?

--Karl.

Like Karl, I'm kind of surprised, because both drivers must be very close. Instead of removing the ES driver, can't we have both drivers actually merged into a single one, that may take into accounts the very small differences (if any) between the 2 types of clusters? Code factorization is always good...

Cheers,

Thomas Goirand (zigo)

-- Rafael Weingärtner