Releases: voxpupuli/puppet-corosync
5.0.0 - LTS release
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.
5.0.0-beta1
- Allow multiple rings in nodelist (#262, #291, #336)
- Improve tests (#335, #337, #331 #328)
- Modulesync (#330)
- New class parameter: vsftype (#345)
- Add the nodelist to corosync.conf even if we set the expected votes count
(#347)
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)
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 releases
of this module. In v6.0.0, this module could be rebranded to a better name.
4.0.1
4.0.0
Summary
- Validate corosync configuration before overwriting (available in EL7, Ubuntu
16.04, and Debian Jessie) (#294) - multicast_address and unicast_addresses are no longer mandatory if
clustername is set (#318) - Modulesync updates
Backward incompatible changes
- Support for Puppet <= 3.6.0 is removed (#319)
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 three major releases
of this module. In v6.0.0, this module could be rebranded to a better name.
3.0.0
Summary
- Fixed a bug with two_nodes option and three-node clusters (#316)
- Improved corosync readiness detection (#314)
- Modulesync updates
- Introduce a public roadmap
Backward incompatible changes
- Providers now wait up to 60 seconds to get a non null CIB. On new clusters, it
means that you wait 60 seconds for nothing, but when adding a node to the
cluster, it means that we join the cluster before operating it with this
puppet module. If you are using Cs_shadow and all your resources depend on
that one, then instead of a non-null (non0.0
) epoch, we wait for a non
0.*
epoch, because the Cs_shadow and Cs_commit couple will update the
epoch anyway. (#314)
Deprecation notes
Deprecating old Puppet releases:
- We will remove support for Puppet <= 3.6.0 in the next major release of this
module (v4.0.0). - We will remove support for Puppet <= 3.8.0 in two major releases of this
module (v5.0.0). - We will remove support for Puppet <= 4.6.0 in three major releases of this
module (v6.0.0).
Puppet 3 support
The 5.0.0 release will be a LTS and will be supported until VoxPupuli stops
Puppet 3 support (voxpupuli/plumbing#21). It will be the latest release to
support Puppet 3. After its release, only bugfixes and security fixes will be
applied. We will not introduce backward incompatible changes in this LTS
release.
That LTS release will be available under the "puppet3" branch of this module.
Please consider moving straight to Puppet 4.
Naming of this module
The issue #32 concerning the naming of this module will be closed in three major releases
of this module. In v6.0.0, this module could be rebranded to a better name.
2.0.1
2.0.0
2016-06-28 - Release 2.0.0
Summary
- Replace Cs_primitive[manage_target_role] parameter by
Cs_primitive[unmanaged_metadata] parameter (#275) - Support Debian 8. Requires jessie-backports apt repository (not included in
this module) (#282) - Set Puppet requirement version to >= 3.0.0 < 5.0.0 (#286)
- Add a
cib
parameter to cs_rsc_default (#296)
Backward incompatible changes
- Cs_primitive[manage_target_role] parameter (introduced in 1.1.0, deprecated
in 1.2.0) has ben replaced by the more powerful
Cs_primitive[unmanaged_metadata] parameter (#275). To update, you need to
replacemanage_target_role => false
byunmanaged_metadata => ['targes-role']
- The class parameter corosync::packages has been removed (was deprecated in
0.8.0) (#282)
Deprecation notes
We will remove support for Puppet <= 3.6.0 in two major releases of this module
(4.0.0).
1.2.1
1.1.1
1.2.0
- Deprecate Cs_primitive[manage_target_role] in favour of
Cs_primitive[unmanaged_metadata]