hello,

We are pleased to announce the release of a new Production release
of The Marionette Collective.

This release brings to general availability all the features added 
in the 1.1.x development series.

A summary of changes since 1.0.0 can be seen below:

Enhancements:

 * The concept of sub-collectives were introduced that help you partition
   your MCollective traffic for network isolation, traffic management and 
security
 * The single executable framework has been introduced replacing the old
   mc-* commands
 * A new AES+RSA security plugin was added that provides strong encryption,
   client authentication and message security
 * New fact matching operators <=, >=, <, >, !=, == and =~
 * Actions can be written in external scripts and therefore other languages
   than Ruby, wrappers exist for PHP, Perl and Python
 * Plugins can now be configured using the _plugins.d_ directory
 * A convenient and robust exec wrapper has been written to assist in calling
   external scripts
 * The MCOLLECTIVE_EXTRA_OPTS environment variable has been added that will
   add options to all client scripts
 * Network timeout handling has been improved to better take account of latency
 * Registration plugins can elect to skip sending of registration data by
   returning nil, previously nil data would be published
 * Multiple libdirs are supported
 * The logging framework is pluggable and easier to use
 * Fact plugins can now force fact cache invalidation.  The YAML plugin will
   force a cache clear as soon as the source YAML file updates
 * The ping application now supports filters
 * Network payload can now be Base64 encoded avoiding issues with Unicode 
characters
   in older Stomp gems
 * All fact plugins are now cached and only updated every 300 seconds
 * The progress bar now resizes based on terminal dimensions
 * DDL files with missing output blocks will not invalidate the whole DDL
 * Display of DDL assisted complex data has been improved to be more readable
 * Stomp messages can have a priority header added for use with recent versions
   of ActiveMQ
 * Almost 300 unit tests have been written, lots of old code and any new code 
being
   written is subject to continuous testing on Ruby 1.8.5, 1.8.6 and 1.9.2
 * Improved the Red Hat RC script to be more compliant with distribution 
policies
   and to reuse the builtin functions

Deprecations and removed functionality:

 * The old mc-* commands are being removed in favor for the new mco command.
   The old style is still available and your existing scripts will keep working 
but
   porting to the new single executable system is very easy and encouraged.
 * MCOLLECTIVE_TIMEOUT and MCOLLECTIVE_DTIMEOUT were removed in favor of 
MCOLLECTIVE_EXTRA_OPTS
 * mc-controller could exit all mcollectived instances, this feature was not 
ported
   to the new mco controller application

Bug Fixes:

 * mcollectived and all of the standard supplied client scripts now disconnects
   cleanly from the middleware avoiding exceptions in the ActiveMQ logs
 * Communications with the middleware has been made robust by adding a timeout
   while sending
 * Machines that do not pass security validation are now handled as having not
   responded at all
 * When a fire and forget request was sent, replies were still sent, they are
   now suppressed

Backwards compatibility

This release can communicate with machines running older versions of MCollective
there are though a few steps to take to ensure a smooth upgrade.

Users upgrading from 1.0.x must read the release notes[1] as there are 
configuration
changes you need to perform.  Users upgrading from 1.1.4 should have no 
problems or
config changes.

The release can be downloaded from the usual locations[2] and is available as 
Debian
and RPM packages.

[1] http://srt.ly/mc120
[2] http://www.puppetlabs.com/misc/download-options/

-- 
R.I.Pienaar

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to