search

ovh / public-cloud-roadmap

Agile roadmap for OVHcloud Public Cloud services. Discover the features our product teams are working on, comment and influence our backlog.
https://www.ovhcloud.com/en/public-cloud/
185 stars 5 forks source link

Allow to modify / update network #424

Open lenglet-k opened 1 year ago

lenglet-k commented 1 year ago

Hello,

Today is not possible to update a private network of a managed database. We are obliged to fork a database.

It's possible to have a call api like this --> https://api.ovh.com/console/#/cloud/project/%7BserviceName%7D/database/mongodb/%7BclusterId%7D~PUT which allow us to update a network of existing database service ?

ElGigi commented 1 year ago

Hi,

It will be very appreciable to change private network or add another private networks.

The solution to fork database is not acceptable because bring about production stop. Even more true in the case of a big database.

Regards.

matmicro commented 1 year ago

+1

I would like to update network and also subnet of my Managed DB private network, but it is curently not possible

thild42 commented 1 year ago

Hello everyone.

I need your feedback on what you guys are trying to achieve. Could you tell me in which category your need falls into:

  1. Moving a database service from public network to private network
  2. Moving a database service from one vrack to another
  3. Moving a database service from one private network (vlan) to another. Probably changing the openstack region at the same time.
  4. Moving a database service from one subnet to another subnet within the same private network.

Trying to provide an automated/no-downtime move from one network to another is a great way to fall into a split-brain scenario, which obviously is something we try to avoid. This also why we currently prescribe to fork as a workaround.

Understanding your needs will help us focus on the real value for this feature.

matmicro commented 1 year ago

Moving from one DC to another one. Eg moving an infra from GRA to SBG with no downtime

ElGigi commented 1 year ago

Hi,

The minimum functionality missing is being able to manage private networks as is done on instances. That is to say, attach one or more private networks, detached ones...

Moving a base or just a node to another DC would be a plus. If we could move a node to another region, the ideal would be to be able to elect a replica as master, in the event of failure of the current master's region. And perhaps have a multi-zone IP Load Balancer to point towards the current master.

Regards.

thild42 commented 1 year ago

Thank you guys for the feedback.

What I had in mind, as highlighted by @ElGigi, was to move on the read-replica #269 (credit to @matmicro) feature that would provide a well-rounded work around to moving a DB to another region if a read-replica could be promoted to master.

In the meantime I will sync with my fellow PM on instance and network to check if there isn't any low hanging fruit.

matmicro commented 1 year ago

Another need is being able to switch a Managed DB from public network to private network only.