eSynergy Keiran Sweet - Bringing order to chaos with puppet
Upcoming SlideShare
Loading in...5
×
 

eSynergy Keiran Sweet - Bringing order to chaos with puppet

on

  • 532 views

 

Statistics

Views

Total Views
532
Views on SlideShare
531
Embed Views
1

Actions

Likes
0
Downloads
4
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

eSynergy Keiran Sweet - Bringing order to chaos with puppet Presentation Transcript

  • 1. Keiran SweetBringing order to chaos with Puppet
  • 2. Bringing orderto Chaos withPuppetKeiran Sweet
  • 3. About me• UNIX Administrator in the Financial sector• ~10 years UNIX experience across anumber of industries• Using Puppet for 3+ years• Devops advocate• Likes automating things• Likes keeping things simple
  • 4. Obligatory..disclaimer { keiran:opinions => mine,representing => myself,}
  • 5. Puppet ?• What is it ?• What can it do ?• Who uses it ?• What is its role in Devops ?• Similar to ?What is i
  • 6. Example DSL #1# Managing a User accountuser { Keiran.Sweet:ensure => present,comment => Keiran Sweet,gid => 10042,groups => [wheel],home => /home/Keiran.Sweet,shell => /bin/bash,uid => 10042,}
  • 7. Example DSL #2# Deploying and managing a filefile { /etc/security/limits.conf:ensure => file,source => puppet:///modules/ostune/limits.conf,owner => root,group => root,mode => 644,}
  • 8. Case study
  • 9. Case Study - Original Environment• OS - Enterprise Linuxo RHEL 4 & 5o CentOS 4 & 5o RHEL 6 was on the way• "Management" toolso Satellite Server - RHEL Managemento Spacewalk Server - CentOS Managemento Glued together with Cobbler, DHCP, TFTP & PXEo Numerous "rogue" serverso External 3rd Party repositorieso Lots of hand crafted servers
  • 10. Case Study - Original Environment• Provisioningo Kickstart via Satellite & Spacewalk Basic installs of the OS only Servers were built as localhost.localdomain Configuration done by hand post kickstart Packages werent being utilised (tar, zips, scripts) VMTools, HP PSPs, HW Agents - Often missingo DVD/CD Installs still being done Left disconnected from Satellite / Spacewalk Non-standard configurations Some talked to unknown repos on the internet (!)
  • 11. Arriving in the office each morning...
  • 12. Linux TeamReaction
  • 13. Case Study - Original Environment• Result - Utter carnageo Business was suffering Application & Server instability == Outages Delays in deployment of new platforms Delays in upgrading and deploying ourapplicationso The Linux admins were suffering Flying blind - Unknown fleet composition Every issue resulted in a journey of discovery Inconsistent configurations made delivering otherinfrastructure projects difficult - ie, Monitoring Wasnt enjoyable (not enough time for reddit)
  • 14. Aint nobody gottime fo dat
  • 15. Case Study - What did we need ?• Configuration Managemento Self healingo Rich Reportingo Vendor neutralo Flexibleo Version controlo Integrates with provisioning workflow• Software Management and Distributiono Centralised, Simple & Scalableo Secure (Signed Packages & TLS)o Redundancy - Supported mirrors/slaves
  • 16. Case Study - What we chose• Puppeto Configuration Managemento Self healingo Rich reportingo Cross platformo Extensible• Foremano Puppet node classifier (ENC)o DHCP/TFTP/PXE Integrationo Puppet report visualisationo Host inventory & CMDB
  • 17. Case Study - How it was assembled
  • 18. Case Study - Fixing ProvisioningHostnameOS VersionMAC AddressPartition TableData Center
  • 19. Case Study - Importing the fleet• Install Puppet agent• Boot strap the client• Apply the standardmodules• TestResult:
  • 20. Case Study - End result - Stability• Costs are down• Business applications are more stable• React to requests more rapidly• Users have a common experience• Fleet management is much easier
  • 21. Questions ?• Contacto Twitter: @keiran_so Email: Keiran@gmail.com• Imageso Devops Reactionso Reddit
  • 22. Case Study - End result - Dashboard
  • 23. Case Study - End result - Reports
  • 24. Case Study - End result - Node data