bdii

contributions requested
Manages BDII servers

6,037 downloads

5,527 latest version

2.8 quality score

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

  • 1.3.2 (latest)
  • 1.3.1
released Jul 13th 2020
This version is compatible with:
  • RedHat
    ,
    CentOS
    ,
    Scientific

Start using this module

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

Add this module to your Puppetfile:

mod 'cnafsd-bdii', '1.3.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add cnafsd-bdii
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install cnafsd-bdii --version 1.3.2

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

cnafsd/bdii — version 1.3.2 Jul 13th 2020

puppet-bdii

Synopsis

Manage the BDII grid information system.

Documentation for BDII is available here

To use a bdii resource, it should be enough to simply:

include bdii

To manage site bdii, it is expected that hiera should be used to configure the sitebdii parameters, however it is in theory possible to modify the defaults in params.pp if this is more convenient.

Class Parameters to bdii

  • manage_firewall Defaults to true.
  • log_level defaults to DEBUG
  • port defaults to 2170
  • user defaults ldap
  • slapdconf defaults to /etc/bdii/bdii/bdii-slapd.conf
  • deletedelay defaults to 0 (no delay)
  • $selinux defaults to true

Deprecations

Previously all configurations could be specified by setting e.g. bdii::params::site_name within hiera. These are all now class parameters so this one should be bdii::site_name for instance. Eventually support for settings via the params.pp will be removed.