Re: [Puppet Users] Re: RFC: Default File Permissions
Hello all, Just a quick update on this issue. We're planning to fix this for 3.4 and there's a pull request at: https://github.com/puppetlabs/puppet/pull/2087 Also, after some discussion with Nick F, we renamed the 3 values of source_permissions to: use, use_when_creating, ignore Thanks for any comments. It will be great to have this issue addressed! Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014, September 23-24 in San Francisco* -- 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/CALsUZFF7w4E4WJFOqDYkfPGpypffoZmLkp%3D6K0%3DCMyyA%3D0cWng%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Failed running the puppet tests: bundle exec rake spec
On Tue, Apr 15, 2014 at 9:20 AM, David Portabella < david.portabe...@gmail.com> wrote: > I've added more memory to the virtual machine, > and now it works. > 19753 examples, 0 failures, 86 pending > > (although I still get one "Cannot allocate memory" error) > > If you run 'bundle exec rake parallel:spec[1]' instead of 'bundle exec rake spec' it should use less memory. That number in square brackets is the number of processes to run in parallel, so if you've given your vm multiple processors, bump that number and specs should run faster as well. Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 22-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFHjy4ftTeS1mwZcNQMCV_vA9Kq2qmR_eM2Z_mfc4mrXvQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] API
On Thu, Apr 17, 2014 at 6:30 AM, Marcio Ordoñez wrote: > Do you know why I get 404 erro on GET? > > curl -u user:password -k -H 'Accept: s' > https://puppet.mydomain.com.br/certificate/ca > > By default the puppetmaster listens on port 8140. So you might try: curl -k -H 'Accept: s' https://puppet.mydomain.com.br:8140/certificate/ca<https://puppet.mydomain.com.br/certificate/ca> HTH Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFEeBCvRAzAbB-KsiK-zsHPSwci8b9JjXOah0FrQCYMTog%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] 3.6, file resources, and warnings
On Thu, May 15, 2014 at 3:55 PM, Tristan Smith wrote:
> So I'm testing out puppet 3.6 with our existing environment and in general
> i'm pleased.
>
> There's one oddity that I'm tripping on and I'm not sure how to address
> it. We have a number of places where we leverage the 'file' resource with
> an array of sources - using fileservers to pick the first match of a file
> for a host, for an operating system, or a fallthrough file, like, say:
>
>
> file { "$sudoersd/005_$hostname":
> require => File[$sudoersd],
> ensure => "file",
> owner => root,
> group => 0,
> mode => "0440",
> source => ["puppet:///modules/sudo/etc/sudoers.hosts/$hostname",
>
> "puppet:///modules/sudo/etc/sudoers.hosts/no_unique_entries"]
> }
>
>
> In previous versions, this has worked fine - and it still _works_ today.
>
> However, I'm seeing warning messages regarding the hostname entry, the one
> that fails. That seems excessive when the resource doesn't fail or even do
> something improper.
>
This sounds like https://tickets.puppetlabs.com/browse/PUP-2584, which
should be fixed in 3.6.1. Those warning messages definitely make for a lot
of log spam!
Glad 3.6 is looking good for you in general.
Kylo
>
> My question then: Should I
>
> a) consider another idiom for these needs?
>
> Or
>
> b) take advantage of the new log_level directive (thank you, by the way)
> and set log_level=err and not worry about warnings except when debugging
> failures?
>
>
> --Triss
>
> --
> 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/70070de5-ea62-4406-94c6-12632e3e0c7c%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/70070de5-ea62-4406-94c6-12632e3e0c7c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Kylo Ginsberg
k...@puppetlabs.com
*Join us at PuppetConf 2014**, September 23-24 in San Francisco
- http://puppetconf.com <http://puppetconf.com/>*
*Register by May 30th to take advantage of the Early Adopter discount
<http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!*
--
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/CALsUZFE%2BZSvxjpzh-ps31Hfuvtcchm0vOKpuQegadpQ18Mi1Qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] YUM Provider in 3.x
On Fri, May 16, 2014 at 12:54 AM, Paul Seymour wrote:
> Hello,
>
> Working through some issues with upgrading our environment from 2.x to 3.5
> (now I should probably target 3.6 !) anyway we have a module which
> does basically.
>
> package { 'openssh-server':
> ensure => 'absent',
> }
>
> package { '3rd-party-ssh':
> ensure => 'installed'
> }
>
> This 3rd party SSH package has a "provides" of openssh-server on it. As
> such if you issue a "yum remove openssh-server" manually it will try and
> remove
> the 3rd party version. Which is the standard YUM behaviour I believe.
>
Yes, 3.5 fixed puppet's behavior to match yum's with respect to virtual
packages, a long requested feature. See
https://tickets.puppetlabs.com/browse/PUP-897 for details.
However, it was a regression wrt *puppet* which took a number of people by
surprise, so in 3.6.1, there's a fix to make the new (3.5-style,
yum-matching) behavior opt-in via a new "allow_virtual" parameter (with the
intent to change the default to be the yum-matching behavior in puppet 4).
See https://tickets.puppetlabs.com/browse/PUP-2182 for discussion.
Kylo
> So therefore on the 3.x servers the package is being removed/installed
> every time and as there is no dependencies here it can leave us without an
> SSH
> server running.
>
> Which I guess is probably what we are actually telling it to do. But this
> never happens in the 2.x series.
>
> Any ideas on why, and how we can stop this behaviour ?
>
> Thanks
> Paul
>
> --
> 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/daba08fe-85bc-426d-90ee-a01d3bd91ec8%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/daba08fe-85bc-426d-90ee-a01d3bd91ec8%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Kylo Ginsberg
k...@puppetlabs.com
*Join us at PuppetConf 2014**, September 23-24 in San Francisco
- http://puppetconf.com <http://puppetconf.com/>*
*Register by May 30th to take advantage of the Early Adopter discount
<http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!*
--
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/CALsUZFFZa2SNe4eXSDTq8JP6bZtpX3eVP-T9w3_qi6p_4zeQJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Nasty.
On Fri, May 16, 2014 at 7:20 AM, Paul Seymour wrote: > Hello, > > Just updated to 3.6.0 and a strange thing is happening (might not be > related to 3.6 specifically just testing before making the jump from 2.7 > for real). > > I have a puppet master running under Apache/Passenger and when testing a > client this happens:- > > $ puppet agent -t --no-daemonize --noop > Info: Retrieving pluginfacts > Info: Retrieving plugin > Notice: /File[/var/lib/puppet/lib/puppet]/ensure: removed > Notice: /File[/var/lib/puppet/lib/facter]/ensure: removed > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not find class for > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > > However if I shutdown the master and run it under a shell with "--debug > --no-daemonize" everything is fine and clients (re-download) the > facts/plugins > and get a catalog etc. > > I am a bit mystified about this, and ideas ? > Kind of a guess, but this *may* be https://tickets.puppetlabs.com/browse/PUP-2610, which is a rack-specific bug we stumbled across yesterday. If so, you *may* be able to workaround it by setting environment_timeout = 0 (for details on that settings see http://docs.puppetlabs.com/puppet/latest/reference/environments.html#tuning-environment-caching ). So that's a conjecture on top of a conjecture, but if you don't mind experimenting, you could see if that setting makes any difference. Thanks, Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFEkeXPaXPcBfT6nB-MEH10wi9QfOk%3DCJaHqPW1tHyMQ0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Nasty.
On Mon, May 19, 2014 at 2:09 AM, Paul Seymour wrote: > >>> >>> However if I shutdown the master and run it under a shell with "--debug >>> --no-daemonize" everything is fine and clients (re-download) the >>> facts/plugins >>> and get a catalog etc. >>> >>> I am a bit mystified about this, and ideas ? >>> >> >> Kind of a guess, but this *may* be https://tickets.puppetlabs. >> com/browse/PUP-2610, which is a rack-specific bug we stumbled across >> yesterday. If so, you *may* be able to workaround it by setting >> environment_timeout = 0 (for details on that settings see >> http://docs.puppetlabs.com/puppet/latest/reference/ >> environments.html#tuning-environment-caching). >> >> So that's a conjecture on top of a conjecture, but if you don't mind >> experimenting, you could see if that setting makes any difference. >> >> That appears to have worked around that particular issue. Many thanks for > the tips. > Cool, glad that worked. Just to reiterate for posterity: that is definitely a *workaround* and should not be needed in 3.6.1+. Thanks for trying that out! Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFFKWnoo0YHZ5TSHW%3DfH8XvBcH4L64tUYQA2X-WjvnkxPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet 3.6.1 Virtual Packages, and unrelated facts questions...
On Fri, May 23, 2014 at 2:58 AM, Paul Seymour wrote: > >> +1 - let's file a bug report. >> > > https://tickets.puppetlabs.com/browse/PUP-2650 > For more context here, puppet has a 'deprecation_warning' method which is used for this new message and also in a number of other places. In puppet 3.7, we're planning to introduce a number of additional deprecation messages (for functionality which will be removed in puppet 4) So there are at least two possibilities here: 1) Make all deprecation messages Info-level rather than Warning-level. So you'd need to specify --verbose to see the deprecation messages. 2) Leave the deprecation messages at Warning-level, but add a 'warn-on-deprecation' setting (possibly with a better name). In either case, you'd need to flip a setting to see the deprecation messages (whereas they are in your face today). The downside to (1) is that the deprecation messages would be mixed in with other Info messages that might not be of interest to the person planning their migration to puppet 4. The downside to (2) is it's Yet Another Setting and as such it might not be used as much (i.e. puppet 4 might take more people by surprise). Thoughts? Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFEb9%3DF4vXxc9O6E%3D_agzjuNi_sOgx0P2W-y1C0xA1KHXA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Hiera 1.3.3 available!
On Thu, May 22, 2014 at 9:42 PM, David Gillies wrote: > So I hope you actually meant Ubuntu *13.04* (Raring Ringtail) and not > Ubuntu 12.04 (Precise Pangolin) right? > Yes, we meant 13.04. That was a typo in the announcement. The release notes should be updated shortly as well. Thanks Kylo > > > On Friday, 23 May 2014 13:08:16 UTC+10, Eric Sorenson wrote: > >> Hiera 1.3.3 is a backwards-compatible performance and fixes release in >> the 1.3 series. It provides a substantial speed increase for lookups >> compared to Hiera 1.3.2. This release also adds support for Ubuntu 14.04 >> (Trusty Tahr) and discontinues support for Fedora 18 and Ubuntu 12.04 >> (Raring Ringtail). >> >> Shout-out to Sean Millichamp for the original patch providing the >> performance boost! >> >> Please read through the Release Notes for the full list of changes: >> http://docs.puppetlabs.com/hiera/1/release_notes.html#hiera-133 >> To install Hiera, follow the installation guide: >> http://docs.puppetlabs.com/hiera/1/installing.html >> To report issues with the release, file a ticket in the "HI" project on >> http://tickets.puppetlabs.com/ and set the "Affects version/s" field to >> "1.3.3" >> >> Eric Sorenson - eric.s...@puppetlabs.com - freenode #puppet: eric0 >> puppet platform // coffee // techno // bicycles >> >> > NOTICE > > This e-mail and any attachments are confidential and may contain copyright > material of Brandscreen or third parties. If you are not the intended > recipient of this email you should not read, print, re-transmit, store or > act in reliance on this e-mail or any attachments, and should destroy all > copies of them. Brandscreen does not guarantee the integrity of any emails > or any attached files. The views or opinions expressed are the author's own > and may not reflect the views or opinions of Brandscreen. > > -- > 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/0d8be9d3-a3f7-401a-9de9-0c3c4a4c3164%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/0d8be9d3-a3f7-401a-9de9-0c3c4a4c3164%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFFJpvXqBhRMDqHBNV8%3D82pg%3Dgt9%3Dx2ou3t4K02eOPfHjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet 3.6.1 Virtual Packages, and unrelated facts questions...
On Tue, May 27, 2014 at 7:16 AM, Chuck wrote: > The ability to turn off the deprecation messages would be great. The only > things these messages provide are a drain on logging resources, noise in > the logs, and confusion from end users. > > Seems like we have consensus on an ignore-deprecation-warnings setting, which defaults to false. And I like Felix's suggestion that the (as yet unwritten) puppet-4 migration guide will recommend restoring that default. Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFFXRiQX4wDc5TjoZWXAz-q7-kdO%2Bx%2B6%3DpdsdvN4HKYFvw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet 3.6.1 Virtual Packages, and unrelated facts questions...
On Wed, May 28, 2014 at 1:53 PM, Andy Parker wrote: > On Tue, May 27, 2014 at 11:33 AM, Kylo Ginsberg > wrote: > >> On Tue, May 27, 2014 at 7:16 AM, Chuck wrote: >> >>> The ability to turn off the deprecation messages would be great. The >>> only things these messages provide are a drain on logging resources, noise >>> in the logs, and confusion from end users. >>> >>> Seems like we have consensus on an ignore-deprecation-warnings setting, >> which defaults to false. >> >> > I think a 'deprecation-level' setting might be more in keeping with > logging. It defaults to warn, but can be turned down to debug if you don't > want to normally see them. > > This seems like it might cause some confusion if users are grepping their logs and not sure if the deprecations are warning/info/debug? I'm more familiar with the model of enabling/disabling a class of warnings (a la gcc or linters, etc). But I have no strong feelings here other than wanting to get this addressed in 3.6.2. Anyone else care to weigh in? -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014**, September 23-24 in San Francisco - http://puppetconf.com <http://puppetconf.com/>* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CALsUZFHyt4UvcNKk0W5L1eZnN2h_qVT3UEF_muQPNz4xyH%2B3hw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] signing multiple certificate request at once
On Mon, Jul 21, 2014 at 6:27 AM, Ankita kumari wrote: > Is there a way to sign the certificate request by giving the hostname of > the agents as regular expression? in this way one can sign the requests > coming by multiple agents at time. > There are several options for autosigning, including policy-based autosigning where you provide an executable (which could do regex-based processing of certname). More info at http://docs.puppetlabs.com/puppet/latest/reference/ssl_autosign.html Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September 20-24 in San Francisco* *Register by July 31st to take advantage of the Early Bird discount <https://puppetconf2014.eventbrite.com/?discount=EarlyBird> **—**save $249!* -- 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/CALsUZFEDV_HcHN9dLX%2BY62sJQdzjcjVvRZ9SRx_Vpsogu9KahA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: [Puppet Users] Re: Announce: Facter 2.0.1
Hi Madd,
On Thu, Jul 31, 2014 at 5:08 AM, Madd Sauer
wrote:
> [root@devel69 facts.d]# cat /var/lib/puppet/lib/facter/kis_horcm.rb
> if Facter.kernel == "Linux"
> Facter.add("kis_horcm") do
> setcode do
> File.exist?("/etc/horcm.conf")
>end
> end
> end
>
>
>
One other idea: try changing Facter.kernel to Facter.value(:kernel). The
former syntax was deprecated, and the latter works with older facter
versions as well.
Kylo
--
Kylo Ginsberg
k...@puppetlabs.com
*Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September
20-24 in San Francisco*
*Register by July 31st to take advantage of the Early Bird discount
<https://puppetconf2014.eventbrite.com/?discount=EarlyBird> **—**save $249!*
--
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/CALsUZFE6Bu6iqa40Mb1FQknDp-p8RO2tu%2Bup678isGmvB297hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Facter 2.2.0
On Tue, Aug 26, 2014 at 11:57 PM, Daniele Sluijters < daniele.sluijt...@gmail.com> wrote: > Hey, > > I agree with the spirit of the fix but the fact that it isn't mentioned > anywhere in the release notes is a bit annoying. > Yep, it's a release notes fail, and it happened because we didn't track the change with separate tickets. What happened is we made this change as part of adding lsbminordistrelease (FACT-637 <https://tickets.puppetlabs.com/browse/FACT-637>) and adding the new 'os' structured fact (FACT-614) <https://tickets.puppetlabs.com/browse/FACT-614>, but it wasn't called out separately. Anyway that's an explanation, but not really an excuse - we dropped the ball on publicizing this change. We've added tickets for the changes and pushed updated release notes for facter 2.2 here <https://docs.puppetlabs.com/facter/2.2/release_notes.html>. > I personally also consider this a backwards incompatible release, you're > changing old behaviour. Albeit for the better, but people depended on that > behaviour and no prior warning or deprecation warning was issued. > Although we clearly should have documented this differently, since it's in the wild and there's consensus that this change *is* for the better, we'd like to leave it be. But going forward there's a question about how to handle changes to fact *values*. One proposal is that we identify (and of course test against) some essential facts that we "care a lot about" (such as 'lsbmajdistrelease") and set some rules, like: (a) we do not change those in x.y.Z releases (b) we highlight it when they DO change in x.Y or X releases > Do also keep in mind that though we can easily fix our own manifests with > a regexp match, since the launch of the Forge people have started to use > more and more modules maintained by others. Unless the maintainer has > already issued an update you're stuck with manually patching an upstream > module and carrying that change. Depending on how you deploy your > environment this might be difficult to do. > I grep'd my way through forge modules looking for affected modules and there are actually just a handful (3 related to postgresql, and 3 others). I'll ping those authors to let them know. There's already a fix in for puppetlabs-postgresql. Btw, one last thing: another plug for the recently announced <https://groups.google.com/forum/#!topic/puppet-users/gtXrUgQZmJ0> nightly repos, which would have exposed this issue if we'd had repos all in place ahead of time (this change went in two weeks before release). Thanks! -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September 20-24 in San Francisco* *Register by September 8th to take advantage of the Final Countdown <https://www.eventbrite.com/e/puppetconf-2014-tickets-7666774529?discount=FinalCountdown> * *—**save $149!* -- 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/CALsUZFHQ_Pho_%2Bq9VCBMdMhe4DjcZRhvmF5NU74wTU-DXoZ9xg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: nightly repos available
On Tue, Aug 26, 2014 at 10:23 AM, Eric Sorenson < eric.soren...@puppetlabs.com> wrote: > In lieu of release candidates, we are moving toward a more automated > system which will have the latest green builds (passed spec and Beaker > acceptance tests) cut off the 'master' branch for most of our projects. > What this means is that as we near feature complete on a release, like the > coming Puppet 3.7.0 release, users like yourself can begin trying out the > packages to ensure that the new features haven't broken anything you depend > on, and that the new features work the way you expect/want them to. > > The repos are live now and you can try them out by following these > directions: > > https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#using-the-nightly-repos > > As a heads up, we're shooting for releasing Puppet 3.7.0 on Tuesday. It'll have loads of goodies: https://tickets.puppetlabs.com/issues/?filter=12628 As discussed above, we're *not* doing RCs for this release, but we still love to get feedback prior to release. So if you're accustomed to trying out RCs, or just curious about an early glimpse at 3.7.0, please try out puppet-latest on the nightly repos, using the instructions above. Thanks! Kylo -- Kylo Ginsberg k...@puppetlabs.com *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September 20-24 in San Francisco* *Register by September 8th to take advantage of the Final Countdown <https://www.eventbrite.com/e/puppetconf-2014-tickets-7666774529?discount=FinalCountdown> * *—**save $149!* -- 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/CALsUZFHB%2BOYOYowm_eM6rFzWmhTFPNASw%3DAxY-Vy%2BMMpb25_7Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How can I trace "comparison of String with Array failed" error to actual values?
On Wed, Sep 10, 2014 at 3:46 AM, Stephan wrote: > Hi All, > > I'm getting the following error: > > Error: Got an uncaught exception of type ArgumentError: comparison of > String with Array failed > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/property/list.rb:38:in > `sort' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/property/list.rb:38:in > `dearrayify' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/property/list.rb:48:in > `should' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type/user.rb:365:in `block > (2 levels) in ' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type.rb:1962:in > `instance_eval' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type.rb:1962:in `block in > autorequire' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type.rb:1940:in `block in > eachautorequire' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type.rb:1939:in `each' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type.rb:1939:in > `eachautorequire' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/type.rb:1957:in > `autorequire' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/graph/relationship_graph.rb:168:in > `block in build_autorequire_dependencies' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/graph/relationship_graph.rb:167:in > `each' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/graph/relationship_graph.rb:167:in > `build_autorequire_dependencies' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/graph/relationship_graph.rb:25:in > `populate_from' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/resource/catalog.rb:195:in > `relationship_graph' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/transaction.rb:141:in > `relationship_graph' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/transaction.rb:55:in > `evaluate' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/resource/catalog.rb:167:in > `block in apply' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/util/log.rb:149:in > `with_destination' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/transaction/report.rb:112:in > `as_logging_destination' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/resource/catalog.rb:166:in > `apply' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/configurer.rb:117:in > `block in apply_catalog' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/util.rb:161:in `block in > benchmark' > /opt/freeware/lib/ruby/2.0.0/benchmark.rb:296:in `realtime' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/util.rb:160:in `benchmark' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/configurer.rb:116:in > `apply_catalog' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/configurer.rb:191:in `run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:47:in `block (4 > levels) in run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent/locker.rb:20:in > `lock' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:47:in `block (3 > levels) in run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:117:in > `with_client' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:44:in `block (2 > levels) in run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:82:in > `run_in_fork' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:43:in `block in > run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application.rb:179:in > `call' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application.rb:179:in > `controlled_run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/agent.rb:41:in `run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application/agent.rb:355:in > `onetime' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application/agent.rb:321:in > `run_command' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application.rb:371:in > `block (2 levels) in run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application.rb:477:in > `plugin_hook' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application.rb:371:in > `block in run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/util.rb:479:in > `exit_on_fail' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/application.rb:371:in `run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/util/command_line.rb:137:in > `run' > /opt/freeware/lib/ruby/vendor_ruby/2.0.0/puppet/util/command_line.rb:91:in > `execute' > /opt/freeware/bin/puppet:8:in `' > > I'm seeing this error only when I try to realize a virtual defined > resource: > > User::Config <| title == "jo
Re: [Puppet Users] Constant "end of file reached"
On Thu, Sep 18, 2014 at 9:37 AM, Steve Perry wrote: > Wondering if anyone has seen this issue before: > > [root@xxpuppet2 puppet]# puppet agent -t > Warning: Unable to fetch my node definition, but the agent run will > continue: > Warning: end of file reached > Info: Retrieving pluginfacts > Info: Retrieving plugin > Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources > using 'eval_generate': end of file reached > Info: Loading facts > Error: Could not retrieve catalog from remote server: end of file reached > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > [root@xxpuppet2 puppet]# > > I am seeing this happen on every node that runs against this master. This > seems to have started randomly... > Hi Steve, What version of puppet are you running? If you recently upgraded to 3.7.x, you could be seeing https://tickets.puppetlabs.com/browse/PUP-3238. The tldr there is that the new http_keepalive_timeout setting should be less than the puppet master's keep alive timeout (e.g. KeepAliveTimeout on apache). Thanks! Kylo -- 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/CALsUZFFFwq2VDtS-_%3DbJX8HSqP%2BCYW4gHNQ6s0t3QTg%2Bt4gEtA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: facter error message - what does this mean?
I don't know where that "Invalid facter option(s)" exception is coming from. Can you run with trace=true? Thanks! On Fri, Sep 26, 2014 at 3:02 AM, kaustubh chaudhari wrote: > > Hi, > > I am also facing same issue. unable to find where to look for, puppet > agent runes file facter runes fine if run manually. > > > But schedule run still not working. > > Any help is appreciated. > > FYI: This happened after upgrade from 3.3.2 to 3.6.2 > > -Kaustubh > > On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote: >> >> I'm seeing this error appear on a client machine (/var/log/syslog): >> >> puppet-agent[17158]: Failed to apply catalog: Could not retrieve local >> facts: Invalid facter option(s) type >> >> If I run 'puppet agent --test' it runs fine. >> >> If I run 'puppet agent --test --debug' there is no mention of this error. >> >> Yet if I wait until the next scheduled run the error will reappear. >> >> >> What's going on? >> > -- > 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/30f04d48-b51c-4360-9a1c-feb205438639%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/30f04d48-b51c-4360-9a1c-feb205438639%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFEL0sBio65wPcCLiaerG2tycyB1GWuVqREtG9kTBbsS0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet Server 0.2.0
On Fri, Sep 26, 2014 at 4:42 PM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > On 09/26/2014 11:12 PM, Rob Reynolds wrote: > > Felix, if your "what?" is about Java (the language), that was a >> mistake. JVM on the server side, generally written in Clojure, is the >> direction things are heading. C++ on the client side. Ruby is still >> sticking around in order to support extensions. That said, some things >> we'll need to discuss and figure out what the best way to move forward is. >> Luke wrote up a good post about some of these changes at >> http://puppetlabs.com/blog/evolving-puppet-for-next-ten-years >> >> I'm good with JVM, but C++ feels like a backward step in many regards. > My judgment here may be clouded by reading too many blogpost of them > naysayers. > C++ should be a forward step from a performance/footprint perspective. I'm guessing your backward step is from an ease of devel/debug perspective for core? But say more so the concern is clear. Keep in mind that this would just be C++ for the client *core*. Puppet very much needs to continue to support its existing Ruby API for extensions (e.g. type and providers, custom facts). And yes this implies that the API needs to be *defined* better than it is today (which is undoubtedly going to take some collective rolling up of sleeves). And further, I'd really like to see non-Ruby scripting languages enabled to participate as first-class citizens for the extension points - this (coupled with better definition of core APIs) would really make the on-ramp for new puppet users much lower friction. Kylo -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFHsJEV2iG7CVcjGCBBxK5MotiAcd%2Bvg_2rpXVDjy5Uc9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: facter error message - what does this mean?
On Wed, Oct 1, 2014 at 10:05 AM, Wil Cooley wrote: > On Wed, Oct 1, 2014 at 9:48 AM, jmp242 wrote: > >> I also see this on 3.7.1... Same symptoms. >> > >> On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote: >>> >>> I'm seeing this error appear on a client machine (/var/log/syslog): >>> >>> puppet-agent[17158]: Failed to apply catalog: Could not retrieve local >>> facts: Invalid facter option(s) type >>> >>> If I run 'puppet agent --test' it runs fine. >>> >>> If I run 'puppet agent --test --debug' there is no mention of this error. >>> >>> Yet if I wait until the next scheduled run the error will reappear. >>> >>> >>> What's going on? >>> >> > You've restarted the agent I presume? In the past I've seen errors that > would show up only in the scheduled agent runs but not when running it from > the command line after upgrading Facter. > Or do any of the affected parties have two versions of facter installed? If so the difference between standalone and daemonized agent runs might be about ruby load path. I ask because the "Invalid facter option(s)" message was in the 1.7 series and is gone in 2.x. One of the reports above mentioned that they were running 2.x, but seeing that message, which suggests multiple facter installs. You could get this if, say, you had done a 'gem install facter' and also a package-based install of facter. (Among various scenarios.) Kylo -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFEYZqDStPNvBtKxUjo%3D918XU6aSj3gw7LChcArZn-0BSQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] annoying "allow_virtual parameter" warning
On Tue, Oct 7, 2014 at 7:26 AM, Tim Dunphy wrote:
> Hey guys,
>
> I kept getting this annoying warning in the output of my puppet runs:
>
>
> Warning: The package type's allow_virtual parameter will be changing its
> default value from false to true in a future release. If you do not want to
> allow virtual packages, please explicitly set allow_virtual to false.
> (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
>
>
> So I found this article:
>
> https://inuits.eu/blog/puppet-361-depreciation-warning
>
> That suggesting putting this value in your site.pp for your environment:
>
> Package {
> allow_virtual => true,
> }
>
> Which DOES suppress that annoying output on the majority of the hosts. But
> a few of them have ruby 2.2 installed on some of the newer OSs.
>
> And all the hosts with the newer ruby throw the following error instead of
> performing clean puppet runs like the hosts with the older rubies (1.8.7
> and 1.9.3).
>
What's the 2.2 error?
Also FYI we're doing zero testing with ruby 2.2 at this time.
Kylo
>
> And I notice that I can't get puppet to work on the ruby 2.2 hosts even
> after deleting that allow_virtual override from my site.pp.
>
> So how do I fix the nodes with the newer ruby? Is there any value I can
> set that will make that annoying error message go away, yet allow the
> puppet server to play nicely with all the nodes?
>
> --
Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog
--
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/CALsUZFFHoWCm_pTVu%2BzxXKD9F_boSpFQgVJDsqt7weZaP%3D273A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] annoying "allow_virtual parameter" warning
On Tue, Oct 7, 2014 at 12:31 PM, Tim Dunphy wrote:
> What's the 2.2 error?
>> Also FYI we're doing zero testing with ruby 2.2 at this time.
>
>
>
> Hi Kaylo,
>
> The error that I'm getting is this one:
>
> err: Failed to apply catalog: Invalid parameter allow_virtual at
> /etc/puppet/environments/production/modules/puppet/manifests/install.pp:5
>
> And zero testing with ruby 2.2? Well that's the version that comes with
> the latest version of Mac OS X (Mavericks)
>
Hmm, my OS X 10.9.5 reports:
ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin13]
While I believe ruby 2.2 is still in preview:
https://www.ruby-lang.org/en/news/2014/09/18/ruby-2-2-0-preview1-released/
Kylo
> and Amazon AWS Linux.. Not sure what other flavors of Unix come with this
> by default. But based on that alone maybe it's time? Maybe look into what
> other new distros are on 2.2? I know you guys are busy, but as we all
> know, you can't stop the wheels of time from grinding forward! ;)
>
> Thanks
> Tim
>
>
> On Tue, Oct 7, 2014 at 12:14 PM, Kylo Ginsberg
> wrote:
>
>> On Tue, Oct 7, 2014 at 7:26 AM, Tim Dunphy wrote:
>>
>>> Hey guys,
>>>
>>> I kept getting this annoying warning in the output of my puppet runs:
>>>
>>>
>>> Warning: The package type's allow_virtual parameter will be changing its
>>> default value from false to true in a future release. If you do not want
>>> to
>>> allow virtual packages, please explicitly set allow_virtual to false.
>>> (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
>>>
>>>
>>> So I found this article:
>>>
>>> https://inuits.eu/blog/puppet-361-depreciation-warning
>>>
>>> That suggesting putting this value in your site.pp for your environment:
>>>
>>> Package {
>>> allow_virtual => true,
>>> }
>>>
>>> Which DOES suppress that annoying output on the majority of the hosts.
>>> But a few of them have ruby 2.2 installed on some of the newer OSs.
>>>
>>> And all the hosts with the newer ruby throw the following error instead
>>> of performing clean puppet runs like the hosts with the older rubies (1.8.7
>>> and 1.9.3).
>>>
>>
>> What's the 2.2 error?
>>
>> Also FYI we're doing zero testing with ruby 2.2 at this time.
>>
>> Kylo
>>
>>
>>>
>>> And I notice that I can't get puppet to work on the ruby 2.2 hosts even
>>> after deleting that allow_virtual override from my site.pp.
>>>
>>> So how do I fix the nodes with the newer ruby? Is there any value I can
>>> set that will make that annoying error message go away, yet allow the
>>> puppet server to play nicely with all the nodes?
>>>
>>> --
>> Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog
>>
>> --
>> 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/CALsUZFFHoWCm_pTVu%2BzxXKD9F_boSpFQgVJDsqt7weZaP%3D273A%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-users/CALsUZFFHoWCm_pTVu%2BzxXKD9F_boSpFQgVJDsqt7weZaP%3D273A%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> GPG me!!
>
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>
> --
> 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/CAOZy0ekFX5vHStdxWNjkCGV3wdpaYiLJ375F%2BT3tQ7bF-K0wcQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAOZy0ekFX5vHStdxWNjkCGV3wdpaYiLJ375F%2BT3tQ7bF-K0wcQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog
--
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/CALsUZFEJjZP2_3XqgLUbrgC7KgZdi8e2TFZ2mkV%3Dx%2BVkZ%3DZnqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Debian jessie and puppet packages
Hi John, As you found, the default debian packages lag, so I'd definitely recommend using the puppetlabs packages. Two other things to note: * the package names of interest have changed: you'll want to install 'puppet-agent' and 'puppetserver' (not 'puppet' and 'puppet-master', which it sounds like you may have done) * the package install does *not* update your path, but it puts puppet/facter/hiera/puppetserver/mco in /opt/puppetlabs/bin There are instructions on using the puppetlabs repos here: https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html Hope that helps! Kylo On Mon, Nov 23, 2015 at 10:31 AM, John Gateley wrote: > Hello, > > I'm a complete novice at puppet, trying to set up a couple of debian > systems with puppet on them. > > With a brand new install of Debian 8 (jessie), I have used both the > default packages from Debian, and the packages from puppetlabs (available > after installing the puppetlabs-release-jessie.deb package). > > With both puppet-master and puppet, the "facter rubysitedir" returns a > non-existent directory (/usr/local/lib/site_ruby/2.1.0). I think it should > return /usr/lib/ruby/vendor_ruby/. > > With puppet, the command "puppet resource service" fails with: > > Error: Could not run: Execution of '/bin/systemctl show -pSourcePath > autovt@' returned 1: Failed to get properties: Unit name autovt@.service > is not valid. > > Does Debian 8 support puppet via packages only? Or do I need to install > from source? > > I also set up Debian 7, and that worked, but it was with puppet 2.7.23, > which is quite old (both Puppet 3 and 4 are now available). > > Google search didn't help with this. > > Would I have more luck with Ubuntu? > > Thank you, and my apologies for the novice questions. > > John > > -- > 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/d45b50b6-8d84-4ade-8ee0-4b1f59418336%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/d45b50b6-8d84-4ade-8ee0-4b1f59418336%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFEe_BjHeJcYzfBGkDgWf7SWpqVMAwdTnFcG4L1-JiJwyA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet 4 : questions about PXP agent and its goal
On Wed, Jan 6, 2016 at 4:15 PM, Francois Lafont < francois.lafont.1...@gmail.com> wrote: > Hi, > > On 04/01/2016 20:44, Ryan Coleman wrote: > > > Hello and happy new year to you as well, > > Thanks, ;) > > > In my CentOS 7 install of puppet-agent 1.3.2, the pxp-agent service is > not > > enabled or started by default. > > Ok. I have noticed that in Debian Jessie too. > But in Ubuntu Trusty, the pxp-agent daemon seems enabled by default. > Hmm, pretty sure that inconsistency was unintentional. I filed https://tickets.puppetlabs.com/browse/PA-141 to track that. Kylo > > > You can safely disable it without impacting the operations of Puppet. > > Ok. I'm going to do that in this case (I have several Trusty servers). > > > As you noticed, there's no listening service for pxp-agent. Think of it > > more like a modern puppet-kick than a replacement for MCollective. In > > Puppet Enterprise 2015.3, it's configured to connect to its broker and > wait > > for instructions like start a puppet run or inspect the state of the last > > run. It's capable of doing more than this but that's its purpose today; a > > light-weight way for puppet-server infrastructure to have more direct > > control of when an agent enforces new configuration without changing how > > the puppet-agent operates. We use this for the new orchestration service > > and web console run puppet controls in PE. It will coexist with > MCollective > > until (and if) there's a compelling reason for them to converge. For > > example, we don't provide extension APIs for PXP like you get with > > MCollective. It's intended only for programmatic control of the > > puppet-agent, today. > > Ok I see. > > > The broker [1], agent [2] and client libraries [3] are open-source for > > those not running PE but I'm not aware of anything using it beyond PE > (yet). > > > > [1] https://github.com/puppetlabs/pcp-broker > > [2] https://github.com/puppetlabs/pxp-agent > > [3] https://github.com/puppetlabs/cpp-pcp-client > https://github.com/puppetlabs/clj-pcp-client > https://github.com/puppetlabs/ruby-pcp-client > > Ok, that's clear for me now. Thanks for all these explanations. ;) > Regards. > > François Lafont > > -- > 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/568DAE23.6090507%40gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFHyC89Z9P8etBzrC66X43fM45Gf-0u8KrLoxvKsn3cG0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Facter 2.4.5 Available
On Mon, Jan 25, 2016 at 8:35 AM, robbyt wrote: > On Friday, January 22, 2016 at 1:27:33 PM UTC-5, Hailee Kenney wrote: >> >> Facter 2.4.5 is a backwards-compatible bug-fix release in the Facter 2 >> series. >> >> This release includes minor bug fixes to several different facts. >> >> To download Facter, follow the instructions here: >> http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html >> >> Release notes are available here: >> https://docs.puppetlabs.com/facter/2.4/release_notes.html#facter-245 >> A complete list of issues fixed in the release is available here: >> https://tickets.puppetlabs.com/browse/FACT-380?filter=17113 >> We're tracking bugs with an "Affected Version" of "2.4.5" here: >> https://tickets.puppetlabs.com/browse/FACT-1316?filter=17114 >> > > To add a bit more constructive conversation around this release of > Facter... > > Changing the behavior for a very common and important fact (non-backwards > compatible) in a minor point release seems a bit strange to me. The > behavior of the ipaddress fact has been essentially the same for many > years, and many users might not expect this behavior to change in a minor > release marked as a "bugfix". > Thanks for your comments. For context, FACT-380 was a long-standing bug report, which has gotten more requests as container infra has gotten more common, so we thought we could do a Good Thing by fixing it in the 2.x series (it's already addressed in the 3.x series). But that fix has clearly broken too may workflows depending on the previous behavior. So we've decided to revert the fix for FACT-380 and release 2.4.6 with that change. Look for that release tomorrow, Jan 26. Thanks for your patience. Kylo > -- > 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/b1f93510-6618-4cf1-9865-bfd86b8efaea%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/b1f93510-6618-4cf1-9865-bfd86b8efaea%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFFNV2E4933kZ4xSty3iG%3DmPj3%2Br%2BtcDR%3D_M3B_GwiVGzA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet 3.8.5 available
On Thu, Feb 11, 2016 at 8:02 AM, Christopher Wood < christopher_w...@pobox.com> wrote: > For idle interest's sake, I calculated the catalog compilation times > across our puppetmasters on Thursday January 28th with (open source) 3.8.4 > and did the same thing just now for Thursday February 4th with (open > source) 3.8.5. > > Average catalog compilation times improved from 23.59 s to 20.44 s, or > approximately 13% improvement. > \o/ We're giving more and more attention to performance improvements, so glad to get data-driven feedback like this. Thanks! Kylo > > On Wed, Jan 27, 2016 at 02:58:29PM -0800, Eric Sorenson wrote: > >Puppet 3.8.5 is now available. This is a bugfix release that contains > >performance improvements to catalog compilation and Mac OS X service > >management, along with fixes for Windows agents and the Puppet 4 > language > >parser. See the full release notes here: > >http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html > >For installation and upgrade instructions, see this doc: > >http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html > >A special community shout-out for this release to Github user > 'earsdown' > >for the PR to fix PUP-5212, which added HTTP proxy support to the PIP > >package provider. > >Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: > eric0 > >puppet platform // coffee // techno // bicycles > > > >-- > >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 [1]puppet-users+unsubscr...@googlegroups.com. > >To view this discussion on the web visit > >[2] > https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com > . > >For more options, visit [3]https://groups.google.com/d/optout. > > > > References > > > >Visible links > >1. mailto:puppet-users+unsubscr...@googlegroups.com > >2. > https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com?utm_medium=email&utm_source=footer > >3. https://groups.google.com/d/optout > > -- > 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/20160211160222.GA20645%40iniquitous.heresiarch.ca > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFFewEebnPXbjezHhbwJpyxsSv7_HOba-W9XZ_MmMg6LpQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Simple question about recent Puppet versions
On Thu, Feb 11, 2016 at 1:04 PM, David Karr wrote: > I know very little about Puppet, as I'm just starting to examine it. > > I had a couple of very high level questions about versions. > > As soon as I entered this group, I noticed the announcement about Puppet > 3.8.5 being released, and the docs pointer for that goes to the Puppet web > site, showing version 3.8. When I go to the latest docs on the Puppet web > site, it shows version 4.3. > > I thought perhaps this indicates that there are parallel release trains, > being at least 3.x and 4.x, but I casually searched in this group for > announcements that seemed to be in the version 4.x range, and I didn't see > anything. > > I also noticed that very recent books on Puppet are talking about version > 4. > > Can someone explain the versions landscape? I do understand that the > commercial version has a different versioning scheme. At this point, I'm > just concerned about the versioning of the open source project(s). > You are correct - there are two parallel release trains, one for 3.x and one for 4.x. In the 4.x train, puppet is released as the anchor of an all-in-one package including puppet and lots of other related components (ruby, openssl, facter, hiera, etc). That all-in-one package is called puppet-agent and you will see announcements in this group for puppet-agent, e.g. most recently the announcement for puppet-agent 1.3.5. [1] Note that in a agent-master setup you'd also want to grab a puppet server package. The most recent announcement there is for puppetserver 2.2.1. [2] [1] https://groups.google.com/forum/#!topic/puppet-users/2ewaLZYZ94c [2] https://groups.google.com/forum/#!topic/puppet-users/HNdZYddYvRY > -- > 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/e289f2bc-edc8-414c-9108-4797b7576e14%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/e289f2bc-edc8-414c-9108-4797b7576e14%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFF5%3DUhSz_QnoQs0Hcc7sHoMpceBWFjAKUhDdkC%3Dcjbv0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Simple question about recent Puppet versions
On Fri, Feb 12, 2016 at 1:56 PM, David Karr wrote: > On Thursday, February 11, 2016 at 2:28:04 PM UTC-8, Kylo Ginsberg wrote: >> >> On Thu, Feb 11, 2016 at 1:04 PM, David Karr >> wrote: >> >>> I know very little about Puppet, as I'm just starting to examine it. >>> >>> I had a couple of very high level questions about versions. >>> >>> As soon as I entered this group, I noticed the announcement about Puppet >>> 3.8.5 being released, and the docs pointer for that goes to the Puppet web >>> site, showing version 3.8. When I go to the latest docs on the Puppet web >>> site, it shows version 4.3. >>> >>> I thought perhaps this indicates that there are parallel release trains, >>> being at least 3.x and 4.x, but I casually searched in this group for >>> announcements that seemed to be in the version 4.x range, and I didn't see >>> anything. >>> >>> I also noticed that very recent books on Puppet are talking about >>> version 4. >>> >>> Can someone explain the versions landscape? I do understand that the >>> commercial version has a different versioning scheme. At this point, I'm >>> just concerned about the versioning of the open source project(s). >>> >> >> You are correct - there are two parallel release trains, one for 3.x and >> one for 4.x. In the 4.x train, puppet is released as the anchor of an >> all-in-one package including puppet and lots of other related components >> (ruby, openssl, facter, hiera, etc). That all-in-one package is called >> puppet-agent and you will see announcements in this group for puppet-agent, >> e.g. most recently the announcement for puppet-agent 1.3.5. [1] >> > > So you're telling me that "Puppet 4" is actually "puppet-agent", the > latest version of which is 1.3.5? > More like: the puppet-agent package installs puppet (plus additional batteries useful when running puppet), and wrt specific versions, puppet-agent 1.x contains puppet 4.x. For a more complete listing of all the batteries included in puppet-agent, and all the versions of those batteries: https://docs.puppetlabs.com/puppet/latest/reference/about_agent.html > So there won't be any release announcements for "Puppet 4", just for > "puppet-agent"? > Correct. > > >> >> Note that in a agent-master setup you'd also want to grab a puppet server >> package. The most recent announcement there is for puppetserver 2.2.1. [2] >> >> [1] https://groups.google.com/forum/#!topic/puppet-users/2ewaLZYZ94c >> [2] https://groups.google.com/forum/#!topic/puppet-users/HNdZYddYvRY >> >> >>> -- >>> 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...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/e289f2bc-edc8-414c-9108-4797b7576e14%40googlegroups.com >>> <https://groups.google.com/d/msgid/puppet-users/e289f2bc-edc8-414c-9108-4797b7576e14%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Kylo Ginsberg | ky...@puppetlabs.com | irc: kylo | twitter: @kylog >> >> -- > 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/ef1508b2-4e12-4513-a4d9-916b4c760154%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/ef1508b2-4e12-4513-a4d9-916b4c760154%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFGmGAH_O%2Bani1k9GUpcDqnL9CdQt%2B-Xywr0h1fhgMZsUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Force Fact within manifest
without Puppet at all, just via Facter), seems like > something that could be made better. > > Right now, (especially since postrun_command is broke in windows) I run a > quick powershell script in its own new session that calls puppet upload > facts, or a nohup in the background (if nix), after every puppet run. This > keeps it in its own environment and outside of puppets ruby process and env > vars. I then use a ENC script to pull in the latest facts and push them to > reporting. If I need to see the facts prior to Puppets run, I can also > view those, as I store them on the master as well. Best of both worlds; > latest correct and latest prior to puppet. Or if need be, we can even go > back 2 weeks and see every fact for each time puppet was ran. > > Thanks for your input and its always good to hear others reasonings and > opinions. > FYI this same suggestion came up recently in https://tickets.puppetlabs.com/browse/PUP-5934 (and I've linked this thread there). This strikes me as an ecosystem concern: i.e. I'm not convinced offhand we'd want to address the base use cases here by submitting facts with the report, because I wouldn't want to lose the current fact-set-to-catalog linkage in puppetdb. So I think we'd want to consider how this would be supported in puppetdb if/as we consider something like this. Also, in the spirit of linking related conversations: this idea may also dovetail with a current thread on puppet-dev: https://groups.google.com/d/msg/puppet-dev/bebmBUyRETg/v0VFTogWCgAJ. Specifically, one idea there is to specify fact ttl's, which might in turn impact fact submission times and fact storage schema, etc. Kylo > > > > > -- > 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/d36b749c-7717-49e2-a057-8faccafb2dc5%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/d36b749c-7717-49e2-a057-8faccafb2dc5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFGiOoH2gjqaCzE-5pzO97%2BqJ3%2BYvz1SFpakySn8icsbKQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet 3.8.5 available
On Mon, Apr 4, 2016 at 10:42 AM, Christopher Wood < christopher_w...@pobox.com> wrote: > (Pardon the necro, I felt these interesting results should be filed with > the other ones.) > Thanks for the necro actually. It's much appreciated to see the real-world improvements. And ~20s to ~6s is a very nice improvement! Kylo > > On Thu, Feb 11, 2016 at 08:50:32AM -0800, Kylo Ginsberg wrote: > >On Thu, Feb 11, 2016 at 8:02 AM, Christopher Wood > ><[1]christopher_w...@pobox.com> wrote: > > > > For idle interest's sake, I calculated the catalog compilation times > > across our puppetmasters on Thursday January 28th with (open source) > > 3.8.4 and did the same thing just now for Thursday February 4th with > > (open source) 3.8.5. > > > > Average catalog compilation times improved from 23.59 s to 20.44 s, > or > > approximately 13% improvement. > > > >\o/ > >We're giving more and more attention to performance improvements, so > glad > >to get data-driven feedback like this. Thanks! > >Kylo > > The above was all apache/passenger. > > After another upgrade the puppetmasters here have been running these since > Wednesday March 30th: > > [root@puppetmaster4 ~]# rpm -q puppetserver > puppetserver-2.2.1-1.el6.noarch > [root@puppetmaster4 ~]# rpm -q puppet-agent > puppet-agent-1.3.6-1.el6.x86_64 > > On Thursday March 31st catalog compilation times averaged 5.93 s across > all production puppetmasters. > > > > > On Wed, Jan 27, 2016 at 02:58:29PM -0800, Eric Sorenson wrote: > > >Puppet 3.8.5 is now available. This is a bugfix release that > > contains > > >performance improvements to catalog compilation and Mac OS X > > service > > >management, along with fixes for Windows agents and the Puppet > 4 > > language > > >parser. See the full release notes here: > > > > > [2] > http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html > > >For installation and upgrade instructions, see this doc: > > >[3] > http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html > > >A special community shout-out for this release to Github user > > 'earsdown' > > >for the PR to fix PUP-5212, which added HTTP proxy support to > the > > PIP > > >package provider. > > >Eric Sorenson - [4]eric.soren...@puppetlabs.com - freenode > #puppet: > > eric0 > > >puppet platform // coffee // techno // bicycles > > > > > >-- > > >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 [1][5]puppet-users+unsubscr...@googlegroups.com. > > >To view this discussion on the web visit > > > > > [2][6] > https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com > . > > >For more options, visit [3][7] > https://groups.google.com/d/optout. > > > > > > References > > > > > >Visible links > > >1. mailto:[8]puppet-users+unsubscr...@googlegroups.com > > >2. > > [9] > https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com?utm_medium=email&utm_source=footer > > >3. [10]https://groups.google.com/d/optout > > -- > > 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 [11]puppet-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > [12] > https://groups.google.com/d/msgid/puppet-users/20160211160222.GA20645%40iniquitous.heresiarch.ca > . > > For more options, visit [13]https://groups.google.com/d/optout. > > > >-- > >Kylo Ginsberg | [14]k...@puppetlabs.com | irc: kylo | twitter: @kylog > > > >-- > >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
[Puppet Users] Puppet now has a Community Slack
Hey folks, Just a quick note that Puppet now has a Community Slack! More details at: https://puppet.com/blog/welcome-to-puppet-community-slack See you there! Kylo -- Kylo Ginsberg | k...@puppet.com | irc: kylo | twitter: @kylog PuppetConf 2016 <http://2016.puppetconf.com/>, October 17-21, San Diego, California *Early Birds save $350* <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> - Register by June 30th -- 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/CALsUZFFXmRCBu%2Bbp0-rJj75n_CPW3y8K9DdjqdqftTfVOdNfHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Docs Typo (I think)
On Wed, Jun 22, 2016 at 6:53 AM, Dan White wrote: > <https://docs.puppet.com/puppet/4.5/reference/config_file_main.html> > > https://docs.puppet.com/puppet/4.5/reference/config_file_main.html#example-master-config > > Example master config > <https://docs.puppet.com/puppet/4.5/reference/config_file_main.html#example-master-config> > > [main] > certname = puppetmaster01.example.com > server = puppet > environment = production > runinterval = 1h > strict_variables = truetrusted > > [master] > dns_alt_names = > puppetmaster01,puppetmaster01.example.com,puppet,puppet.example.com > reports = puppetdb > storeconfigs_backend = puppetdb > storeconfigs = true > environment_timeout = unlimited > > What's with that "trusted" under [main] ? > Caused an error when I copied it and there is no reference to such a config > setting in the docs. > > That does look wrong. Thanks for pointing that out! Do you mind filing a quick ticket at https://tickets.puppetlabs.com/browse/DOCUMENT? Thanks, Kylo > > > Dan White | d_e_wh...@icloud.com > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” (Bill Waterson: > Calvin & Hobbes) > > -- > 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/40413bad-a1bc-49a4-b9bd-78fa22c3270d%40me.com > <https://groups.google.com/d/msgid/puppet-users/40413bad-a1bc-49a4-b9bd-78fa22c3270d%40me.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppet.com | irc: kylo | twitter: @kylog PuppetConf 2016 <http://2016.puppetconf.com/>, October 17-21, San Diego, California *Early Birds save $350* <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> - Register by June 30th -- 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/CALsUZFFSs1UDakcUvJrs0MAPGHqoKD8z8H4d%2BYRfuM%2BBKAjsGA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] facter compatibility and nest facts info
On Mon, Oct 17, 2016 at 1:09 PM, Jakov Sosic wrote: > On 10/17/2016 07:52 PM, rakare2...@gmail.com wrote: > >> Hi, >> >> Is there any issues with facter 2.4.6 + puppet 3.6.2 for writing >> manifest files? since facter 2.4.6 has nested facts. At present I have >> facter 2.1.0 + puppet 3.6.2. I am planning to upgrade facter with 2.4.6. >> So before that I just want to confirm if there is any compatibility issues >> > No known compatibility issues, but of course read the release notes, and test before deploying :) > >> Also in facter 2.4.6 if i want to get os family how can i do that? since >> its nested kind of format I tried 'facter os.family' which returns blank >> value >> > > > [jsosic] % facter os.family > RedHat > > [jsosic] % facter --version > 3.4.1 (commit d0f32490f41ca12722c13e4c48d4572ae4f9bfdc) > > > Seems to be working in newer versions... The dotted syntax for structured facts on the command line was introduced in facter 3 so, yes, it wouldn't work with 2.4.6. However, with either facter 2 or facter 3 you can access structured facts from puppet code with something like: $facts["os"]["family"] Also, wrt this specific fact, it's worth noting that both facter 2 and facter 3 retain the (non-structured) fact called 'osfamily'. Kylo > > > -- > 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/ms > gid/puppet-users/712fb6e3-5286-7012-423c-9f628ddf8615%40gmail.com. > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppet.com | irc: kylo | twitter: @kylog -- 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/CALsUZFGAJ8_iYgctiB5A-7ytmFeC0FcXRKWG%3DNh3r32tWr8Lcw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Using gem from new puppetserver custom function?
On Wed, Oct 15, 2014 at 11:50 AM, Schofield wrote: > I am testing out the new puppetserver > <https://github.com/puppetlabs/puppet-server/blob/master/documentation/install_from_packages.markdown>and > finding a problem with referencing a gem installed to the local ruby. > > A custom function is installed to > /usr/lib/ruby/site_ruby/1.8/pupppet/parser/functions/myfunction.rb. It > makes use of the mysql2 gem > > module Puppet::Parser::Functions > newfunction(:myfunction, :type => :rvalue) do |args| > require 'mysql2' > ... > end > > The mysql2 gem is installed to > /usr/lib/ruby/gems/1.8/gems/mysql2-0.3.16/lib/mysql2.rb. > > When doing a puppet run on a managed node we get the following error. > > Error: Could not retrieve catalog from remote server: Error 400 on > SERVER: no such file to load -- mysql2 > > My question is: How make a gem visible to the new puppetserver so it can > be used by a custom function? > Have you done the steps described here: https://github.com/puppetlabs/puppet-server/blob/master/documentation/gems.markdown Best, Kylo -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFGuP0rNe%2B5DR%2B%3DirF8V-UzhG%3DToo6tUNfcSP9CeRUhzjQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Client-side tech stack
[I am forking from the thread announcing Puppet Server 0.2.0, for which this was OT.] Sorry for the delayed response on this - hard to keep up with email at times :) On Fri, Oct 10, 2014 at 4:55 PM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > On 10/03/2014 03:50 PM, jcbollinger wrote: > > > I feel compelled to point out that if the "faster language" happens to be > C++, then you will *need* a plug-in interface in some different language > (presumably Ruby, but straight C would be more typical). C++ APIs are > sensitive to compiler and compile options used, and they provide > essentially no compile-time encapsulation of API classes' private members, > so it would not be wise to suppose that you will ever be able to directly > support unwrapped, third-party, C++ plugins. Especially with the current > fast pace of Puppet development. > > Absolutely correct. C++11 is an *implementation* choice, but not an *interface* choice, for the reasons you've given. For cfacter (at least initially) the tldr on plugin support is two-fold: * for custom facts, we dynamically load the ruby library (if not already loaded) and implement the facter API used by custom facts * implement external facts The non-tldr version is at https://github.com/puppetlabs/cfacter/blob/master/Extensibility.md and also discusses some future ideas for getting external facts on a par with custom facts (e.g. providing built-in facts as a json blob on stdin). We definitely could implement a C interface for adding facts as well. There were one or two questions about that at PuppetConf. I'd be curious to know how much demand there is for that approach. Thinking about the extension points for the agent, notably providers, we may be able to follow a similar-ish model there of: * dynamically load ruby and implement the provider api (tricky b/c the api needs improved definition/hardening) * introduce a concept of external providers * maybe add a C API here as well? Feedback or ideas in this space would be great! > > I somehow just realized yesterday that CFacter is a thing already. So I > guess we're already somewhere down this road. > > Just cloned the repo - doesn't seem to build on Debian sid with Ruby > 2.1.0. Will likely take some fiddling. > Of the debians, I haven't tried sid, though we are building it on wheezy (packages coming in the next week or two, so stay tuned). FYI the build doesn't depend on ruby-devel packages (the MRI embedding relies on the relevant bits of the Ruby C API being stable, which it generally has been). If you have build issues on sid (or anywhere for that matter), just ping on irc/email/etc; I'm sure people can sort it out. And these are early days for this tech stack, so it would be nice to surface oddities or friction points early. Best, Kylo -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFGi6-6YT2UO9ETGX_70-L8YfA%3D%2Bad4mFEaS140N58mfJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet agent message: Could not retrieve local facts: Could not find fact 'define_fact'
On Fri, Oct 24, 2014 at 5:43 AM, Andreas Dvorak wrote: > After downgrade facter to 1.7.1 the error is gone. > Then I did the update again and the error was back again. > Can you double-check that this server doesn't have multiple versions of facter installed? E.g. this can happen with one installed from packages and one from gem, etc. Kylo > > I have many server that already have the version 2.1, without an update. > > I don't understand why the update does not work. > > -- > 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/e6383291-1fee-4fe1-abf0-73f9e627e737%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/e6383291-1fee-4fe1-abf0-73f9e627e737%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com. *Register early to save 40%!* -- 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/CALsUZFHevpNuZ95qn3nkBjaFCmWu5Ux4P25znmGat96g%2BoQf7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] master - error(s) on fresh installation (EC2)
On Fri, Nov 14, 2014 at 4:27 AM, JonY wrote: > AMI? I'm new to this world. > There are AMIs for many different OSs/distros. What does 'facter operatingsystem' report? Thanks Kylo > > > On Thursday, November 13, 2014 2:42:31 PM UTC-8, Felix.Frank wrote: >> >> On 11/13/2014 08:00 PM, JonY wrote: >> > Installed latest from puppetlabs repro on an EC2 instance. >> >> ...running...which platform? >> > -- > 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/fbf34adc-e317-415d-a3aa-01e11957ec57%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/fbf34adc-e317-415d-a3aa-01e11957ec57%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com. *Register early to save 40%!* -- 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/CALsUZFGWMyYvmZ7iZa5_3nDTPL8nFCZ-PwPuyB-%2BQQ5Fqjj6Aw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] master - error(s) on fresh installation (EC2)
On Fri, Nov 14, 2014 at 6:03 AM, Kylo Ginsberg wrote: > On Fri, Nov 14, 2014 at 4:27 AM, JonY wrote: > >> AMI? I'm new to this world. >> > > There are AMIs for many different OSs/distros. > > What does 'facter operatingsystem' report? > > Thanks > Kylo > > >> >> >> On Thursday, November 13, 2014 2:42:31 PM UTC-8, Felix.Frank wrote: >>> >>> On 11/13/2014 08:00 PM, JonY wrote: >>> > Installed latest from puppetlabs repro on an EC2 instance. >>> >>> ...running...which platform? >>> >> One guess, which I put in https://tickets.puppetlabs.com/browse/PUP-3672 as well, is that this is on Amazon Linux, for which we don't currently have packages. Kylo > -- >> 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/fbf34adc-e317-415d-a3aa-01e11957ec57%40googlegroups.com >> <https://groups.google.com/d/msgid/puppet-users/fbf34adc-e317-415d-a3aa-01e11957ec57%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog > > *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * > http://2015.puppetconf.com. > *Register early to save 40%!* > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com. *Register early to save 40%!* -- 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/CALsUZFFj0jneOmv0t5ODbPTtYMDK9%3DDjKHhgKa6EK59099yPVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How about an AMI?
On Sun, Nov 16, 2014 at 6:07 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > On 11/16/2014 01:25 PM, JonY wrote: > > Since p-server 3.7 doesn't appear to work on the AWS linux AMI how > > about creating an AMI that does work? > > Such as "the official Puppet Linux"? > > I don't think that I'd care for that. After all, Puppet aims at > supporting a large range of platforms, not imposing its own standard. > > The whole concept of specialized AMIs seems to be at least a bit > controversial: https://www.exratione.com/2014/08/do-not-use-amazon-linux/ > > You should be able to use Ubuntu (or CentOS?) on AWS. Puppet should Just > Work on those. > Yep. Keep in mind that there are AMIs for numerous distros: https://aws.amazon.com/marketplace/b/2649367011/ref=gtw_navlft_node_2649367011?page=1&category=2649367011 You happened to try an AMI with the Amazon Linux distro first, for which Puppet Labs doesn't provide packages currently. But if you choose an AMI for one of the distros we *do* have packages for, it should indeed Just Work. I do it all the time. (And yes, CentOS would fit the bill.) Hope this helps! Kylo > Cheers, > Felix > > -- > 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/5468AF9A.5020303%40Alumni.TU-Berlin.de > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - * http://2015.puppetconf.com. *Register early to save 40%!* -- 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/CALsUZFGMxF9eSvv5Jq%2B3hEke5x5jGYXFWjHLD3sKRHDNDaxdqA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Native Facter (cfacter) 0.3.0 is available!
On Wed, Feb 4, 2015 at 3:07 PM, Melissa Stone wrote: > On Tue, Feb 3, 2015 at 5:37 AM, Paul Seymour wrote: > >> >> >>> Thanks for this. Just put the RHEL7 x86_64 on a puppet client and it >>> complains:- >>> >> >> "Error: Could not initialize global default settings: cfacter version >> 0.2.0 or later is not installed." >> >> Tracing it through it is looking for the libraries in /usr/lib64 and they >> are installed via the RPM in /usr/lib this doesn't happen when running via >> the command line so maybe something with my environment. >> > > Could you give us a little more information about how you're running > cfacter? It sounds like puppet isn't playing with cfacter as well as it > should, but I'd like to confirm that. Can you also let us know what version > of the puppet you're running? > I repro'd this with puppet 3.7.4: standalone cfacter itself works fine, but "puppet --cfacter" doesn't. Two things to workaround this: 1) gem install ffi 2) libfacter.so* should be in /usr/lib64 rather than /usr/lib Kylo -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFEHnkM0ReJnjRCZWfmi8ZFjQzzWSpxTi8RrygGTfrCQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Hiera 2.0.0 available
Hiera 2.0.0 is a new major version that includes several new features that expand Hiera's abilities. It also includes one breaking change so please read the release notes linked below. New features include the ability to pass options to the deep merge gem, new sub-keys to allow lookups to index into data structures, and an `alias()` function to make a key an alias for another key. It also includes a fix for interpolation recursion loops and several other bugs. Release notes are available here: http://docs.puppetlabs.com/hiera/latest/release_notes.html To see a complete list of issues fixed in this release: https://tickets.puppetlabs.com/issues/?filter=13825 We're tracking bugs people find in this release with the "Affected Version" field set to "HI 2.0.0": https://tickets.puppetlabs.com/issues/?filter=13824 -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> * *—**save $349!* -- 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/CALsUZFGpG2RL0tSSqqduZPdVuDXnY3ZbQ%3De6T1W%2BCfoj6AVBCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet 4 available!
On Thu, Apr 16, 2015 at 6:04 AM, Dennis Hoppe < dennis.ho...@debian-solutions.de> wrote: > Hello Eric, > > what happened to the packages for Debian testing? The release of Debian > Jessie is scheduled for 2015-04-25. > We had Jessie in our build pipeline a few weeks ago, but there was some churn in Debian testing packages that caused our builds to fail several nights in a row (sorry, don't remember the details), and we decided to hold off until it was actually released. It should be very straightforward to add back in once it's released. Cheers, Kylo > > Kind regards, Dennis > > On 15 Apr 2015, at 20:40, Eric Sorenson > wrote: > > I'm super excited to announce the availability of Puppet 4. It's the first > major version of Puppet in almost 2 years, and there are a ton of great > changes and improvements. Stephanie Stouck wrote a post that summarizes the > release: > > https://puppetlabs.com/blog/say-hello-open-source-puppet-4 > > Read the release notes and install/upgrade guides carefully, especially if > you haven't been tracking the Release Candidates: > > http://docs.puppetlabs.com/puppet/4.0/reference/index.html > > Also of note is that the repositories have changed in order to keep > incompatible changes from auto-updating onto your systems. Read more about > "Puppet Collections", our name for these Linux-distribution-like groups of > packages, in Mike Stahnke's blog post: > > https://puppetlabs.com/blog/welcome-puppet-collections > > Please give it a try! If you file bugs, please make sure to flag them with > an "Affects Version" of "PUP 4.0.0". > You can see the bugs currently open against the release here: > https://tickets.puppetlabs.com/issues/?filter=14021 > > Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 > puppet platform // coffee // techno // bicycles > > > Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 > puppet platform // coffee // techno // bicycles > > > -- > 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/196E9F51-5EDF-4057-9479-9D1256F94003%40puppetlabs.com > <https://groups.google.com/d/msgid/puppet-users/196E9F51-5EDF-4057-9479-9D1256F94003%40puppetlabs.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > 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/3AA8B464-0159-429E-B935-C77B9EA89150%40debian-solutions.de > <https://groups.google.com/d/msgid/puppet-users/3AA8B464-0159-429E-B935-C77B9EA89150%40debian-solutions.de?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> * *—**save $349!* -- 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/CALsUZFE5FtrD4LTxv6HL4DRuDNue3ZkSidE9L8K2OQq-oyLj2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How to deploy Puppet 4 (compared to Puppet 3 from a gem)
On Fri, Apr 17, 2015 at 3:12 PM, Ken Bowley wrote: > Puppet 4 needs a lot of new directories in order to even attempt to run. > It would be nice if puppet had a way to create the directory structure that > it needs in order to run. > Hi Ken, I've just filed https://tickets.puppetlabs.com/browse/PUP-4436, which I think is the issue you're seeing. If that doesn't describe the problem, let's dig in some more. > > For now I'm trying to ignore the seemingly non-existent upgrade path from > puppet 3 to puppet 4 that doesn't involve firing up a new puppet 4 server > to run alongside the puppet 3 server. > Yep, that's the only upgrade path at the moment but upcoming releases aim to make the 3 -> 4 upgrade smoother. Stay tuned! Thanks, Kylo > > On Friday, April 17, 2015 at 3:04:51 PM UTC-7, Tim Skirvin wrote: >> >> Ken Bowley writes: >> >> > We've been using Puppet since the 0.24 days, and it's always been >> fairly >> > simple to add in a new system. >> >> > Do a base install (Linux or Mac OS X) >> > Install Ruby if Linux >> > gem install puppet >> > run puppet >> > sign the cert on the puppetmaster >> > let puppet take care of everything else. >> >> [...] >> >> > This workflow no longer works with Puppet 4. >> >> I haven't investigated any of this yet; what doesn't work? >> >> - Tim Skirvin (tski...@fnal.gov) >> -- >> HPC Systems Administrator / Developer >> http://www.linkedin.com/in/tskirvin >> Fermilab - USCMS-T1 CollaborationExperiment Computing >> Facilities >> > -- > 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/bd5ade5e-169f-4d30-be91-b3fc6152bff9%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/bd5ade5e-169f-4d30-be91-b3fc6152bff9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> * *—**save $349!* -- 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/CALsUZFFvoG5%2BJghNib79wCNwVv748tJUeWJEjhVU5VRnZmmKQg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Why doesn't my install_options get picked by my package resource?
On Wed, Apr 22, 2015 at 4:44 PM, Russell Cecala
wrote:
> Here is what I am doing ...
>
> [root@mgmt-el7-002 ~]# puppet -V
>
> 3.6.2 (Puppet Enterprise 3.3.2)
>
> [root@mgmt-el7-002 ~]# cat kernel_upgrade.pp
>
> package {'kernel-3.10.0-123.20.1.el7':
>
> ensure => present,
>
> allow_virtual => false,
>
> install_options => [ { '--enablerepo' =>
> 'Redhat_7_Updates'} ],
>
> }
>
>
> [root@mgmt-el7-002 ~]# puppet apply kernel_upgrade.pp
>
> ... and here is the error I am getting ...
>
> Notice: Compiled catalog for mgmt-el7-002 in environment
> production in 0.38 seconds
>
> Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list
> kernel-3.10.0-123.20.1.el7' returned 1: Error: No matching Packages to list
>
> Error:
> /Stage[main]/Main/Package[kernel-3.10.0-123.20.1.el7]/ensure: change from
> absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list
> kernel-3.10.0-123.20.1.el7' returned 1: Error: No matching Packages to list
>
> Notice: Finished catalog run in 1.89 seconds
>
I think you may be running into
https://tickets.puppetlabs.com/browse/PUP-2971, which is fixed in puppet
3.7.
Hth,
Kylo
> [root@mgmt-el7-002 ~]# yum --enablerepo=Redhat_7_Updates list
> kernel-3.10.0-123.20.1.el7
>
> Loaded plugins: fastestmirror, priorities, product-id,
> subscription-manager
>
> This system is not registered to Red Hat Subscription Management.
> You can use subscription-manager to register.
>
> Loading mirror speeds from cached hostfile
>
> * Openstack-Juno-Repo: wwwin-kickstart-sj.example.com
>
> * example-linux-common: wwwin-kickstart-dev.example.com
>
> * example-linux-server: wwwin-kickstart-dev.example.com
>
> 91 packages excluded due to repository priority protections
>
> Available Packages
>
> kernel.x86_64 3.10.0-123.20.1.el7
> Redhat_7_Updates
>
> I am kinda of confused as to how to enable a yum repo in my package
> resource.
>
>
> Thanks!
>
> --
> 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/CAHu%2B3Oz5%2BGz_iF%2BY88MvwJDjNXoUafxP6K7KV65bh4VEb0Qh2w%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAHu%2B3Oz5%2BGz_iF%2BY88MvwJDjNXoUafxP6K7KV65bh4VEb0Qh2w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog
*PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland,
Oregon! Join us October 5-9.*
*Register now to take advantage of the Early Adopter discount
<https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter>
*
*—**save $349!*
--
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/CALsUZFG1fcTNLUe%2B%2B7Pq%3DE%2Bf6sfCQjVN7UP1J%2BjOKL9wKKqZ2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Announce: Puppet 3.8.1 available
Puppet 3.8.1 is a bug fix release (with future parser changes) in the Puppet 3.8 series. It’s first official open source release in the 3.8 series. The main focus of this release is to make sure the 3.8 future parser is forward-compatible with the Puppet language as of Puppet 4.1. It also fixes several bugs. Check out the release notes for more information: https://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html#puppet-381 You can see the full list of changes on the release's JIRA page: https://tickets.puppetlabs.com/secure/ReleaseNote.jspa?version=13116&styleName=&projectId=10102 If you're installing Puppet for the first time, follow the Installation Guide: https://docs.puppetlabs.com/guides/install_puppet/pre_install.html -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> * *—**save $349!* -- 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/CALsUZFHNOBN-W7rzHxat2vdVVPW5Ed1szVNXsEZHc6ytfeiUSA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Announce: Puppet 3.8.1 available
On Tue, May 26, 2015 at 10:53 PM, Poil wrote: > Hi, > > PUP-1208 is not included :( ? > Fixed in puppet 4! Best, Kylo -- 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/CALsUZFFun_LGayXcRpSqF8z4Zj%2BzCSqd62Kpe3WX7icX5-CG0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Puppet 3.8.1 available
On Wed, Jun 3, 2015 at 2:19 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2015-03-06 19:32, Stefan Lasiewski wrote: > >> Kylo, >> >> Can you make sure this information is added >> to http://docs.puppetlabs.com/release_notes/#current-releases ? That >> page still says that 3.7 and PE 3.7 are the current releases, which is a >> bit confusing when Yum is telling me otherwise. >> >> > It shows 3.8 and 4.1 as current releases now. > Yep, we fixed it. Thanks for the ping on that, Stefan!! Kylo > > - henrik > > Thanks, >> >> -= Stefan >> >> On Tuesday, May 26, 2015 at 4:44:58 PM UTC-7, Kylo Ginsberg wrote: >> >> Puppet 3.8.1 is a bug fix release (with future parser changes) in >> the Puppet 3.8 series. It’s first official open source release in >> the 3.8 series. >> >> >> The main focus of this release is to make sure the 3.8 future parser >> is forward-compatible with the Puppet language as of Puppet 4.1. It >> also fixes several bugs. >> >> >> Check out the release notes for more information: >> >> >> https://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html#puppet-381 >> < >> https://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html#puppet-381 >> > >> >> >> You can see the full list of changes on the release's JIRA page: >> >> >> https://tickets.puppetlabs.com/secure/ReleaseNote.jspa?version=13116&styleName=&projectId=10102 >> < >> https://tickets.puppetlabs.com/secure/ReleaseNote.jspa?version=13116&styleName=&projectId=10102 >> > >> >> >> If you're installing Puppet for the first time, follow the >> Installation Guide: >> https://docs.puppetlabs.com/guides/install_puppet/pre_install..html >> <https://docs.puppetlabs.com/guides/install_puppet/pre_install.html> >> >> >> -- >> Kylo Ginsberg | ky...@puppetlabs.com | irc: kylo | >> twitter: @kylog >> * >> * >> *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to >> Portland, Oregon! Join us October 5-9.* >> /Register now to take advantage of the Early Adopter discount >> < >> https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter >> > >> //—//save $349!/ >> >> -- >> 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 >> <mailto:puppet-users+unsubscr...@googlegroups.com>. >> To view this discussion on the web visit >> >> https://groups.google.com/d/msgid/puppet-users/6769655b-908b-4fcb-976d-d7219d419980%40googlegroups.com >> < >> https://groups.google.com/d/msgid/puppet-users/6769655b-908b-4fcb-976d-d7219d419980%40googlegroups..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 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/mknr1o%245jv%241%40ger.gmane.org > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> * *—**save $349!* -- 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/CALsUZFEReOfEWT49jJ%3D0y8qFM%2BSqh4ZHdc8Rdt_5hLVhVxELpw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] where is PC1 for Debian Jessie?
Hey all, We're planning to release the next puppet-agent drop on June 22nd and that should include Jessie packages/repos. Meanwhile, you can grab jessie packages from our nightly builds, e.g. http://nightlies.puppetlabs.com/puppet-agent/3a6740a0753b6fb20d27e45071eedc29dd8b436c/repos/deb/jessie/PC1/puppet-agent_1.1.0.170.g3a6740a-1jessie_amd64.deb Builds only promote to nightly if they pass CI, but these are nightlies, so standard caveats apply. Thanks, Kylo On Tue, Jun 9, 2015 at 5:54 AM, Louis Coilliot wrote: > Hello, many people are waiting for this, including me. > > You can vote for the ticket here : > > https://tickets.puppetlabs.com/browse/CPR-111 > > "Please provide repository for Debian jessie" > > Some people also asked for it on the thread "[Puppet Users] Announce: > Puppet 4 available!" > > That said, for me it works on Jessie with the repos meant for Wheezy : > > deb http://apt.puppetlabs.com wheezy PC1 > > Regards, > > Louis Coilliot > > > 2015-06-09 14:28 GMT+02:00 Rachel Andrew : > >> Hi all >> >> comments on this post >> https://puppetlabs.com/blog/say-hello-open-source-puppet-4 state that >> packages are available for Jessie, however they don't appear to be in the >> list at http://apt.puppetlabs.com/ >> >> Does anyone know where the package might be? >> >> Rachel >> >> -- >> 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/73767d7a-7676-48ac-a89a-134975821b89%40googlegroups.com >> <https://groups.google.com/d/msgid/puppet-users/73767d7a-7676-48ac-a89a-134975821b89%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CAE9jN3050Ao7KMiRL6zJu1v-tPFhuXLPDQw41TShqEfRHGn3gA%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CAE9jN3050Ao7KMiRL6zJu1v-tPFhuXLPDQw41TShqEfRHGn3gA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter> * *—**save $349!* -- 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/CALsUZFFBsTL81v-ii05BwKayLPi9L-iKU3JeJLC5zQuNFA9sJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet 3.8.2 available
Puppet 3.8.2 is a bug fix release (with future parser changes) in the Puppet 3.8 series. The main focus of this release is to make sure the 3.8 future parser is forward-compatible with the Puppet language as of Puppet 4.2. It also add some new reserved keywords (if using the future parser) and it fixes several bugs. Check out the release notes for more information: https://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html#puppet-382 You can see the full list of changes on the release's JIRA page: https://tickets.puppetlabs.com/jira/secure/ReleaseNote.jspa?projectId=10102&version=13415 If you're installing Puppet for the first time, follow the Installation Guide: https://docs.puppetlabs.com/guides/install_puppet/pre_install.html -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Bird discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird> * *—**save $249!* -- 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/CALsUZFHf%3D3q4%3DF3BzrKHo-q6Phu4p%2BABMyNyYuaevRZCjf444Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] 2015.2 strange message
On Thu, Aug 13, 2015 at 9:20 PM, Vince Skahan wrote: > > I'm sorry but you're going to need to reparse that one into English. > You want me to check for what (where?) and change what (where?) ? > The easiest fix for you would be to update to 2.3.0 or greater of the gentoo-portage module. Kylo > > > On Thursday, August 13, 2015 at 11:44:25 AM UTC-7, Peter Huene wrote: > >> On Thu, Aug 13, 2015 at 10:21 AM, Vince Skahan >> wrote: >> >>> Spun up a 2015.2 system and every time an agent runs we see "Error: >>> Facter: error while resolving custom facts in >>> /opt/puppetlabs/puppet/cache/lib/facter/portage.rb: cannot load such file >>> -- facter/util/resolution". Any ideas ? >>> >>> I saw one bug report at >>> https://github.com/gentoo/puppet-portage/issues/136 saying facter >>> needed to be updated and this was allegedly done in 2015.2, but perhaps not >>> (???) >>> >> >> This was fixed in the puppet-portage module itself, so updating the >> module to a fixed version or porting the fix to the fact file (simply >> delete the require 'facter/util/resolution' line) should solve the problem >> with Facter 3. This particular fix is also backwards compatible with 2.x, >> as 2.x also required this file before resolving any custom facts. >> >> If memory serves, I searched through the Forge for references in custom >> facts depending on the Facter 2.x implementation's file structure and found >> only this one. Therefore I didn't end up adding the workaround to Facter >> itself to support requiring parts of 2.x Facter beyond simply `require >> 'facter'` (which itself is also unnecessary, but was more frequently >> done). We could revisit fixing this in Facter itself (basically >> manipulating the load path to fake the load of 'facter/util/resolution') if >> it proves to be a more widespread problem affecting other modules. >> >> >>> >>> Vagrant box I'm testing on is centos-6.7 fully patched up. >>> >>> -- >>> 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...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/puppet-users/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com >>> <https://groups.google.com/d/msgid/puppet-users/e23e8c46-3b97-4a7e-bb88-ccba4abc06a4%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> -- >> Peter Huene >> Software Engineer, Puppet Labs >> Puppet Open Source Team >> --- >> >> PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9! >> >> -- > 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/f1afa917-2cd3-4955-8056-5c47feba170f%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/f1afa917-2cd3-4955-8056-5c47feba170f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog *PuppetConf 2015 <http://2015.puppetconf.com/> is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Bird discount <https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyBird> * *—**save $249!* -- 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/CALsUZFEOhSWg2%3DFQ4uYoR06SG%3D2AGC5gWPKTbd2V%3D3-860VPeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Facter 3.1 gem
On Tue, Oct 20, 2015 at 4:24 AM, Mickaël Canévet wrote: > What will happen when puppet (5?) will require facter 3+? > Will puppet still be available on rubygems.org or only within AIO > packages? > This would be very annoying for puppet module development... > There is one small improvement coming in this area, namely to register puppet/facter/hiera as gems in the puppet-agent package. See https://tickets.puppetlabs.com/browse/PA-25. This should make module development against puppet-agent packages a little bit easier. Longer term though, we'd like to develop an SDK for puppet module development to make module development against puppet-agent packages much easier, ideally allowing some facility for rapidly switching between puppet-agent release versions. And in the meantime, we certainly wouldn't change puppet to *require* facter 3+. Kylo > -- > 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/859397ff-ca71-4eda-bca5-89b769f327e1%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/859397ff-ca71-4eda-bca5-89b769f327e1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFGbS2ykp3eGMvi%2BtOU1C2qAQYpnPcES2XEGS6MCt404JQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Open Source Puppet 3.8 agent for SUSE Sles
On Tue, Oct 20, 2015 at 10:23 AM, cmiller76 wrote: > I am running Puppet Open Source, version 3.8.3. I have inherited a large > SUSE Sles 11 environment that I would like to start managing with Puppet. I > cannot find a Sles 3.8.3 puppet agent package anywhere, and am > inexperienced at building packages for Sles. Can anyone point me to where I > can find a 3.8.3 puppet agent package that will work on Sles 11 > SLES is a PE-only platform, meaning no open-source packages: http://docs.puppetlabs.com/puppet/latest/reference/system_requirements.html > , or even instructions on how to build my own package? I'm totally new to > this, so any help or guidance will be much appreciated. > > -- > 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/26e518c5-ce96-4672-a21f-15da33161f3e%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/26e518c5-ce96-4672-a21f-15da33161f3e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog -- 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/CALsUZFFeLXp%2BmpJDV3%2BHR2aZRgyXCVQqOnDJt%2B8qizNCLhK%2B5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
