Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Overview of Puppet and Ansible
Similaire à Overview of Puppet and Ansible (20)
Dernier
Dernier (20)
Overview of Puppet and Ansible
- 1. Puppet
- 2. Describe resources and their desired state
- 4. Resources described in platform agnostic way
- 5. Code stored in manifest files
- 6. (Cohesive) Code + data = modules
- 7. Applied directly or compiled into a catalog
- 9. # /etc/puppetlabs/puppet/site.pp node webserver { include apache class { 'ntp': enable => false, } apache::vhost {'personal_site': port => 80, docroot => '/var/www/personal', options => 'Indexes MultiViews', } }
- 10. Agent requests catalog from master
- 11. architecture => x86_64 hostname => ksmith-mbp interfaces => lo0,gif0,stf0,en0,en1,en2,p2p0,awdl0,bridge0 ipaddress_en0 => 192.168.1.12 kernel => Darwin memorysize_mb => 16384.00 processorcount => 8
- 12. Master determines desired state based on applied classes
- 13. class role::web_service { require role::onshape_app include profile::jetty_environment }
- 14. Master combines facts + manifests + data (Hiera) into catalog
- 15. Hiera: hierarchical data source with pluggable backends
- 16. All this happens every 30 minutes
- 17. Non-idempotent operations can get tricky
- 18. exec { 'format-drive': command => “mkfs.ext4 ${device}", onlyif => "blkid ${device} | grep 'ext4'", }
- 20. Environments: isolated groups of agent nodes
- 22. r10k • Installs Puppet modules using an standalone list (Puppetfile) • Creates and manages environments based on Git branches
- 23. mod "puppetlabs/rabbitmq", "4.0.0" mod "puppetlabs/stdlib" mod "saz/memcached" mod "thias/sysctl" mod "morphlabs/debootstrap" mod 'dyn_module', :git => 'https://github.com/dyninc/Dyn-Puppet-Module.git', :ref => 'd842f775c3671a73167ddf0e33cc89303ce807c0'
- 24. Role —> profiles —> modules —> resources
- 25. Ansible
- 26. Push-based
- 28. Playbook = YAML description of actions
- 29. - hosts: tag_onshape_puppetRole_internal_repo gather_facts: false sudo: true remote_user: buildbot tasks: - name: Run script to update onshape repo metadata script: files/onshape_repo_gen_metadata.sh
- 30. Plays against groups of hosts
- 31. Inventory: static or dynamic (i.e. EC2)
- 32. agent ansible_ssh_host=192.168.128.12 ansible_ssh_user=root [infrastructure:children] use1-dev usw2-dev [use1-dev] jumpbox-use1a ansible_ssh_host=10.1.0.7 nat1a ansible_ssh_host=10.1.0.6 vpn1a ansible_ssh_host=10.1.0.5 [usw2-dev] jumpbox-usw2a ansible_ssh_host=10.2.0.7 nat2a ansible_ssh_host=10.2.0.6 vpn2a ansible_ssh_host=10.2.0.5
- 33. Ad-hoc commands
- 35. Separation of platform from application
- 38. Credentials —> Hiera Platform config —> Hiera App config —> ZK
- 39. Create instance Wait for it to start CloudInit runs Puppet runs Ansible runs Instance ready
- 41. Create instance Wait for it to start CloudInit runs Puppet runs Ansible runs Instance ready
- 42. Create instance Wait for it to start CloudInit runs Puppet runs Ansible runs Instance ready role::web_service deploy_web_service.yml
- 43. Questions?
Notes de l'éditeur
- Enterprises & mainframes (centralized) —> distributed Scripts tended to be too system specific, not portable
- In 1994 Mark Burgess created CFEngine to help him admin Unix workstations at Oslo University Configuration management policy made into code
- Declarative: what, not how Abstract: let the tool decide how to achieve the goal Idempotent: yields the same results when invoked multiple times Convergent: cooperating actors that over time bring the system into compliance These ideas live on in Puppet, Ansible, and Chef
- What do we get if we take this to its natural conclusion? From http://www.slideshare.net/gmccance/cern-data-centre-evolution
- Switch to mvim for examples
- Catalog is a compiled representation of the desired system state Agent supplies facts collected by Facter
- Example facts
- For us, that’s determined by a role fact
- We use YAML files, but you could also use a database, etc.
- Its only argument is the name of the node to be classified, and it returns a YAML document describing the node. Examples include Puppet Dashboard and Foreman
- Defined by puppet.conf, by the ENC, other means
- Module organization http://www.craigdunn.org/2012/05/239/ https://puppetlabs.com/presentations/designing-puppet-rolesprofiles-pattern
- Only runs if you invoke it, no scheduled timetable
- Ansible controller
- Notice the templating (Jinja2)
- No playbook necessary. Just specify actions on the CLI, kinda like (Puppet’s) MCollective
- Starts with a custom AMI that’s pre-configured as role::base
- Switch to mvim