728271 - post talos results to graphs.mozilla.org instead of graphs-old.m.o

Status: VERIFIED FIXED

(Release Engineering :: General, defect, P2)

Description

[Robert Helmer [:rhelmer]]

Now that bug 727355 has landed, graphs.mozilla.org is ready to take HTTP POSTs from Talos (it's been writing to graphs-old.mozilla.org ever since bug 706729).

We have tested on staging (graphs.allizom.org) and also a dummy post using curl on prod seems to work.

Once the change is made to Talos, please check that results are showing up in the graphs.mozilla.org interface - you can back out to writing graphs-old again if there are any problems.

FYI I will be out on PTO next week, this isn't super urgent so you can wait for me to get back if you want (or not, should be easy to back out if it doesn't work).

Comment 1

[Armen [:armenzg]]

Attachment: switch to graphs.m.o

Comment 2

[Robert Helmer [:rhelmer]]

BTW if you have any problems accessing the collect URL from any machines, please file an IT bug - access is controlled via the Zeus load balancer.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 598317 [details] [diff] [review]
switch to graphs.m.o

Please update talos-pool/config.py to cover the Tiger slaves too (we forgot last time, bug 714722). 

Have you tested this in staging to make sure the POSTs work ?

Comment 4

[Joel Maher ( :jmaher ) (UTC -8) (PTO back normal Nov 17)]

Comment on attachment 598317 [details] [diff] [review]
switch to graphs.m.o

Review of attachment 598317 [details] [diff] [review]:
-----------------------------------------------------------------

The changes you have are great.  Just the missing change that nrthomas mentioned.

Comment 5

[Armen [:armenzg]]

Rather than try live on production, let's see how to test it somewhere (probably graphs.allizom.org) instead of graphs-stage.

Comment 6

[Robert Helmer [:rhelmer]]

(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #5)
> Rather than try live on production, let's see how to test it somewhere
> (probably graphs.allizom.org) instead of graphs-stage.

Feel free to test this anytime, just keep in mind that the production DB is imported to stage every night, so any changes you make will be clobbered around midnight Pacific.

Comment 7

[Armen [:armenzg]]

Attachment: switch to graphs.m.o

Carrying forward review and addressing comments.

Comment 8

[Armen [:armenzg]]

Comment on attachment 603865 [details] [diff] [review]
switch to graphs.m.o

It seems I don't officially have the r+ from nthomas.

Comment 9

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 603865 [details] [diff] [review]
switch to graphs.m.o

Looks fine, thanks for testing in staging.

Based on grepping buildbot-configs, SeaMonkey will need a nudge to move off graphs-old before rhelmer can deprecate that.

Comment 10

[Armen [:armenzg]]

Comment on attachment 603865 [details] [diff] [review]
switch to graphs.m.o

http://hg.mozilla.org/build/buildbot-configs/rev/707327837623

Comment 11

[Armen [:armenzg]]

This change went live in a reconfiguration around 9AM.

Comment 12

[Robert Helmer [:rhelmer]]

This looks good so far - I see results being logged in production and visible in the UI.

Just FYI it looks like Talos records the datestamp at the beginning of each run (before any tests are set up or run) and sends that value to graphserver which then uses it in the UI, so there's a gap between the HTTP POST log and the date displayed in the UI which.

Comment 13

[Justin Wood (:Callek)]

(In reply to Nick Thomas [:nthomas] from comment #9)
> Comment on attachment 603865 [details] [diff] [review]
> switch to graphs.m.o

> Based on grepping buildbot-configs, SeaMonkey will need a nudge to move off
> graphs-old before rhelmer can deprecate that.

On my todo, was holding out until it was done here, to be sure it worked at least for you guys. Thanks though