1184951 - disable old tooltool hosts

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

http://tooltool.pvt.build.mozilla.org/pvt/build/
still has a few hits, I think from a windows host

    http://tooltool.pub.build.mozilla.org/pub/temp-sm-stuff/
All seamonkey

    http://runtime-binaries.pvt.build.mozilla.org/tooltool/
Gah! Still has a few hits!

    https://secure.pub.build.mozilla.org/tooltool/pub/temp-sm-stuff/
    https://secure.pub.build.mozilla.org/tooltool/pvt/build/
No hits :D

Comment 1

[C. Liang [:cyliang]]

I've tweaked the Apache conf for both tooltool-pvt.build.mozilla.org and runtime-binaries.pvt.build.mozilla.org so that external IPs for HTTP connections are captured in various log files.  If there are any unintended (detrimental) consequences, let me know and I can revert.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

I'll wait a bit (since we only get a few hits per hour) and then re-evaluate what might be using these old endpoints.  Hopefully just old try jobs.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

I tracked

"10.26.36.70, 10.22.81.211" - - [17/Jul/2015:08:53:25 -0700] "GET /build/sha512/0b71a936edf5bd70cf274aaa5d7abc8f77fe8e7b5593a208f805cc9436fac646b9c4f0b43c2b10de63ff3da671497d35536077ecbc72dba7f8159a38b580f831 HTTP/1.1" 200 167175 "-" "Python-urllib/2.7"

down to a spidermonkey build.

No hits since C's fix on runtime-binaries.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Attachment: bug1184951.patch

I can't think of why this might not work..

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

remote:   https://hg.mozilla.org/build/buildbot-configs/rev/1a5a7c94b2c0

Comment 6

[Release Engineering SlaveAPI Service]

In production: https://hg.mozilla.org/build/buildbot-configs/rev/1a5a7c94b2c0

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

What we didn't realize is that android beta -> esr are still running out of buildbot, so this change can't land until that esr is done and/or we have release promotion finished.  So we can't do much here until that happens.

Comment 8

[Edmund Wong (:ewong)]

(In reply to Dustin J. Mitchell [:dustin] from comment #0)
> http://tooltool.pvt.build.mozilla.org/pvt/build/
> still has a few hits, I think from a windows host
> 
>     http://tooltool.pub.build.mozilla.org/pub/temp-sm-stuff/
> All seamonkey

Yes, we use this tooltool url.


> 
>     http://runtime-binaries.pvt.build.mozilla.org/tooltool/
> Gah! Still has a few hits!
> 
>     https://secure.pub.build.mozilla.org/tooltool/pub/temp-sm-stuff/

SeaMonkey doesn't use the secure.pub.build.mozilla.org url, assuming
the 'temp-sm-stuff' is the same as the tooltool.pub url above.

Comment 9

[Edmund Wong (:ewong)]

Looking at the attached patch, it looks like api.pub.build.mozilla.org is
replacing the tooltool link.

Is this just a simple url replacement or are there specific releng changes
that need to be setup in order to get SeaMonkey's infra to run with
this new api url, assuming the SeaMonkey project is permitted to use
this api url? If so, will it include the stuff from 
tooltool.pub.build.mozilla.org/temp-sm-stuff/ ?

Comment 10

[Dustin J. Mitchell [:dustin] (he/him)]

You can just use the new URL.  I believe it includes all of the data you need.

Comment 11

[Edmund Wong (:ewong)]

(In reply to Dustin J. Mitchell [:dustin] from comment #10)
> You can just use the new URL.  I believe it includes all of the data you
> need.

Dustin,  when do we need to switch over?

Comment 12

[Amy Rich [:arr] [:arich]]

FYI Dustin is on PTO till 2015-08-19

Comment 13

[Dustin J. Mitchell [:dustin] (he/him)]

:ewong -- as soon as possible.  Once the current ESR expires, we'll be shutting down the existing endpoints.  I think that means a few months (you'd know better than I), but better to get ahead of the curve :)

Comment 14

[Michael Shal [:mshal]]

Does anyone know if we're still blocked on some android builds here? And if so, why those fail with the newer tooltool url? Maybe we just need to upload some packages to the new system.

Comment 15

[Amy Rich [:arr] [:arich]]

dustin: do you know if we're good to decom the old tooltool hosts now? Who is managing those?

Comment 16

[Dustin J. Mitchell [:dustin] (he/him)]

I assume webops is still managing them?

I don't know if we're good to go -- you'd have to look at the traffic and see what's left.

Comment 17

[Amy Rich [:arr] [:arich]]

Sorry, I mean who is managing the tooltool application.

Comment 18

[Dustin J. Mitchell [:dustin] (he/him)]

Rok

Comment 19

[Rok Garbas [:garbas]]

i think it is safe to decom the "old" tooltool (if they weren not already). we are already switching to even newer version of tooltool (tooltool.mozilla-releng.net) and "api.pub.build.mozilla.org" will be decommissioned on sept 2018.

:jlund who should i contact from webops team to ask about this?

Comment 20

[Jordan Lund (:jlund)]

(In reply to Rok Garbas [:garbas] from comment #19)
> i think it is safe to decom the "old" tooltool (if they weren not already).
> we are already switching to even newer version of tooltool
> (tooltool.mozilla-releng.net) and "api.pub.build.mozilla.org" will be
> decommissioned on sept 2018.
> 
> :jlund who should i contact from webops team to ask about this?

both the older tooltool.*.build.mozilla.org and the less old Relengapi based tooltool: api.pub.build.mozilla.org/tooltool, live within Releng Cluster and is managed by IT (webops): https://mana.mozilla.org/wiki/display/websites/Releng+Cluster

Both generations of hosts will die with SCL3 exit and will not be migrated by IT. Nothing to do here afaict.