Slide 32
Slide 32 text
FINAL THOUGHTS
• Ansible attempts to be a reset in making some earlier automation tool concepts more accessible, and mostly succeeds at this.
YAML language is not great, but it’s quick. Less moving parts is a huge win and makes tooling accessible to audiences that
struggled with previous efforts, which is why it’s so widely deployed. Still, it’s a stepping stone towards immutable - but with
various shops at various points on that journey. Many have enough other things to deal with that they aren’t ready for that now.
• Still, IT systems are evolving more towards immutable systems (image-based) and PaaS-enabling systems over time,
particularly in leading edge shops or new ventures. Progress is good! Various things still getting refined. Containers will help, but
right now also add a degree of complexity. Just building AMIs if you’re on Amazon is a great start. Immutable systems means you
can skip learning automation languages, which is nice (ex: Docker files), but you likely still need automation to deploy your
container management system itself.
• The infrastructure and nuts and bolts behind the apps, cloud, and network will matter less to more people over time. More
so, intent can be coded, rather than form and common building blocks.
• True IaaS applications are significantly different, and should be written differently. Flexibility, lock-in, and cost is traded for
better reliability, scalability, ease of management. Write apps for the business, not reinventing the same wheels everyone has to
invent.
• Much more people writing code in Ops land. Will “10 years in AWS Services” is going to be the new “10 years in J2EE”
for Ops professionals?