Divorcing your single vendor cloud
Florian Heigl - Monday, February 6, 15:40 - 16:20 - B4.042
We look at how Rudder was used to solve some of the common issues faced by maturing startups:
- * being too small to benefit from many best practices
- * silent absence of documentation
- * lack of reproducibility
- * danger of non-restricted SSH access and random "clever fixes"
- * tasks stuck on personal roles
- * lack of even trivial ops procedures
- * finally and foremost, being LOCKED IN with your starting provider
What we did was to model most of the things a real admin would do into Rudder.
The policy is deep. SSH access is 'gone'. Able to bring any random AMI into shape, yet well abstracted to run on anything from bare metal to AWS *at the same time*."
About Florian Heigl
Florian has enjoyed being a systems administrator in mission critical environments for a long time. He first peeked into automation around 2005, applied some of that while fine-tuning & hardening industrial-style systems with 10-year lifecycles. Between that, he's doing monitoring consulting.
He believes all those things are one:
Making stuff work[tm] for your users.
He became a complete Rudder convert in 2014 and has used it in multiple setups by now.