Presentation
1 like368 views
This document provides an introduction to configuration management with Puppet. It discusses the problems system administrators and developers face with managing multiple servers and applications manually. It introduces configuration management as a way to automate and centralize management of packages, files, services and other system components. The document outlines the benefits of Puppet, including visibility, predictability, efficiency and reduced errors. It describes the typical Puppet architecture including the Puppet master, agents, modules and Puppet DSL language. Finally, it demonstrates Puppet concepts through a presentation and code examples.
Presentation
- 1. An introduction to configuration management with Puppet Rudy Gevaert
- 2. About me GNU/Linux sysadmin Post- and Puppetmaster at Ghent University Doing ICT for development projects in Ethiopia and Cuba http://webworm.org @rgevaert Rudy.Gevaert@UGent.be
- 3. Today’s presentation. . . From the past to the present Config management? Puppet components Puppet language Demonstration
- 4. From the past . . .
- 5. . . . to the present
- 6. . . . and the future
- 7. The future is already here — it’s just not very evenly distributed. (William Gibson) Downloads of Puppet forge modules October 20121 1 https://puppetlabs.com/blog/mapping-the-puppet-forge
- 8. Problem of the system administrator How to manage:
- 9. Problem of the system administrator How to manage: Multiple applications Different stacks 1000 servers (and more!)
- 10. More problems: from a developers perspective Before: Monolithic application Development on the server Sole developer Long time to market software
- 11. More problems: from a developers perspective Before: Monolithic application Development on the server Sole developer Long time to market software Now: Distributed application Set up local dev environment Multiple teams Short time to market
- 12. More problems: from a developers perspective Before: Monolithic application Development on the server Sole developer Long time to market software Now: Distributed application Set up local dev environment Multiple teams Short time to market How do you build a local development environment that is similar to production?
- 13. More problems: from a developers perspective Before: Monolithic application Development on the server Sole developer Long time to market software Now: Distributed application Set up local dev environment Multiple teams Short time to market How do you build a local development environment that is similar to production? =⇒ Puppet
- 14. What is configuration management? Is a method to automatically and centrally manage: the packages, configuration files process state firewall rules and other settings to do their assigned job Without config mgt? Manually or handwritten scripts
- 15. Configuration Management It’s also about making changes to the system in an organized way so your servers and modified deliberately and correctly while accounting for relationships between system components
- 16. Why you need automated configuration management? Not automating config mgt causes pain! Manual errors, custom scripts can be fragile, custom scripts aren’t accessible to everyone, you can’t scale Configuration management eliminates manual work, and creates dependability and predictability
- 17. Why you need automated configuration management? Another problem with the manual-change and script-based approach is the lack of a single source of truth. Automation makes you productive; lets the people who are dependent on you be more productive; and gives you the time to up level your job and your skills. Spend less time on manual configuration and putting out the inevitable fires
- 18. Who benefits Everyone benefits from automated configuration management! Sysadmins get: visibility into the state of the overall system, and each component of it faster identification of problems, and faster remediation efficiency in performing regular maintenance documentation, so fixes and updates can be referenced and repeated an end to 3:00 am emergency calls
- 19. Who benefits Quality assurance and test engineers get: the confidence that they’re testing code in an environment that’s identical to where the code was created and where it will finally run
- 20. Who benefits IT managers get: visibility into what the IT team is doing: maintenance, remediation, provisioning faster time to recovery, so greater satisfaction for internal and external customers more efficient, predictable operations better ability to plan better ability to report to other teams in the company
- 21. Who benefits The entire company gets: more stable and dependable systems and software to work on faster service from IT when things need to be installed or fixed the ability to expand IT services while containing costs the confidence to make changes more quickly and learn from market response Customers (the people who pay us!) get: better products, better services, faster innovation and better response to their needs
- 22. The typical life cycle of a server ⇒ ⇒
- 23. The typical life cycle of a server ⇒ ⇒ Installation and bootstrap Configure applications Administer system
- 24. The typical life cycle of a server ⇒ ⇒ Installation and bootstrap Configure applications Administer system Automatic install with net boot or VM image Puppet Puppet
- 25. Puppet Configuration management software developed by Puppetlabs http://www.puppetlabs.com Free Software version and Proprietary version (Puppet Enterprise) Supports: GNU/Linux, Windows, Solaris Competition: Cfeninge, Chef, Ansible, Saltstack
- 27. Components of Puppet Facter Puppet master Puppet agent PuppetDB Hiera Puppet Forge Puppet Domain Specific Language (DSL)
- 28. Architecture
- 29. Architecture
- 31. Puppet DSL Managing packages package { ’openssh’: ensure => present; } package { ’vim’: ensure => absent; }
- 32. Puppet DSL Managing services service { ’apache2’: ensure => running; }
- 33. Puppet DSL Managing files file { ’/etc/motd’: ensure => present, mode => ’0600’, owner => ’root’, group => ’root’, source => ’puppet:///modules/motd/motd’; }
- 34. Puppet DSL: resource types augeas computer cron exec file filebucket group host interface k5login macauthorization mailalias maillist mcx mount nagios_command nagios_contact nagios_contactgroup nagios_host nagios_hostdependency nagios_hostescalation nagios_hostextinfo nagios_hostgroup nagios_service nagios_servicedependency nagios_serviceescalation nagios_serviceextinfo nagios_servicegroup nagios_timeperiod notify package resources router schedule scheduled_task selboolean selmodule service ssh_authorized_key sshkey stage tidy user vlan yumrepo zfs zone zpool
- 35. Puppet DSL Managing a node node ’www.domain.com’ { include apache include mysql }
- 36. Verifying style puppet-lint and meta-data-json-lint
- 37. How the get started https://puppetlabs.com/download-learning-vm https://puppetlabs.com/resources/books http://ask.puppetlabs.com/questions/ https://docs.puppetlabs.com/puppet/
- 38. Demonstration
- 39. Thank you for your attention. Questions?
- 40. Pictures... www.theluxuryspot.com/wp-content/uploads/2013/05/Fashion-pug.jpg plyojump.com/classes/images/computer_history/ibm_360_color.jpg www.cse.unsw.edu.au/opencms/export/sites/cse/.content/images/ feature_boxes_750x400/server_room.jpg_687647283.jpg www.alvantia. es/blog/wp-content/uploads/2015/02/cloud-computing.jpg www.linuxplanet.org/blogs/?cat=177 www.rcesecurity.com/wp-content/uploads/2014/08/tux-egg.jpeg www.greatleadersserve.com/wp-content/uploads/2012/08/iStock_ 000020378687XSmall.jpg https://pensarlaescuela.files.wordpress.com/ 2015/03/persona-en-rueda-de-entrenamiento.jpg doc.ubuntu-fr.org/_media/administration/puppet.png https://docs. puppetlabs.com/pe/latest/images/puppet/pe-configuration-data.png https://docs.puppetlabs.com/learning/images/manifest_to_defined_ state_split.png