Project

General

Profile

Actions

CMS-Report » History » Revision 11

« Previous | Revision 11/19 (diff) | Next »
Arnold Bechtoldt, 10/25/2013 04:19 PM


CMS-Report-Data

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.

See json-report-format and json-fact-format

Puppet

Vocabulary:
Configuration management tool : puppet
System data informations tool : facter

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:

Chef

Vocabulary:
Configuration management tool : chef
System data informations tool : ohai

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:

CFengine3 / Rudder

Salt

Vocabulary:
Configuration management tool : salt
System data informations tool : grains

General information:

Notions in reports:

See:

Ansible

Updated by Arnold Bechtoldt over 10 years ago · 11 revisions