Azure Database for MySQL single server is on the retirement path

[ciprianmaf]

Hello,

as the "Azure Database for MySQL single server" is on the retirement path, please update to "Azure Database for MySQL - Flexible Server".

Thank you!

Regards,

Ciprian Maftei
NTT DATA

[marrobi]

@ciprianmaf thanks, if this is an issue for yourselves, maybe you could look at doing a PR to update the terraform?

[migldasilva]

@marrobi I have advanced in this issue. So far I was able to move to MySQL Flexible Server for Gitea Shared service and Gitea Workspace service. Flexible Server requires a dedicated VNet, so I had to change TRE's Core for Gitea Shared service, and the workspace definition, for Gitea Workspace service.

I would be able to create a PR in a couple of days.

[tamirkamara]

@migldasilva thank you for having a look at this.
Changes in the core network can be disruptive for existing deployments and need to be done carefully.
Azure MySQL flexible server is about to receive support for private endpoints which will make it far easier to be integrated into an exiting framework. Let us give Microsoft the summer to release it and then revisit (single server isn't going away anytime soon). wdyt?

[migldasilva]

@tamirkamara Perfect. Let's wait. On the other hand, I've been testing the changes in core, so that everything keeps working. The main idea is to use one of the free subnets declared in core/terraform/network/locals.tf.

[tamirkamara]

@migldasilva apparently it's available already: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-networking-private-link

[SvenAelterman]

This has some new urgency, as in a few days, the creation of new MySQL DB Single Servers will be blocked.

@tamirkamara, @marrobi

[marrobi]

We discussed this and plan of action for anything using MySQL single server should be:

1. Update the bundles with new major version numbers so new deployments can succeed
2. Document manual migration approach and if deemed appropriate automate.
3. Move on to Postgres for MLflow (or retire MLflow entirely as used in Azure ML?)

[nasaldrops]

Any feedback on the Compute size name? Looking at General Purpose.

azurerm_mysql_server has sku_name "GP_Gen5_2"

azurerm_mysql_flexible_server doesn't have that option, so these are the GP ones available (see image)

[marrobi]

Any feedback on the Compute size name? Looking at General Purpose.

azurerm_mysql_server has sku_name "GP_Gen5_2"

azurerm_mysql_flexible_server doesn't have that option, so these are the GP ones available (see image)

Ideally they would be options in the bundle, defaulting to the lowest burstable spec maybe? The CPU usage for TRE use cases is typically very low.