search

mozilla / ensemble

The platform that powers the Firefox Public Data Report :violin: :trumpet: :musical_keyboard:
https://data.firefox.com/
Mozilla Public License 2.0
21 stars 14 forks source link

Move ensemble to DataOps #108

Closed openjck closed 6 years ago

openjck commented 6 years ago

Heroku is great for starting up, but we can shift some of the burden of managing the application by switching to AWS. @pdehaan made a great argument for this in #63:

Although, I still strongly suggest that you guys consider getting OPs involved and have them host this on our battle proven AWS stacks, and then they can handle the auto-scaling and notifications and everything else that OPs excels at. Self managing your own stuff can get very risky and having to be on call when something stops working at 2am on a Sunday is never fun. And reinventing scaling and performance alerts probably isn't a fun task either.

openjck commented 6 years ago

I spoke with Wesley about this today. He said that as long as we can get the site running in Docker / Dockerflow, Cloud Ops can get it on AWS in about one day. I thought it would take much longer, but with this timeframe we could get this done before release and solve a lot of problems (like #63 and #69) in the process by having Cloud Ops manage the site from that point forward.

openjck commented 6 years ago

187 is open to run Ensemble in Docker(flow) on production. That appears to be all that's needed on our end.

Bug 1473151 is open with DataOps about the rest. The bug is private for the same reason this repo is private: to not get ahead of Marketing about the release of this data. Let me know if you want read access to the bug.

openjck commented 6 years ago

Also, I'm holding #187 for now until we get the go-ahead from DataOps to move ensemble into Docker.

openjck commented 6 years ago

187 is merged as we will very likely want this running in Docker.

openjck commented 6 years ago

There's nothing else for us to do here until we hear back from DataOps.

If DataOps is unable the host the application for launch, we'll need to launch the site ourselves on Heroku. If we launch it on Heroku, we'll probably want to address these Heroku issues first. If DataOps does host the application for the launch, we can probably ignore those Heroku issues.

openjck commented 6 years ago

I actually didn't intend to close this with d3bb5614a52e46d785a3a64494ef4aabcf15cadb, but it should be closed nonetheless. DataOps has a staging site and they're prepared to launch a production site on Tuesday.