So, just to clarify, this is having a similar independent setup like we have in eqiad:m5 but in codfw?

In T218029#5015217, @Marostegui wrote:

So, just to clarify, this is having a similar independent setup like we have in eqiad:m5 but in codfw?

Yes. But I think eqiad:m5 contains more databases not strictly related to openstack, right?

We are only talking about these databases, more or less:

| designate              |
| designate_pool_manager |
| glance                 |
| keystone               |
| mysql                  |
| nova                   |
| nova_api               |
| pdns                   |

Yes, it was kinda to understand the setup.
I guess it would need to be renamed to m6 or whatever we decide.

So there are a few things to mention here:

• codfw doesn't have a proper misc setup yet
• we do not have proxies for codfw (although for m5 on eqiad we do have proxies, we are currently not using it for m5):

# host m5-master
m5-master.eqiad.wmnet is an alias for db1073.eqiad.wmnet.
db1073.eqiad.wmnet has address 10.64.16.79

I assume these hosts would need to be writable right? (Right now we do have hosts replicating m5, but those are read-only, it is just replication for DC disaster recovery). So if you need specific DB writable hosts, we'd also need to buy that extra hardware.

@Marostegui I mentioned the same issues at T217891#5015199

Ah - thanks, I didn't see that, good that we are aligned though :)

We would also want labtestwiki here (the MW database for labtestwikitech)

We discussed about this in our last WMCS team meeting and we agreed that having a m6-master (or whatever is the name) in codfw would be really great, and we would like to see it happening.

I will follow-up shortly with the DBA team.

This was discussed and agreed upon, so I am going to remove the DBA tag as the actionable for us are on the subtasks