Puppet mcelog Module

Table of Contents

  1. Overview
  2. Description
  3. Usage
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations
  6. Versioning
  7. Support
  8. Contributing
  9. See Also

Overview

Manages the mcelog utility for x86-64 CPU Machine Check Exception data

Description

This is a puppet module for the installation and configuration of the mcelog utility. Which can be used either from the cli or run as a daemon that extracts and decodes Machine Check Exception (MCE) data.

Usage

Simple

include ::mcelog

mcelog

This class is presently the only public API in this module.

# defaults
class { '::mcelog':
  config_file_template => 'mcelog/mcelog.conf.erb',
}

Reference

See REFERENCE.

Limitations

This module is extremely basic. A few obvious improvements would be to:

  • provide more configuration options; specifically enable/disable mce events being sent to syslog
  • logrotated setup of the mcelog log file
  • provide support for running mcelog as a daemon on EL5.x

Please note that MCE is only avaiable on x86_64. It /can not/ work and the package is likely not avaible on i386 hosts.

Versioning

This module is versioned according to the Semantic Versioning 2.0.0 specification.

Support

Please log tickets and issues at github

Contributing

  1. Fork it on github
  2. Make a local clone of your fork
  3. Create a topic branch. Eg, feature/mousetrap
  4. Make/commit changes
    • Commit messages should be in imperative tense
    • Check that linter warnings or errors are not introduced - bundle exec rake lint
    • Check that Rspec-puppet unit tests are not broken and coverage is added for new features - bundle exec rake spec
    • Documentation of API/features is updated as appropriate in the README
    • If present, beaker acceptance tests should be run and potentially updated - bundle exec rake beaker
  5. When the feature is complete, rebase / squash the branch history as necessary to remove "fix typo", "oops", "whitespace" and other trivial commits
  6. Push the topic branch to github
  7. Open a Pull Request (PR) from the topic branch onto parent repo's master branch

See Also