Also if you are a mcollective user it might be worth waiting a bit. Many deprecation warnings will show on your client and server logs which are really annoying
I made PRs to fix them so maybe next release --- R.I.Pienaar > On 28 Jun 2017, at 16:28, R.I.Pienaar <[email protected]> wrote: > > People upgrading should note the PuppetDB dependency is now postgres > postgresql96, this is not stated on the package dependency metadata so > upgrade works fine but puppetdb fails to start until you update > >> On Wed, Jun 28, 2017, at 15:40, Trevor Vaughan wrote: >> Awesome! We'll start working on testing with this as soon as we can. >> >> First issue found: When using rspec-puppet, we need to test with >> 'server_facts' but now can no longer set those since they are 'reserved' >> but appear to be unset by default. Any idea how to get around this? >> >>> On Tue, Jun 27, 2017 at 10:13 PM, Eric Sorenson <[email protected]> wrote: >>> >>> I have run out of superlatives to try to express how excited I am for this >>> release: the Puppet 5 Platform is available for download now. >>> >>> The primary goals of this release are to harmonize numbering across the >>> major components (Puppet Agent, PuppetDB, Puppet Server) to "5", as a first >>> step towards delivering these components as a unified platform; include >>> Hiera 5 with eyaml as a built-in capability; provide clean UTF-8 support; >>> move network comms to fast, interoperable JSON. Our current Ruby versions >>> are EOL'ed, so we're moving to MRI Ruby 2.4 on the agent and (opt-in) >>> jruby9k on the server. The PE-only puppet-server metrics service is now >>> open-sourced. >>> >>> In addition to the features, there are some substantial performance boosts >>> waiting for you. According to our perf testing (thanks Doug!): >>> >>> • Puppet 5 Agent run-times were 30% lower at equivalent loads. (Average of >>> 8 seconds vs 5.5 seconds) >>> • Puppet 5 Server CPU utilization was at least 20% lower than Puppet 4 in >>> all scenarios. >>> • CPU utilization for Puppet 5 PuppetDB and PostgreSQL were also lower in >>> all scenarios. >>> • Puppet 5 catalog compile times reported by Puppet Server were between >>> 7-10% lower than Puppet 4. >>> • Puppet 5 scaled to an additional 40% increase in the number of agents >>> while Puppet 4 agent run-times became dangerously high. >>> >>> This is a "semver major" with some backwards incompatibilities, but we >>> have worked very hard to retain module compatibility with Puppet 4.x >>> modules. With a few careful (and hopefully rarely used) exceptions, *module >>> code that works under Puppet 4 should not need revision to work under >>> Puppet 5*. >>> >>> For a full list of changes and download instructions, check out the full >>> release notes: https://docs.puppet.com/puppet/5.0/release_notes.html >>> >>> I'd like to send out huge thanks to the Puppet teams who worked on this >>> release and to community members who provided feedback on both the design >>> discussions and early preview releases — extra special thanks to Josh >>> Cooper for shepherding this out the door. It has a special significance for >>> me since it's version five and (by total coincidence!) yesterday was my >>> five year anniversary at Puppet :) I think it's going to be a great release >>> series. >>> >>> Eric Sorenson - [email protected] >>> director of product, ecosystem and platform >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Puppet Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/puppet-dev/C17DC8B4-D7D3-417D-A3D5-43066C5BCB3F%40puppet.com >>> <https://groups.google.com/d/msgid/puppet-dev/C17DC8B4-D7D3-417D-A3D5-43066C5BCB3F%40puppet.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Trevor Vaughan >> Vice President, Onyx Point, Inc >> (410) 541-6699 x788 >> >> -- This account not approved for unencrypted proprietary information -- >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoWD%2BN9B%3DHAGxs7DtOdydzDN2SNVE4miZfeeEToOMy5kZQ%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > R.I.Pienaar / www.devco.net / @ripienaar -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/E4EB0E8C-B890-45F1-BD36-903A212162D1%40devco.net. For more options, visit https://groups.google.com/d/optout.
