Move kpi collector and kpi dashboard into production vpc

[kparlante]

The kpiggybank collector and kpi dashboard are currently hosted on an ephemeral awsbox and managed by @kparlante, without real monitoring, etc. We need to move this into a true production setup.

• Better from a security perspective
• We're going to start counting on the data & visualizations for strategic decision making
• q3!

(We could stage this and do the collector and dashboard separately).

[gene1wood]

Can you point me to the steps you use to provision the machine and the rpms that kpi is packaged in? I'll start building the provisioning logic from that

[kparlante]

@gene1wood : There are two servers, the collector (https://github.com/mozilla/kpiggybank) and the dashboard (https://github.com/mozilla/kpi-dashboard). Notes on deploying them: https://id.etherpad.mozilla.org/kpi-dev-production. (Yes, its nasty! No rpms. I moved some work into awsbox & the post deploy scripts, but I add the volumes by hand. Note that both require couchdb, and use different versions.)

[gene1wood]

@kparlante would it be possible to generate an RPM of the kpi code (maybe using fpm) I can work on the provisioning logic for the rest of it while you get that

[kparlante]

@gene1wood sure I'll give fpm a spin

[kparlante]

Current plan is to shut down kpiggybank and kpi-dashboard (and use heka/es/kibana stack instead), so closing this out.