Hello,

I am very please to announce a number of releases from the Choria
Project.
This is a major release that delivers on a number of the roadmap items I
mentioned recently and that will unfortunately require some
reconfiguration of your site.  A number of items are being deprecated
for newer, faster, lighter and easier to use versions of the same.
*Major New Features:*

 * There is now a Puppet Tasks runner that does not rely on SSH, does
   not need Bolt and have strong RBAC and Auditing
 * We now have a new Choria Network Broker that replace the NATS broker
 * We now have a Choria Federation Broker that replace the previous Ruby
   Federation Broker
 * Choria Data Adapters[1] a step towards stream processing and building
   very large scale node metadata ingest networks
*Deprecations:*

 * The NATS module and the NATS server deployment method
 * The old Ruby based Federation Broker
*Removed:*
 * YAML Playbooks
 * The *mco federation observe* command

This all seems like a huge change, but in reality moving to the new
Choria Broker is really easy and the resulting build is more robust, use
fewer resources and scales further.  Please review the Network Broker
documentation[2].  RPMs and Debs are supplied and some lovely
contributors are working on getting it into Archlinux base distro.
Puppet Tasks are a major new capability that along with the Puppet based
Playbooks from the previous release rounds out the major road map items
I had for delivering cutting edge enterprise level features to the
Puppet Ecosystem as Open Source.  As such they are fast, stable,
consistent and secure.  Please review the Puppet Tasks documentation[3].
Please pay special attention to the Status section.
Network Federation has had a big overhaul - the new Federation Brokers
are incredibly performant and scalable while using significantly
fewerresources and being easier to deploy.  I've tested these to ~ 15
000 federated networks.  Documentation has been updated[4].
While on the topic of scale I would like to point out a blog post I
recently wrote about my first real world 50 000 node Choria deploy[5].
This deployment is using the Network Broker and other components
released today.  Watch this space for a several 100% increase in node
counts and details about that.

*choria/nats version 0.4.0*
 * This module is now deprecated and a easy *ensure => absent* flag has
   been added to clean up after it
*choria/choria version 0.7.0*

 * Support managing the Choria Network Broker
 * Support managing the Choria Federation Broker
 * Support managing the Choria Data Adapters
 * Support managing Ubuntu and Debian repositories
 * Improve internal module ordering
 * Add mandatory name option to the YUM repositories
*choria/mcollective_choria version 0.7.0*

 * When running playbooks default to the users module path
 * Update the NATS client gem to 0.4.0
 * Support Puppet Tasks
 * Support multiple module paths on the playbook CLI
 * Fix dependency handling on Archlinux
 * Deprecate the Ruby Federation Broker
 * Remove YAML playbook
 * Remove the mco federation observe command
--
R.I.Pienaar / www.devco.net / @ripienaar

Links:

  1. https://master.choria.io/docs/adapters/
  2. https://choria.io/docs/deployment/broker/
  3. https://choria.io/docs/tasks/
  4. https://choria.io/docs/federation/
  5. https://www.devco.net/archives/2018/03/07/50-000-choria-node-network.php

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"mcollective-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mcollective-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to