Hi Dominic,
Although I'm not going to contribute to the Trove project anymore, I disagree with what you said that using database containers is a bad example, especially considering the project situation in the open source community in the past several years.
I've explained this several times to different people when I was making the change, but I don't mind repeating myself.
Trove was supporting multiple datastores previously and maintaining a bunch of DIB image elements to build different guest images. However, the task of keeping those elements up to date is not easy, and needs the domain knowledge of the specific database, but most of the active contributors have left and the project itself was on the edge of death.
It was that time when I picked up the project because the database-as-a-service was on the service roadmap of our openstack based public cloud. Given this is such a complicated project with such a small team, it's impossible to maintain those different kinds of datastores. As a result, I made the decision to simplify the trove guest image build process and introduce container based database inside trove guest instance, so the project only needs to maintain a single common guest image but to support as more datastores as possible, offloading the database container image maintenance work to other upstream teams who specialize in the database technology area.
I don't think we had other better choices at that time.
Anyway, hope there will be more people could see my comment here and there will be someone raises his hand to lead this project forward. I'm glad to know Trove is deployed in your cloud, it's a pity that I didn't see any contribution coming from the team behind your cloud.
--- Lingxian Kong
On Sat, Feb 12, 2022 at 7:24 AM DHilsbos@performair.com wrote:
In Victoria, Trove moved to Docker images for the datastores. Any datastores that didn't update themselves were removed, regardless of state. I believe the only datastores currently supported are MariaDB, and PostgreSQL, though MySQL might be supported as well.
Personally. I find this to have been a bad example of the "containerize all the things" mentality. Trove now deploys an instance (vm) for each datastore instance, running a single container. The exception is if you request backups, in which case a backup container is added to the instance (vm).
Trove is installed in our OpenStack cloud, but we don't use it.
Thank you,
Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos@PerformAir.com www.PerformAir.com
From: Ришат Азизов [mailto:rishat.azizov@gmail.com] Sent: Sunday, February 6, 2022 11:10 AM To: openstack-discuss@lists.openstack.org Subject: OpenStack Trove experimental datastores
Hello!
Why were the experimental datastores removed in the Trove OpenStack Victoria release? https://review.opendev.org/c/openstack/trove/+/728419
Thanks!