Closed
Bug 1342947
Opened 9 years ago
Closed 7 years ago
Move mozaggregator service to dockerflow
Categories
(Data Platform and Tools :: General, defect, P3)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rvitillo, Assigned: hwoo)
References
Details
(Whiteboard: [DataOps])
No description provided.
Updated•9 years ago
|
Points: --- → 3
Priority: -- → P2
Updated•9 years ago
|
Whiteboard: [SvcOps]
Updated•8 years ago
|
Component: Metrics: Pipeline → Datasets: Telemetry Aggregates
Product: Cloud Services → Data Platform and Tools
Updated•8 years ago
|
Component: Datasets: Telemetry Aggregates → Telemetry Aggregation Service
Updated•8 years ago
|
Priority: P2 → P3
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → hwoo
Assignee | ||
Comment 1•8 years ago
|
||
Note: this also requires us to migrate the local test env from ansible/vagrant to docker-compose
Assignee | ||
Comment 2•8 years ago
|
||
PR to migrate everything to docker and docker-compose for tests
https://github.com/mozilla/python_mozaggregator/pull/50
Todo after:
- Remove travis build for tests
- add endpoints to flask service for health, version, etc to adhere to dockerflow spec
- cloudops-deployment jenkins pipeline job (ansible, aws, puppet) to deploy service in aws
- fix gunicorn flask ssl issue
- add newrelic-admin entrypoint?
Updated•8 years ago
|
Whiteboard: [SvcOps] → [DataOps]
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Telemetry Aggregation Service → General
You need to log in
before you can comment on or make changes to this bug.
Description
•