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
Its happening !
On Mon, Apr 13, 2020, 6:25 AM Arturo Borrero Gonzalez < aborrero@wikimedia.org> wrote:
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
Wikimedia Cloud Services announce mailing list Cloud-announce@lists.wikimedia.org (formerly labs-announce@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hi there!
This is a reminder about the ongoing migration for the new domain and URL/path scheme for webservices running in Toolforge. On 2020-05-31 we have the soft deadline for this migration period.
For trying the change you only need to run the webservice command with the --canonical argument. Please review the documentation here:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
Early adopting this change is interesting for many reasons, specially a more secure environment by means of proper domain isolation. Also, the new domain better reflects the identity of the Toolforge service :-) Moreover, during the compatibility period, we would like to collect feedback and bug reports from our users before the soft deadline.
As of today, we have 40 tool webservices that are running in the new domain and using the new path scheme, find them here:
https://replag.toolforge.org https://testwikis.toolforge.org https://meetingtimes.toolforge.org https://speedpatrolling.toolforge.org https://wiki-tennis.toolforge.org https://xslack.toolforge.org https://urbanecm-test-1.toolforge.org https://wdmm.toolforge.org https://quickcategories.toolforge.org https://wikiportretdev.toolforge.org https://zppixbot-test.toolforge.org https://anticompositetools.toolforge.org https://james.toolforge.org https://bd808-ruby.toolforge.org https://ytcleaner.toolforge.org https://wd-shex-infer.toolforge.org https://github-pr-closer.toolforge.org https://wikistream.toolforge.org https://secwatch.toolforge.org https://giftbot.toolforge.org https://pagepile-visual-filter.toolforge.org https://zppixbot.toolforge.org https://stashbot.toolforge.org https://moedata.toolforge.org https://sal.toolforge.org https://covid-obit.toolforge.org https://docker-registry.toolforge.org https://wb2rdf.toolforge.org https://massmailer.toolforge.org https://wd-image-positions.toolforge.org https://versions.toolforge.org https://lexeme-forms.toolforge.org https://ukbot.toolforge.org https://machtsinn.toolforge.org https://bikeshed.toolforge.org https://gmt.toolforge.org https://ipcheck.toolforge.org https://signatures.toolforge.org https://templatedata-filler.toolforge.org https://wordcount.toolforge.org
Please reach out for any comments, doubts or questions.
regards.
Hi there!
The soft deadline for migrating to the toolforge.org domain was two days ago, on 2020-05-31.
For adopting the change in a controlled way you only need to run the webservice command with the --canonical argument. Please review the documentation here:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
Next event is the hard deadline. In about 2 weeks (on 2020-06-15) we will introduce forced redirection from the legacy URL to the new one.
Please contact your fellow tool developers if you think they aren't aware of this migration. And please reach out to us if you have doubts or need help.
I checked today, and at least about 110 webservices are already running on the new domain and URL scheme:
https://alphatest.toolforge.org/ https://anticompositetools.toolforge.org/ https://author-disambiguator.toolforge.org/ https://base-encode.toolforge.org/ https://bd808-ruby.toolforge.org/ https://bd808-test2.toolforge.org/ https://bd808-test.toolforge.org/ https://bikeshed.toolforge.org/ https://bookreader.toolforge.org/ https://cdnjs-beta.toolforge.org/ https://cdnjs.toolforge.org/ https://chie-bot.toolforge.org/ https://copypatrol.toolforge.org/ https://covid-obit.toolforge.org/ https://dna.toolforge.org/ https://docker-registry.toolforge.org/ https://event-streams.toolforge.org/ https://fastilybot-reports.toolforge.org/ https://fist.toolforge.org/ https://flickr2commons.toolforge.org/ https://flickrdash.toolforge.org/ https://fontcdn.toolforge.org/ https://fountain-test.toolforge.org/ https://fountain.toolforge.org/ https://ftools.toolforge.org/ https://giftbot.toolforge.org/ https://github-pr-closer.toolforge.org/ https://global-search-test.toolforge.org/ https://global-search.toolforge.org/ https://globalsearch.toolforge.org/ https://gmt.toolforge.org/ https://grantmetrics.toolforge.org/ https://hgztools.toolforge.org/ https://ia-upload.toolforge.org/ https://indic-wscontest.toolforge.org/ https://indic-wsstats.toolforge.org/ https://interaction-timeline.toolforge.org/ https://intersect-contribs.toolforge.org/ https://ipcheck.toolforge.org/ https://ip-range-calc.toolforge.org/ https://itwikinews-rss.toolforge.org/ https://james.toolforge.org/ https://k8s-status.toolforge.org/ https://langviews.toolforge.org/ https://ldap.toolforge.org/ https://lexeme-forms.toolforge.org/ https://machtsinn.toolforge.org/ https://majavah-bot.toolforge.org/ https://massmailer.toolforge.org/ https://meetingtimes.toolforge.org/ https://mix-n-match.toolforge.org/ https://moedata.toolforge.org/ https://morfeusz.toolforge.org/ https://musikanimal.toolforge.org/ https://mwph-api.toolforge.org/ https://mwversion.toolforge.org/ https://mysql-php-session-test.toolforge.org/ https://pagepile-visual-filter.toolforge.org/ https://pageviews-test.toolforge.org/ https://pageviews.toolforge.org/ https://pathoschild-contrib.toolforge.org/ https://phabsearchemail.toolforge.org/ https://phabulous.toolforge.org/ https://plagiabot.toolforge.org/ https://plnode.toolforge.org/ https://qrcode-generator.toolforge.org/ https://quickcategories.toolforge.org/ https://replacer.toolforge.org/ https://replag.toolforge.org/ https://sal.toolforge.org/ https://searchsbl.toolforge.org/ https://section-links.toolforge.org/ https://secwatch.toolforge.org/ https://signatures.toolforge.org/ https://siteviews.toolforge.org/ https://speedpatrolling.toolforge.org/ https://sql-optimizer.toolforge.org/ https://stashbot.toolforge.org/ https://superzerocool.toolforge.org/ https://svgtranslate-test.toolforge.org/ https://svgtranslate.toolforge.org/ https://taxoboxalyzer.toolforge.org/ https://templatedata-filler.toolforge.org/ https://testwikis.toolforge.org/ https://text2hash.toolforge.org/ https://tool-db-usage.toolforge.org/ https://toolviews.toolforge.org/ https://ukbot.toolforge.org/ https://urbanecm-test-1.toolforge.org/ https://url-converter.toolforge.org/ https://versions.toolforge.org/ https://wb2rdf.toolforge.org/ https://wd-image-positions.toolforge.org/ https://wdmm.toolforge.org/ https://wd-shex-infer.toolforge.org/ https://wikicontrib.toolforge.org/ https://wikidata-externalid-url.toolforge.org/ https://wikifile-transfer.toolforge.org/ https://wikiportretdev.toolforge.org/ https://wikisource-bot.toolforge.org/ https://wikistream.toolforge.org/ https://wiki-tennis.toolforge.org/ https://wiki-topic.toolforge.org/ https://wordcount.toolforge.org/ https://wsexport.toolforge.org/ https://xn--dk8hv9g.toolforge.org/ https://xslack.toolforge.org/ https://xtools.toolforge.org/ https://ytcleaner.toolforge.org/ https://zppixbot.toolforge.org/
Hi there!
The hard deadline for migrating to the toolforge.org domain was 3 days ago, on 2020-06-15.
We are aware of some folks from the community still working on finishing up this migration, and we will give an additional 2 weeks before introducing the legacy-redirector that will force-redirect all the legacy URLs to the new domain and URL scheme.
If you need additional context about this migration, please read:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
We are tracking missing webservices OAuth grants for for the new domain in this phabricator task:
https://phabricator.wikimedia.org/T254857
If your tool is unchecked, it means it requires additional work to make sure OAuth will work with the new domain.
Please contact your fellow tool developers if you think they aren't aware of this migration. And please, reach out to us if you have doubts or need help.
regards.
Hi there!
Tomorrow 2020-07-06 at about 10:00 UTC we will enable the legacy redirector and this migration will be completed.
All requests to tools.wmflabs.org/<toolname> will be permanently redirected to <toolname>.toolforge.org.
If you need additional context about this, please read:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
Please reach out if you need help or have doubts.
regards.
Hmm, perhaps we should update the interwiki map as well?
Martin
po 6. 7. 2020 v 18:00 odesílatel Arturo Borrero Gonzalez < aborrero@wikimedia.org> napsal:
Hi there!
Tomorrow 2020-07-06 at about 10:00 UTC we will enable the legacy redirector and this migration will be completed.
All requests to tools.wmflabs.org/<toolname> will be permanently redirected to <toolname>.toolforge.org.
If you need additional context about this, please read:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
Please reach out if you need help or have doubts.
regards.
-- Arturo Borrero Gonzalez SRE / Wikimedia Cloud Services Wikimedia Foundation
Wikimedia Cloud Services mailing list Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud
On Mon, Jul 6, 2020 at 10:15 AM Martin Urbanec martin.urbanec@wikimedia.cz wrote:
Hmm, perhaps we should update the interwiki map as well?
Yes, per https://phabricator.wikimedia.org/T247432 we will update the interwiki map. This will be a step that we can start right after the cutover that Arturo has announced. The redirect service will keep the old interwiki links working indefinitely, but we will want to update things so that new tools which are not covered by the redirector service can use interwiki links.
Bryan
On 2020-07-06 17:59, Arturo Borrero Gonzalez wrote:
Hi there!
Tomorrow 2020-07-06 at about 10:00 UTC we will enable the legacy redirector and this migration will be completed.
All requests to tools.wmflabs.org/<toolname> will be permanently redirected to <toolname>.toolforge.org.
If you need additional context about this, please read:
https://wikitech.wikimedia.org/wiki/News/Toolforge.org
Please reach out if you need help or have doubts.
This has been done!
regards.
cloud-admin@lists.wikimedia.org