Closed Bug 1676401 Opened 4 years ago Closed 4 years ago

set up eliot in stage

Categories

(Cloud Services :: Operations: Tecken, task)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: brian)

References

Details

Eliot is the new implementation of the symbolication API. Previously, symbolication was handled by the Tecken webapp. This splits it out as a separate microservice.

This bug covers getting Eliot running in stage.

It needs its own hostname separate from the existing Tecken webapp. I'll let you decide on that.

It needs infrastructure and deploy bits. It can deploy to stage along with the Tecken webapp.

It needs configuration. Configuration is documented here:

https://tecken.readthedocs.io/en/latest/configuration.html#eliot-configuration

Status: NEW → ASSIGNED

https://github.com/mozilla-services/cloudops-deployment/pull/4109 is up for review. This adds Eliot for stage but not in prod. I've temporarily made it the default branch in Jenkins.

We talked in Slack about a few things. Figured I'd copy them here so they're easier to find:

This bug covers working on getting Eliot in stage. We have a bunch of testing and bug-fixing work before we put it in prod. We'll set Eliot up in prod in a future bug.

For now, we're not going to forward symbolication API requests from the Tecken webapp to Eliot. We want to be able to access both the Tecken webapp symbolication API and the Eliot symbolication API in order to test Eliot out. We'll change this in a future bug.

Eliot in stage and prod will be configured with ELIOT_SYMBOLS_URLS=https://symbols.mozilla.org/try/ . The Tecken webapp will look for symbols in both the public regular location and the public try location when using that symbols url. We want Eliot in stage to use production Tecken webapp for symbol downloads because there aren't any useful symbols in the stage environment and we wouldn't be able to test symbolication correctness.

I've landed the PR.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.