Puppet Camp Melbourne 2014: Node Collaboration with PuppetDB
•Download as PPTX, PDF•
6 likes•1,288 views
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (6)
Similar to Puppet Camp Melbourne 2014: Node Collaboration with PuppetDB
Similar to Puppet Camp Melbourne 2014: Node Collaboration with PuppetDB (20)
More from Puppet
More from Puppet (20)
Recently uploaded
Recently uploaded (20)
Puppet Camp Melbourne 2014: Node Collaboration with PuppetDB
- 1. Node Collaboration with PuppetDB Michael Richardson @m_richo
- 2. Agenda 1. Who am i 2. The challenges we face 3. What is PuppetDB 4. How can PuppetDB help 5. Examples
- 3. $ whoami • Michael Richardson @m_richo • engineer at Odecee • Solaris/Linux Sys Admin • currently battling Windows • coffee consumer • devops enthusiast • puppet certified
- 5. The Challenge Faster provisioning
- 6. The Challenge Faster provisioning
- 7. The Challenge Faster provisioning more environments
- 8. The Challenge Faster provisioning more environments
- 9. The Challenge Faster provisioning more environments
- 10. micro-services The Challenge Faster provisioning more environments
- 11. micro-services The Challenge Faster provisioning more environments
- 12. Tools like Puppet have become essential
- 13. The need for automated, repeatable, versioned provisioning and configuration management of infrastructure and services
- 14. Let’s raise the bar We need automated, repeatable, versioned learning, reactive and adaptive provisioning and configuration management of infrastructure and services
- 15. This is where PuppetDB and tools can help
- 16. So what is PuppetDB?
- 17. So what is PuppetDB? 1. PuppetLabs product. 2. Storage service for Puppet produced data. 3. Written in Clojure. 4. Persists data to a Postgres DB 5. Supports Puppet Enterprise and Puppet Open Source environments.
- 18. PuppetDB PuppetDB Puppet Master agent agent agent agent Postgres
- 19. PuppetDB PuppetDB Puppet Master agent agent agent agent Postgres
- 20. PuppetDB PuppetDB Puppet Master agent agent agent agent Postgres PuppetDB Puppet Master Load balancer
- 21. What data goes in PuppetDB
- 22. Node Facts
- 23. ipaddress network macaddress sshrsakey kernel osfamily Node Facts operatingsystemrelease FQDN
- 24. Node Catalog’s
- 25. Node Catalog’s
- 26. Facts about every node Catalog for every node CMDB?? So much useful data
- 27. How do we access it?
- 28. PuppetDB has an API
- 29. PuppetDB API PuppetDB REST API has the following endpoints: • Nodes • Catalogs • Facts • Fact-names • Resources • Environments • Metrics • Reports • Events • And more
- 30. Query PuppetDB Query all the nodes
- 31. Query PuppetDB Query nodes and filter results
- 32. Query PuppetDB Query all facts for a given node
- 33. Query PuppetDB Query an individual fact for a given node
- 34. Sick of running curl?
- 35. Check out Puppet Explorer thank you Erik Dalén and
- 36. Check out Puppetboard thank you Daniele Sluijters
- 37. Dashboards are lovely. But how can we use this data to allow node collaboration
- 38. Introducing PuppetDBquery module https://forge.puppetlabs.com/dalen/puppetdbquery Again, thank you Erik Dalén
- 39. PuppetDB query Provides 1. CLI commands 2. PuppetDB Hiera backend 3. PuppetDB functions
- 40. PuppetDB query Provides 1. CLI commands 2. PuppetDB Hiera backend 3. PuppetDB functions
- 41. PuppetDB query Provides 1. CLI commands 2. PuppetDB Hiera backend 3. PuppetDB functions o query_nodes o query_facts
- 42. Puppet run Puppet Master agent facts Hiera data Puppet code catalog report
- 43. Puppet run with puppetdbquery Hiera data PuppetDB Puppet Master agent facts Puppet code catalog report
- 44. query_nodes Accepts 2 arguments 1. Query to filter nodes 2. Fact to return (optional)
- 45. query_nodes Accepts 2 arguments 1. Query to filter nodes 2. Fact to return (optional) Returns an array of results webservers = [‘node2.local’, ‘node3.local’] foo_db_ip = [‘10.10.40.12’]
- 46. query_facts Accepts 2 arguments 1. Query to filter nodes 2. List of facts to return
- 47. query_facts Accepts 2 arguments 1. Query to filter nodes 2. List of facts to return Returns nested hash of results webserver_network = {"node2.local"=>{"macaddress” =>"08:00:27:99:4B:CB", "ipaddress"=>"10.0.2.15"}, "node3.local"=>{"macaddress"=>"08:00:27:99:4B:CB", "ipaddress"=>"10.0.2.15"}}
- 48. What’s this give us?
- 49. What’s this give us? The ability to dynamically configure a system based on the state of other systems in the infrastructure.
- 50. Examples
- 51. populate files with query results
- 52. populate files with query results
- 53. populate files with query results
- 54. Examples – load balancer
- 55. Examples – whitelist addresses
- 56. Examples – search for service
- 57. Summary • PuppetDB has a wealth of information about your systems. Start using it! • Populate dynamic configuration based on PuppetDB data. • Allow hosts and services to simply be discovered by their peers.
- 58. Thank you. #protip Go buy this book now By Alessandro Franceschi It is EXCELLENT!
- 59. Thank you. For folks from Sydney Sydney Puppet User Group http://www.meetup.com/Sydney-Puppet-User-Group/ Come along
- 60. Thank you Any Questions? Michael Richardson @m_richo
Editor's Notes
- Let’s not forget about people
- You need automated, repeatable, versionable provisioning and management of infrastructure and services.
- You need automated, repeatable, versionable provisioning and management of infrastructure and services.
- Discuss adding and removing services, Multiple environments React to auto-scaling
- Puppet agent includes facter Base install produces > 100 facts Custom facts
- Base install produces > 100 facts Custom facts