Do we have any initiatives under discussion regarding DBaaS on Apache CloudStack?

[ewerton-silva00]

I've been looking at Autobase (https://github.com/vitabaks/autobase) and I think it would be a suitable solution.

To request future integration with Apache CloudStack directly through the Autobase project, you need to be at least a sponsor.

Furthermore, I don't know if there are any implications in converging MIT licenses with Apache-2.0.

[DaanHoogland]

@ewerton-silva00 , MIT license is Apache 2 compatible so MIT licensed product can be used as components in apache projects. Can you expand on what integration would mean for the Apache CloudStack code base?

[ewerton-silva00]

@DaanHoogland, I'm not a developer and I don't know the Apache CloudStack code base well, but I'm thinking of something like this:

I believe the Autobase project could function as a plugin, an optional solution for Apache CloudStack users.

The control plane would run as SystemVMs, while the data plane would be VMs in user accounts.

Enabling the DBaaS plugin would make a new option available in Compute => Databases.

[jgotteswinter]

Autobase deploys the databases directly on vms, thats one approach. Another approach would be to use one of the widely adopted postgres, mysql, whatever k8s operators and build on top of the CKS feature. Databases in Kubernetes are great, especially when they come in masses.

[sekychan11]

I saw that Percona released their DBaaS solution (OpenEverest) under apache-2.0 not long ago (I have not tested this):

https://github.com/openeverest/openeverest

Would be interesting to see if anyone has an idea on how to integrate it in ACS.

[jgotteswinter]

thats one thing, but Everest is one of the younger projects which is probably still changing a lot. I would more go with raw operators, like the percona ones (which i personally like a lot). Everest has its own ui, this would not fit very nice in the acs ui i think. Check the postgres operator from percona for example, thats one of the few which has no requirements for object storage as backup target. It would fit good in the acs stack.

Sidenote: i tested everest a while ago when it still was under control of percona, no deep testing just clicking around to see if it does what it pretends. It was looking fine, but i did not like that it only supports s3 as backup target. the operator below also supports pgrest on pvc.