Skip to content

5.0.0 - LTS release

Latest
Compare
Choose a tag to compare
@roidelapluie roidelapluie released this 17 Sep 06:10
· 345 commits to master since this release
118db21

This release is the last major release supporting Puppet 3. It will be maintained as long as Vox Pupuli supports Puppet 3.

  • Allow multiple rings in nodelist (#262, #291, #336, #358)
  • Add support for cs_location rules (#132, #310, #356)
  • Allow 1-element arrays for primitives in cs_group (#152, #368)
  • Add support for clone of groups (#176, #371)
  • New class parameter: vsftype (#345)
  • Add the nodelist to corosync.conf even if we set the expected votes count
    (#347)
  • Add autorequirement between cs_location and cs_primitives/cs_clone (#359)
  • Add autorequirement between cs_clone and cs_primitive (#357, #365)
  • Lots of fixes regarding cs_clone (#367, #149, #370)
  • Add "Managed By Puppet" header to corosync.conf (#360)
  • Improve tests (#335, #337, #331, #328, #364, #369, #370)
  • Modulesync (#330)

Backward incompatible changes

  • Support for Puppet < 3.8.0 is removed (#334)
  • Logging to file is enabled by default. (#345)
  • Corosync.conf got a major cleanup. Most of the parameters are now implicit so
    we get pacemaker defaults. List of affected parameters: compatibility,
    consensus, join, max_messages, rrp_mode, threads, token,
    token_retransmits_before_loss_const, vsftype.
    Those parameters can now be specified as class parameters. (#345)
  • Removed legacy configuration sections: amf, aisexec, logging.logger_subsys
    (#345)
  • Fix two_nodes behaviour with expected_votes = 2 introduced in 3.0.0 (#246)
  • Cs_clone: clones are now stopped before being removed (crm provider) (#367)
  • Cs_clone now uses the resource name as clone id (pcs provider) (#149, #367)
  • Cs_clone purges parameters that are not explicitly set (#370)

Deprecation notes

We have plans to rename this module and deprecated old Puppet releases and
Puppet distributions. Please refer to our roadmap for further
details.

Naming of this module

The issue #32
concerning the naming of this module will be closed in the next major release
of this module. In v6.0.0, this module could be rebranded to a better name, as
well as the types and resources.