-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is the beta2 release of Puppet 0.25.0.

It is available at:

http://reductivelabs.com/downloads/puppet/puppet-0.25.0beta2.tar.gz

This is not production ready code - it is a beta release for testing.

The beta is not fully feature complete (we anticipate adding Windows
support and a number of language enhancements to beta3) and the
extent of testing and issues will determine how soon we move to a
release candidate after that.

We would ask everyone to test and report issues with the beta.

Please log any issues found during testing at:

http://projects.reductivelabs.com/projects/puppet/issues/new

Please select the Affected Version as 0.25.0beta2.

Please email any other specific questions, comments or feedback to
the puppet-user list.

Specific Changes between beta1 and beta2
- ----------------------------------------

* Fixing #1064 - Deprecating module 'plugins' directories - you
should now use 'lib' instead of 'plugins'.
* Removing deprecated :pluginpath setting
* Fixing #2094 - filebucket failures are clearer now
* Fixed pi binary so --meta option works and updated documentation
* Fixing #2323 - Modules use environments correctly
* Fixed #2102 - Rails feature update fixed for Debian and Ubuntu
* Fixed #2052 - Added -e option to puppet --help output
* Fix #2333 - Make sure lexer skips whitespace on non-token
* Fixed #2222 - Cleanup pi binary options and --help output
* Fixing #2329 - puppetqd tests now pass
* Fixing #2336 - qualified variables only throw warnings
* Fix #2246 - take2: make sure we run the rails tag query only when
needed
* vim plug-in: several improvements + cleanup
* Fixed #2229 - Red Hat init script error
* Fix #1907 (or sort) - 'require' puppet function
* Fixed #2332: Remove trailing slashes from path commands in the plugin
* Fix #2246 - Array tagged resources can't be collected or exported
* Whitespace & indentation cleanup across code base
* Fix #2308 - Mongrel should use X-Forwarded-For
* Fixes Bug #2324 - Puppetd fails to start without rails
* Numerous Augeas provider enhancements and fixes
* Fixing #2230 - exported resources work again
* Fixing the rails feature to be compatible
* Fixing #2315 - ca --generate works again
* Fix #2220 - Make sure stat is refreshed while managing Files
* JRuby OpenSSL implementation is more strict than real ruby one and
requires certificate serial number to be strictly positive.
* Fixing #2240 - external node failures now log output
* Fixing #2237 - client_yaml dir is always created by puppetd
* Fixing #2228 - --logdest works again in puppetd and puppetmasterd
* Fixing #2248 - --no-client correctly leaves off client
* Fixing #2243 - puppetrun works again
* Fixed #2304 - Added naggen script to directly generate nagios
configuration files from a stored configuration
* Sync conf/redhat/puppet.spec with Fedora/EPEL
* Fixed #2280 - Detailed exit codes fix
* Fixing #2253 - pluginsync failures propagate correctly
* Fix #2300 - Update ssh_authorized_key doc
* Enable maillist on centos, redhat, fedora
* Fixing #2288 - fixing the tests broken by my attr_ttl code
* Fix for #2234: test fails with old Rack version
* Fixing #2273 - file purging works more intuitively
* Fixed #2666 - Broken docstring formatting
* Deprecating factsync - pluginsync should b
* Fixed #2271 - Fix to puppetd documentation
* Fixing #2250 - Missing templates throw a helpful error
* Fixing #2273 - CA location is set correctly in puppetca
* Fixes #2268 - "Rack::RewindableInput is not a valid input stream."
* Fixing #2234 - fixing all of the tests broken by my bindaddress fix
* Fixing #2221 - pluginsignore should work again
* Fix bug #2124 - ssh_authorized_key always changes target if target
is not defined
* Fixing #2265 - rack is loaded with
* Fixed #1409
* Added split function

What's Changed?
- ---------------

There are substantial changes in Puppet 0.25.0 and more changes to
come in the future.  Most of the changes in 0.25.0 are internal
refactoring rather than behavioural.  The 0.25.0 release should be
fully backwards compatible behaviourally with the 0.24.x branch.

This means a 0.25.0 master will be able to manage 0.24.x clients.
You will need, however, to upgrade both your master and your clients
to take advantage of all the new features and the substantial gains
in performance offered by 0.25.0.

The principal change is the introduction of Indirected REST to
replace XML-RPC as the underlying Puppet communications mechanism.
This is a staged change with some functions migrated in this release
and some in the next release.  In the first stage of the Indirected
REST implementation the following functions have been migrated:

- - Certificates
- - Catalogue
- - Reports
- - Files

In 0.26.0 (the next release) the following remaining functions will
be migrated:

- - Filebucket
- - Resource handler
- - Runner handler
- - Status handler

The new REST implementation also comes with authorisation
configuration in a similar style to the namespaceauth used for
XML-RPC.  This new authorisation is managed through the auth.conf
file (there is an example file in the conf directory of the
tarball). This does not yet fully replace the namespaceauth.conf
file but will when the remaining handlers are migrated to REST.  It
works in a similar way to the namespaceauth.conf file and the
example file contains additional documentation.

As a result of the introduction of REST and other changes you should
see substantial performance improvements in this release.  These
particularly include improvements in:

- - File serving
- - The performance of large graphs with lots of edges
- - Stored configuration (see also Puppet Queuing below)

Other new features include (this is not a complete list - please see
the Roadmap for all tickets closed in this release):

Puppet Queuing
- ---------------

There is a new binary called puppetqd that supports queuing for
stored configurations.  You can read about how it works and how to
implement it at:

http://reductivelabs.com/trac/puppet/wiki/UsingStoredConfiguration

Further documentation is in the README.queuing file in the tarball.

Application Controller
- ----------------------
All the logic has been moved out of the binary commands and added to
an Application Controller.  You can see the controller code at
lib/puppet/application.rb and the logic for each application at
lib/puppet/application/binaryname.rb.

Binary Location Move
- --------------------
To bring Puppet more in line with general packaging standards the
puppetd, puppetca, puppetrun, puppetmasterd, and puppetqd binaries
now reside in the sbin directory rather than the bin directory when
installed from the source package.

New functions
- -------------

There are three new functions:

require - Similar to the include function but creates a dependency
on the required class in the current class.  This means the required
class will be loaded before the current class is processed.
split - allows you to split strings and arrays
versioncmp - allows you to compare versions

Other features
- --------------

You can find a full list of the tickets closed thus far for version
0.25.0 is at:

http://projects.reductivelabs.com/versions/show/3

Regards

James Turnbull

- --
Author of:
* Pro Linux Systems Administration
(http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet
(http://tinyurl.com/pupbook)
* Pro Nagios 2.0
(http://tinyurl.com/pronagios)
* Hardening Linux
(http://tinyurl.com/hardeninglinux)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKQDXx9hTGvAxC30ARAi/yAKDF0C+dApyrKGf/hlS7VVL3EyGeZwCeME1g
lORgVMxMB2b1geq9bjtqoVs=
=d2My
-----END PGP SIGNATURE-----

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

Reply via email to