On 28/06/17 16:31, Trevor Vaughan wrote:
I'm seeing a lot of Warning: Defining "data_provider": "hiera" in
metadata.json is deprecated. How do we successfully support both Puppet
4.7 (LTS) and Puppet 5 (Today) without this garbage popping up at every run?
I don't want to kill any *real* deprecation warnings, just ones that
conflict between LTS and New Shiny.
You should be able to suppress the deprecation warnings. However, there
were bugs in several places that logged deprecations so they may not all
be suppressed by that action alone. You may also need to set strict=off.
- henrik
Thanks,
Trevor
On Wed, Jun 28, 2017 at 9:40 AM, Trevor Vaughan <tvaug...@onyxpoint.com
<mailto:tvaug...@onyxpoint.com>> 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 <e...@puppet.com
<mailto:e...@puppet.com>> 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
<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 - e...@puppet.com <mailto:e...@puppet.com>
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 puppet-dev+unsubscr...@googlegroups.com
<mailto:puppet-dev+unsubscr...@googlegroups.com>.
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
<https://groups.google.com/d/optout>.
--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699 x788 <tel:(410)%20541-6699>
-- This account not approved for unencrypted proprietary information --
--
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 puppet-dev+unsubscr...@googlegroups.com
<mailto:puppet-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoUtm8k6iHXcpC5qZPps%3DMGjZTNR972aGUra8aD6gXS5yQ%40mail.gmail.com
<https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoUtm8k6iHXcpC5qZPps%3DMGjZTNR972aGUra8aD6gXS5yQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
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 puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/oj0lot%245ph%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
