Re: [Puppet Users] Re: puppet-dashboard Explorer 8

On 13 August 2010 18:59, ScubaDude wrote: > Ticket filed (bug, refactor) > > On Aug 13, 7:56 am, Matt Robinson wrote: > > We weren't aware as none of us are using Internet Explorer. We'll > > have to have someone get a copy to test with at some point. > > > > Can you file a ticket? > > > > http

Re: [Puppet Users] Wrong module path when using external nodes vs. CLI args

On Mar 22, 2011, at 19:21, Thomas Bellman wrote: > https://projects.puppetlabs.com/issues/3910 Thanks. I can try to work around it for now and watch the ticket for a resolution. -bjc -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post t

Re: [Puppet Users] RFC: Refactoring the mount provider.

On Tue, Mar 22, 2011 at 4:05 PM, Stefan Schulte wrote: > So splitting the mounttype can lead to better reports when puppet sync > mountpoint and entry in fstab seperatly. Because I'm lazy I'll propably > write a define (maybe I will call it mount) that will create two > resources for the two new

Re: [Puppet Users] Wrong module path when using external nodes vs. CLI args

Brian Cully wrote: When I run puppet with --environment=development everything works great. When I use my external none classifier which sets the environment, for some reason, puppet uses the wrong module path for file references even though my puppetmasterd log shows that it compiled the catalo

Re: [Puppet Users] RFC: Refactoring the mount provider.

On Tue, Mar 22, 2011 at 09:19:16PM +0100, Thomas Bellman wrote: > Nigel Kersten wrote: > > > TL;DR The mount provider has used a mish-mash of checking fstab and > > actual mount state to determine state. A possible solution we're > > looking at is splitting into two types, one that manages /etc/fs

[Puppet Users] Wrong module path when using external nodes vs. CLI args

I've started using the environment capabilities with puppet and set up a [development] environment which points the modulepath to /etc/puppet/development/modules. The [main] section puts it in /etc/puppet/modules. When I run puppet with --environment=development everything works great. When I

Re: [Puppet Users] RFC: Splitting up the file{} type functionality.

On Tue, Mar 22, 2011 at 3:06 PM, Christian Kauhaus wrote: > Am 22.03.2011 02:53, schrieb Nigel Kersten: >> >> The intersection of files and directories isn't that big a deal, but >> we could split out directories too if we wanted. > > From the user's perspective, it's more like the other way round

Re: [Puppet Users] RFC: Splitting up the file{} type functionality.

Am 22.03.2011 02:53, schrieb Nigel Kersten: The intersection of files and directories isn't that big a deal, but we could split out directories too if we wanted. From the user's perspective, it's more like the other way round. We should not let implementation issues guide the design of the man

RE: [Puppet Users] augeas slooow

Oho, this --evaltrace is what I was looking for. Thanks! > -Original Message- > From: puppet-users@googlegroups.com [mailto:puppet- > us...@googlegroups.com] On Behalf Of Nigel Kersten > Sent: Tuesday, March 22, 2011 4:40 PM > To: puppet-users@googlegroups.com > Cc: saurabh verma > Subject

Re: [Puppet Users] augeas slooow

On Tue, Mar 22, 2011 at 1:24 PM, saurabh verma wrote: >> >> >> How can I profile my Puppet catalog, to see what resources take the >> longest to set straight? (I've only got puppet apply for now - no master >> yet) >> >> -- > > +1 for profiling feature More than --evaltrace ? > > -- > You rec

Re: [Puppet Users] Testing changes before deployment

I actually wrote up a post about using multiple environments for this purpose. It includes the process flow chart as well. http://cwebber.ucr.edu/2011/03/multiple-environments-in-puppet/ --cwebber On 3/22/11 2:10 PM, "Thomas Bellman" wrote: >Giovanni Bordello wrote: > >> But what if I need to

Re: [Puppet Users] Testing changes before deployment

Giovanni Bordello wrote: But what if I need to do a web-server specific change? And then Mail-server specific change? If I had only one test client machine I would have to reinstall it every time I needed to do verify a change for a different group of servers. That's hardly a way to go. There

Re: [Puppet Users] Re: parameterized classes and variable inheritance

On Mon, Mar 21, 2011 at 01:05:56PM -0700, jcbollinger wrote: > > On Mar 21, 1:20 pm, Ashley Gould wrote: > > Please forgive my ignorance.  I find myself, a linux admin brought > > up on howtos and books with animals on the cover, suddenly plunged > > by puppet into a world of developers and compu

Re: [Puppet Users] Foreman 0.2 Release Candidate

Ohad Levy wrote: > Hello All, > > I'm happy to announce a new release candidate of Foreman, top highlights > for this release includes: > Ohad Awesome stuff. Just had a play with it and very impressed. Cheers James -- James Turnbull Puppet Labs 1-503-734-8571 -- You received this message

Re: [Puppet Users] Foreman 0.2 Release Candidate

I replaced all shbangs in the tarball, with REE, still no go! what binary would be liked to /usr/bin/ruby in the forman tree? cd /usr/src/redhat/SOURCES tar jzvf foreman-0.2rc1.tar.bz2 cd forman grep -lr '#!/usr/bin/env ruby' . | xargs sed -i -e 's|/usr/bin/env ruby|/opt/ruby-enterprise/bin/ruby|

Re: [Puppet Users] Foreman 0.2 Release Candidate

On 03/22/2011 04:32 PM, Ohad Levy wrote: On Tue, Mar 22, 2011 at 10:28 PM, Cody Robertson > wrote: On 03/22/2011 04:23 PM, Ohad Levy wrote: On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini mailto:scarpell...@gmail.com>> wrote: Super coo

Re: [Puppet Users] Foreman 0.2 Release Candidate

On Tue, Mar 22, 2011 at 10:23 PM, Ohad Levy wrote: > > > On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini < > scarpell...@gmail.com> wrote: > >> Super cool, Ohad. >> Is there a RPM for this RC? >> > http://yum.theforeman.org/test/RPMS/foreman-0.2-rc1.1.noarch.rpm > > Ohad > Note that the

Re: [Puppet Users] Foreman 0.2 Release Candidate

On Tue, Mar 22, 2011 at 10:28 PM, Cody Robertson wrote: > On 03/22/2011 04:23 PM, Ohad Levy wrote: > > > On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini < > scarpell...@gmail.com> wrote: > >> Super cool, Ohad. >> Is there a RPM for this RC? >> > http://yum.theforeman.org/test/RPMS/forem

Re: [Puppet Users] Foreman 0.2 Release Candidate

On 03/22/2011 04:23 PM, Ohad Levy wrote: On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini mailto:scarpell...@gmail.com>> wrote: Super cool, Ohad. Is there a RPM for this RC? http://yum.theforeman.org/test/RPMS/foreman-0.2-rc1.1.noarch.rpm The version of rubygem-rest-client

Re: [Puppet Users] Foreman 0.2 Release Candidate

On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini < scarpell...@gmail.com> wrote: > Super cool, Ohad. > Is there a RPM for this RC? > http://yum.theforeman.org/test/RPMS/foreman-0.2-rc1.1.noarch.rpm Ohad > On Mar 22, 2011 4:52 PM, "Martin Willemsma" wrote: > > Thanks guys. Really cool ne

Re: [Puppet Users] Foreman 0.2 Release Candidate

RPM checks the linked libraries (ldd) and some shbangs (#!) in buildtime (rpmbuild). These deps could came from these ruby-ee shbang paths. On Mar 22, 2011 5:14 PM, "Mohamed Lrhazi" wrote: > am trying to rebuild the source rpm to remove deps on ruby, as i use > entreprise-ruby... > the resulting r

Re: [Puppet Users] augeas slooow

> > > How can I profile my Puppet catalog, to see what resources take the > longest to set straight? (I've only got puppet apply for now - no master > yet) > > -- +1 for profiling feature -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To

Re: [Puppet Users] Re: Trying to set up per-environment manifest file

I use this pattern: [master] templatedir = /etc/puppet/environments/$environment/ modulepath = /etc/puppet/environments/$environment/modules manifest= /etc/puppet/environments/$environment/manifests/site.pp manifestdir = /etc/puppet/environments/$environment/manifests On

Re: [Puppet Users] RFC: Refactoring the mount provider.

Nigel Kersten wrote: TL;DR The mount provider has used a mish-mash of checking fstab and actual mount state to determine state. A possible solution we're looking at is splitting into two types, one that manages /etc/fstab (or /etc/filesystem on other OSes), and one that manages actual mount stat

Re: [Puppet Users] RFC: Splitting up the file{} type functionality.

What initially attracted me to puppet wast that puppet described state and not (in general) actions to achieve that state. Yet, I, too, was initially confued that to manage symlinks I needed to manage "files" which had something to "ensure" called "symlink". To make sure a directory is absent I hav

Re: [Puppet Users] Foreman 0.2 Release Candidate

am trying to rebuild the source rpm to remove deps on ruby, as i use entreprise-ruby... the resulting rpm still instisi it needs ruby... were does that dep come from? during install: Resolving Dependencies --> Running transaction check ---> Package foreman.noarch 0:0.2-rc1.1 set to be updated -->

Re: [Puppet Users] Foreman 0.2 Release Candidate

Super cool, Ohad. Is there a RPM for this RC? On Mar 22, 2011 4:52 PM, "Martin Willemsma" wrote: > Thanks guys. Really cool new features to try out tomorrow! > > I would love to see the unattended installation part replace our deployer > solution which is currently installing hosts 1 by 1. > > --

[Puppet Users] Re: RFC: Splitting up the file{} type functionality.

On Mar 22, 10:10 am, Nigel Kersten wrote: > On Tue, Mar 22, 2011 at 7:20 AM, jcbollinger > wrote: > > > On Mar 21, 8:53 pm, Nigel Kersten wrote: > >> The file{} type can do all of the following: > > >> * manage single files > >> * manage directories > >> * manage symlinks > >> * manage recurs

[Puppet Users] Re: RFC: Splitting up the file{} type functionality.

On Tue, Mar 22, 2011 at 12:39 PM, Jeffrey Goldschrafe wrote: > On Monday, March 21, 2011 9:53:26 PM UTC-4, Nigel Kersten wrote: >> >> The file{} type can do all of the following: >> >> * manage single files >> * manage directories >> * manage symlinks >> * manage recursive file copies >> >> The in

Re: [Puppet Users] Foreman 0.2 Release Candidate

Thanks guys. Really cool new features to try out tomorrow! I would love to see the unattended installation part replace our deployer solution which is currently installing hosts 1 by 1. -- Kind regards, Martin Willemsma 2011/3/22 Ohad Levy > Hello All, > > I'm happy to announce a new releas

[Puppet Users] Re: Trying to set up per-environment manifest file

Thanks Cody. The client's environment does need to be set, either through the puppet.conf or on the command line, but the environments also need to be defined on the master, as far as I know. On Mar 22, 12:46 pm, Cody Robertson wrote: > On 03/22/2011 03:41 PM, elliott wrote: > > > > > > > > > >

Re: [Puppet Users] Trying to set up per-environment manifest file

On 03/22/2011 03:41 PM, elliott wrote: Hi guys, I've had separate development/testing environments partially working for a while, in that modules get pulled from the correct per- environment path. However, something that has never seemed to work was a per-environment manifest. I have more need

[Puppet Users] Trying to set up per-environment manifest file

Hi guys, I've had separate development/testing environments partially working for a while, in that modules get pulled from the correct per- environment path. However, something that has never seemed to work was a per-environment manifest. I have more need for this now so I'd like to track it dow

[Puppet Users] Re: RFC: Splitting up the file{} type functionality.

On Monday, March 21, 2011 9:53:26 PM UTC-4, Nigel Kersten wrote: > > The file{} type can do all of the following: > > * manage single files > * manage directories > * manage symlinks > * manage recursive file copies > > The intersection of all these bits of functionality makes it difficult > to und

Re: [Puppet Users] Listing puppet modules

Nice, thanks guys .. On Tue, Mar 22, 2011 at 2:05 PM, Cody Robertson wrote: > On 03/22/2011 02:51 PM, hai wu wrote: > >> Is there a commond to list all puppet modules applied for a certain node? >> I tried puppet-concat (motd-register), but it is not working if some >> puppet module is in some r

Re: [Puppet Users] Listing puppet modules

Our puppet agent stores classes.txt in /var/puppet/state/ ~Charles~ On Tue, Mar 22, 2011 at 1:51 PM, hai wu wrote: > Is there a commond to list all puppet modules applied for a certain node? > > I tried puppet-concat (motd-register), but it is not working if some puppet > module is in some run

Re: [Puppet Users] Re: RFC: Splitting up the file{} type functionality.

On Tue, Mar 22, 2011 at 08:10:40AM -0700, Nigel Kersten wrote: > On Tue, Mar 22, 2011 at 7:20 AM, jcbollinger > wrote: > > > > > > On Mar 21, 8:53 pm, Nigel Kersten wrote: [...] > >> Thoughts? > > > > I agree that File is a mishmash, but I don't think symlinks and > > recursive copying are the k

[Puppet Users] augeas slooow

I've got somewhere around 130 Augeas resources in my policy (catalog, entire set of manifests, what-have-you) and 11 custom lenses, each for only one or two files, and it takes like 2 1/2 minutes to apply the whole thing. Looking at the --debug output, there are a whole lot of pauses right after "o

Re: [Puppet Users] Listing puppet modules

On 03/22/2011 02:51 PM, hai wu wrote: Is there a commond to list all puppet modules applied for a certain node? I tried puppet-concat (motd-register), but it is not working if some puppet module is in some run stage that is before or after "main" run stage. Is there another way to show all pupp

[Puppet Users] Listing puppet modules

Is there a commond to list all puppet modules applied for a certain node? I tried puppet-concat (motd-register), but it is not working if some puppet module is in some run stage that is before or after "main" run stage. Is there another way to show all puppet modules to be applied for each puppet

Re: [Puppet Users] add all group members to file

I think you would have each host export @@host { $fqdn: ..., tag => 'mygroup', } then also have each host consume those hosts Host <<| tag == 'mygroup' |>> On Tue, Mar 22, 2011 at 7:40 AM, danh wrote: > Hello all, > > I am trying to work out how to populate "/etc/hosts" with the IPs and

Re: [Puppet Users] about http basic authentication dashboard

On 03/22/2011 04:34 PM, chp wrote: > Hi, > > I am running dashboard 1.1.0rc1 under passenger 3.0.5 and apache 2.2.3 > with puppet 2.6.6. Im trying to get urls like this > > http://user:password@host > > working as suggested in the docs for reporting but atm i did not get > it (401 auth requided)

[Puppet Users] about http basic authentication dashboard

Hi, I am running dashboard 1.1.0rc1 under passenger 3.0.5 and apache 2.2.3 with puppet 2.6.6. Im trying to get urls like this http://user:password@host working as suggested in the docs for reporting but atm i did not get it (401 auth requided). Maybe I am forgetting something? I use a common .h

[Puppet Users] Foreman 0.2 Release Candidate

Hello All, I'm happy to announce a new release candidate of Foreman, top highlights for this release includes: * New look and feel * Extended restful API * Support for New Puppet Reports format * Full VM/physical host Provisioning * Powerful template generator ( pxelinux, gpxe, kickstart, preseed

Re: [Puppet Users] Re: RFC: Splitting up the file{} type functionality.

On Tue, Mar 22, 2011 at 7:20 AM, jcbollinger wrote: > > > On Mar 21, 8:53 pm, Nigel Kersten wrote: >> The file{} type can do all of the following: >> >> * manage single files >> * manage directories >> * manage symlinks >> * manage recursive file copies >> >> The intersection of all these bits of

[Puppet Users] Re: RFC: Splitting up the file{} type functionality.

On Mar 21, 8:53 pm, Nigel Kersten wrote: > The file{} type can do all of the following: > > * manage single files > * manage directories > * manage symlinks > * manage recursive file copies > > The intersection of all these bits of functionality makes it difficult > to understand exactly what is

[Puppet Users] Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

Nigel Kersten: > The file{} type can do all of the following: > > * manage single files > * manage directories > * manage symlinks > * manage recursive file copies I tend to use different defaults for the different types, so I would love to be able to do: File { mode => 0444 } Di

[Puppet Users] add all group members to file

Hello all, I am trying to work out how to populate "/etc/hosts" with the IPs and names of all nodes in a group. For instance, I define a node "webserver" and derive all my webservers from it so I want to populate "/etc/hosts" with the IPs and names of all the nodes that derive from "webserver".

Re: [Puppet Users] Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

On Mon, Mar 21, 2011 at 09:06:51PM -0700, James Turnbull wrote: > Nigel Kersten wrote: >> The file{} type can do all of the following: >> * manage symlinks >> How would people feel about at least splitting out these into their own >> types? >> >> * symlinks > On a final note ... can we not overl

Re: [Puppet Users] parameterized classes and variable inheritance

> Hi, > > is it me, or is class sudoers not actually parameterized? Gah! It *is* me and my sort of ambiguous font. Never mind that bit then: > What I'm seeing is a good old class with local variables. The way they > are initialized, they cannot even be overridden by (ab-)using dynamic > scoping,

Re: [Puppet Users] parameterized classes and variable inheritance

> node default { > class { sudoers: } > } > > node 'sl11lab02' inherits default { > > # this runs but does nothing > Class[sudoers] { additional_rules => [ "$rules_uas" ] } > > # this errors with "Cannot assign to variables in other namespaces" > #$sudoers::additional_rules =

Re: [Puppet Users] Client no longer reads catalog

On 03/16/2011 03:48 PM, Dennis Jacobfeuerborn wrote: > Hi, > One of my machines has started to refuse reading the catalog from the > server. The log shows the following: > > Mar 16 15:36:42 wmembf10 puppetd[7411]: Starting Puppet client version > 0.25.5 > Mar 16 15:36:46 wmembf10 puppetd[7411]: