Hi Lingxian, Sorry for late reply, I couldn’t reply to your mail due to my health issue. We have team in Europe and US time zone and can have call between 8 am to 10 am UTC +12. Please let us know you’re your availability and suitable time. Based on that we will share meeting invite. Regards, Arunkumar Palanisamy From: Lingxian Kong <anlin.kong@gmail.com> Sent: Wednesday, September 2, 2020 12:06 PM To: ARUNKUMAR PALANISAMY <arunkumar.palanisamy@tcs.com> Cc: openstack-discuss@lists.openstack.org; Pravin Mohan <pravin.mohan@tcs.com>; Murugan N <murugan.n@tcs.com> Subject: Re: Trove images for Cluster testing. "External email. Open with Caution" Hi Arunkumar, For how to join IRC channel, please see https://docs.opendev.org/opendev/infra-manual/latest/developers.html#irc-acc... Currently there is no trove team meeting because we don't have any other people interested (for some historical reasons), but if needed, we can schedule a time suitable for both. I'm in UTC+12 btw. --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz<http://www.catalystcloud.nz> On Wed, Sep 2, 2020 at 2:56 AM ARUNKUMAR PALANISAMY <arunkumar.palanisamy@tcs.com<mailto:arunkumar.palanisamy@tcs.com>> wrote: Hi Lingxian, Hope you are doing Good. Thank you for your mail and detailed information. We would like to join #openstack-trove IRC channel for discussions. Could you please advise us the process to join IRC channel. We came to know that currently there is no IRC channel meeting happening for Trove, if there is any meeting scheduled and happening. we would like to join and understand the works and progress towards Trove and contribute further. Regards, Arunkumar Palanisamy From: Lingxian Kong <anlin.kong@gmail.com<mailto:anlin.kong@gmail.com>> Sent: Friday, August 28, 2020 12:09 AM To: ARUNKUMAR PALANISAMY <arunkumar.palanisamy@tcs.com<mailto:arunkumar.palanisamy@tcs.com>> Cc: openstack-discuss@lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>; Pravin Mohan <pravin.mohan@tcs.com<mailto:pravin.mohan@tcs.com>> Subject: Re: Trove images for Cluster testing. "External email. Open with Caution" Hi Arunkumar, Unfortunately, for now Trove only supports MySQL and MariaDB, I'm working on adding PostgreSQL support. All other datastores are unmaintained right now. Since this(Victoria) dev cycle, docker container was introduced in Trove guest agent in order to remove the maintenance overhead for multiple Trove guest images. We only need to maintain one single guest image but could support different datastores. We have to do that as such a small Trove team in the community. If supporting Redis, Cassandra, MongoDB or Couchbase is in your feature request, you are welcome to contribute to Trove. Please let me know if you have any other questions. You are also welcome to join #openstack-trove IRC channel for discussion. --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz<http://www.catalystcloud.nz> On Fri, Aug 28, 2020 at 6:45 AM ARUNKUMAR PALANISAMY <arunkumar.palanisamy@tcs.com<mailto:arunkumar.palanisamy@tcs.com>> wrote: Hello Team, My name is ARUNKUMAR PALANISAMY, As part of our project requirement, we are evaluating trove components and need your support for experimental datastore Image for testing cluster. (Redis, Cassandra, MongoDB, Couchbase) 1.) We are running devstack enviorment with Victoria Openstack release and with this image (trove-master-guest-ubuntu-bionic-dev.qcow2<https://tarballs.opendev.org/openstack/trove/images/trove-master-guest-ubuntu-bionic-dev.qcow2>), we are able to deploy mysql instance and and getting below error while creating mongoDB instances. “ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' “ 2.) While tried creating mongoDB image with diskimage-builder<https://opendev.org/openstack/diskimage-builder> tool, but we are getting “Block device ” element error. Regards, Arunkumar Palanisamy Cell: +49 172 6972490 =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you