Closed
Bug 1171050
Opened 10 years ago
Closed 10 years ago
Deploy micro services on Heroku?
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rvitillo, Unassigned)
References
Details
(Whiteboard: [unifiedTelemetry])
We have some small Telemetry services, such as the revision and aggregation service, which require to be deployed on AWS and maintained over time.
Heroku offers a neat service [1] that integrates with github which would allow us to easily maintain and scale those services.
Wesley, do you have any thoughts? Do we have an account with Heroku that we can use?
[1] https://devcenter.heroku.com/articles/github-integration
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(whd)
Comment 1•10 years ago
|
||
Triage notes: Wes is going to get some credentials for Roberto to test with. We will also see if it's possible to integrate Heroku with our existing AWS IAM.
Priority: -- → P2
Comment 2•10 years ago
|
||
Details for getting credentials here: https://mana.mozilla.org/wiki/display/TS/Heroku. As discussed, anything with PII (see https://mana.mozilla.org/wiki/display/SECURITY/Heroku) or that is critical to the operation of UT should be run by Cloud Operations in our production environment.
Flags: needinfo?(whd)
Updated•10 years ago
|
Whiteboard: [unifiedTelemetry]
Comment 3•10 years ago
|
||
is this still needed? for triage
Reporter | ||
Comment 4•10 years ago
|
||
We have decided to not deploy services on Heroku as Ops doesn't support it.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•