Closed Bug 1309622 Opened 9 years ago Closed 8 years ago

Move Airflow deployment away from ECS

Categories

(Data Platform and Tools :: General, defect, P1)

defect
Points:
3

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: jezdez)

References

Details

Attachments

(1 file)

- Investigate alternative deployment options (Heroku? AWS-based deployment services? Remove some steps [e.g. Ansible]?) - Migrate repo & production deployment to the best alternative
Blocks: 1269754
No longer blocks: 1290146
Looking into this a notch, Airflow can be run on Heroku as shown in https://github.com/heroku/heroku-airflow Alternatively I think following Cloudops' dockerflow (https://github.com/mozilla-services/Dockerflow) makes sense if we decide to continue to run Airflow on our own infrastructure. For the matter, the Python library that implements dockerflow patterns for Python project (https://github.com/mozilla-services/python-dockerflow) would need to get a Flask extension. Ironically the heroku-airflow shows how to implement a custom flask extension as a Airflow plugin: https://github.com/heroku/heroku-airflow/blob/b87a5a83198c1b00072c41f5f4ff0532e9534b19/plugins/ssl_everything.py
Blocks: 1283484
Jason has reviewed and approved my PR that changes our Airflow instance to use Dockerflow patterns instead of Ansible/Beanstalk. I think it would make sense to hand this over to ops now to set up the WTMO (Airflow) instance similarly to ATMO. I'll be working on adding Flask support to python-dockerflow ASAP and update the Airflow code but I don't think we should block on this since we need to let the move to Dockerflow happen first before so we can update Airflow to use spot instances. Can you think of something that is missing from the Airflow side?
Flags: needinfo?(jthomas)
Flags: needinfo?(bimsland)
Priority: P3 → P1
Assignee: nobody → jezdez
Status: NEW → ASSIGNED
(In reply to Jannis Leidel [:jezdez] from comment #3) > > Can you think of something that is missing from the Airflow side? As of right now things look good, but if we run into issues we will reach out to you. Bug 1336975 for the actual migration into JenkinsV2.
Flags: needinfo?(jthomas)
Flags: needinfo?(bimsland)
Component: Metrics: Pipeline → Scheduling
Product: Cloud Services → Data Platform and Tools
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Scheduling → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: