More information along these lines, highlighting ease of use and
tools for users to see their catalogs, will go along way towards soothing us
touchy sysadmins.
Totally understand, I was a very touchy admin myself before working at
Puppet Labs and when the tools let you down it can be
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.
Python support would be lovely.
I'm new to puppet and hope somebody can help me. I have a master server with
a few Mac and Windows Agents. I created a custom fact for windows that will
show the current logged in users Sid. I have a manifest that will edit the
HK Users registry Keys. My issue is when I run the agent it fails
Puppet Version : 2.7.25
So I don't get it at all..
snip
err: Could not apply complete catalog: Found 1 dependency cycle:
(Exec[chown_logdir] = Class[Jetty] = User[evolve] = Exec[chown_logdir])
Cycle graph written to /var/lib/puppet/state/graphs/cycles.dot.
/snip
Cycle graph
digraph
On Saturday, September 27, 2014 12:48:01 PM UTC-5, Jason Antman wrote:
Not built-in to puppet, but this should be trivial to do with nmap or a
similar tool and a list of the nodes that *are* running puppet.
No, not at all. With nmap you could probably identify nodes running the
puppet
On Monday, September 29, 2014 5:28:18 AM UTC-5, omfg9899 wrote:
Puppet Version : 2.7.25
So I don't get it at all..
snip
err: Could not apply complete catalog: Found 1 dependency cycle:
(Exec[chown_logdir] = Class[Jetty] = User[evolve] = Exec[chown_logdir])
Cycle graph written to
On Sep 25, 2014 6:02 AM, Johan De Wit jo...@open-future.be wrote:
For rspec unit testing, one must keep in mind that you are testing the
content of the catalog.
For *rspec-puppet* unit testing, that is.
There is also *rspec-puppet-augeas*, but unfortunately it requires a
downrev of
On Mon, Sep 22, 2014 at 10:07 AM, Britt Gresham br...@puppetlabs.com
wrote:
Hello,
We are interested in collecting puppet profile data from the puppet master
in the real world. This data will be used to help us find a direction to go
to increase the throughput of the puppet master master.
Not sure what about my attitude you do not like.. /me scratches head..
But anyway.
Everything you have posted is accurate and when I took a closer look at
graph output I realized that something was trying to set the permissions
on the log directory a second time. After some searching I
I came a across this post and like what I see but would off the following
addition to Ian's suggestion so that the expire cache is not executed on
every puppet run.
exec { 'yum-clean-expire-cache':
command = '/usr/bin/yum clean expire-cache',
refreshonly = true,
}
package
On Sun, Sep 28, 2014 at 6:25 AM, mohit modi mohitmodi...@gmail.com wrote:
Thanks a bunch for reply.
It would be great if someone can suggest ,do we need dumps too for
preparation.
If you need dumps for preparation then you are not actually
preparing yourself for nothing, you are cheating.
I
On 9/29/14 2:09 AM, Ken Barber wrote:
The information around tuning Passenger/Puppet explicitly provided
by Puppet Labs was mostly crap.
Indeed, it was a bit of a black art because of this. It wasn't until
later that Passenger even added the ability to reasonably introspect
what was
Just to add on things that I'd like to see:
Tuning
- When it's not CPU, it's RAM. What to do when you have massive catalogs
(maybe not an issue?).
Operating
- Proper log rotation and maintenance
Security
- What do I need to let through?
- What do I need to lock down?
- How do I easily split off
On Mon, Sep 29, 2014 at 1:01 PM, Miguel Di Ciurcio Filho
mig...@instruct.com.br wrote:
On Sun, Sep 28, 2014 at 6:25 AM, mohit modi mohitmodi...@gmail.com wrote:
Thanks a bunch for reply.
It would be great if someone can suggest ,do we need dumps too for
preparation.
If you need dumps for
On Thu, Sep 18, 2014 at 2:16 PM, Tim Skirvin tskir...@fnal.gov wrote:
I decided to try out 'parser = future' today, and the first thing
to fail was puppetlabs-apache, with errors along the lines of:
Filepath:
/srv/puppet/env/puppet/modules/apache/templates/httpd.conf.erb
Puppet Server 0.2.1 is a security release. This release addresses
CVE-2014-7170. All users of Puppet Server are encouraged to upgrade as
soon as possible.
** CVE-2014-7170 **
Local information leakage
Due to a packaging bug[1], there is a window between package
installation/upgrade and service
On 2014-30-09 24:30, Hunter Haugen wrote:
On Thu, Sep 18, 2014 at 2:16 PM, Tim Skirvin tskir...@fnal.gov
mailto:tskir...@fnal.gov wrote:
I decided to try out 'parser = future' today, and the first
thing
to fail was puppetlabs-apache, with errors along the lines of:
17 matches
Mail list logo
