Your SlideShare is downloading. ×
The Future of System Administration
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

The Future of System Administration

10,713
views

Published on

I was asked to replace a talk at the #CCCEU13 conf .. I kept the original title... This is the result. …

I was asked to replace a talk at the #CCCEU13 conf .. I kept the original title... This is the result.

The Future of System Administration

Published in: Education, Technology

0 Comments
19 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
10,713
On Slideshare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
94
Comments
0
Likes
19
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The future of System Administration Kris Buytaert Apache CloudStack Collaboration Summit Amsterdam 2013 @krisbuytaert
  • 2. Kris Buytaert ● ● ● ● ● ● ● 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. Why Me ?
  • 5. The future is here, it's just not evenly distributed yet
  • 6. 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
  • 7. What has changed ● Software was delivered on CD's, then DVD's, ● Then online , periodically ● Then internally , more frequently ● Continuously
  • 8. Deploying an Infrastructure ● 1996 : Manual Installations ● 2001 : Mondo rescue = Reproducable single instances
  • 9. Deploying an Infrastructure ● 1996 : Manual Installations ● 2001 : Mondo rescue ● 2003 : SystemImager • Reproducable Infrastructure , with “OVERRIDES” • Fast Multicast Image deployments • Image Sprawl (thank you VMware)
  • 10. Deploying an Infrastructure ● 1996 : Manual Installations ● 2001 : Mondo rescue ● 2003 : SystemImager ● 2005 : Dreaming of Jeos + IAC (Cfengine) • Kickstart / FAI
  • 11. Deploying an Infrastructure ● 1996 : Manual Installations ● 2001 : Mondo rescue ● 2003 : SystemImager ● 2005 : Dreaming of Jeos + IAC (CFengine) ● 2008 : Actual JeOS + IAC ● 2010 : Vagrant for development
  • 12. What has changed ● End users ● 1 user using their own PC, ● 500 users using the intranet application ● 500000 users the cloud / saas (.eu)
  • 13. 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
  • 14. 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
  • 15. What has changed ● End users working 9-5 ● Local users using your application during daytime ● A global economy, no downtime an be tolerated
  • 16. High Availability & Scaleout ● KISS ● Clustered Storage is finally in it's 10's ● Most apps still don't get it • Stateless vs Statefull
  • 17. 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 ?
  • 18. 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, ....
  • 19. Testdriven Infrastructure
  • 20. Jenkins Pipeline
  • 21. 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
  • 22. Repository Management
  • 23. Continuous Delivery or Deployment of Infrastructure
  • 24. Orchestration ● Distributed ssh++ ● Trigger actions on selected nodes ● Think : Mcollective, Ansible, Salt, Rundeck ● (& Discuss :))
  • 25. nd Orchestration 2 ● While .... ● First install X ● When it is ready configure Y ● Then notify Z ● Think : Noah , Zookeeper, Serf , Juju gen
  • 26. Juju
  • 27. 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
  • 28. Deploying an Infrastructure ● 1996 : Manual Installations ● 2001 : Mondo rescue ● 2003 : SystemImager ● 2005 : Dreaming of Jeos + IAC (CFengine) ● 2008 : Actual JeOS + IAC ● 2010 : Vagrant ● 2014: Stateless , Immutable infrastructure ?
  • 29. Are Docker, Packer , next ? Stateless Immutable
  • 30. #monitoringsucks -> #monitoringlove ● 1996 : BigBrother ● 2001: Netsaint => Nagios + OpenNMS ● 2009: Shootout => Nagios (& Forks) clear winner ● 2011: @lusis #monitoringsucks ● 2012: @ulfmansson #monitoringlove
  • 31. I love CheckMK ● Autodetection ● Multiplexing ● Trend Forecasting
  • 32. I hate CheckMK • Autodetection ? • • Functionalities • • Service, eg. vhosts etc Single Source of Truth
  • 33. Monitoring & Metrics • Oculus , Skyline, Riemann, Esper, • FlapJack (2nd incarnation) • BPM & Monitoring • Creating Information out of this data • Big data • Machine Learning
  • 34. I`m scared of the future ! ● Juniors ● Lack of Passion ● Broken education
  • 35. Our role tomorrow: ● Teacher (for both collegues and suppliers) ● Student ● Math Expert ● Developer ● Troubleshooter ● Evangelist ● Shrink ● Gap Bridger
  • 36. Work to be done.. ● #releasemanagement ● #Backupsucks ● #printingsucks
  • 37. Every 18 months, automate yourselve out of your job Someone at Google, longtime ago
  • 38. CfgMgmtCamp.eu Gent 3 & 4 February 2014 Ansible, Chef, Puppet, Cfengine, Rudder, Juju,Saltstack, Foreman & You ?
  • 39. Contact Kris Buytaert Kris.Buytaert@inuits.be Further Reading @krisbuytaert http://www.krisbuytaert.be/b log/ http://www.inuits.be/ Inuits Duboistraat 50 2060 Antwerpen Belgium 891.514.231 +32 475 961221