Forge Home

rancid

Manage RANCID

11,588 downloads

9,673 latest version

3.4 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.1.4 (latest)
  • 0.1.3
  • 0.1.1
  • 0.0.1
released Mar 27th 2015

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'eolsen-rancid', '0.1.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eolsen-rancid
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eolsen-rancid --version 0.1.4

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

eolsen/rancid — version 0.1.4 Mar 27th 2015

Build Status

puppet-rancid

Rancid Puppet Module

This module will install the Rancid package, manage Rancid groups, initialize per group router.db files, create the rancid-run cron job, and has the capability to add router entries to your router.db file with Hiera. Also manages .cloginrc.

===

Compatibility

Compatible with Puppet v3.x on the following platforms.

  • EL 6 (rancid package from EPEL)
  • Ubuntu 12.04 LTS

===

class rancid

Parameters

'USE_DEFAULTS' denotes that defaults are made based on osfamily and other such factors.

filterpwds

Determines which passwords are filtered from configs.

NO – does not filter any password. All passwords are included in configs in RANCID repository

YES – passwords which are stored in plain-text or using reversible enryption method will be removed from configs.

ALL – all password will be removed from configs

NOTE: When setting password filtering be aware that RANCID is sending configuration and changes via email, so including any passwords is not recommended. String can be 'ALL', 'YES', or 'NO'.

  • Default: 'ALL'

nocommstr

Optionally strip snmp community strings from the configs. String can be 'YES' or 'NO'.

  • Default: 'YES'

maxrounds

Defines how many times rancid should retry collection of devices that fail. The minimum is 1.

  • Default: '4'

oldtime

Specified as a number of hours, OLDTIME defines how many hours should pass since a successful collection of a device’s configuration and when control_rancid(1) should start complaining about failures. The value should be greater than the number of hours between rancid-run cron runs.

  • Default: '4'

locktime

Defines the number of hours a group’s lock file may age before rancid starts to complain about a hung collection. String that must be a digit.

  • Default: '4'

parcount

Defines the number of rancid processes that par(1) will start simultaneously as control_rancid(1) attempts to perform collections. Raising this value will decrease the amount of time necessary for a complete collection of a (or all) rancid groups at the expense of system load. The default is relatively cautious. If collections are not completing quickly enough for users, use trial and error of speed versus system load to find a suitable value. String that must be a digit.

  • Default: '5'

groups

Array of rancid groups.

  • Default: [ 'routers', 'switches', 'firewalls' ]

devices

Hash of devices. See Sample Hiera Structure.

  • Default: undef

packages

  • Default: 'USE_DEFAULTS'

rancid_config

Path to rancid.conf.

  • Default: 'USE_DEFAULTS'

rancid_path_env

PATH to use in rancid.conf.

  • Default: 'USE_DEFAULTS'

homedir

Rancid user's home directory.

  • Default: 'USE_DEFAULTS'

logdir

Directory for storing rancid logs.

  • Default: 'USE_DEFAULTS'

user

Rancid user.

  • Default: 'USE_DEFAULTS'

group

Rancid group

  • Default: 'USE_DEFAULTS'

shell

Rancid user's shell.

  • Default: 'USE_DEFAULTS'

cron_d_file

Path to file in cron.d that will periodically execute rancid.

  • Default: '/etc/cron.d/rancid'

cloginrc_content

Content of ~rancid/.cloginrc

  • Default: 'USE_DEFAULTS'

===

define rancid::router_db

Example Usage

If you specify a hash in Hiera, you will not need to call this define directly.

Parameters

devices

Hash of devices. See Sample Hiera Structure.

  • Default: undef

rancid_cvs_path

PATH for finding rancid-cvs and test programs.

  • Default: '/bin:/usr/bin',

router_db_mode

Mode of router.db files.

  • Default: '0640',

===

Sample Hiera Structure

===

License

Apache Software License v2.0

===

Support

Please log tickets and issues at our Projects site