CMS-Report » History » Version 2
Romain Vrignaud, 10/07/2013 02:26 PM
1 | 1 | Romain Vrignaud | h1. CMS-Report |
---|---|---|---|
2 | |||
3 | This page aim is to find common elements between all configuration management systems reports. |
||
4 | |||
5 | See [[Chef-reporting]] for first discussion about implementation on a Foreman plugin. |
||
6 | |||
7 | 2 | Romain Vrignaud | h2. Puppet |
8 | 1 | Romain Vrignaud | |
9 | * Sent from Puppetmaster (centralized) |
||
10 | * Multiple report processor allowed |
||
11 | |||
12 | Notions : |
||
13 | * Node name |
||
14 | * Time elapsed (File, Exec, User, Group, Conf Retrieval, Service, Package, Total) |
||
15 | * Resources Managed (Skipped, Scheduled, Out of Sync, Applied, Failed, Restarted, Failed Restarts, Total) |
||
16 | * Changes (number of changes in transaction) |
||
17 | * Log (bulk message) : |
||
18 | ** level (debug,info, notice, warning, ..) |
||
19 | ** source (resource name, puppet) |
||
20 | |||
21 | See: |
||
22 | * http://docs.puppetlabs.com/guides/reporting.html |
||
23 | * http://docs.puppetlabs.com/puppet/3/reference/format_report.html |
||
24 | |||
25 | 2 | Romain Vrignaud | h2. Chef |
26 | 1 | Romain Vrignaud | |
27 | * Sent from chef-client (nodes) |
||
28 | * Multiple report processor allowed |
||
29 | |||
30 | Notions: |
||
31 | * Node name |
||
32 | * Success or Failed run |
||
33 | * Global run backtrace |
||
34 | * |
||
35 | |||
36 | |||
37 | See: |
||
38 | * http://docs.opscode.com/essentials_handlers.html |
||
39 | * https://github.com/opscode/chef/blob/master/lib/chef/event_dispatch/base.rb |
||
40 | * https://github.com/opscode/chef/blob/master/lib/chef/resource_reporter.rb |
||
41 | |||
42 | 2 | Romain Vrignaud | h2. CFengine3 |
43 | 1 | Romain Vrignaud | |
44 | 2 | Romain Vrignaud | h2. Ansible |
45 | 1 | Romain Vrignaud | |
46 | 2 | Romain Vrignaud | h2. Puppet |