[Puppet-dev] builds for EL 10 - CentOS Stream 10 / AlmaLinux 10

Hi All, The RHEL 10 is shapping: https://www.redhat.com/en/blog/red-hat-enterprise-linux-10-beta-now-available CentOS Stream 10 is out: https://lwn.net/Articles/1002044/ AlmaLinux has their Kitten Variant https://lwn.net/Articles/995140/ as well as they have also their AlmaLinux Beta10 avai

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 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.

[Puppet-dev] Support for CentOS Stream 9

Hi All, since CentOS Stream 9 test compose builds are there and thus we can all see what will be coming in RHEL 9: https://lists.centos.org/pipermail/centos-devel/2021-April/076802.html When could we expect a build of at least puppet-agent for CentOS Stream 9? What needs to happen to get that b

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

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

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 using the 'puppet' release packages (such > as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm >

[Puppet-dev] Re: [Puppet Users] Issue with puppet6 release packages

> * If /etc/yum.repos.d/puppet.repo exists -- you are affected. Unless > you want to be subscribed to the repo with rolling updates, you > should uninstall and reinstall the release package. > * If /etc/yum.repos.d/puppet6.repo exists -- you are not affected. So what is the intend for

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 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

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

> 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

[Puppet-dev] lookup from external script

Hi all, I have a bunch of ruby script that are munging data around, part of that data is based out of hiera. Until now, with hiera 3, I just required hiera in my ruby script, called lookup with a certain scope and I got my data out of hiera. Now looking forward to puppet not anymore shipping hie

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,

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

Hi All, I'm stumbling over two problems, while trying to port over a custom hiera backend from hiera 3 to hiera 5. I was able to simplify the problem I have to a simple example and I think it shows a) Documentation is wrong b) You can't use Puppet Data types in ruby functions, at least not in my

Re: [Puppet-dev] Caching catalogs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, > Is there already some kind of code doing that, or any > opinion/feedback on this idea? I have written once a change management guard, that does some of the stuff you mentioned and as a side-effect also includes caching - or I abused caching

Re: [Puppet-dev] Re: puppet-dev status the week ending 14-11-14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> Please note that some changes in puppet 4 mean that puppet 3 >> agents won’t be able to talk to puppet 4 masters (or vice-versa). >> This probably means you don’t want to be updating puppet itself >> with “ensure => latest” :) >> > point taken, but

Re: [Puppet-dev] Re: Lightweight PuppetDB replacement

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > - I've had no trouble running PuppetDB *and postgres* alongside a > master in a relatively small VM for testing purposes The only problem I see with deprecating active_record storeconfigs is: How are you going to use exported resources in puppet app

Re: [Puppet-dev] RFC - Grammar quirks I want to remove...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Can we get rid of this, it is bad enough that all other keywords > can be used (if, unless, case, class, define, etc. etc.) Couldn't we ban them as well? I think in most other "programming" languages this won't work as well. > Can we disallow white

Re: [Puppet-dev] ROADMAP/REDESIGN: Puppetlabs-mysql

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > To bring this back to mysql I guess I'd see: > > mysql-provider mysql-server mysql-server-accounts > mysql-server-backup mysql-client > > As potential places to split a module like this into smaller bits. > It would definitely be more complex to h

Re: [Puppet-dev] Need advice on PUP-1592

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/07/2014 08:26 PM, John Bollinger wrote: > > > On Friday, February 7, 2014 3:57:00 AM UTC-6, Brice Figureau > wrote: > > In this specific bug, I'm wondering if we really need to have > those defined type as resources in the RAL catalog (I belie

Re: [Puppet-dev] #8433 Globbing imports are now considered undefined behavior

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > It seems that now the recommendation is to have one file per > class? Yes it is. > If no, where puppet will look for foo::a::b class, (aside from > module/foo/manifest/a/b.pp)? But you can also have this class in module/foo/manifest/a.pp module

Re: [Puppet-dev] #8433 Globbing imports are now considered undefined behavior

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I'm trying to find an official document explaining how classes > should be organized. This should probably help you: http://docs.puppetlabs.com/puppet/latest/reference/lang_namespaces.html ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15

Re: [Puppet-dev] Encoding bug in Puppet 3.3.1 when using Ruby 1.9.3 (and above)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2013 02:00 AM, Jos Backus wrote: > One of our RPM packages has some UTF-8 characters in its > description, leading to an exception ("Error: Could not prefetch > package provider 'yum': invalid byte sequence in US-ASCII") in > rpm.rb, causing

Re: [Puppet-dev] Help regarding puppet installation and configuration on RHEL 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I am new to puppet and have no idea about how to install and > configure puppet. I want to install puppet on RHEL 5. Please tell > me in very simple way that how to install and configure *PUPPET > open source* and what are its prerequisites for RHEL

Re: [Puppet-dev] puppet-internal: loading ruby files and classes the right way

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Luke, thanks for your answer. > I'm confident there's an easier way; just the way you're using the > autoloader there seems unecessarily complicated. Why are you even > using autoloading? Why don't you just hard-code the invalidator > name, a

[Puppet-dev] puppet-internal: loading ruby files and classes the right way

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I'm currently working on an own terminus for the catalog. One of the ideas of this terminus is, that it can ask a configurable invalidator, whether a certain catalog is still valid or not. This invalidator should also be configurable in an own term

Re: [Puppet-dev] Adding trusted information to puppet manifests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > So in order to get the trusted name we should create a top level > hash named “trusted”, with a key called “nodename”. I think this a good idea. However, I don't really like the name, I think it's not specific enough and is confusing for people who

Re: [Puppet-dev] State of Facter development / bug fixing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Andy, Thanks for your comments on my mail. >> I'm wondering what the state of the development and especially >> bug fixing of Facter is: > > For the state of puppet development we've been trying to keep the > tickets in redmine as up to date as

Re: [Puppet-dev] State of Facter development / bug fixing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > None of that is about bugs being ignored, but it might help explain > why some of those bugs are so sticky... I'm all in for a new way how facts are provided, like a more nested datastructure (eg: hash). And I think at the point this is introduced i

[Puppet-dev] State of Facter development / bug fixing

Hi all, I'm wondering what the state of the development and especially bug fixing of Facter is: Currently I have on my (very own) list 3 really nasty bugs, that make it really hard to rely on values of core facts (e.g.: virtual, is_virtual, ipaddress etc.) within manifest/module developme

Re: [Puppet-dev] why I don't feel that ENCs are very functional right now (performance)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> Although, I do a lot of hiera lookups now, but also switched >> from full storeconfigs to thin storeconfigs, I think the >> difference is huge and I'm wondering what might cause it. > > fwiw hiera isn't caching - there was a caching yaml backend >

Re: [Puppet-dev] why I don't feel that ENCs are very functional right now (performance)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I committed the caching YAML code to master, and it should be > merged. Just boarding a plane, but can link when I land :) I thought that have already be included in one of the 1.0.0 hiera rc-releases? Or are you talking about a different cache? I'

Re: [Puppet-dev] why I don't feel that ENCs are very functional right now (performance)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Actually, this is a group where y'all probably *can* deliver on > this request: > > If you are experiencing poor performance, it would be awesome if > you could generate some profiling data for us. > > perftools.rb is the nicest profiler for Ruby I

Re: [Puppet-dev] why I don't feel that ENCs are very functional right now (performance)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I would really appreciate that. I recently moved a larger > installation to 2.7 (latest) and I'm probably going back, as the > slow down + extended memory usage is just not worth it. > > Compile time doubled in my case (~60s compared to 27s). We > m

Re: [Puppet-dev] why I don't feel that ENCs are very functional right now (performance)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> I'm hoping that 3.0 brings some significant performance >> improvements. >> > > We discovered some functionality regressions that we are working > on right now and hope to have out of the way soon. We've also made > the decision to hold off on re

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

> I can't stress how strongly I (we?) discourage the use of Ruby 1.8.6. =) Yeah, this is a backported version from one of the fedoras for EL5... > We (Puppet Labs) really don't do any testing; quality, performance, or > otherwise, against this version of Ruby. > > I'm not saying you'll see a hu

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

+      beginning_time = Time.now      Puppet.info "Caching #{self.name} for #{request.key}"      cache.save request(:save, result, *args) +      Puppet.debug "Caching catalog time: #{(Time.now - beginning_time)}" Here're my results for a catalog of ~2000 resources, some of which are tidys of big

Re: [Puppet-dev] Community input requested on potential `unless_uid` addition to user resources

> What are your thoughts? Is this intuitive enough? Is it a must-have feature? I think it's valuable and as you said there are valid uses cases where such operations are currently not possible with the default language features. Why do you call it terrific? What are your concerns? I couldn't find

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

> On that note: After spending a few hours hunting yesterday, we > identified the cause of a significant performance regression in > compilation when using modules with metadata. I've attached a patch > for anyone who would like to test it out. We're seeing approximately > 5-10x faster compilation.

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

Fourth, Peter, Émile, and Trevor (or anyone else experiencing the problem), would you be willing to be pre-release testers of improvements? Our ops team is seeing the problem too, but that's only a single real-world data point. We need to make sure we don't self-optimize. We need your hel

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

But anyway I remember that caching the catalog (read serializing it as yaml to disk) has been very slow for years and also known. It usually makes the agent look like it's hanging. This especially happens on huge catalogs - I have catalogs with up to 10k resources. It would be great to improve t

Re: [Puppet-dev] here is new resource type sysprop v1.0

Also... my earlier assumption seems to be correct. In principle, at least. Just looking at the "best practices layout" autogenerated there... this seems to be primarily geared towards *classes*, and end user "modules". Not back end "here's a whole new resource type" code. A module is more than j

Re: [Puppet-dev] Trying to isolate performance issues with config retrieval.

Otherwise i work on Puppet optimizations and i have seen some strange things too. I work on big catalog (more than 1000 resources) and i want to reduce the application time (around 20 sec). I have seen two kind of things: - First, recent Puppet versions are slowest (see PuppetVersions.png in

Re: [Puppet-dev] does this mean no 2.7.14 ?

Zitat von Jo Rhett : On Apr 30, 2012, at 10:57 AM, Daniel Pittman wrote: As of this morning the Puppet codebase has been frozen in preparation for the Telly release. Does this mean that 2.7.14 "died in the thunderdome" ? Unlikely, as up to now usually two major releases were supported for

Re: [Puppet-dev] puppet with otrs

this is something that imho is better placed on the puppet-users list. ~pete On 12/02/2011 07:32 AM, siddhartha chowdhury wrote: > * For having control on clients and reporting purpose we would like to > increase the information given by Puppet Dashboard. > 1. Curren

Re: [Puppet-dev] How to execute sqlplus cmds through puppet module

This is Anjan. I am trying to create a database for oracle 11g through puppet module.Their i am unable to execute oracle cmds through puppet . sqlplus "/as sysdba" < you should ask this question on the puppet-users-list: http://groups.google.com/group/puppet-users ~pete -- You received this

Re: [Puppet-dev] Re: [Puppet Users] Re: Is it possible to get a list of all nodes in your manifests and all classes assigned to those nodes programatically in Ruby?

Hi In the case of a default node, regexp nodes or an external node classifier, there *is* no well-defined "list of potential nodes" any more. Having said that, a solution might be to use the puppet compiler's internals to parse the site.pp and friends "manually" and access the AST resulting fro

Re: [Puppet-dev] Is is possible to have common defines used in server side functions and still be self contained in a module?

On 11/18/2011 08:16 PM, Trevor Vaughan wrote: > Here's an example reference: > http://avdi.org/devblog/2009/10/22/double-load-guards-in-ruby/ Yes, but that's only a warning (not an exception) and it only happens if you require a file twice with different loading paths. Which should not happen if y

Re: [Puppet-dev] Is is possible to have common defines used in server side functions and still be self contained in a module?

> Peter's solution of a 'require' has the potential to hit the > double-load scenario in Ruby which throws an exception. This was rare > but happened occasionaly. hmmm, exceptions when calling a require twice? Never encountered that so far. Am I missing a fundamental possible problem in ruby so fa

Re: [Puppet-dev] Is is possible to have common defines used in server side functions and still be self contained in a module?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > The problem that I'm having is getting the autoloader to find it. > > I've called it 'module Foobar' with no luck. > > Should I be using a require with file expansion? I think I used what you need in my trocla functions: https://github.com/durito

lost/forgotten merges (was Re: [Puppet-dev] #7982 (and consort) in 2.7.4?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Is there any chance (after failing to get considered for 2.7.3) that the > 3 patches of the network device code could be merged-in in time for 2.7.4? I have the feeling that a couple of pending (!) merges got lost to be in 2.7.3. They also didn't ge

Re: [Puppet-dev] (puppetlabs/puppet) New pull request: Fix storedconfig tests for 1886 and reenable them

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Please review the pull request #92: Fix storedconfig tests for 1886 and > reenable > them opened by (duritong) can we get that merged into 2.7.4? ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1

Re: [Puppet-dev] ANNOUNCE: Puppet 2.7.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > c315da0 Fix #1886 - Add node cleanup capability unfortunately this capability was introduced only partially... :( ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

Re: [Puppet-dev] [PATCH/puppet 1/1] (Maint.) Disable cleaning of storeconfigs.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > We do want to re-enable this functionality, and we will get back around to > it. In the meantime, we'd more than welcome any patches regarding this. Ok, thanks for the explanation. I didn't know about that in-house rule. Though, I have to admit th

Re: [Puppet-dev] Pulling the trigger on using GitHub Pull Requests for patch submission (and internal development).

On 08/03/2011 11:32 PM, Jacob Helwig wrote: > I didn't remember seeing a way to get the diff from the v3 API, and I > won't really be able to try things out until I get back to a real > computer. I only saw ways to get which files changed, and which commits > are part of a pull request. If you know

Re: [Puppet-dev] Pulling the trigger on using GitHub Pull Requests for patch submission (and internal development).

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > As I'm sure most people reading this have noticed, we've already > arranged for puppet-dev to receive mail notifications of opened and > closed pull requests. Like it that way, although it would be much more useful if the diff could still be include

Re: [Puppet-dev] [PATCH/puppet 1/1] (Maint.) Disable cleaning of storeconfigs.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/29/2011 12:35 AM, Pieter van de Bruggen wrote: > This feature (and the corresponding tests) were causing intermittent > failures which we were unable to trace. We will reintroduce this > behavior when we can do so without test fragility. This i

Re: [Puppet-dev] [PATCH/puppet 1/1] Fix #1886 - Add node cleanup capability

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I have appended it to our list of Faces issues to work on this week. > Hopefully we should be able to review, test, and merge this fairly > soon. awesome! thanks! ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using

Re: [Puppet-dev] Facter 2.0?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> Facter is one of those things that's never quite worth spending a lot >> of time on, but I still have a lot of things I'd like to do it. >> E.g., I'd love to port most/all of the existing facts to this format, >> and then rebuild the core in a compi

Re: [Puppet-dev] Re: [PATCH 1/1] Add insync? checks to Onyx Point Concat module

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > If you deleted the target, it wont recreated. What is diff(filea,fileb) > returning when one of its arguments does not exist ? it looks like it returns an empty string. I fixed this in my work on the module[1]. ~pete [1] https://github.com/duriton

[Puppet-dev] Re: [Puppet Users] Re: "Open Source Team" planning meeting summary

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi First, I would like to thank for that open process and the commitment you are putting into that. And I'm really excited that there is now a team dedicated to address the things in core puppet. Awesome! Thanks! However, as this thread seemed to bec

Re: [Puppet-dev] testing new puppet versions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> Also it could record compile time etc. so we wouldn't fall into another >> regression as we did with 2.6.0 > > As a note here, we're working on standardized performance testing with a > baseline of manifests so we know when we're introducing perfor

[Puppet-dev] testing new puppet versions - was Re: [Puppet Users] enabling of 'thin_storeconfigs'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi >> I'd avoid any version of puppet that ends in a "0" like the plague if you >> want stability. > > > The project has been steadily improving in this regard, but it's definitely > been a problem. > > I have great hopes for 2.7.0 though, and the

Re: [Puppet-dev] [PATCH/puppet 1/1] Fix #1886 - Add node cleanup capability

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/27/2011 06:05 PM, Peter Meier wrote: > Here is a changeset that adds a new action to the puppet node face. Sorry for sending twice. Somehow I thought the patch got lost as it didn't show up in my inbox nor did it show up in the googl

[Puppet-dev] [PATCH/puppet 1/1] Fix #1886 - Add node cleanup capability

already offer read access for the yaml, this changeset adds the destroy handler which only removes the yaml file for a request. This can be used to remove cached entries. This work is based on the initial work of Brice Figureau Signed-off-by: Peter Meier --- lib/puppet/face/node/clean.rb

[Puppet-dev] [PATCH/puppet 1/1] Fix #1886 - Add node cleanup capability

already offer read access for the yaml, this changeset adds the destroy handler which only removes the yaml file for a request. This can be used to remove cached entries. This work is based on the initial work of Brice Figureau Signed-off-by: Peter Meier --- lib/puppet/face/node/clean.rb

[Puppet-dev] Node cleanup (#1886) as a node face action

so here comes my outstanding migration of the proposed clean app to the new node face. It was pretty straight forward to port it over to the new faces infrastructure. Nick helped me a bit at the puppetcamp to get into it, but still some small bits were missing. As I finally found time to clean t

Re: [Puppet-dev] run mode in faces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Daniel, thanks for your answer. > The only way to specify the run mode is at the very start of the > application; this is one of the limitations of the older Puppet > architecture that we didn't completely excise during the initial move > to faces

[Puppet-dev] run mode in faces?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I tried to port the clean application (#1886) with help of Nick to faces. So far it looks good (POC pushed to my github account), except that faces seem to run in user mode (by default). This is for example likely a problem when we try to figure ou

Re: [Puppet-dev] [PATCH/puppet-dashboard 1/1] (#6988) rpm should include logrotate file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Except that it uses the -D option, so it should be alright. From > install(1): > > -D create all leading components of DEST except the last, then > copy SOURCE to DEST all right, good catch. :) ~pete -BEGIN PGP SIGNATURE- Ve

Re: [Puppet-dev] [PATCH/puppet-dashboard 1/1] (#6988) rpm should include logrotate file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi > +install -Dp -m0644 %{confdir}/%{name}.logrotate $RPM_BUILD_ROOT/%{_sysconfdir}/logrotate.d/puppet-dashboard you should prefix that with the creation of logrotate.d (as usual in RedHat based spec files deploying logrotate files). So this should

Re: [Puppet-dev] [PATCH/puppet 1/1] Fixed #3127 - Fixed gem selection regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > diff --git a/lib/puppet/provider/package/gem.rb > b/lib/puppet/provider/package/gem.rb > index 19414ce..64544db 100755 > --- a/lib/puppet/provider/package/gem.rb > +++ b/lib/puppet/provider/package/gem.rb > @@ -1,5 +1,6 @@ > require 'puppet/provide

Re: [Puppet-dev] [PATCH/facter 1/1] Fixed #5485 - Updated selinux_mode fact

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I've deliberately changed this because the original use of mode from > policy is totally wrong IMHO. I've reached out to the original author > for some feedback on why he chose that but I suspect if anyone is using > it (and I doubt it) the change w

Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 5 available!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> Have you already tested compatibility? I know we did a bunch of work >> on it at one point, but I don't actually remember the current status. > > We've closed a few ruby 1.9.x issues in puppet 2.6.x, such as #2608, > #1849, and some generic syntax

Re: [Puppet-dev] Re: ANNOUNCE: Puppet 2.6.5 - Release Candidate 4 available!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Thanks for putting these together to help get these RCs tested on the > RPM based systems. fyi: I tested all of them and so far no problems, althought rc4 is only for a few seconds in the repo. ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1

Re: [Puppet-dev] Puppetlast command for 2.6?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/24/2011 08:00 PM, Trevor Vaughan wrote: > Is anyone rewriting puppetlast for 2.6? It was quite useful. You can find a rewritten and extended version here: http://git.puppet.immerda.ch/?p=module-puppet.git;a=blob;f=files/master/lastruncheck;h=42

[Puppet-dev] how to deal with "asynchronous" provider actions

Hi so I was currently reworking the floating around Zenoss provider to work properly with Zenoss 3. However, I encountered the following problem: The Webservice-Call (whether it is XMLRPC or REST) to add a device will in Zenoss 3 now create a task on the Zenoss Server, which will add a device. So

Re: [Puppet-dev] indirector caches

> After doing some debugging, I see that even if I specify the > --facts_termunus to be yaml, that puppet is still using active_record (I > traced it through the indirector/indirection#find_in_cache method) to get my > facts from stroredconfigs. Does ignorecache turn this behavor off? How does > in

Re: [Puppet-dev] implementing #1886 - Round III

As announced I'll send a squashed commit, as I assume that nobody reviewed the previous patch so far, hence I assume nobody is interested in the changes I did between these two series. Or is somebody? Thanks for reviewing! Peter We're interested - I promise! There's a huge clinet deadline

[Puppet-dev] implementing #1886 - Round III

so this is round three for #1886. The only changes to the previous patch series are related to the second (Implementation of #1886) patch and are: - lookup exported resources also in the known definitions if we can't find a native type. - don't do anything at all if we don't find a corresponding

[Puppet-dev] [PATCH/puppet 2/2] Fix #1886 - Add node cleanup capability

yaml indirections we already offer read access for the yaml, this changeset adds the destroy handler which only removes the yaml file for a request. This can be used to remove cached entries. This work is based on the initial work of Brice Figureau Signed-off-by: Peter Meier --- lib/puppet

[Puppet-dev] [PATCH/puppet 1/2] Refactor --debug and --verbose into Puppet::Application

As these options should be available to all applications we move them into Puppet::Application. This moves also various initialize and setup code into Puppet::Application. Signed-off-by: Peter Meier --- lib/puppet/application.rb| 22 +++--- lib/puppet/application/agent.rb

Re: [Puppet-dev] [PATCH/puppet 2/2] Fix #1886 - Add node cleanup capability

>> I'm unsure how to do that in the clean app. Any hints how I could get >> the same autoload behavior as one has within the catalog to get it >> outside of any scope etc. working? > > Without going into the full context of what you're doing, the answer to your > final question is pretty straight

Re: [Puppet-dev] [PATCH/puppet 2/2] Fix #1886 - Add node cleanup capability

Hi so I found one issue while using the code a bit more in production: > + def unexport(node) > +# fetch all exported resource > +query = {:include => {:param_values => :param_name}} > +query[:conditions] = ["exported=? AND host_id=?", true, node.id] > + > +Puppet::Rails::Resourc

[Puppet-dev] [PATCH/puppet 2/2] Fix #1886 - Add node cleanup capability

yaml indirections we already offer read access for the yaml, this changeset adds the destroy handler which only removes the yaml file for a request. This can be used to remove cached entries. This work is based on the initial work of Brice Figureau Signed-off-by: Peter Meier --- lib/puppet

[Puppet-dev] [PATCH/puppet 1/2] Refactor --debug and --verbose into Puppet::Application

As these options should be available to all applications we move them into Puppet::Application. This moves also various initialize and setup code into Puppet::Application. Signed-off-by: Peter Meier --- lib/puppet/application.rb| 22 +++--- lib/puppet/application/agent.rb

[Puppet-dev] implementing #1886 - Round II

First: Sorry that it took me such a long time to integrate all your comments. This was mainly because I was busy with a lot of other things. However, the indirector is sometimes still a big magic part of the puppet framework for me. But, I think, that with the work for these changes I gain more ins

Re: [Puppet-dev] New Feature request/idea

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi > Anyways, I thought that since there is a sha1 already implemented why > not add a sha2 function into puppet to provide a more secure and > better hashing algorithm as another more secure option as well. Thanks for your proposal. The best way to

Re: [Puppet-dev] [PATCH/puppet 2/2] fix #5392 - do not evaluate empty collections

> Whoops, somehow I failed to notice that you updated the ticket last week. > Thanks for reminding me about it. No problem. > I'll update the ticket title to clarify > that the problem is the error message. I can't guarantee how soon we can > get to fixing it, but fixing error messages is prett

Re: [Puppet-dev] [PATCH/puppet 2/2] fix #5392 - do not evaluate empty collections

On 12/07/2010 07:58 PM, Paul Berry wrote: > It looks like this may not be the bug we thought. See comments on > http://projects.puppetlabs.com/issues/5392 Paul: I'm not sure if I find time to address this problem on my own. So if you think you have solution at hand, go for it. ~pete -- You rec

Re: [Puppet-dev] Another try to implement #1886

Hi Paul and Jesse, > Thanks for working on this long-standing feature request. Jesse Wolfe and I > reviewed the code, and there are a few issues that would need to be > addressed before we can merge the patches into the codebase. thanks for looking at my patch. It took me some time to revise you

Re: [Puppet-dev] Optimizing the catalog which is sent to the client

> However, there are a few technical hurdles we need to cross before we > can do it in the core. In particular, we need to resolve all > relationships before we trim the catalog in this way - e.g., someone > can currently depend on one of those wrapping definitions, and if you > just remove that w

[Puppet-dev] Optimizing the catalog which is sent to the client

Hi so I just created #5464 - One reason is that I still have the old thread regarding optimizing file resource calls in mind [1]. Another issue which might be related to this feature request and which might be addressable through this feature request, is something with which I was recently confro

Re: [Puppet-dev] [PATCH/puppet 1/2] refactoring towards fixing #5392

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > This isn't the same behavior, is it? This will only ever result in a > single flat array, whereas we previously could have returned arrays > of arrays, right? Don't you mean flatten? compact: [1] Returns a copy of self with all nil elements rem

[Puppet-dev] [PATCH/puppet 5/5] Finish implementation of #1886

* Rename application to new puppet application style * Adapt tests * Minor fixes that occured during usage Signed-off-by: Peter Meier --- lib/puppet/application/clean.rb | 119 + lib/puppet/application/puppetclean.rb| 118 - lib/puppet/indirector

[Puppet-dev] [PATCH/puppet 4/5] Unlink only existing files

To not blindly remove files and therefore maybe getting an exception we check first on the existance of the file. Signed-off-by: Peter Meier --- lib/puppet/indirector/yaml.rb |3 ++- spec/unit/indirector/yaml_spec.rb | 16 +++- 2 files changed, 13 insertions(+), 6

[Puppet-dev] [PATCH/puppet 2/5] Adding destroy method for Yaml indirector

From: Brice Figureau we already offer read access for the yaml, this changeset adds the destroy handler which only removes the yaml file for a request. This can be used to remove cached entries. Signed-off-by: Brice Figureau Signed-off-by: Peter Meier --- lib/puppet/indirector/yaml.rb

[Puppet-dev] [PATCH/puppet 3/5] Add a destroy method for the various reports processor types.

From: Brice Figureau Yet, only the store reports has an implementation. Signed-off-by: Brice Figureau Signed-off-by: Peter Meier --- lib/puppet/indirector/report/processor.rb | 10 +- lib/puppet/reports/log.rb |3 ++ lib/puppet/reports/rrdgraph.rb

[Puppet-dev] [PATCH/puppet 1/5] Fix #1886 - Add node cleanup capability

Signed-off-by: Brice Figureau Signed-off-by: Peter Meier --- bin/puppetclean | 65 + lib/puppet/application/puppetclean.rb | 118 + spec/unit/application/puppetclean.rb | 235 + 3 files changed, 418 insertions(+), 0

  1   2   3   4   >