Managing Deployment Monster with Apache Ambari

Summary:

 Does your software require more than 1 service to be run in the back-end (yes include your database too!)?
 Do you spend hours on a fresh install?
 Do you need to dig through multiple logs to debug a production issue?
 Do you miss having alerts of the unstable environment (disk full? too much swap? network down? process died?) before it becomes a visible production issue?
 Did you ever by mistake overwrote a configuration file doing a new release?
 Do you even have a full history of ALL release and configuration history of a production environment?
 Does your customer DO NOT give shell access to even do deployments?
 Does your app have admin UI to tune configuration parameters?
 Do you want to impress your customer by showcasing beautiful self-care portal to see /tune (potentially revert too!) your whole application cluster from single view?

Agenda:

 Need for "Operation Manager Systems" for Installation / Configuration / Lifecycle management / Monitoring / Log Aggregation / Alerting
 Replacing Orchestration tools with Ambari: puppet, Ansible, Ansible Tower, Rancher Kubernates
 Replacing Unified Log collection viewer: Logstash/Beats, ElasticSearch
 Replacing Configuration Management tools: Puppet, Ansible, Consul
 Replacing Metric collection and Monitoring tools: Nagios, Ganglia, Elastic stack, Prometheus, Graphite, InfluxDB, OpenTSDB
 Replacing Operational dashboards and visualizations: Kibana, Grafana, Sensu
 Replacing host onboarding & Auto Scaling: Docker-Compose, Docker-Swarm, Rancher

About Speakers:
Nishit is working at Ishi systems as a Full-stack developer with many
years of experience in Java / Spring Boot / RESTful Services / CI/CD and
Ambari.

Niket Shah, again a full stack developer with many years of experience in building and deploying large applications at Ishi Systems, he primarily works in SpringBoot, Ambari, Ansible etc