[Puppet-dev] Re: Puppetconf 2015: pre-summit tea party
+1 for me On Friday, September 11, 2015 at 12:26:25 PM UTC-5, Daniele Sluijters wrote: > > > Want to join? Throw a +1 in the list so I get a rough idea of how people > are going to show. > > Can't join on Tuesday the 6th of October at 15:30 because you're not in > town yet? Not a problem, there's still ample time for you to adjust your > flight schedule accordingly ;)! > > > -- 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/93e7254a-3878-471d-aa85-9f94ed961a1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] Re: Announce: PuppetDB 3.0 has been released!
Awesome news! Especially love the full data available in DB and native failover support, my hacky standby mode can finally DIAF :) On Thursday, July 9, 2015 at 6:16:30 PM UTC-5, Wyatt Alt wrote: PuppetDB 3.0.0 - July 9, 2015 PuppetDB 3.0.0 Downloads Available in native package format as part of Puppet Collection 1 (PC1). More information on the PC1 repositories is available here: http://bit.ly/1HQJDNb Binary tarball: http://downloads.puppetlabs.com/puppetdb/ Source: http://github.com/puppetlabs/puppetdb Please report feedback via the Puppet Labs tickets site, using an affected PuppetDB version of 3.0.0: https://tickets.puppetlabs.com/browse/PDB Documentation: http://docs.puppetlabs.com/puppetdb/3.0/ Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb PuppetDB 3.0.0 Release Notes PuppetDB 3.0.0 is a major, backward-incompatible release containing powerful new features and packaging changes to conform with the All-In-One packaging standards adopted by Puppet 4. It is important to note that PuppetDB 3.0 depends on Puppet 4. Users should consult the release notes here: https://docs.puppetlabs.com/puppetdb/3.0/release_notes.html and the specific notes on new and backward-incompatible API features here: https://docs.puppetlabs.com/puppetdb/3.0/api/query/v4/upgrading-from-v3.html for detailed information and upgrading advice. Some changes we’re excited about are: - retirement of the v2 and v3 query APIs, and promotion of v4 as the stable API - support for automatic failover between multiple instances of PuppetDB - group_by query operator and foundational support for aggregate functions in queries (currently only count) - reports now include logs, metrics, and events from the associated Puppet run, and express whether or not the run used the --noop flag - extract can be used as a top-level query operator, to limit the fields a query returns - retirement of support for versions of PostgreSQL prior to 9.4 - deprecation of support for HSQLDB (with retirement slated for the next major release) Contributors Andrew Roetker, Andrii Nikitiuk, Chris Price, deadpoint, Eric Sorenson, Jean Bond, John Duarte, Jorie Tappa, Ken Barber, Brian LaMetterey, Lars Windolf, Mathieu Parent, Matthaus Owens, Melissa Stone, Nick Fagerlund, Rob Braden, Rob Browning, Roger Ignazio, Russell Mull, Ryan Senior, Wayne Warren, Wyatt Alt -- 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/bcc4a157-38c4-436c-a19c-e10d2cfcf709%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Puppet 4 delivery and upgrades
One could ague puppetlabs is better off sharing the package specs for included rubies so people can keep them current themselves, security updates directly from ruby vs having to wait for downstream backports and vendor repos sounds better to me long term. Not only can puppetlabs push updates quicker but the community can embrace them in the puppetworld without having to wait for impact analysis to their Shared dependencies. -byron On Sunday, December 14, 2014 3:08:21 PM UTC-6, David Schmitt wrote: The usual argument at this point in the discussion is that AIO packages of any vendor will - by definition - have worse security support than the system versions. People who have to certify/verify/validate/audit all binaries that are running on a given system will have additional high costs from bundled components that may render using those packages infeasible. Adding more binaries to a system will mean that they will require additional non-dedup-able hardware resources. Independently of those technical arguments, freeing puppetlabs from the ruby hell will be read by free software proponents(sic!) as unwillingness to support the diversity of the free software ecosystem. See also http://islinuxaboutchoice.com/ and so on. My own opinion is split between the economical realities of vendors and the fact that everything outside Debian main (+ backports) is not *Debian*. -- 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/3a8c1e2b-ba74-48df-9f70-77d659c90402%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Puppet 4 delivery and upgrades
I don't see these negatives at all. I think having puppet decoupled is a good thing - for reliability, management and freeing us from ruby hell. I can't see an AIO package altering the native behavior of the OS or system rubbies either.. Since it is OSS as well, is there a reason you wouldn't be able to pull down the git repo and update ruby according to your own needs? my assumption is that its a LOT easier to upgrade puppet ruby if it is indeed decoupled from system ruby or ruby used by apps on the platform your trying to manage. -byron On Thursday, December 11, 2014 3:53:15 PM UTC-6, John Bollinger wrote: On Thursday, December 11, 2014 3:34:17 PM UTC-6, John Bollinger wrote: If I cannot install Puppet into a Ruby installation of my choice (of sufficiently recent version) and have it work correctly, or if its installation alters the behavior of other software relying on that Ruby, then I do not foresee updating until I or someone else can fix those problems. I am unlikely to be able to devote any effort to such an endeavor any time soon, so my adoption of the new version would be forestalled indefinitely. Similarly, as long as Puppet is unable to share general-purpose third-party components, such as Ruby modules or a Java runtime, with other subsystems, I do not anticipate updating. Although I am disappointed that PL intends to offer only AIO packages, that decision will be only an inconvenience for me as long as the software does not inherently *depend* on AIO structure and layout. You may make suggestions, but you may not make system configuration decisions for me. John -- 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/052267c9-5504-4587-84d5-a2f5442065e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] Re: beaker 2.0 and beaker-rspec 4.0 released
Awesome! Off to go pull it down and give it a spin! On Friday, December 5, 2014 4:47:49 PM UTC-6, Alice Nodelman wrote: beaker 2.0 and beaker-rspec 4.0 are now released and available publicly from rubygems. These updates to beaker and beaker-rspec EOL ruby 1.8, update minitest dependency and provide a long list of improvements and bug fixes. See here for the complete rundown: https://github.com/puppetlabs/beaker/blob/master/HISTORY.md#LATEST If you have any questions please follow up here, on freenode irc #puppet-dev, or email al...@puppetlabs.com javascript:. alice. -- 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/7e497063-3b1f-4e13-96ba-19caf3331010%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Puppet 4 delivery and upgrades
Yay! On Tuesday, November 18, 2014 7:11:03 PM UTC-6, Michael Stanhke wrote: We'll be picking one Ruby (2.1.z), and using that everywhere for a consistent stack. -- 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/8e4aaef3-b07b-4a10-9298-20f9478987a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: puppet-dev status the week ending 14-11-14
I for one would love to feel more safe when tempting fate upgrading my puppet infrastructure. I like the idea of rolling upgrades (if upgraded, point here), but i would love to have some sort of process in puppet to handle this. A configuration/feature flag that says hey puppet, we're upgrading, lets converge. Have some sort of orchestration/reporting capability in this migration state (a light convergence catalog - hey, my file service in upgrade mode is only serving new agent code and if i see you have new agent code, converge to new master and call home) MCollective does make things slightly easier/more flexible in this regard but i hardly come across many people using it. i'm mostly thinking out loud remembering my last big upgrading but kicking myself for not writing down my wishlist -byron On Friday, November 14, 2014 12:16:07 PM UTC-6, Felix Frank wrote: On 11/14/2014 07:09 PM, Henrik Lindberg wrote: Please note that some changes in puppet 4 mean that puppet 3 agents won’t be able to talk to puppet 4 masters (or vice-versa). This probably means you don’t want to be updating puppet itself with “ensure = latest” :) Hi, point taken, but what will the update plan look like for a large installation? Will users be required to incorporate MCollective or similar to be able to upgrade their agents? Or should they try making all their agents update themselves until each last one won't talk to the master again, which can then be safely updated. The latter will not fly. Cheers, Felix -- 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/f61bfb41-8748-47f7-bb27-91d09f140301%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: Announce: Puppet 3.6.2 [ Security and Bug fix Release ]
Josh, Yeah, i'm getting warning on environments still. I run theforeman which doesn't support the new environments yet, so i was just curious if i could sleep the error until foreman is patched up. -byron On Tuesday, June 17, 2014 11:35:28 AM UTC-5, Josh Partlow wrote: (I clipped puppet-announce from this thread) Hi Byron, Stefan, Which deprecation warning are you continuing to see? There is an open issue with the disable_warnings, which is that static environment blocks in puppet.conf will continue to warn: https://tickets.puppetlabs.com/browse/PUP-2739 Is that the issue you are seeing? thanks, Josh On Tue, Jun 17, 2014 at 2:28 AM, Stefan Heijmans heij...@gmail.com javascript: wrote: Aha, experienced the same thing last week, didn't have time to look into it yet... On Monday, June 16, 2014 3:30:31 PM UTC+2, Byron Miller wrote: Running puppet 3.6.2 and disable_warnings = deprecations appears to make no difference to prohibiting the alert about environments. -- 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+...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/163f893b-3f66-497b-8618-a0213583e74e%40googlegroups.com https://groups.google.com/d/msgid/puppet-dev/163f893b-3f66-497b-8618-a0213583e74e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Josh Partlow jpar...@puppetlabs.com javascript: Developer, Puppet Labs Join us at PuppetConf 2014, September 20-24 in San Francisco Register by July 31st to take advantage of the Early Bird discount —save $249! -- 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/edacff4a-ca6e-4efb-b6de-52cc3e64bf2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] Re: Announce: Puppet 3.6.2 [ Security and Bug fix Release ]
Running puppet 3.6.2 and disable_warnings = deprecations appears to make no difference to prohibiting the alert about environments. On Tuesday, June 10, 2014 1:19:05 PM UTC-5, Moses Mendoza wrote: Puppet 3.6.2 is a security and bug fix release in the Puppet 3.6 series. This release addresses CVE-2014-3248 and CVE-2014-3250. ** CVE-2014-3248 ** Arbitrary Code Execution with Required Social Engineering An attacker could convince an administrator to unknowingly create and execute malicious code on platforms with Ruby 1.9.1 and earlier. CVSSv2 Score: 5.2 Vector: AV:L/AC:M/Au:S/C:C/I:C/A:C/E:POC/RL:OF/RC:C Affected Puppet versions (ruby 1.9.1 and earlier platforms only): All Fixed Puppet versions: 3.6.2 2.7.26* ** CVE-2014-3250 ** Information Leakage Vulnerability In Apache 2.4, SSLCARevocationCheck directive was added to mod_ssl, which defaults it to none and must be explicitly configured. This setting enables checking of a certificate revocation list. The default Puppet master vhost config shipped with Puppet does not include this setting. If a Puppet master is set up to run with Apache 2.4, and this default vhost configuration file is used, the Puppet master will continue to honor a host's certificate even after it is revoked. CVSSv2 Score: 3.1 Vector: AV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:OF/RC:C Affected Puppet versions: All (must be configured as a master behind Apache 2.4 using the default puppet master vhost). Fixed Puppet versions: 3.6.2 For more information on these vulnerabilities, please visit https://puppetlabs.com/security/cve/cve-2014-3248 https://puppetlabs.com/security/cve/cve-2014-3250 ## Bug Fixes Chatty warning/deprecation messages can now be suppressed – as we near the end of the 3.x series, there's going to be a slew of deprecations coming which need to be visible so everyone knows what's going to change, but some messages trigger tons of log spam, so now it's possible to turn them off. Directory environments under webrick now work; they no longer fail with Attempted to pop, but already at root of the context stack errors. A memory leak in loading functions was fixed. Community shout-out for this release goes to Joshua Hoblitt for testing the memory leak patch and providing awesome usage graphs (PUP-2692). Please read through the Release Notes for the full list of changes: http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html To install Puppet, follow the Installation Guide:http://docs.puppetlabs.com/guides/install_puppet/pre_install.html To report issues with the release, file a ticket in the “PUP” project on https://tickets.puppetlabs.com/ and set the “Affects version/s” field to 3.6.2”. * The Puppet 2.7.x series is officially end of life, but continues to be maintained by community members. See the release announcement to puppet-announce/puppet-users/puppet-dev regarding Puppet 2.7.26. -- Moses Mendoza Puppet Labs Join us at PuppetConf 2014, September 20-24 in San Francisco Register by July 31st to take advantage of the Early Bird discount —save $249! -- 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/bc01a5e8-cf30-4152-bbba-b0b50621b9f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
