Node collaboration - Exported Resources and PuppetDB
Download as PPTX, PDF5 likes4,492 views
The document discusses the concept of exported resources in Puppet, which are declarations specifying desired states for resources that can be managed by any node. It compares this with Chef's approach using automatic indexing of node data and introduces PuppetDB, a data collection service enabling advanced Puppet features, including exported resources. Ultimately, it emphasizes various methods for sharing information between nodes, including exported resources, PuppetDB, and alternative tools.
Node collaboration - Exported Resources and PuppetDB
- 2. This talk contains both Facts and Opinions*. *don’t believe everything I say.
- 5. Exported Resources * https://docs.puppetlabs.com/puppet/latest/reference/lang_exported.html Definition: An exported resource declaration specifies a desired state for a resource, does not manage the resource on the target system, and publishes the resource for use by other nodes. Any node (including the node that exported it) can then collect the exported resource and manage its own copy of it. *
- 7. Exported Resources For those that can’t afford DNS servers…
- 8. Exported Resources Common Examples • Backend servers configured in a load balancer • Monitoring Servers updated with monitoring clients (nagios_host / nagios_service) • Distribute public keys (ssh and openssl)
- 9. Exported Resources Question for the audience
- 10. Exported Resources Question for the audience What do you think of Exported Resources?
- 11. Exported Resources Question for the audience What do you think of Exported Resources? Great. Alright. So so. Let’s explore alternatives
- 12. What about our friends @
- 13. Ohai Node data (think facter) is automatically added, indexed and searchable in the Chef Server. No need to export facts or resources.
- 14. How to use Chef Search Query the the Chef server data via • Method within recipe (think puppet manifest) • Search subcommand of ‘knife’ • /search or /search/INDEX endpoints of Chef Server API
- 15. How to use Chef Search 1. Method within recipe (think puppet manifest)
- 16. How to use Chef Search 1. Method within recipe (think puppet manifest)
- 17. Chef Search What do people think?
- 18. Chef Search What do people think? Personally I feel this approach can sometimes be better than exported resources approach. * * Remember this is an opinion
- 19. But what about Puppet?
- 21. PuppetDB Definition: collects data generated by Puppet. It enables advanced Puppet features like the inventory service and exported resources, and can be the foundation for other applications that use Puppet’s data. * https://docs.puppetlabs.com/puppetdb/2.1/index.html
- 22. PuppetDB • Written in Clojure. • Runs on the JVM • Backed by PostgreSQL • Scales horizontally
- 23. PuppetDB PuppetDB stores: • The most recent facts from every node • The most recent catalog for every node • Optionally, 14 days of event reports for every node • Exported Resources
- 24. PuppetDB PuppetDB REST API V3 API includes the following endpoints: • Facts • Resources • Nodes • Fact-names, • Metrics • Reports • Events • And more
- 26. PuppetDB GET /v3/nodes/ QUERY = (JSON array of queries)
- 27. PuppetDB GET /v3/nodes/<NODE>/facts Return all facts for given node
- 28. PuppetDB GET /v3/nodes/<NODE>/facts/<NAME> Return facts by their name
- 29. PuppetDB I know what you’re thinking So much awesome information How can I make use of it?
- 30. PuppetDB checkout Puppetdbquery module by Erik Dalén https://forge.puppetlabs.com/dalen/puppetdbquery https://github.com/dalen/puppet-puppetdbquery
- 31. PuppetDB Puppetdbquery module • Command line tools • Puppet functions to query PuppetDB • Hiera backend to return query results from PuppetDB
- 32. PuppetDB Puppetdbquery CLI - nodes
- 33. PuppetDB Puppetdbquery CLI – facts
- 34. PuppetDB Puppetdbquery functions in manifests • query_nodes • query_facts
- 36. PuppetDB Puppetdbquery functions note: Output is abbreviated
- 37. Where to from here? Exported Resources vs PuppetDB + puppetdbquery
- 38. Where to from here? What about something completely different
- 39. Where to from here? What about something completely different • Confd • Etcd • Consul • Zookeeper • Doozer • Skydns
- 40. Where to from here? What about something completely different • Confd • Etcd • Consul • Zookeeper • Doozer • Skydns Really interesting space… but that’s for another talk.
- 41. Summary How can you share information between your nodes/servers?
- 42. Summary How can you share information between your nodes/servers? Plenty of ways • Exported resources • PuppetDB • Many, many others.
- 43. Summary How can you share information between your nodes/servers? Plenty of ways • Exported resources • PuppetDB • Many, many others. Pick the method that works best for you
- 44. Thank you
- 45. Thank you #protip go buy this book now By Alessandro Franceschi It is excellent!
- 46. IS HIRING
- 47. QUESTIONS?
Editor's Notes
- #21: The Datastore for information generated by Puppet
- #22: Large inventory of metadata about every node in your infrastructure and a searchable database of every single resource being managed on any node.
- #23: Large inventory of metadata about every node in your infrastructure and a searchable database of every single resource being managed on any node.
- #25: Return all nodes matching the given queryprocessorcount
- #26: Return all nodes matching the given queryprocessorcount
- #27: Return all nodes matching the given queryprocessorcount
- #28: Return all nodes matching the given queryprocessorcount
- #32: Query based upon resources and facts Returns a list of nodes
- #33: Returns a hash of facts
- #34: Returns a hash of facts
- #35: Returns a hash of facts
- #36: Query_node - Accepts 2 arguments Query to discover nodes Fact that should be returned (optional) Returns array of certnames or fact values Query_facts – requires 2 arguments query list of facts to return in a nested hash
- #37: Accepts 2 arguments Query to discover nodes Fact that should be returned (optional) Returns array of certnames or fact values
- #38: Problems with PuppetDB – puppetdbquery generates results based on compiled catalogs by the puppet master. We are not actually sure whether resources have been applied successfully How frequently do you run Puppet? Too slowly and infrastructure is slow to adapt to change Too fast and there maybe race conditions.