The only thing I might caution is that using a floating IP might be ideal for being able to quickly fail over to a new load balancer, if needed (and a bit nicer than DNS in general). I believe that is the whole rationale behind the current name. It’s a standard name added in OpenStack with a floating IP, which makes it fairly easy to work with and reason about for any Toolforge admin (when it’s documented…obviously when we didn’t know about it, we had a lovely outage on trying to move to the new region).

I don’t care too much about the name per se.  I do care about whether it is straightforward.  That’s the only reason I was thinking of the wmcloud.org domain.  I don’t know if that’s doable with the other one or not.

Brooke Storm
Senior SRE
Wikimedia Cloud Services
bstorm@wikimedia.org
IRC: bstorm_

On Oct 17, 2019, at 1:21 PM, Bryan Davis <bd808@wikimedia.org> wrote:

On Thu, Oct 17, 2019 at 9:33 AM Arturo Borrero Gonzalez
<aborrero@wikimedia.org> wrote:

On 10/17/19 10:39 AM, Arturo Borrero Gonzalez wrote:
Complete FQDNs options would be:

* k8s.eqiad1.tools.wikimedia.cloud
* k8s-control.tools.eqiad1.wikimedia.cloud
* k8s.tools.wikimedia.cloud
* k8s-control.tools.wikimedia.cloud

* k8s.eqiad1.tools.wmcloud.org
* k8s-control.tools.eqiad1.wmcloud.org
* k8s.tools.wmcloud.org
* k8s-control.tools.wmcloud.org

It seems I'm trying to do this more confusing :-P I just realized many of the
options are wrong.

Hope you get my point anyway.

@Bryan, we just had a conversation on this and I already forgot what were our
conclusions for this particular case.

<hostname>.<project>.<deployment>.wikimedia.cloud is the FQDN scheme I
would expect for instances in a project under the new naming system.
The current equivalent is <hostname>.<project>.<datacenter>.wmflabs.
In both cases these are Designate managed DNS entries, and service
aliases can be managed in Horizon as either CNAME or A records in the
project's zone.

I think this would mean that the "right" service name for a load
balancer in front of the new k8s API would be one of:
* <hostname>.tools.eqiad1.wikimedia.cloud
* <hostname>.tools.eqiad.wmflabs

I have no strong opinion about the <hostname> to use here.

I'm all for starting to introduce the wikimedia.cloud domain, but
really only if we have time and energy right now to get it set up. The
whois for wikimedia.cloud shows the current top level NS being pointed
to ns{1,2,3}.wikimedia.org, so getting the basics for it going in
Designate should be something like:

* Create 'eqiad1.wikimedia.cloud.' zone in eqiad1's Designate
* Create 'wikimedia.cloud.' zone in operations/dns.git
* Delegate NS for 'eqiad1.wikimedia.cloud.' to
cloud-ns{0,1}.wikimedia.org in operations/dns.git
* Repeat for Designate and delegation steps for 'codfw1dev.wikimedia.cloud.'

What I am not sure about is how much confusion it will make for us and
others to have mixed usage of *.<datacenter>.wmflabs and
*.<deployment>.wikimedia.cloud without a bigger plan to completely
remove (or at least deprecate) *.<datacenter>.wmflabs. Does anyone
have strong feelings about that?

Bryan
-- 
Bryan Davis              Technical Engagement      Wikimedia Foundation
Principal Software Engineer                               Boise, ID USA
[[m:User:BDavis_(WMF)]]                                      irc: bd808