The document discusses how system administration has changed over time and will continue to change in the future. Some of the key points made include: - Infrastructure used to be deployed manually but now utilizes infrastructure as code approaches like Chef, Puppet, and Ansible for automated deployments. - Virtualization has largely replaced physical servers and made infrastructure more flexible and cost-effective. - Continuous delivery practices from software development are being applied to infrastructure to allow for reliable, tested changes. - Monitoring has improved from early tools to current approaches that leverage metrics, machine learning, and aim to provide actionable information. - Emerging technologies like containers, orchestration, and software-defined infrastructure will further transform system

1. The future of System
Administration
Kris Buytaert
January 2014
@krisbuytaert

2. Kris Buytaert
●
●
●
●
●
●
●
In the 90'ies I used to be a Dev ,
Then Became an Op
Chief Trolling Officer and Open Source
Consultant @inuits.eu
Everything is an effing DNS Problem
Building Clouds since before the bookstore
Some books, some papers, some blogs
Evangelizing devops

3. Why Me ?

4. The future is here,
it's just not evenly distributed
yet

5. Why we study history ?
●
Because I`m a grumpy old frustrated sysadmin
●
Because I`m an old opiniated guy
●
Because history repeats
●
We need to learn from our mistakes

6. What has changed
●
Software was
delivered on CD's,
then DVD's,
●
Then online ,
periodically
●
Then internally , more
frequently
●
Continuously

7. What has changed
●
End users
●
1 user using their own
PC,
●
●
●
End users working 95
●
Local users using your
application during
daytime
●
A global economy,
no downtime an be
tolerated
500 users using the
intranet application
500000 users the
cloud / saas
(.eu)

8. Deploying an Infrastructure
●
1996 : Manual Installations
●
2001 : Mondo rescue (reproducable single instances)
●
2003 : SystemImager
•
Reproducable Infrastructure , with
“OVERRIDES”
•
Fast Multicast Image deployments
•
Image Sprawl (thank you VMware)

9. Deploying an Infrastructure
●
1996 : Manual Installations
●
2001 : Mondo rescue
●
2003 : SystemImager
●
2005 : Kickstart / FAI
•
Dreaming of Jeos + IAC (Cfengine)

10. Deploying an Infrastructure
●
1996 : Manual Installations
●
2001 : Mondo rescue
●
2003 : SystemImager
●
2005 : Dreaming of Jeos + IAC
●
2008 : Actual JeOS + IAC
●
2010 : Vagrant for development

11. Physical to Virtual
WARNING : Adoption vs Introduction
●
Up till 2000 , Virtualization was a desktop thing,
running emulation on your desktop (Plex, Bochs
●
Early 2000's Paravirtualization , Xen starts and
gains adoption
●
August 2006 : Amazon announced EC2
●
2009 : US started adopting EC2, Europe never
really did
●
2012 – now : Private clouds

12. Virtualization should be Cheap
●
1 host with way too much services
•
●
No isolation, dependency hell , management
hell
1 host multiple vm's , same CAPEX
•
VM's are cheap !
●
Public clouds => multiple vm's , growing OPEX
●
Private clouds => multiple vm's same CAPEX

13. High Availability & Scaleout
●
KISS
●
Clustered Storage is finally in it's 10's
●
Most apps still don't get it
•
Stateless vs Statefull

14. For years we've tolerated humans to to make
structural manual changes to the infrastructure
our critical applications are running on.
Whilst at the same time demanding those critical
applications to go trough rigid test scenarios.
Who let this happen ?

15. Infrastructure as Code
●
Treat configuration automation as code
●
Development best practices
•
Model your infrastructure
•
Version your cookbooks / manifests
•
Test your cookbooks/ manifests
•
Dev/ test /uat / prod for your infra
●
Model your infrastructure
●
A working service = automated ( Application Code + Infrastructure
Code + Security + Monitoring )
●
Think Puppet, Chef, Cfengine, ....

16. Testdriven Infrastructure

17. Jenkins Pipeline

18. A pipeline
●
Checkout code
●
Upload to Repo
●
Syntax
●
Deploy on Test
●
Style
●
Check Puppetruns
●
Code Coverage
●
Check Icinga
●
Tests
●
Promote to UAT
●
Build
●
More Tests
●
Package

19. Software Release
management is not a
solved problem

20. Repository Management

21. Continuous Delivery or Deployment
of Infrastructure

22. Orchestration
●
Distributed ssh++
●
Trigger actions on selected nodes
●
Think : Mcollective, Ansible, Salt, Rundeck
●
(& Discuss :))

23. nd
Orchestration 2 gen
Aka
Choreography
●
While ....
●
First install X
●
When it is ready configure Y
●
Then notify Z
●
Think : Noah , Zookeeper, Serf , Juju

24. Juju

25. Serf
Serf is a decentralized solution for service
discovery and orchestration that is lightweight,
highly available, and fault tolerant.
Gossip based, Detecting Failure, etc.
By HashiCorp

26. Deploying an Infrastructure
●
1996 : Manual Installations
●
2001 : Mondo rescue
●
2003 : SystemImager
●
2005 : Dreaming of Jeos + IAC (CFengine)
●
2008 : Actual JeOS + IAC
●
2010 : dev/test/prod with Vagrant & IAC
●
2014: Stateless , Immutable infrastructure ?

27. Are Docker, Packer , next ?
Stateless
Immutable

28. #monitoringsucks -> #monitoringlove
●
1996 : BigBrother
●
2001: Netsaint => Nagios + OpenNMS
●
2009: Shootout => Nagios (& Forks) clear
winner
●
2011: @lusis #monitoringsucks
●
2012: @ulfmansson #monitoringlove

30. Monitoring & Metrics
•
Oculus , Skyline, Riemann, Esper,
•
FlapJack (2nd incarnation)
•
BPM & Monitoring
•
Creating Information out of this data
•
Big data
•
Machine Learning

31. But what about hardware?
●
Software Defined Networking
●
Software Defined Storage
●
Software Defined Anything ?

32. Yet I`m scared
●
Burnouts
●
Juniors, they don't build em like they used to
•
Lack of Passion
•
Broken education

33. Our role tomorrow:
●
Teacher (for both collegues and suppliers)
●
Student
●
Math Expert
●
Developer
●
Troubleshooter
●
Evangelist
●
Shrink
●
Gap Bridger

34. Work to be done..
●
#releasemanagement
●
#Backupsucks
●
#printingsucks

35. Every 18 months, automate yourselve out of your
job
Someone at Google, longtime ago

36. CfgMgmtCamp.eu
Gent
3 & 4 February 2014
Ansible, Chef, Puppet, Cfengine, Rudder,
Juju,Saltstack, Foreman & You ?

37. Contact
Kris Buytaert
Kris.Buytaert@inuits.be
Further Reading
@krisbuytaert
http://www.krisbuytaert.be/blog/
http://www.inuits.be/
Inuits
Duboistraat 50
2060 Antwerpen
Belgium
891.514.231
+32 475 961221