tl;dr:
VMs created on or after September 8th will stop having .eqiad.wmflabs
domains, and be found only under .eqiad1.wikimedia.cloud
The whole story:
Currently cloud-vps VMs stand astride two worlds: wmflabs and
wikimedia.cloud. Here's the status quo:
- New VMs get three different DNS entries:
hostname.project.eqiad1.wikimedia.cloud, hostname.project.eqiad.wmflabs,
and hostname.eqiad.wmflabs [0]
- Reverse DNS lookups return hostnames under eqiad1.wikimedia.cloud
- VMs themselves believe (e.g. via hostname -f) that they're still under
eqiad.wmflabs
That hybrid system has done a good job maintaining backwards
compatibility, but it's a bit of a mess. In the interest of simplifying,
standardizing, and eliminating ever more uses of the term 'labs', we're
going to start phasing out the wmflabs domain name. Beginning on
September 8th, new VMs will no longer receive any naming associated with
.wmflabs [1].
- New VMs will get one DNS entry: hostname.project.eqiad1.wikimedia.cloud
- New VMs will continue to have a pointer DNS entry that refers to the
.wikimedia.cloud name
- New VMs will be assigned an internal hostname under .wikimedia.cloud
In order to avoid breaking existing systems, these changes will NOT be
applied retroactively to existing VMs. Old DNS entries will live on
until the VM is deleted and should be largely harmless. If, however,
you find yourself rewriting code in order to deal with VMs under both
domains (due to the change in hostname -f behavior), don't worry --
adjusting an old VM to identify as part of .wikimedia.cloud only
requires a simple change to /etc/hosts. I'll be available to make that
change for any project that chooses consistency over
backwards-compatibility.
[0]
https://phabricator.wikimedia.org/phame/post/view/191/new_names_for_everyone
[1] https://phabricator.wikimedia.org/T260614
A change was just now made to the shared proxy system for Toolforge
which makes the proxy respond with default content for /favicon.ico
and /robots.txt when a tool's webservice returns a 404 Not Found
response for these files.
The default /favicon.ico is the same as
<https://tools-static.wmflabs.org/toolforge/favicons/favicon.ico>.
The default robots.txt denies access to all compliant web crawlers. We
decided that this "fail closed" approach would be safer than a "fail
open" telling all crawlers to crawl all tools. Any tool that does wish
to be indexed by search engines and other crawlers can serve their own
/robots.txt content. Please see <https://www.robotstxt.org/> for more
information on /robots.txt in general.
These changes fix a regression [0] in functionality caused by the
toolforge.org migration and the introduction of the 2020 Kubernetes
ingress layer. Previously the /robots.txt and /favicon.ico from the
"admin" tool were served for all tools due to the use of a shared
hostname.
[0]: https://phabricator.wikimedia.org/T251628
Bryan, on behalf of the Toolforge admin team
--
Bryan Davis Technical Engagement Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808
TL;DR:
* HTTP -> HTTPS redirection is live (finally!)
* Currently allowing a "POST loophole"
* "POST loophole" will be closed on 2021-02-01
Today we merged a small change [0] to the front proxy used by Cloud
VPS projects [1]. This change brings automatic HTTP -> HTTPS
redirection to the "domain proxy" service and a
Strict-Transport-Security header with a 1 day duration.
The current configuration is conservative. We will only redirect GET
and HEAD requests to HTTPS to avoid triggering bugs in the handling of
redirects during POST requests. This "POST loophole" is the same
process that we followed when converting the production wiki farm and
Toolforge to HTTPS.
When we announced similar changes for Toolforge in 2019 [2] we forgot
to set a timeline for closing the POST loophole. This time we are
wiser! We will close the POST loophole and make all HTTP requests,
regardless of the verb used, redirect to HTTPS on 2021-02-01. This 6
month transition period should give us all a chance to find and update
URLs to use https and to fix any dependent software that might break
if a redirect was sent for a POST request.
If you find issues in your projects resulting from this change, please
do let us know. The tracking task for this change is T120486 [3]. We
also provide support in the #wikimedia-cloud channel on Freenode and
via the cloud(a)lists.wikimedia.org mailing list [4].
[0]: https://gerrit.wikimedia.org/r/c/operations/puppet/+/620122/
[1]: https://wikitech.wikimedia.org/wiki/Help:Using_a_web_proxy_to_reach_Cloud_V…
[2]: https://phabricator.wikimedia.org/phame/post/view/132/migrating_tools.wmfla…
[3]: https://phabricator.wikimedia.org/T120486
[4]: https://lists.wikimedia.org/mailman/listinfo/cloud
Bryan, on behalf of the Cloud VPS admin team
--
Bryan Davis Technical Engagement Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808