An Ops Primer to Productionalizing Datameer
Download as PPTX, PDF0 likes194 views
This document provides guidance on productionalizing Datameer by packaging it into installable artifacts, making it a service, using configuration management, versioning components, setting up a primary and secondary system for failure scenarios, monitoring using HTTP 200 checks, and using JMX. It emphasizes versioning, monitoring, and planning for failure scenarios when deploying Datameer into a production environment.
An Ops Primer to Productionalizing Datameer
- 1. An Operations Primer to Productionalizing Datameer
- 3. Package your bundle Convert your bundles into installable artifacts RPM or DEB ?
- 4. Make it a service • Because they don’t do it for you • Because
- 5. Use Config Management Files you need to manage: • conf/default.properties • conf/live.properties • etc/das-env.sh • etc/jetty-https.xml • etc/jetty-rewrite.xml • etc/jetty.xml • webapps/conductor/WEB-INF/web.xml
- 8. And when they change…. Datameer does this:
- 10. Version your Database! Make copies because once you upgrade….
- 11. Failure Scenarios Primary Secondary This setup is kind of pointless, because the only time you will ever actually use the secondary is
- 12. Failure Scenarios Primary Secondary Is if this happens
- 13. Monitor, Monitor, Monitor Use HTTP 200 checks.
- 14. Monitor, Monitor, Monitor Use HTTP 200 checks. Because when this happens:
- 15. JMX is doing this:
- 16. Have Fun & Thanks !