10 minute lightning talk given at the first Stockholm DevOps meetup on why and how we wound up with a certain level of infrastructure automation at Hitta.se.
INFRA 2.0 (BETA) static + api (linux) web (windows) cache + api (windows) unique visitors / week Thursday, June 2, 2011 For various reasons Linux got introduced in parts of the solution
INFRA 2.0 (REFINED) static + api (linux) static (linux) api (linux) Thursday, June 2, 2011 Those Linux nodes where then split out into two main node groups
INFRA 2.0 api (linux) static (linux) web (windows) web (linux) unique visitors / week Thursday, June 2, 2011 The much simplified high level overview of the current solution
web (windows) PROBLEM? 4 + 4 + 3 = 11 •11 nginx •11 tomcat •11 sshd •11 /etc/sudoers •11 foo... •11 bar... All manually configured (by us or by per-ticket by provider) api (linux) static (linux) web (linux) Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Define once Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata Define once Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata How many X do we have? Define once Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata How many X do we have? How many Z of version Y are we running? Define once Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata Query your infrastructure! How many X do we have? How many Z of version Y are we running? Define once Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata Query your infrastructure! How many X do we have? How many Z of version Y are we running? Define once Consistency Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata Query your infrastructure! How many X do we have? How many Z of version Y are we running? Define once Consistency Predictability Thursday, June 2, 2011
WE WANT Reproducible infrastructure Disaster recovery Free expansion (3 or 100 won’t differ) Apply everywhere (it should be applied) We use X in way Y Metadata Query your infrastructure! How many X do we have? How many Z of version Y are we running? Define once Consistency Predictability Confidence Thursday, June 2, 2011
TOOLING http://en.wikipedia.org/wiki/Comparison_of_open_source_configuration_management_software Thursday, June 2, 2011 cfengine, then puppet, then chef
Thursday, June 2, 2011 Right from the start it’s pretty obvious what’s being used as far as my network and “research” counts. The long timers started with cfengine and most tend to be on puppet with some on
Thursday, June 2, 2011 At the time of selecting tech we didn’t have the manpower nor the time to learn and introduce any tool ourselves. And we were unable to find anyone who could assist us with