We're pleased to announce that Puppet Server 1.1.0 and 2.1.0 are both now available!
Both of these releases are backwards compatible feature releases in their respective Semantic Versioning <http://semver.org/> major versions. This email is a combined announcement for 2.1 and 1.1. Puppet Server 2.1 Puppet Server 2.1 now supports both Puppet 4 and Puppet 3 agents. This is new functionality compared to Puppet Server 2.0 which only supported Puppet 4 agents. This compatibility necessitates some special consideration, however, so please review the Puppet Server 2.1 release notes <http://docs.puppetlabs.com/puppetserver/2.1/release_notes.html> and Backwards Compatibility with Puppet 3 Agents <http://docs.puppetlabs.com/puppetserver/2.1/compatibility_with_puppet_agent.html> if you intend to run Puppet 3 agents against Puppet Server 2.1. Puppet Server 2.1 also introduces a new feature that allows the JRuby containers and associated threads to be flushed and re-initialized after a configurable number of HTTP requests. This functionality is similar to the PassengerMaxRequests functionality that is often tuned in Puppet+Passenger configurations. Please see the Tuning Guide <http://docs.puppetlabs.com/puppetserver/2.1/tuning_guide.html> for more information. In addition, the following issues have been resolved in Puppet Server 2.1: Maintenance & Small Improvements - SERVER-380 - Upgrade Jetty to 9.2.x. - SERVER-437 - Upgrade stable branch to jvm-ssl-utils 0.8.0. - SERVER-517 - Re-raise HttpClientExceptions as Ruby SocketError from http-client handler. - SERVER-518 - Removed the hyphen from “puppet-server” in the project.clj in order to preserve backward compatibility with dujour check-ins of Puppet Server which previously used “puppetserver” as the artifact-id. The group-id also changed from “puppetlabs.packages” to “puppetlabs”. - SERVER-530 - Merge up stable branch from 1.0.8 release commit to 2.1 branch. - SERVER-544 - Reduced the amount of memory used by the master to cache the payload for incoming catalog requests. - SERVER-598 - To improve ability to introspect routes, we ported Puppet Server to use comidi for web routes. - SERVER-599 - Long-running memory test that covers latest JRuby changes in stable. - SERVER-614 - Fix set_connect_timeout_milliseconds error when sending report to PuppetDB. - SERVER-680 - Upgraded JRuby dependency to 1.7.20 in order to take advantage of some of the memory management improvements we’ve seen in our internal testing. Misc Bug Fixes - SERVER-157 - Utilize keylength puppet conf value for generating SSL cert keys. - SERVER-273 - Upgrade to JRuby 1.7.19 / fix for jruby-pool DELETE memory leak. - SERVER-345 - Fixup usages of cacert / localcacert in master. - SERVER-404 - Properly create /var/run/puppetserver dir at service startup. - SERVER-442 - Fix for a problem where file_metadatas requests to the master which include multiple ignore parameters were being mishandled. This had previously led to an agent downloading files from the master which should have been ignored. - SERVER-535 - Tests in the jruby-puppet-service-test namespace were using an invalid configuration map, which caused them to throw an error. - SERVER-541 - Disabled the display of verbose output that appeared during a package upgrade. - SERVER-564 - Re-enabled the master status endpoint - SERVER-647 - Puppet Server failed to start with with an uncaught exception when master-{code, run, log}-dir settings were not defined. This patch addresses the problem by setting the values to nil, which will cause Puppet Server to consult Puppet for the values. - SERVER-657 - Fixed puppetserver foreground on Ubuntu. - SERVER-655 - Upgrade to JRuby 1.7.20 caused server fail loading the Bouncy Castle jar. - SERVER-659 - Restored broken http client timeout settings. - SERVER-682 - Fixed an issue where logback levels weren’t changed unless you restarted Puppet Server. This functionality had been provided in Puppet Server 1.0.2 but was inadvertently removed in Puppet Server 1.0.8, then merged with 2.0. - SERVER-683 - Changed the logic in the legacy-routes-service to get the route of the master-service via the service protocol name rather than by a hard-coded service name. This allows for the legacy-routes-service to pull the route from whatever service implementing the MasterService protocol happens to be in the service stack, i.e., master-service for open source Puppet or pe-master-service for PE. - SERVER-684 - Append source_permissions=use to 3.x file_metadata requests. See the complete release notes for details about these changes: https://docs.puppetlabs.com/puppetserver/2.1/release_notes.html For a list of all changes in this release, check out the JIRA page: https://tickets.puppetlabs.com/browse/SERVER/fixforversion/13007 Puppet Server 1.1 In addition to several bug fixes, this release adds a new feature which can be configured to allow the master to automatically flush individual JRuby pool instances after a specified number of web requests have been handled. This upgrades Puppet Server’s dependency on JRuby to 1.7.20 in order to take advantage of memory optimizations and other fixes. Bug fixes - SERVER-564 Re-enabled the master status endpoint - SERVER-442, SERVER-696 ignore parameters were being mishandled - SERVER-157 keylength value now being determined by setting - SERVER-541 Verbose output disabled - SERVER-682 Previous logback level issue fix had been reverted Miscellaneous improvements - SERVER-544 - Reduced the amount of memory used by the master to cache the payload for incoming catalog requests. - SERVER-680 - Upgraded JRuby dependency to 1.7.20 in order to take advantage of some of the memory management improvements we’ve seen in our internal testing. - SERVER-391 - Made the error message displayed for a JRubyPool “borrow-timeout” a little more clear. See the complete release notes for details about these changes: https://docs.puppetlabs.com/puppetserver/1.1/release_notes.html For a list of all changes in this release, check out the JIRA page: https://tickets.puppetlabs.com/browse/SERVER/fixforversion/12631 EOF -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOXx1vF0qaCkUNwgOzTbUaAdv90b%2BLRnEbuuR6Sptf_ok3-2UA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
