Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-07 Thread Travis Briggs 
I'm getting a 403 forbidden for
https://tools.wmflabs.org/enwp10/cgi-bin/pindex.fcgi which redirects to
https://enwp10.toolforge.org/cgi-bin/pindex.fcgi

Does this have to do with allowed hosts? What are allowed hosts and where
are they configured?

Thanks,
-Travis

On Tue, Jul 7, 2020 at 7:02 AM Martin Urbanec 
wrote:

> Yes, you need to add the host to the allowed hosts.
>
> Martin
>
> On Tue, Jul 7, 2020, 3:13 PM Roy Smith  wrote:
>
>> I've started getting:
>>
>> > Invalid HTTP_HOST header: 'spi-tools-dev.toolforge.org'. You may need
>> to add 'spi-tools-dev.toolforge.org' to ALLOWED_HOSTS.
>>
>> I assume that's related to the change?
>>
>>
>>
>> > On Jul 7, 2020, at 6:50 AM, Arturo Borrero Gonzalez <
>> aborr...@wikimedia.org> wrote:
>> >
>> > 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/ will be permanently
>> redirected to
>> >> .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.
>> >
>> > --
>> > Arturo Borrero Gonzalez
>> > SRE / Wikimedia Cloud Services
>> > Wikimedia Foundation
>> >
>> > ___
>> > Wikimedia Cloud Services mailing list
>> > Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
>> > https://lists.wikimedia.org/mailman/listinfo/cloud
>>
>>
>> ___
>> Wikimedia Cloud Services mailing list
>> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
>> https://lists.wikimedia.org/mailman/listinfo/cloud
>
> ___
> Wikimedia Cloud Services mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-07 Thread Martin Urbanec 
Yes, you need to add the host to the allowed hosts.

Martin

On Tue, Jul 7, 2020, 3:13 PM Roy Smith  wrote:

> I've started getting:
>
> > Invalid HTTP_HOST header: 'spi-tools-dev.toolforge.org'. You may need
> to add 'spi-tools-dev.toolforge.org' to ALLOWED_HOSTS.
>
> I assume that's related to the change?
>
>
>
> > On Jul 7, 2020, at 6:50 AM, Arturo Borrero Gonzalez <
> aborr...@wikimedia.org> wrote:
> >
> > 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/ will be permanently
> redirected to
> >> .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.
> >
> > --
> > Arturo Borrero Gonzalez
> > SRE / Wikimedia Cloud Services
> > Wikimedia Foundation
> >
> > ___
> > Wikimedia Cloud Services mailing list
> > Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> > https://lists.wikimedia.org/mailman/listinfo/cloud
>
>
> ___
> Wikimedia Cloud Services mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-07 Thread Roy Smith 
I've started getting:

> Invalid HTTP_HOST header: 'spi-tools-dev.toolforge.org'. You may need to add 
> 'spi-tools-dev.toolforge.org' to ALLOWED_HOSTS.

I assume that's related to the change?



> On Jul 7, 2020, at 6:50 AM, Arturo Borrero Gonzalez  
> wrote:
> 
> 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/ will be permanently redirected 
>> to
>> .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.
> 
> -- 
> Arturo Borrero Gonzalez
> SRE / Wikimedia Cloud Services
> Wikimedia Foundation
> 
> ___
> Wikimedia Cloud Services mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud


___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-07 Thread Arturo Borrero Gonzalez 
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/ will be permanently redirected to
> .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.

-- 
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation

___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-06 Thread Bryan Davis 
On Mon, Jul 6, 2020 at 10:15 AM Martin Urbanec
 wrote:
>
> Hmm, perhaps we should update the interwiki map as well?

Yes, per  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
-- 
Bryan Davis  Technical Engagement  Wikimedia Foundation
Principal Software Engineer   Boise, ID USA
[[m:User:BDavis_(WMF)]]  irc: bd808

___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-06 Thread Martin Urbanec 
Hmm, perhaps we should update the interwiki map as well?

Martin

po 6. 7. 2020 v 18:00 odesílatel Arturo Borrero Gonzalez <
aborr...@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/ will be permanently
> redirected to
> .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 lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-07-06 Thread Arturo Borrero Gonzalez 
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/ will be permanently redirected to
.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 lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-06-02 Thread Arturo Borrero Gonzalez 
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/

-- 
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation

___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-05-15 Thread Arthur Smith 
Ah, never mind, I missed the OAuth section in the documentation! Will
request the new consumer then, thanks.

On Fri, May 15, 2020 at 3:53 PM Arthur Smith  wrote:

> Hi all - I was exploring my tool (author-disambiguator) - which uses
> OAuth. Is there a recommended practice for fixing/updating the OAuth
> details? I got an OAuth error when I first connected using the new URL, but
> that was I think because the callback is hardcoded in the OAuth
> configuration to the old server. Anyway, what are other people doing to fix
> this? Should I request new OAuth credentials for the new URL?
>
>Arthur
>
> On Mon, May 4, 2020 at 11:59 AM Arturo Borrero Gonzalez <
> aborr...@wikimedia.org> wrote:
>
>> 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.
>>
>> --
>> Arturo Borrero Gonzalez
>> SRE / Wikimedia Cloud Services
>> Wikimedia Foundation
>>
>> ___
>> Wikimedia Cloud Services mailing list
>> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
>> https://lists.wikimedia.org/mailman/listinfo/cloud
>
>
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-05-15 Thread Arthur Smith 
Hi all - I was exploring my tool (author-disambiguator) - which uses OAuth.
Is there a recommended practice for fixing/updating the OAuth details? I
got an OAuth error when I first connected using the new URL, but that was I
think because the callback is hardcoded in the OAuth configuration to the
old server. Anyway, what are other people doing to fix this? Should I
request new OAuth credentials for the new URL?

   Arthur

On Mon, May 4, 2020 at 11:59 AM Arturo Borrero Gonzalez <
aborr...@wikimedia.org> wrote:

> 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.
>
> --
> Arturo Borrero Gonzalez
> SRE / Wikimedia Cloud Services
> Wikimedia Foundation
>
> ___
> Wikimedia Cloud Services mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-05-04 Thread RhinosF1 - 
The two tools I migrated did so seamlessly.

Thanks to everyone involved!

Samuel

On Mon, 4 May 2020 at 16:59, Arturo Borrero Gonzalez 
wrote:

> 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.
>
> --
> Arturo Borrero Gonzalez
> SRE / Wikimedia Cloud Services
> Wikimedia Foundation
>
> ___
> Wikimedia Cloud Services mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud

-- 
Thanks,
Samuel
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-16 Thread Bryan Davis 
On Thu, Apr 16, 2020 at 2:56 PM Huji Lee  wrote:
>
> Oops, I don't know how I pressed the Send button, sorry!
>
> When I run something like this from the console, I get a CORB error:
>
> $.ajax({url: 
> 'https://whois.toolforge.org/whois/8.4.4.8/lookup/json'}).done(function(data){console.log(data)})
>
> Yet I know there are some tools on labs that are being referenced through JS.

The CORS error [0] would be related to the lack of a
"Access-Control-Allow-Origin: *" header in the response from the
Toolforge side. I don't see an access control header from either of
https://whois.toolforge.org/whois/8.4.4.8/lookup/json or
https://tools.wmflabs.org/whois/8.4.4.8/lookup/json.

Is this a regression you are seeing from using the tools.wmflabs.org
URL to access the tool or just a general question?


[0]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

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

___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-16 Thread Huji Lee 
Oops, I don't know how I pressed the Send button, sorry!

When I run something like this from the console, I get a CORB error:

$.ajax({url: '
https://whois.toolforge.org/whois/8.4.4.8/lookup/json'}).done(function(data){console.log(data)
})

Yet I know there are some tools on labs that are being referenced through
JS.

On Thu, Apr 16, 2020 at 4:55 PM Huji Lee  wrote:

> Quick question: what does it take for a JS script to be allowed to
> interact with a toolforge tool?
>
> When I run something like this, I get a Cross-Origin Request Blocked error
> in the console:
>
>
> On Tue, Apr 14, 2020 at 6:40 AM billinghurst 
> wrote:
>
>> Checking our interwiki map, we have the following:
>>
>> wmflabs
>>
>>- guchttps://tools.wmflabs.org/guc/?user=$1
>>- gucprefix
>>https://tools.wmflabs.org/guc/?isPrefixPattern=1=rc=$1
>>- luxohttps://tools.wmflabs.org/guc/?user=$1
>>- petscanhttps://petscan.wmflabs.org/?psid=$1
>>- quarryhttps://quarry.wmflabs.org/$1
>>- stewardryhttps://tools.wmflabs.org/meta/stewardry/?wiki=$1
>>- toolforge -> https://tools.wmflabs.org/$1
>>- toollabs  ->  https://tools.wmflabs.org/$1
>>- utrshttps://utrs.wmflabs.org/appeal.php?id=$1
>>- wmfdashboardhttps://outreachdashboard.wmflabs.org/$1
>>
>>
>> Toolserver
>>
>>- jirahttps://jira.toolserver.org/browse/$1
>>- tools-> //toolserver.org/$1
>>
>>
>> Please let us know what it is you want done with these, and for when you
>> would like that scheduled. Thanks.
>>
>> To also note that we should probably look to update
>> https://www.mediawiki.org/wiki/Toolserver:Main_Page
>> which lovingly still has the interwiki tswiki:  :-)
>>
>>
>> -- billinghurst
>>
>>
>> -- Original Message --
>> From: "Arturo Borrero Gonzalez" 
>> To: cloud-annou...@lists.wikimedia.org
>> Cc: "Cloud Services administration and infrastructure discussion" <
>> cloud-ad...@lists.wikimedia.org>; "Wikimedia Cloud Services general
>> discussion and support" 
>> Sent: 13/04/2020 9:25:22 PM
>> Subject: [Cloud] Toolforge: new domain toolforge.org
>>
>> 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//
>> * to https://.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 mailing list
>> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
>> https://lists.wikimedia.org/mailman/listinfo/cloud
>>
>> ___
>> Wikimedia Cloud Services mailing list
>> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
>> https://lists.wikimedia.org/mailman/listinfo/cloud
>
>
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-16 Thread Huji Lee 
Quick question: what does it take for a JS script to be allowed to interact
with a toolforge tool?

When I run something like this, I get a Cross-Origin Request Blocked error
in the console:


On Tue, Apr 14, 2020 at 6:40 AM billinghurst 
wrote:

> Checking our interwiki map, we have the following:
>
> wmflabs
>
>- guchttps://tools.wmflabs.org/guc/?user=$1
>- gucprefix
>https://tools.wmflabs.org/guc/?isPrefixPattern=1=rc=$1
>- luxohttps://tools.wmflabs.org/guc/?user=$1
>- petscanhttps://petscan.wmflabs.org/?psid=$1
>- quarryhttps://quarry.wmflabs.org/$1
>- stewardryhttps://tools.wmflabs.org/meta/stewardry/?wiki=$1
>- toolforge -> https://tools.wmflabs.org/$1
>- toollabs  ->  https://tools.wmflabs.org/$1
>- utrshttps://utrs.wmflabs.org/appeal.php?id=$1
>- wmfdashboardhttps://outreachdashboard.wmflabs.org/$1
>
>
> Toolserver
>
>- jirahttps://jira.toolserver.org/browse/$1
>- tools-> //toolserver.org/$1
>
>
> Please let us know what it is you want done with these, and for when you
> would like that scheduled. Thanks.
>
> To also note that we should probably look to update
> https://www.mediawiki.org/wiki/Toolserver:Main_Page
> which lovingly still has the interwiki tswiki:  :-)
>
>
> -- billinghurst
>
>
> -- Original Message --
> From: "Arturo Borrero Gonzalez" 
> To: cloud-annou...@lists.wikimedia.org
> Cc: "Cloud Services administration and infrastructure discussion" <
> cloud-ad...@lists.wikimedia.org>; "Wikimedia Cloud Services general
> discussion and support" 
> Sent: 13/04/2020 9:25:22 PM
> Subject: [Cloud] Toolforge: new domain toolforge.org
>
> 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//
> * to https://.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 mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
>
> ___
> Wikimedia Cloud Services mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-14 Thread billinghurst 

Checking our interwiki map, we have the following:

wmflabs
guchttps://tools.wmflabs.org/guc/?user=$1gucprefix
https://tools.wmflabs.org/guc/?isPrefixPattern=1=rc=$1luxo
https://tools.wmflabs.org/guc/?user=$1petscan
https://petscan.wmflabs.org/?psid=$1quarry
https://quarry.wmflabs.org/$1stewardry
https://tools.wmflabs.org/meta/stewardry/?wiki=$1toolforge -> 
https://tools.wmflabs.org/$1toollabs  ->  
https://tools.wmflabs.org/$1utrs
https://utrs.wmflabs.org/appeal.php?id=$1wmfdashboard
https://outreachdashboard.wmflabs.org/$1


Toolserver
jirahttps://jira.toolserver.org/browse/$1tools-> 
//toolserver.org/$1


Please let us know what it is you want done with these, and for when you 
would like that scheduled. Thanks.


To also note that we should probably look to update
https://www.mediawiki.org/wiki/Toolserver:Main_Page
which lovingly still has the interwiki tswiki:  :-)


-- billinghurst


-- Original Message --
From: "Arturo Borrero Gonzalez" 
To: cloud-annou...@lists.wikimedia.org
Cc: "Cloud Services administration and infrastructure discussion" 
; "Wikimedia Cloud Services general 
discussion and support" 

Sent: 13/04/2020 9:25:22 PM
Subject: [Cloud] Toolforge: new domain toolforge.org


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//
* to   https://.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 mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Bryan Davis 
On Mon, Apr 13, 2020 at 11:59 AM Gerard Meijssen
 wrote:
>
> Hoi,
> Will the old URL-s continue to work.. I have a considerable amount of text 
> linking to allsorts.

Yes, at least at the URL handling level, the legacy URLs will continue
to work. This was mentioned in the original announcement:

On Mon, Apr 13, 2020 at 5:25 AM Arturo Borrero Gonzalez
 wrote:
>
> 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.

Once the 'final' switch to the new URL scheme is complete we will
introduce a static webservice somewhere in Cloud VPS that will issue
"308 moved permanently" redirects for all of the
tools.wmflabs.org/$TOOL root URLs that existed at that point in time.
This will be similar in spirit if not implementation to the service we
run which redirects toolserver.org/$WHATEVER URLs to tools.wmflabs.org
URLs today.

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

___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Gerard Meijssen 
Hoi,
Will the old URL-s continue to work.. I have a considerable amount of text
linking to allsorts.
Thanks,
  GerardM

On Mon, 13 Apr 2020 at 13:25, Arturo Borrero Gonzalez <
aborr...@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//
> * to   https://.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 mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Huji Lee 
Sorry, one more question. Do we need to update the ProxyJump settings[1]
because of this, or would those remain the same? Asking because those
settings also reference eqiad.*wmflabs*

  [1]
https://wikitech.wikimedia.org/wiki/Help:Accessing_Cloud_VPS_instances#ProxyJump_(recommended)

On Mon, Apr 13, 2020 at 11:52 AM Huji Lee  wrote:

> Thanks for sharing the news!
> When I log into login.toolforge.org the login message that is shown still
> references the old domain name. Can we update that too?
>
> On Mon, Apr 13, 2020 at 7:25 AM Arturo Borrero Gonzalez <
> aborr...@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//
>> * to   https://.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 mailing list
>> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
>> https://lists.wikimedia.org/mailman/listinfo/cloud
>
>
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Huji Lee 
Thanks for sharing the news!
When I log into login.toolforge.org the login message that is shown still
references the old domain name. Can we update that too?

On Mon, Apr 13, 2020 at 7:25 AM Arturo Borrero Gonzalez <
aborr...@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//
> * to   https://.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 mailing list
> Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/cloud
___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Arturo Borrero Gonzalez 
On 4/13/20 4:18 PM, Maarten Dammers wrote:
> We sure like to rename and move around. I hope Toolforge.org lasts a lot 
> longer!
> 

Hi Maarten,

I think I understand your concern. Sometimes, naming things is hard :-)

However, let me point out that toolserver and toolforge, while similar in spirit
and scope, are different services, with different technologies involved, and
more things to offer to the users (developers).

The new domain, for me, means the service is evolving even more, in the good 
sense.

Also, please note the change is not only a cosmetic one. It involves a more
secure approach to host each tool webservice, from an all-shared domain to a
domain per tool.

-- 
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation

___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

Re: [Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Maarten Dammers 

Hi Arturo,

That looks like a nice new domain name. To put this a bit in 
perspective, this is not the first time we change the domain where are 
shared tools are hosted. If I remember correctly we started at 
tools.wikimedia.de ( 
http://web.archive.org/web/20060202215516/http://tools.wikimedia.de/ ). 
At some point we started using the toolserver.org domain ( 
http://web.archive.org/web/20130402034854/http://toolserver.org/ ). 
Toolserver was replaced by the Tool Labs ( 
http://web.archive.org/web/20160505220308/https://tools.wmflabs.org/admin/ 
) part of Wikimedia Labs. Tool Labs not too long ago got re-branded to 
Toolforge and (and Wikimedia Labs became Wikimedia Cloud).


We sure like to rename and move around. I hope Toolforge.org lasts a lot 
longer!


Maarten

On 13-04-20 13:25, Arturo Borrero Gonzalez 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//
* to   https://.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



___
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud

[Cloud] Toolforge: new domain toolforge.org

2020-04-13 Thread Arturo Borrero Gonzalez 
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//
* to   https://.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 mailing list
Cloud@lists.wikimedia.org (formerly lab...@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud