855392 - proxy /correlations URLs to old PHP service

Status: RESOLVED WONTFIX

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Robert Helmer [:rhelmer]]

This is commented out in local.py:

# CORRELATION_SERVER = 'https://crash-stats-dev.allizom.org'

Please uncomment and set to production on all instances:

CORRELATION_SERVER = 'https://crash-stats.mozilla.com'

If we ship in this configuration, we'll need to keep a PHP instance around (does not need to be public) and point it there...

Comment 1

[Jake Maul [:jakem]]

I'm confused... maybe because I don't know what this setting does.

To clarify: you want the new dev/stage/prod django crash-stats app to have this setting pointing at the *current* non-django crash-stats app?

Want to make sure we're one the same page here. :)

Comment 2

[Robert Helmer [:rhelmer]]

(In reply to Jake Maul [:jakem] from comment #1)
> I'm confused... maybe because I don't know what this setting does.
> 
> To clarify: you want the new dev/stage/prod django crash-stats app to have
> this setting pointing at the *current* non-django crash-stats app?
> 
> Want to make sure we're one the same page here. :)

Right, this is a workaround until the new correlations service is ready in bug 788048

The PHP app does not actually need to be public, just reachable by the django server. Since we'll have them running in parallel for a while this seems like an OK workaround for the moment.

Comment 3

[Robert Helmer [:rhelmer]]

(In reply to Robert Helmer [:rhelmer] from comment #2)
> (In reply to Jake Maul [:jakem] from comment #1)
> > I'm confused... maybe because I don't know what this setting does.
> > 
> > To clarify: you want the new dev/stage/prod django crash-stats app to have
> > this setting pointing at the *current* non-django crash-stats app?
> > 
> > Want to make sure we're one the same page here. :)
> 
> Right, this is a workaround until the new correlations service is ready in
> bug 788048

We are working on a better way to do this in bug 876051, now (closed older correlations bugs)

Comment 4

[Robert Helmer [:rhelmer]]

This is the only bug holding us up from going live with django crash-stats.

In the meantime, can we do the following? :

Proxy correlations-related URLs from Apache on the django servers to the PHP servers, using an internal hostname/IP

Then we can leave CORRELATIONS_SERVER alone, and not have to deal with cross-site origin issues, worry about what the public PHP URL is, etc. etc.

Comment 5

[Robert Helmer [:rhelmer]]

Assuming comment 4 is ok, what we need to do here is proxy any URL that begins with /correlations to the old PHP servers (to the load balancer IP/hostname specifically)

Comment 6

[Robert Helmer [:rhelmer]]

In the meantime we went ahead and ported this directly to the Django app (see bug 876022 and bug 876051), huzzah!