CMS-Report¶

This page aim is to find common elements between all configuration management systems reports.

See Chef-reporting for first discussion about implementation on a Foreman plugin.

Puppet¶

General information:

• Sent from Puppetmaster (centralized)
• Multiple report processor allowed

Notions in reports:

• Node name
• Time elapsed (File, Exec, User, Group, Conf Retrieval, Service, Package, Total)
• Resources Managed (Skipped, Scheduled, Out of Sync, Applied, Failed, Restarted, Failed Restarts, Total)
• Changes (number of changes in transaction)
• Log (bulk message) :
  • level (debug,info, notice, warning, ..)
  • source (resource name, puppet)

See:

• http://docs.puppetlabs.com/guides/reporting.html
• http://docs.puppetlabs.com/puppet/3/reference/format_report.html

Chef¶

General informations:

• Sent from chef-client (nodes)
• Multiple report processor allowed

Notions in reports:

• Node name
• Success or Failed run
• Global run backtrace
• Time elapsed by type of resource
• All resources in run_list
• All resources in run_list updated during chef-run

See:

• http://docs.opscode.com/essentials_handlers.html
• https://github.com/theforeman/chef-handler-foreman
• https://github.com/opscode/chef/blob/master/lib/chef/event_dispatch/base.rb
• https://github.com/opscode/chef/blob/master/lib/chef/resource_reporter.rb

CFengine3¶

Ansible¶

Puppet¶