Le jeudi 11 novembre 2010 à 06:09 -0800, Tim a écrit :
> Hi,
Hello,
> Anyway what other approaches are there? I'd like to simply see 2
> things:
> 1) If there were any failures during the puppet run on the client
> 2) When the last puppet run on each client was (ie. if it was more
> than 50 mins
Hi Kent,
Thanks for bringing this issue to our attention. I have recreated and filed
the following ticket:
http://projects.puppetlabs.com/issues/5318
Feel free to watch the ticket to track the progress of the issue.
-Dan
--
You received this message because you are subscribed to the Google Gr
Eric Sorenson writes:
> On Nov 15, 2010, at 9:53 PM, Daniel Pittman wrote:
>
>> Otherwise, we use code review before committing to the central repository
>> to help reduce the risk of issues - now *two* operations people need to be
>> ignorant of class C for the issue to pop up.
>
> Hi Daniel - it
On Nov 15, 2010, at 9:53 PM, Daniel Pittman wrote:
> Otherwise, we use code review before committing to the central repository to
> help reduce the risk of issues - now *two* operations people need to be
> ignorant of class C for the issue to pop up.
Hi Daniel - it's a bit off-topic from the ori
Yushu Yao writes:
>> > Just wondering is there a way to work around this?
>>
>> Define the service in a third class and include that third class in each of
>> the first two.
>>
>> class a { include c } class b { include c } class c { service {
>> "foobar": } }
>>
>> Classes can be in
On Mon, Nov 15, 2010 at 9:16 PM, Yushu Yao wrote:
>
>
>
>>
>> Why do both classes need to have the same service defined?
>>
> Simple use case:
>
> Want to define two apache based web services on the same server. (e.g.
> passenger + turbogears)
>
> I think module-based definitions are the key conce
> > Just wondering is there a way to work around this?
>
> Define the service in a third class and include that third class in
> each of the first two.
>
> class a {
>include c
> }
> class b {
>include c
> }
> class c {
>service { "foobar": }
> }
>
> Classes can be included multiple tim
> Why do both classes need to have the same service defined?
>
> Simple use case:
Want to define two apache based web services on the same server. (e.g.
passenger + turbogears)
I think module-based definitions are the key concept behind puppet (no?), so
we use one module for turbogears, another m
You have to use
@@sshkey { $fqdn:
type => rsa,
key => $sshrsakey,
host_aliases => [ $hostname, $ipaddress],
}
The following happened:
Puppet joins resourcename and hostaliases with a "," to put it in the
file. Because you put everything in the resourcename you end up with
$fqdn,$hostname,$i
On Nov 15, 11:11 am, "sanjiv.singh"
wrote:
> 1) Is there any machnism in which we can select puppet modules
> according to build number..?
Look at the support for modulepath with multiple environments[1]. You
can set the "environment" value to any string. So you can use revision
numbers or tags
On Mon, Nov 15, 2010 at 3:08 PM, Yushu Yao wrote:
> Hi Experts,
>
> I define two classes, each of them has the same service defined in it, if I
> include both classes for a node it will fail complaining "Duplicated
> definition: Service[xxx]".
Why do both classes need to have the same service def
On Nov 15, 7:09 am, Christopher McCrory wrote:
> Hello...
>
> I've been testing some new servers. I'm using exported resources for
> several configs (see other email on ssh_known_hosts), including the
> nagios tyoes (very cool!). Now I need to retire several test servers.
> How do I 'properly'
> I define two classes, each of them has the same service defined in it, if I
> include both classes for a node it will fail complaining "Duplicated
> definition: Service[xxx]".
>
> Just wondering is there a way to work around this?
Define the service in a third class and include that third class
Hi Experts,
I define two classes, each of them has the same service defined in it, if I
include both classes for a node it will fail complaining "Duplicated
definition: Service[xxx]".
Just wondering is there a way to work around this?
Thank you !
-Yushu
--
You received this message because yo
Thank you!!!
Pretty much that answers my question.
Thanks again.
On Nov 15, 6:56 am, jcbollinger wrote:
> On Nov 12, 12:28 pm, Roberto Bouza wrote:
>
> > Hello,
>
> > Up to right now everything is working great with puppet. I just have
> > one questions.
>
> > Is there a way to tell a type (li
Nick Moffitt:
> # md5sum /home/foo/.ssh/authorized_keys; puppetd --environment=staging
> -t | grep 'checksum changed'; md5sum /home/foo/.ssh/authorized_keys
> fc9e4d3f84f99cff14a16dbe20f0db70 /home/foo/.ssh/authorized_keys
> notice:
> /Stage[main]//Node[central.example.com]/Fi
hi all,
I am working with development environment .( configured puppet +
LDAP )
each day build number changes from X to Y .( there may be changes
in templates and deployable files -addition/ deletion. or in
configuration parameters ).
Once i have configured puppet modules for build numbe
Ever since I've upgraded from 2.6.0 to 2.6.2 I've been randomly
getting the following reports from my clients:
Sun Nov 14 16:13:35 -0600 2010 Puppet (err): Could not retrieve
catalog from remote server: end of file reached Sun Nov 14 16:13:35
-0600 2010 Puppet (notice): Using cached catalog Sun No
Nick Moffitt:
> Further, grepping for a chunk of the options in this resource in the
> clientbucket finds hundreds of entries, and it would appear that all
> possible orderings are coming from the puppetmaster. I realize that
> technically there is a finite limit to the number of permutations, but
Can you ping me on #puppet at freenode? bodepd.
-Dan
On Mon, Nov 15, 2010 at 9:16 AM, Kent wrote:
> Already tried filetimeout=0 with no success.
>
:(
the description for the setting ignorecache in puppet.conf man page:
>
> "
> Ignore cache and always recompile the configuration. This is
>
Already tried filetimeout=0 with no success.
the description for the setting ignorecache in puppet.conf man page:
"
Ignore cache and always recompile the configuration. This is
useful for testing new configurations, where the
local cache may in fact be stale even if the timestamps are up to d
I have found what I believe to be incorrect checksums in state.yaml, and
somewhat wasteful thrashing in the contents of exported
ssh_authorized_key resources (and possibly others).
My ultimate goal is to create a "stop the line" sort of system: if
someone has manually edited a puppet-managed file,
Hi Kent,
On Mon, Nov 15, 2010 at 8:05 AM, Kent wrote:
> Nigel,
>
> It is number-of-runs based. If I execute two runs in rapid succession
> 2 seconds after changing a manifest on the puppetmaster, the new
> config *will* be pushed on the second run. On the other hand I can
> walk away for 10 minu
Nigel,
It is number-of-runs based. If I execute two runs in rapid succession
2 seconds after changing a manifest on the puppetmaster, the new
config *will* be pushed on the second run. On the other hand I can
walk away for 10 minutes and when I then execute the runs, the new
config will still not
Hi,
I've recently upgraded our puppetmaster to 2.6. Mostly, everything is
fine. However, one thing that I've noticed is that a 0.24 client, when
replacing a file, will log the contents of the file in its syslog and
also in its report emails.
Mon Nov 15 14:50:30 + 2010 /Stage[main]/Misc-apps::
In the end I just changed my script to grep for 'Failed' in the
reports YAML files. My script already uses the time of the most recent
report YAML file to detect if it's been too long since the most recent
report (eg. if the puppetd process has died or something).
I'll wait for http://projects.pup
On Nov 12, 12:28 pm, Roberto Bouza wrote:
> Hello,
>
> Up to right now everything is working great with puppet. I just have
> one questions.
>
> Is there a way to tell a type (like file) not to fail if something
> specific happens.
At that level of generality, why would you consider it anything
In this context i have a question.
I migrate an autoyast settings into Puppet modules. Originally users
are created in the autoyast file for SLES9.
Following setting i have for one of my user.
true
Unfortuniatially i can't find such a flag as a parameter for the
puppet 'user' resource.
Christi
Hello...
I've been testing some new servers. I'm using exported resources for
several configs (see other email on ssh_known_hosts), including the
nagios tyoes (very cool!). Now I need to retire several test servers.
How do I 'properly' purge the exported data for these test servers from
the mys
Hello...
Is this a bug or by design?
I'm using exported resources to generate /etc/ssh/ssh_known_hosts. I
changed the example from the docs to this:
@@sshkey {
"$fqdn,$hostname,$ipaddress": type => rsa,
key => $sshrsakey,
}
so that I would get one line per host in t
Hi
the Swiss Puppet User Group (SPUG) [1] will meet the next time this
Wednesday around 19 o'clock in Bern [2].
Please note that you should announce yourself to the hosters so that you
can get in.
If you have any cool things to present to the local puppet community:
Bring your slides!
Cu there!
31 matches
Mail list logo
