Current openstack endpoints all point to the existing active cloudcontrol server:
```
aborrero@cloudcontrol1004:~ 3s $ sudo wmcs-openstack endpoint list | grep public
| 0a1eb902933c4652ad41e6450fe436ee | eqiad1-r | neutron | network | True | public | http://cloudcontrol1003.wikimedia.org:9696 |
| 4578c49346db479ab6d5b7961af8f60a | eqiad1-r | nova | compute | True | public | http://cloudcontrol1003.wikimedia.org:8774/v2.1 |
| 465f331e03de4bfcbef1f8a7dbb4de15 | eqiad1-r | designate | dns | True | public | http://cloudservices1003.wikimedia.org:9001 |
| be7a84a1af114f94bd1d6cc48b374413 | eqiad1-r | keystone | identity | True | public | http://cloudcontrol1003.wikimedia.org:5000/v3 |
| ebf523fce03a4ff4b859277f0a3d2477 | eqiad1-r | proxy | proxy | True | public | http://proxy-eqiad1.wmflabs.org:5668/dynamicproxy-api/v1/$(tenant_id)s |
| f922afd9417448028ce02734e0420a0b | eqiad1-r | glance | image | True | public | http://cloudcontrol1003.wikimedia.org:9292 |
```
We aim to replace the endpoints with something more generic, ideally introducing our new domain, some options:
* eqiad1.cloudvps.svc.wmcloud.org
* eqiad1.openstack.svc.wmcloud.org
* eqiad1.cloudvps.wmcloud.org
* eqiad1.openstack.wmcloud.org
* eqiad1.api.wmcloud.org
It worth mentioning that perhaps this domain should be hosted **outside** of openstack (designate) so we avoid chicken-egg problems (example: we can't bootstrap the deployment because we can't resolve the FQDN).
Once we decide on a FQDN, we should evaluate how to introduce the endpoints to external proxy/balancers (probably something similar to prod setup).