On 11-01-31 01:09 PM, Nan Liu wrote:
I've done a quick test to print (notify{}) the value of $vardir and it's
empty. Do you guys know of a way I could access this value within the
module's manifests?
Yeah, that would make manifests a lot more flexible. Here's a function
that should work for
On 11-02-01 04:16 AM, R.I.Pienaar wrote:
Since 2.6.0 you can just do notice($settings::vardir)
oh .. I've just tried it out and it works. hurray for 2.6, then! :)
and, I'll also keep Nan Liu's suggestion in mind for 0.25.x
Thanks to everyone for the feedback!
--
Gabriel Filion
--
You
On 02/01/2011 04:01 PM, walexey wrote:
hello everybody!
server:
[awasilyev@puppet ~]$ rpm -q puppet-server
puppet-server-2.6.4-0.7.el5
client:
[root@opensource ~]# rpm -q puppet
puppet-2.6.4-0.7.el5
[root@opensource ~]# puppetd -t
info: Creating a new SSL key for
Nigel Kersten:
On Wed, Feb 2, 2011 at 5:10 PM, Daniel Pittman dan...@puppetlabs.com wrote:
(Also, I went looking and found zero attempts to solve this in a
reusable, FOSS way, let alone working solutions.)
Yep. I've been dreaming of a Puppet-integrated Password Safe for a while :)
Alas!
Martijn Grendelman:
Would you be so kind to post the solution you cho(o)se in the end? I
am interested in this too.. Thank you!
I'm afraid I chose a rather less glamorous solution to a very specific
problem. It suddenly occurred to me that for the majority of my needs
would be served by
On Wed, Feb 2, 2011 at 1:52 PM, Ashley Gould ago...@ucop.edu wrote:
On Mon, Jan 31, 2011 at 06:27:20PM -0800, Daniel Pittman wrote:
In the longer term I would hope to have that information pushed out
from the puppet system, so that if a node *should* be joined with
centrifyDC puppet will make
On Feb 2, 1:12 pm, robertbogdon robertbog...@gmail.com wrote:
I'm running into a bizarre issue. What it boils down to is that when
I start tomcat through puppetd, certain UTF-8 settings do not appear
to take effect and the end result is garbage characters on a web
page. However, when we
On Thu, Feb 3, 2011 at 2:39 AM, Matthew Macdonald-Wallace
li...@truthisfreedom.org.uk wrote:
I'm also wondering what impact the move would have on our puppet
manifests. Are there any gotcha's that I need to be aware of that
could prevent my current manifests working under 2.6.2 or 0.24.5?
I
OK, thanks, that answers the question about whether we can go
backwards (we can't, we're using Regexes and a few other things!)
Anyone know if a Puppet 2.6.2 client can talk to a 0.25.4 puppet master?
M.
On 3 February 2011 15:18, Adam Heinz a...@metricwise.net wrote:
On Thu, Feb 3, 2011 at
On 02/03/2011 04:46 PM, Matthew Macdonald-Wallace wrote:
OK, thanks, that answers the question about whether we can go
backwards (we can't, we're using Regexes and a few other things!)
Anyone know if a Puppet 2.6.2 client can talk to a 0.25.4 puppet master?
Newer masters will entertain older
We're looking at /proc/pid/environ to see the environment of the
tomcat process. We're not using SELinux, and in this case everything
is being run by root, though tomcat does switch over to a tomcat user
at some point during it's startup. What really confuses me is why it
works in with all of
Should I be able to use the built-in tag function...
define nagios::host($hostgroups) {
tag environment:$environment
nagios_host { $name:
address = $ipaddress_eth0,
contact_groups = ops,
hostgroups = $hostgroups,
notify = Service[nagios],
require = File[/etc/nagios/hosts],
target =
Hi,
I want to execute multiple sed commands using the exec commands within
puppet. I can only setup one command parameter. For now i have to give
a long list of commands separated with ; in order to use the single
command parameter. I know there are other efficient ways to solve this
problem.
Are you able to group these sed statements into a script and pass arguments to
the script to do whatever set of executions are needed for that specific
dataset?
I may not understand your 'need' exactly, either. Can you explain more of what
you are trying to accomplish and less about what
While it's perfectly appropriate to have multiple exec{} or a single exec{}
with a multi-line command in your puppet manifest, once you reach a certain
level of complexity you almost invariably want to switch to a
file{/usr/local/scripts: ...} exec{/usr/local/scripts/doit: ...} model.
The
Just FYI...looks like it was an ordering problem in auth.conf. I did
not know that this file was ordered. Entries in this file have to be
*before*
path /
auth any
On Feb 2, 4:27 pm, rjl rjlin...@gmail.com wrote:
One more piece of infolisten = true in my puppet.conf file on the
clients.
On Thu, Feb 3, 2011 at 08:23, linuxbsdfreak linuxbsdfr...@gmail.com wrote:
I want to execute multiple sed commands using the exec commands within
puppet. I can only setup one command parameter. For now i have to give
a long list of commands separated with ; in order to use the single
command
The only substantial differences in execution environment between
those two should be that the daemon is running in a distinct session
from your shell, has a CWD of '/', and has std{in,out,err} open to
/dev/null.
The rest of the code is identical; it might be interesting to find out
if the
Hi All,
I'm trying to implement a template (for my collectd config) that gives
different results depending on the other modules included on that machine.
I tried to do this by checking for the class tags but it turns out that due
to bug #3049 this is a huge pain and 90% of the time the tags aren't
On Thursday, February 3, 2011 at 9:53 AM, Adam Gibbins wrote:
Hi All,
I'm trying to implement a template (for my collectd config) that gives
different results depending on the other modules included on that machine.
I tried to do this by checking for the class tags but it turns out that due
Add a fact that's derived from parsing /var/lib/puppet/state/classes.txt. It
will be exactly one run behind, but it will have the complete list of classes
as of the previous run and it's reliable.
On Feb 3, 2011, at 9:58 AM, Richard Crowley wrote:
On Thursday, February 3, 2011 at 9:53 AM,
On 3 February 2011 17:58, Richard Crowley r...@rcrowley.org wrote:
On Thursday, February 3, 2011 at 9:53 AM, Adam Gibbins wrote:
Hi All,
I'm trying to implement a template (for my collectd config) that gives
different results depending on the other modules included on that machine.
I tried
On Feb 3, 2011, at 10:22 AM, Adam Gibbins wrote:
On 3 February 2011 18:14, Brian Gallew g...@gallew.org wrote:
Add a fact that's derived from parsing /var/lib/puppet/state/classes.txt. It
will be exactly one run behind, but it will have the complete list of classes
as of the previous run
The other alternative is to call the tag function in a node but it seems the
tag is not inherited so rather than defining the tag in the default node, I'd
have to do so in every node. The lack of inheritance seems to be by design so
I'm fine using a define if I can get it to work.
I am led
I have the class below to export host entries.
However I wish to override the entry for my host to 127.0.0.1
So for all of the hosts other than foo.bar.com I would like them to
have the real IP address but for foo.bar.com I would like to just have
the loopback host entry. 2.6.2 doesn't allow
Hi,
I sometimes get a strange problem with some user's authorized_keys file.
The file should belong to user:users_group but puppet sets it as
root:root:
i.e:
err: /Stage[os]/Computing_ssh/Ssh_authorized_key[neuro...@si.pic.es]:
Could not evaluate: Permission denied -
Hi All,
I'm in the process of creating Puppet modules for my load balanced
environment. I have multiple Apache nodes behind a load balancer and each
Apache virtual host has its own internal IP. I've created an Apache module
that does this by creating an Apache vhost template and define my own
On Wed, Feb 2, 2011 at 11:12 AM, robertbogdon robertbog...@gmail.com wrote:
I'm running into a bizarre issue. What it boils down to is that when
I start tomcat through puppetd, certain UTF-8 settings do not appear
to take effect and the end result is garbage characters on a web
page.
We would like to have a default node applied to systems, but also
trigger a failure so that we notice the system in puppet-dashboard.
At the moment we're doing...
node default {
include system_defaults
fail($hostname doesn't have a node to apply to it)
}
Unfortunately this seems to fail
On Thu, Feb 3, 2011 at 7:02 PM, Rich Rauenzahn rraue...@gmail.com wrote:
We would like to have a default node applied to systems, but also
trigger a failure so that we notice the system in puppet-dashboard.
At the moment we're doing...
node default {
include system_defaults
30 matches
Mail list logo
