Forge Home


Manages BDII servers


5,821 latest version

4.6 quality score

Version information

  • 1.2.2 (latest)
  • 1.1.0
  • 1.0.0
  • 0.2.2
  • 0.2.1
  • 0.1.0
released Aug 31st 2018
This version is compatible with:
  • RedHat

Start using this module

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

Add this module to your Puppetfile:

mod 'CERNOps-bdii', '1.2.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install CERNOps-bdii --version 1.2.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.



CERNOps/bdii — version 1.2.2 Aug 31st 2018


Build Status Code Coverage Puppet Forge Puppet Forge - downloads Puppet Forge - endorsement Puppet Forge - scores


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
  • delete_delay defaults to `/deleted
  • $selinux defaults to true


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.