Hi there!
wanted to share a big THANKS YOU to both Alex Monk (Krenair) and Andrew Bogott
for the amazing work they have been doing to support the codfw1dev openstack
deployment, including deploying an in-cloud puppetmaster to get it even closer
to being a full mirror of our live openstack deployment eqiad1. Note working in
getting the codfw1dev deployment in shape is something we don't usually set an
explicit goal on, even though, from my point of view, is vital for us to have a
proper testing environment.
Traditionally I've been using codfw1dev only for testing non-virtual things,
like openstack services, etc. With the current status, you can even test virtual
stuff (running in VM instances) with an experience very close to eqiad1.
This week I've been using the codfw1dev deployment for testing stuff, and for
the first time since I can remember, the experience was... mostly magically
smooth out of the box.
Now the challenge for myself (and possibly others) is to remember to test stuff
there first :-)
I case you want to try this yourself, I left here some hints on how to use the
deployment:
https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/Testing_deployme…
regards.
--
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation
Hi!
We are happy to announce the new domain 'toolforge.org' is now ready to be
adopted by our Toolforge community.
There is a lot of information related to this change in a wikitech page we have
for this:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
The most important change you will see happening is a new domain/scheme for
Toolforge-hosted webservices:
* from https://tools.wmflabs.org/<toolname>/
* to https://<toolname>.toolforge.org/
A live example of this change can be found in our internal openstack-browser
webservice tool:
* legacy URL: https://tools.wmflabs.org/openstack-browser/
* new URL: https://openstack-browser.toolforge.org
This domain change is something we have been working on for months previous to
this announcement. Part of our work has been to ensure we have a smooth
transition from the old domain (and URL scheme) to the new canonical one.
However, we acknowledge the ride might be bumpy for some folks, due to technical
challenges or cases we didn't consider when planning this migration. Please
reach out intermediately if you find any limitation or failure anywhere related
to this change. The wikitech page also contains a section with information for
common problems.
You can check now if your webservice needs any specific change by creating a
temporal redirection to the new canonical URL:
$ webservice --canonical --backend=kubernetes start [..]
$ webservice --canonical --backend=gridengine start [..]
The --canonical switch will create a temporal redirect that you can turn on/off.
Please use this to check how your webservice behaves with the new domain/URL
scheme. If you start the webservice without --canonical, the temporal redirect
will be removed.
We aim to introduce permanent redirects for the legacy URLs on 2020-06-15. We
expect to keep serving legacy URLs forever, by means of redirections to the new
URLs. More information on the redirections can also be found in the wikitech page.
The toolforge.org domain is finally here! <3
--
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation