Re: [Puppet-dev] Availability of Facter 4 nightly gems

Good question! These are the exact same versions of Facter that are bundled with the nightly puppet-agent builds, so no additional steps are needed if you're already using nightly agent builds. Additionally, as most of you know, Facter 4 is also available as facter-ng on the puppet6 stream. Previo

Re: [Puppet-dev] Availability of Facter 4 nightly gems

Are these also fed into the nightly agent builds, or do I need additional steps to get nightly facter on top of a nightly agent build? On Thu, 20 May 2021 at 13:40, Gabriel Nagy wrote: > Hello, > > We are happy to announce that Facter 4 nightly gems are now available to > use under http://nightl

Re: [Puppet-dev] Re: Support for CentOS Stream 9

Hi Beth, > Thanks for the query. We're tracking the interest from our customers > (both OSP and enterprise) to gauge whether we prioritize adding Rocky > Linux to our test matrices for various reasons, an example being > supported modules.   Sure testing the modules make sense, similar to how you

Re: [Puppet-dev] Re: Support for CentOS Stream 9

Hi Peter, Thanks for the query. We're tracking the interest from our customers (both OSP and enterprise) to gauge whether we prioritize adding Rocky Linux to our test matrices for various reasons, an example being supported modules. Have a great weekend, Beth On Fri, May 14, 2021 at 12:10 PM Pe

Re: [Puppet-dev] Re: Support for CentOS Stream 9

Hi Beth, > I added a CentOS Stream 9 card to our Puppet Idea Portal >  under the Puppet Core tab, the > Idea Portal is how Product tracks feedback/feature requests for the > various products in our portfolio. Thanks for your input! Thank you for adding it.

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

Hi Josh, > All resolved issues should be available in nightly puppet7 builds, such > as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm > . > It'd be great to get confirmation in the next few days that

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

Thanks Pete for putting this together! Some comments below: On Wed, Dec 2, 2020 at 12:33 AM Peter Meier wrote: > Hi All, > > > Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet' > > repos to point to the new 'puppet7' release from a couple of weeks ago. > > If you're already

Re: [Puppet-dev] Improve Puppet Server startup time

Thank you for both of your answers. I'm using a custom Dockerfile as I install Puppet Server from our repositories. It's pretty similar though. I just add bits specific to our infrastracture. Now, to be fair, saying 2 minutes is oversimplifying as that's a slightly high average. The fastest I'

Re: [Puppet-dev] Improve Puppet Server startup time

The biggest single improvement you're going to get is moving from 5.x to the latest 6.x. We started ahead-of-time (AOT) compiling the clojure code to Java in the 6.x series as well as properly supporting Java 11. I think the times Michael is quoting is for the 6.x release and I'd hope you'd see sta

Re: [Puppet-dev] Improve Puppet Server startup time

Are you using a Puppet Server container from https://hub.docker.com/r/puppet/puppetserver? If not, it'd be helpful to know what your Dockerfile is doing. I'm not sure there's been a lot of tuning done for the Puppet Server container we publish. The Puppet Server process itself usually starts in 15

Re: [Puppet-dev] How to update context.xml of tomcat

Hi Kiran, have a look at the https://forge.puppet.com/puppetlabs/tomcat module. The reference contains details on the available functionality for contexts. Regards, David On Fri, Mar 29, 2019 at 5:39 PM Kiran Somisetty wrote: > Hi > I want to update context.xml file of tomcat. > Can you pl

Re: [Puppet-dev] Fwd: Changes coming in PUP-9339

Here is an example showing, after the change, how refresh-only events like the exec shown here, or e.g. a reboot event (which inspired this fix), will now show up in logs and reports: kris.bosland@kris:puppet % cat ../tmp/pup-9339/tmp.pp notify {'notify 9339': } ~> exec {'refreshed exec 9339'

Re: [Puppet-dev] Fwd: Changes coming in PUP-9339

Could you write up an example of what kind of code would have the conditions reversed so that we can share with community members that might be affected? On Wed, Dec 12, 2018 at 2:48 PM Kris Bosland wrote: > Forwarding this to the developer group - does anyone have any feedback on > this change?

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Hi Aécio, We don't have any plans at this time to add support for Ubuntu 16.04 or 18.04 for ARM64. Scott On 08/08/2018 06:16 AM, Aécio wrote: Hello Scott! How are you? I would like to know if it is part of Puppet's roadmap to make the puppet-agent package available for Ubuntu 16.04 or 18.

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Hello Scott! How are you? I would like to know if it is part of Puppet's roadmap to make the puppet-agent package available for Ubuntu 16.04 or 18.04 in the ARM64 architecture. Aécio Pires http://aeciopires.com Em seg, 27 de nov de 2017 às 14:30, Scott Garman escreveu: > Hi Aécio, > > We're n

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

On Fri, 20 Jul 2018, at 02:46, Josh Cooper wrote: > On Wed, Jul 18, 2018 at 8:57 PM R.I.Pienaar wrote: > > > > > > > > On Thu, 19 Jul 2018, at 01:27, Eric Sorenson wrote: > > > > > > > > > > On Jul 16, 2018, at 10:52 PM, R.I.Pienaar wrote: > > > > > > > > > > > > > > > > On Tue, 17 Jul 2018, a

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

On Wed, Jul 18, 2018 at 8:57 PM R.I.Pienaar wrote: > > > > On Thu, 19 Jul 2018, at 01:27, Eric Sorenson wrote: > > > > > > > On Jul 16, 2018, at 10:52 PM, R.I.Pienaar wrote: > > > > > > > > > > > > On Tue, 17 Jul 2018, at 02:40, Eric Sorenson wrote: > > >> Another effort that's underway but not y

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

On Thu, 19 Jul 2018, at 01:27, Eric Sorenson wrote: > > > > On Jul 16, 2018, at 10:52 PM, R.I.Pienaar wrote: > > > > > > > > On Tue, 17 Jul 2018, at 02:40, Eric Sorenson wrote: > >> Another effort that's underway but not yet complete is the extraction of > >> non-core types/providers into

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

> On Jul 16, 2018, at 10:52 PM, R.I.Pienaar wrote: > > > > On Tue, 17 Jul 2018, at 02:40, Eric Sorenson wrote: >> Another effort that's underway but not yet complete is the extraction of >> non-core types/providers into modules. This addresses some long-standing >> requests to, for example,

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

> On 18. Jul 2018, at 00:43, Eric Sorenson wrote: > > On Jul 17, 2018, at 2:26 AM, Martin Alfke wrote: >> >>> On 17. Jul 2018, at 01:40, Eric Sorenson wrote: >>> >>> So my question is - >>> - do you current use/rely on 'gem install puppet' for your workflows? If >>> so, what do you do wi

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

On Jul 17, 2018, at 2:26 AM, Martin Alfke wrote: > >> On 17. Jul 2018, at 01:40, Eric Sorenson > > wrote: >> >> So my question is - >> - do you current use/rely on 'gem install puppet' for your workflows? If so, >> what do you do with it? (does anybody use a 'gem instal

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

> On 17. Jul 2018, at 01:40, Eric Sorenson wrote: > > Another effort that's underway but not yet complete is the extraction of > non-core types/providers into modules. This addresses some long-standing > requests to, for example, be able to change the nagios types and OS-specific > resource

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

On Tue, 17 Jul 2018, at 02:40, Eric Sorenson wrote: > Another effort that's underway but not yet complete is the extraction of > non-core types/providers into modules. This addresses some long-standing > requests to, for example, be able to change the nagios types and OS- > specific resources

Re: [Puppet-dev] [Puppet-Users] Puppet Platform 6 Update

Another effort that's underway but not yet complete is the extraction of non-core types/providers into modules. This addresses some long-standing requests to, for example, be able to change the nagios types and OS-specific resources without needing to get a full agent release out. The extracted

Re: [Puppet-dev] Report Format 8 and 9 Documentation

Hello Garrett and Jacob Thanks a lot for the fast response and the documentation. Highly appreciated. Regards Amdreas On 06/13/2018 09:16 PM, Garrett Guillotte wrote: > > Sorry about that, Andreas, and thanks for catching it. I've got a pull > request up on the puppet-docs repo to resolve this.

Re: [Puppet-dev] Report Format 8 and 9 Documentation

Sorry about that, Andreas, and thanks for catching it. I've got a pull request up on the puppet-docs repo to resolve this. The pertinent commits with diffs of the docs changes between versions are: - https://github.com/puppetlabs/puppet-docs/commit/734a0d80f974cbfde0312ede53f12e0a91d0896c

Re: [Puppet-dev] Report Format 8 and 9 Documentation

Garrett is working on updating that documentation. For now, the summary of the list of changes for formats 8 & 9: * Report Format 8[1]: Added the `transaction_completed` flag. "Whether the transaction completed (e.g. didn't have an unrescued exception)." * Report Format 9[2]: Added the `provider_u

Re: [Puppet-dev] Re: Announcement: Release of Bolt 0.19.1

Check out the hands-on lab: https://github.com/puppetlabs/tasks-hands-on-lab On Tue, May 1, 2018 at 1:14 PM Joaquin Menchaca wrote: > Any good tutorials on tasks/plans, creating tasks/plans, injecting data > into puppetdb or custom facts? Docs very sparse. For command and script, > had to wal

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

Interesting. Maybe I missed this detail. So, if I had 5 different 'vendored' locations across my filesystem, and they were all in my environment configuration, the Puppetfile would dictate which items from these locations would actually be used? I think I can get behind that. My concerns were bo

Re: [Puppet-dev] Puppet Platform 6 pre-release builds available

> On 27 Apr 2018, at 05:07, Miguel Di Ciurcio Filho > wrote: > >> On Mon, Apr 23, 2018 at 6:44 PM, Eric Sorenson wrote: >> Hi all, we've started landing changes for what will become Puppet Platform >> 6. Here's the News You Can Use relating to the release. > > Hello Eric, > > I've noticed

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

On Thu, Apr 26, 2018 at 7:42 PM, Trevor Vaughan wrote: > Oh, and you're possibly setting yourself up for SERVER-94 hell if you're > not EXTREMELY careful. > Yep, I'm aware of the issues with environment isolation, as I filed the initial redmine ticket more than 5 years ago describing the problem

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

On Thu, Apr 26, 2018 at 7:42 PM, Trevor Vaughan wrote: > I would ask that you only vendor items that are super generic and that you > namespace them such that they won't interfere with people already written > codebases. > For modules that were previously in core puppet, we are plan on appending

Re: [Puppet-dev] Puppet Platform 6 pre-release builds available

On Mon, Apr 23, 2018 at 6:44 PM, Eric Sorenson wrote: > Hi all, we've started landing changes for what will become Puppet Platform 6. > Here's the News You Can Use relating to the release. Hello Eric, I've noticed that mcollective has been removed of the puppet-agent package. Would it be possi

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

Oh, and you're possibly setting yourself up for SERVER-94 hell if you're not EXTREMELY careful. On Thu, Apr 26, 2018 at 10:42 PM, Trevor Vaughan wrote: > I would ask that you only vendor items that are super generic and that you > namespace them such that they won't interfere with people already

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

I would ask that you only vendor items that are super generic and that you namespace them such that they won't interfere with people already written codebases. The following seem relatively safe since they've been in use for quite some time: - stdlib - archive (maybe) - inifile - pow

Re: [Puppet-dev] Changes coming to puppet docker containers!

On Wed, Apr 18, 2018 at 5:57 PM Aécio wrote: > Hello Morgan! > > I'm a member of Puppet-Brazil community and author of Portuguese book > about Puppet. > novatec.com.br/livros/puppet > > How great that you are going to focus on improving Puppet images for > Docker. > > I'm trying to use it and I'm

Re: [Puppet-dev] Changes coming to puppet docker containers!

Hello Morgan! I'm a member of Puppet-Brazil community and author of Portuguese book about Puppet. novatec.com.br/livros/puppet How great that you are going to focus on improving Puppet images for Docker. I'm trying to use it and I'm particularly hard on it. I am trying to install it by followin

Re: [Puppet-dev] Custom Hiera Interpolation Functions

> On Apr 17, 2018, at 6:56 PM, adam.gard...@magicmemories.com wrote: > > So, I'm aiming to have a method of interpolating Facter facts in Hiera data > files that works more or less exactly like the `scope` lookup function, > except that if the Facter fact is not defined, this interpolation sho

Re: [Puppet-dev] Re: Ephemeral resources

In terms of the 'after all resources processed' I think this is one of those cases where you present the capability because there is need and caveat it with the fact that you may, or may not, have access to resources that have been modified after the fact. In theory, with a hook like this, you cou

Re: [Puppet-dev] Re: Ephemeral resources

I thought there were dangers with Virtual Resource being accidentally realized sometimes? We found a super-hacky way to call functions at the end of a compile which we use in https://github.com/simp/pupmod-simp-compliance_markup/blob/master/manifests/map.pp. It would be *really nice* if there were

Re: [Puppet-dev] Re: Ephemeral resources

In terms of #2, there's actually a ticket that I put in a while ago for a shared data cache. But, I recently realized that the common pattern is to literally map every line in a file as a separate resource. We've had the same issue with firewall rules, etc... for quite some time. So, the most "use

Re: [Puppet-dev] Significance of 'puppet generate types' and title patterns that use procs

As a note, this *does* appear to be working on the modules that I've tested so far. On Tue, Apr 10, 2018 at 10:02 PM, Trevor Vaughan wrote: > That might just work! Thanks for the pointer, I'll give it a try. > > If it works, I'll see if I can get the augeasproviders_* modules updated > as well.

Re: [Puppet-dev] Significance of 'puppet generate types' and title patterns that use procs

That might just work! Thanks for the pointer, I'll give it a try. If it works, I'll see if I can get the augeasproviders_* modules updated as well. Trevor On Tue, Apr 10, 2018 at 3:20 PM, Josh Cooper wrote: > > > On Tue, Apr 10, 2018 at 11:19 AM, Trevor Vaughan > wrote: > >> I was digging thr

Re: [Puppet-dev] Significance of 'puppet generate types' and title patterns that use procs

On Tue, Apr 10, 2018 at 11:19 AM, Trevor Vaughan wrote: > I was digging through some output from 'puppet generate types' and noticed > that some of my custom types that have composite namevars were throwing an > error "title patterns that use procs are not supported". > When using `puppet genera

Re: [Puppet-dev] cfacter 3.11.0 pre-release gems available on rubygems

Just for some context, the goal of providing facter3 as a gem is primarily so that the testing/tooling ecosystem that relies on running puppet+facter from bundles/source can test against a modern version of Facter... Thanks for getting this going Sean & team. --eric0 > On Mar 14, 2018, at 4:34

Re: [Puppet-dev] Port 8140/TCP (PuppetServer) close

Hello Justin! Thank you very much for your attention and for the tips. I set the PuppetServer memory from 2 to 4 GB. # /etc/default/puppetserver JAVA_ARGS = "- Xms4G -Xmx4G" I also adjusted the number of JRuby instances from 4 to 2. # /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf max-a

Re: [Puppet-dev] Port 8140/TCP (PuppetServer) close

On Sun, Mar 11, 2018 at 4:58 AM, Aécio wrote: > Hello guys! > > I have the following problem: every 30 or 40 minutes, I get a notification > that port 8140 / TCP (from PuppetServer) is closed and puppet-agent (from > client servers) can not get the catalog and / or send reports. > > Looking at th

Re: [Puppet-dev] Port 8140/TCP (PuppetServer) close

Hello, Rob! Thanks for attention. There is no firewall between PuppetServer and Agent. As I said before, the PuppetServer port is open and has communication between them, but every 30 or 40 minutes the PuppetServer port is closed for 60 seconds and then it stays open again. The strange thing is

Re: [Puppet-dev] Port 8140/TCP (PuppetServer) close

You should probably start by verifying it is listening on port 8140, then look at any firewalls between the agents and the master - including iptables or other OS-level firewalls - to ensure they are allowing the traffic. On Sun, Mar 11, 2018 at 7:59 AM Aécio wrote: > Hello guys! > > I have the

Re: [Puppet-dev] Re: Announce: Puppet Platform 5.3.4 is now available

The "no implicit conversion of nil into String" error should be fixed with the recent release of "gettext-setup"[1][2]. While this resolves the issue seen in modules CI with puppet-agent 5.3.4, there was an unrelated regression in the same release, involving non-default environments[3]. So I'd reco

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

We too would love to have ARM64 support for Ubuntu 16 and beyond. We are an enterprise customer as well. On Monday, November 27, 2017 at 9:30:23 AM UTC-8, Scott Garman wrote: > > Hi Aécio, > > We're not currently working on ARM64 for Ubuntu 16.04 - only for > RHEL/CentOS 7. The epic ticket for

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Hi, Scott! Thank for the link. I already added a comment on the ticket. Good work and thanks for the help. Aécio Pires 2017-11-27 14:30 GMT-03:00 Scott Garman : > Hi Aécio, > > We're not currently working on ARM64 for Ubuntu 16.04 - only for > RHEL/CentOS 7. The epic ticket for that work is >

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Hi Aécio, We're not currently working on ARM64 for Ubuntu 16.04 - only for RHEL/CentOS 7. The epic ticket for that work is https://tickets.puppetlabs.com/browse/PA-1330. We're not ruling out eventually adding support for Ubuntu 16.04 on ARM64, but it's currently not planned. I'll certainly p

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Scott, Can you share the JIRA ticket that contains the activity status of generating the puppet-agent package for ARM64 in Ubuntu 16.04? I would like to follow the progress closely and if possible help with the tests. Aécio Pires 2017-11-23 23:47 GMT-03:00 Aécio : > Scott, > > Thank you for th

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Scott, Thank you for the informations. I will await the conclusion of this work. I will need to use Puppet to manage systems Ubuntu 16.04 in the ARM64 architecture. Abraço e fica com Deus. Aécio Pires 2017-11-21 18:13 GMT-03:00 Scott Garman : > On 11/21/2017 12:27 PM, Aécio wrote: > >> Hi S

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

On 11/21/2017 12:27 PM, Aécio wrote: Hi Scott, In these files referenced in an ARM64 architecture says that exists in the packages to puppetserver, puppetdb but does not exist for puppet-agent https://apt.puppetlabs.com/dists/xenial/puppet5/binary-arm64/Packages https://apt.puppetlabs.co

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

Hi Scott, In these files referenced in an ARM64 architecture says that exists in the packages to puppetserver, puppetdb but does not exist for puppet-agent https://apt.puppetlabs.com/dists/xenial/puppet5/binary-arm64/Packages https://apt.puppetlabs.com/dists/xenial/puppet5/binary-arm64/Packag

Re: [Puppet-dev] Is there the puppet-agent package for ARM64?

On 11/21/2017 09:10 AM, Aécio wrote: Hello guys! I searched the Puppet repository for Ubuntu 16.04 (Xenial) https://apt.puppetlabs.com/dists/xenial/ and did not find the *puppet-agent* package available for the *ARM64* architecture. There are binaries for puppetserver, puppetdb, but they do

Re: [Puppet-dev] Facter returns IPv4 address for IPv6 when IPv6 is disabled

Just some additional details I found when looking at the debug output versus the code blocks. I don't yet know how the code for facter in networking_resolver.cc (networking_resolver::read_routing_table() and networking_resolver::populate_from_routing_table) need to be modified. What I do see i

Re: [Puppet-dev] Facter returns IPv4 address for IPv6 when IPv6 is disabled

Thanks. Now I know this is a known issue. I can work with that to find a temporary work around, somewhere. As this is a for a mgmt report I will just drop the IP field from the hammercli and do a host lookup to populate it. At least this issue is not why I'm going crazy! :) On Thursday, Octo

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

On Thursday, October 5, 2017 at 1:45:59 PM UTC-4, Ryan Whitehurst wrote: > > On Thu, Oct 5, 2017 at 10:35 AM, James Perry > wrote: > >> I'm using the saz/sudoers as well and it removes, say ERPM10-20, when I >> remove the user from the host, exactly as expected. >> >> What doesn't happen is the

Re: [Puppet-dev] Facter returns IPv4 address for IPv6 when IPv6 is disabled

This looks like https://tickets.puppetlabs.com/browse/FACT-1475. We're aware of it, but it hasn't been a priority to fix. The Facter team has grown a bit recently, though, so I'm hopeful that we'll be able to fix things like this more quickly in the future. Unfortunately, I still can't say for cert

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

On Thu, Oct 5, 2017 at 10:35 AM, James Perry wrote: > I'm using the saz/sudoers as well and it removes, say ERPM10-20, when I > remove the user from the host, exactly as expected. > > What doesn't happen is the user ERPM10-20 isn't removed from the server. > > Let me try to see if I can put it an

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

I'm using the saz/sudoers as well and it removes, say ERPM10-20, when I remove the user from the host, exactly as expected. What doesn't happen is the user ERPM10-20 isn't removed from the server. Let me try to see if I can put it another way to make it clearer. Say I have ERPM01-01, ERPM01-22

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

Ah, sudoers files. That narrows it down - less of a class issue and more of a multiple defined type instance issue. What module are you using, specifically? I use saz/sudo because it purges ALL sudoer.d files that it does not manage. So if on one run, there were say ERPM01-30 users and then on the

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

you could use the defined(Class[xy]) function to test if the class is included. but be aware that you need to control the manifest parse order for that to work. if you check defined() before the class is included this wont work. - Thomas https://docs.puppet.com/puppet/latest/function.html#defin

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

Thanks Rob. > > As for reclassifying nodes that is a use case outside of what I'm trying to accomplish. Mostly I was trying to work more a scenario like the following: I have a set of restricted accounts for use with ERPM.on Linux. Each DBA is assigned a Linux local ERPM user that is the same

Re: [Puppet-dev] Anyway to trigger cleanups when classes are removed from a host?

Puppet enforces state. It does know about state you have not defined. So if you have a class that takes an ensure propert of absent, for instance, it can enforce that. But it cannot guess what “the absence of this class” means as a state model. Remember, your class model may say ‘make sure apache i

Re: [Puppet-dev] Announce: Puppet Platform 5.2 available

Hey Thomas (and everyone), Sorry for the docs deployment issues! The full Server 5.1 docs, and PuppetDB 5.1 docs, are all live as of a few minutes ago. - https://docs.puppet.com/puppetserver/latest/ and https://docs.puppet.com/puppetserver/5.1/ - https://docs.puppet.com/puppetdb/lates

Re: [Puppet-dev] Announce: Puppet 5 Platform Available!

> So to report back after running it for >2 weeks: 0 problems so far and I > don't really feel a difference to 1.7 > > > Thanks for trying it out! Is there a performance difference if you > change server's "compile-mode" option? I'm mostly curious about running > with JIT compilation on.

Re: [Puppet-dev] Announce: Puppet 5 Platform Available!

On Mon, Sep 18, 2017 at 4:33 AM, Peter Meier wrote: > On 08/31/2017 01:21 AM, Peter Meier wrote: > > So to report back after running it for >2 weeks: 0 problems so far and I > don't really feel a difference to 1.7 > Thanks for trying it out! Is there a performance difference if you change server

Re: [Puppet-dev] Announce: Puppet 5 Platform Available!

On 08/31/2017 01:21 AM, Peter Meier wrote: >> Our current >> Ruby versions are EOL'ed, so we're moving to MRI Ruby 2.4 on the agent >> and (opt-in) jruby9k on the server. > > So what's the current status on that opt-in? > > I'm running into a nasty bug with Jruby 1.7 [1] and while I read the > co

Re: [Puppet-dev] Announce: Puppet Platform 5.2 available

Hi Eric Am 14.09.2017 um 17:25 schrieb Eric Sorenson: > A new release of the Puppet Platform is available. As a reminder, we're doing > monthly releases of the platform components (Agent, Server and PuppetDB) > which are tested and released together. didn't know about the monthly schedule. Is

Re: [Puppet-dev] Re: Announce: puppet server 2.8.0 available!

Hi Matthew, Thank you for pointing this out. The puppetserver 2.8.0 is available at https://downloads.puppetlabs.com/puppet/ On Sat, Sep 2, 2017 at 6:21 PM 'Matthew Thode' via Puppet Developers < puppet-dev@googlegroups.com> wrote: > It looks like the tarball is missing from > https://downloads.

Re: [Puppet-dev] Announce: Puppet 5 Platform Available!

> Our current > Ruby versions are EOL'ed, so we're moving to MRI Ruby 2.4 on the agent > and (opt-in) jruby9k on the server. So what's the current status on that opt-in? I'm running into a nasty bug with Jruby 1.7 [1] and while I read the configure guide [2] I'm still a bit unsure whether I shoul

Re: [Puppet-dev] lookup from external script

For an abandoned experiment awhile back I went to the trouble of mostly getting an external ruby script working that used Hiera 5 as a library. I don't know that you still want to do this, sounds like there may be other options per the conversation in the thread, but I'll post the following lin

Re: [Puppet-dev] lookup from external script

> Maybe this is a bit overkill for your requirements, but this was > > actually one use case for Jerakia (http://jerakia.io). Hiera 5 can use > > it as a backend from your Puppet implementation, and because it runs > > over an HTTP API other tools can easily hook into the same data > > lookups...

Re: [Puppet-dev] lookup from external script

> What would you recommend to do, how would you approach the problem with > getting data out of hiera in something else than puppet? Just stick > around with Hiera 3 and an old non-hiera-5 config file? Which would > likely be feasible if hiera stays somewhat supported, which it does

Re: [Puppet-dev] Re: lookup from external script

> There are however several use cases where people want to be able to > instantiate "a hiera" with a hierarchy of their own to do lookups. There > is the beginnings of such an API in puppet, but it is not well > documented and needs a bit more work. And example, like the one I sent, would totally

Re: [Puppet-dev] lookup from external script

> What would you recommend to do, how would you approach the problem with > getting data out of hiera in something else than puppet? Just stick > around with Hiera 3 and an old non-hiera-5 config file? Which would > likely be feasible if hiera stays somewhat supported, which it doesn't > from my un

Re: [Puppet-dev] Re: [ANN] Puppet Development Kit (pdk) preview (0.6.0)

On Fri, Aug 11, 2017 at 12:19 PM, Corey Osman wrote: > Do you guys have plans to bundle the puppet debugger in the pdk? I can't > think of a more useful tool then a repl and debugger to be part of > development kit. > No current plan to do so and we're in listening mode about where the most ben

Re: [Puppet-dev] Re: [ANN] Puppet Development Kit (pdk) preview (0.6.0)

On 11 August 2017 at 19:06, Corey Osman wrote: > I haven't messed with PDK yet. What problems is this new tool solving > though? How is it different from puppet-retrospec? > https://github.com/nwops/puppet-retrospec > The main problems the PDK attacks today are - *Complexity of setting up

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

In case it helps anyone else, there is likely no need to fiddle with the Heap etc. The root cause in my case was somehow during an upgrade the master was unpinned from the "Pe Certificate Authority" nodegroup. I've seen it on a few boxes that were upgraded using nc_migrate tool FWIW. On Frida

Re: [Puppet-dev] Need for feedback regarding sort_merged_arrays vs sort_merge_arrays lookup behavior

Many thanks for the feedback. We decided to remove sort_merged_arrays option and re-add it once we drop support for Puppet < 4.10.5 > On 01 Aug 2017, at 08:56, Thomas Hallgren wrote: > > I reacted to the formulation "Puppet 4.10.4/5.0.1 or earlier: success - but > no functionality". There was

Re: [Puppet-dev] Need for feedback regarding sort_merged_arrays vs sort_merge_arrays lookup behavior

I reacted to the formulation "Puppet 4.10.4/5.0.1 or earlier: success - but no functionality". There was never a success but rather a hidden failure (which is worse than an apparent one). Puppet never officially named the option to "sort_merge_arrays". The documentation has always had the correct

Re: [Puppet-dev] Need for feedback regarding sort_merged_arrays vs sort_merge_arrays lookup behavior

On Mon, Jul 31, 2017 at 3:53 AM, Martin Alfke wrote: > Hi, > > we (example42) are in need of feedback regarding sort_merged_arrays vs. > sort_merge_arrays when having to support multiple Puppet versions. > > http://www.example42.com/2017/07/31/sort_merged_array-fix/ > > Given that sort_merge_arra

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

cheers Ryan, I have read the guide and made changes, we'll see how it goes. On Friday, July 28, 2017 at 11:27:29 AM UTC-7, Ryan Whitehurst wrote: > > On Fri, Jul 28, 2017 at 9:01 AM, Mike Jeski > wrote: > >> Cheers mate. This version of PE is actually running java 7. >> > > Ah, well in that cas

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

On Friday, July 28, 2017 at 11:27:29 AM UTC-7, Ryan Whitehurst wrote: > > On Fri, Jul 28, 2017 at 9:01 AM, Mike Jeski > wrote: > >> Cheers mate. This version of PE is actually running java 7. >> > > Ah, well in that case bumping up the MaxPermSize will have an effect, but > the problem is sti

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

On Fri, Jul 28, 2017 at 9:01 AM, Mike Jeski wrote: > Cheers mate. This version of PE is actually running java 7. > Ah, well in that case bumping up the MaxPermSize will have an effect, but the problem is still almost certainly caused by too low of a heap size, so you should still read the infor

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

On Thu, Jul 27, 2017 at 1:37 PM, Mike Jeski wrote: > Cheers, > the -XX:MaxPermSize= was there as part of the pe-puppetserver package. I > merely raised the value to 512m from 256m. > > Are you saying it is syntactically incorrect? > It's not syntactically incorrect, it just has no effect on Ja

Re: [Puppet-dev] odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

Maxpermsize isnt available in openjdk8. Look for xmx/xms. And I think UseGC1G is only available for openjdk8. https://docs.puppet.com/puppetserver/latest/tuning_guide.html#jvm-heap-size - Thomas Am 27. Juli 2017 22:16:56 MESZ schrieb Mike Jeski : >Hi group, > >running PE 3.8.7 (while clean

Re: [Puppet-dev] Most Spec tests fail if using fail('some error') to test with and_raise(Puppet::Error, /some error/)

On Wed, Jul 26, 2017 at 11:59 AM, James Perry wrote: > Can anyone assist my confusion on how to use is_expected.to > compile.and_raise(Puppet::Error, /some error/)? > > I have a class where I have fail('some error') and it is only calls class > ABC if parameters A=1, B=2, C=3, which I am using to

Re: [Puppet-dev] It is possible to mock / stub a local variable in the module being tested?

That is the direction I am heading. I think I will change the class logic to check the size of the array before and after the delete to know if the current version is part of the set or not. Then I can take it from there and well as test that it has X file removes based on the versions it shoul

Re: [Puppet-dev] It is possible to mock / stub a local variable in the module being tested?

On Tue, Jul 25, 2017 at 3:15 PM, James Perry wrote: > So I am over thinking it then. I'm taking fact values from a list of > installed directories and removing the one matching the current version. > This is being used to remove the old install directories and I didn't want > it to whack the cur

Re: [Puppet-dev] It is possible to mock / stub a local variable in the module being tested?

So I am over thinking it then. I'm taking fact values from a list of installed directories and removing the one matching the current version. This is being used to remove the old install directories and I didn't want it to whack the current version. I wanted to test that having the local varia

Re: [Puppet-dev] It is possible to mock / stub a local variable in the module being tested?

On Tue, Jul 25, 2017 at 2:33 PM, James Perry wrote: > I'm not sure if it can be done, but I am trying to test a case where I > take an array of values and use stdlib's delete to remove one value before > iterating over it. The class will fail if the removed value is present. > That all works fine

Re: [Puppet-dev] Puppet Rspec - Check against Catalogue Value

Thanks David. Simple things seem more complex with RSpec than they should be. On Tuesday, July 25, 2017 at 6:14:55 AM UTC-4, David Schmitt wrote: > > > > On 25 July 2017 at 00:21, James Perry > > wrote: > >> So I have a simple class, for now, where I am trying to write RSPEC tests >> to check

Re: [Puppet-dev] Puppet Rspec - Check against Catalogue Value

On 25 July 2017 at 00:21, James Perry wrote: > So I have a simple class, for now, where I am trying to write RSPEC tests > to check the following: > > 1. Smart Parameter $current_version is in catalogue. > 2. If $current_version = $installed_version (custom fact that will be > stubbed as a :fact)

Re: [Puppet-dev] calling functions from (ruby-)functions and puppet data types

> On 24 Jul 2017, at 22:29, Peter Meier wrote: > >> Now, the reason your call on line 74 >> >>call_function('lookup', key, 'Hash', 'hash',{}) >> >> fails is that you have to pass in a ruby object for the type, not a >> string representation of the type. There's probably a better way that >

Re: [Puppet-dev] calling functions from (ruby-)functions and puppet data types

> Now, the reason your call on line 74 > > call_function('lookup', key, 'Hash', 'hash',{}) > > fails is that you have to pass in a ruby object for the type, not a > string representation of the type. There's probably a better way that > would generate an appropriate object based on the string,

  1   2   3   4   5   6   7   8   9   10   >