Release 0.0.26

New Features:

• More details added to choria show_config (#243)
• batch_sleep_time added to mcollective tasks in playbooks (#212)
• HTTP code 201 is now also accepted as pass in webhook tasks (#250)
• Certificate validation can be disabled in webhooks (#248)
• Sanity checks for your SSL setup has been improved to provide better early failure feedback (#254)

Bug Fixes:

• choria show_config will now show the correct PuppetDB information (#244)

Thanks to @dhollinger for adding the 201 status code to webhooks

Release 0.0.25

New Features:

• Add Federation of Collectives support (#213)
• Add the ability for the NATS connector to record the route packets take through a collective

Bug Fixes:

• Update the NATS gem to 0.2.2 which resolves a situation where reconnects would not happen in some disconnection scenarios (#229)

Federations of Collectives:

This is a major new feature that is tailored to building very large distributed collectives spanning geographical boundaries. It lets you build many small, easy to manage, Collectives and then via a special cluster of daemons gives your client access to the combined Federated network as one.

Clients offload some of the work onto the brokers which in some scenarios yields a significant speed up and network traffic decrease.

Additionally you have the ability to get precise network route maps of how your messages traverse the global network to assist with debugging and understanding your network.

Review the documentation for details.

Release 0.0.24

New Features:

• You can now emit Graphite Events from within playbooks (#186)
• Generally the NATS connector will honour SRV records and config order, you can now configure randomization using plugin.choria.randomize_middleware_hosts (#201)
• The elapsed time for playbook runs can now be obtained via templates using {{ elapsed_time }} (#173)
• A choria_util agent was added that can display run time information about your nodes such as what middleware host they are connected to and more (#204)

Bug Fixes:

• When a custom SSL directory is configured it was not used for the certificate cache (#199)