On Mon, Nov 2, 2009 at 9:49 PM, Digant C Kasundra wrote:
>
>
> - "Trevor Vaughan" wrote:
>
> > All,
> >
> > I'm looking for a way to obtain information about the managed
> > services
> > on a given client system.
> >
> > Basically, some way to know what services have been enabled by Puppet
>
Brandon Evans wrote:
> Thanks for the RPMs Todd. You may want to consider packing the
> puppet-0.25.1/conf/auth.conf into the RPM also. It is part of the
> "Migration to REST"
> [http://reductivelabs.com/trac/puppet/wiki/ReleaseNotes#migration-to-rest]
> process and is signficantly different the
Todd Zullinger wrote:
> James Turnbull wrote:
>> Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1
>> release is a maintenance release in the 0.25.x branch.
>
> For the moment, I've got packages for Fedora and RHEL/CentOS at
>
> http://tmz.fedorapeople.org/repo/puppet/
>
>
- "Trevor Vaughan" wrote:
> All,
>
> I'm looking for a way to obtain information about the managed
> services
> on a given client system.
>
> Basically, some way to know what services have been enabled by Puppet
> from the client.
>
> I'm hoping to implement something like 'purge' for se
- "lyric" wrote:
> Hello Puppet Friends,
>
> wouldn't it be nice to have a Puppet expert directory with profiles
> and services they offer.
>
> I want to use Puppet but I am not an administration expert, so it
> would be nice to be able to contact local Puppet experts (in my case
> expert
On Mon, Nov 2, 2009 at 12:03 AM, lyric wrote:
>
> Hello Puppet Friends,
>
> wouldn't it be nice to have a Puppet expert directory with profiles
> and services they offer.
>
> I want to use Puppet but I am not an administration expert, so it
> would be nice to be able to contact local Puppet exper
>> A notify for me says run this resource again, or schedule it to be run
>> again (it may be scheduled by other classes).
>
> you don't run resources, you manage resources. It is a fundamental
> concept of puppet that you don't execute a bunch of scripts, instead
> you describe the state of your
lyric wrote:
> Hello Puppet Friends,
>
> wouldn't it be nice to have a Puppet expert directory with profiles
> and services they offer.
>
> I want to use Puppet but I am not an administration expert, so it
> would be nice to be able to contact local Puppet experts (in my case
> experts in Germany)
All,
I'm looking for a way to obtain information about the managed services
on a given client system.
Basically, some way to know what services have been enabled by Puppet
from the client.
I'm hoping to implement something like 'purge' for services such that
any service that is not defined is d
I found the solution. I think it was to easy:
Just set:
certname = puppet
and everythink works well.
BR, Rene
On 2 Nov., 10:55, Rene wrote:
> Hi all
>
> Thanks for all the replies. I want to try to do the following:
>
> I have two servers: server1 server2. /var/lib/puppet is shared via nas
>
> A notify for me says run this resource again, or schedule it to be run
> again (it may be scheduled by other classes).
you don't run resources, you manage resources. It is a fundamental
concept of puppet that you don't execute a bunch of scripts, instead
you describe the state of your infra
I see the logic in your explanation, I just don't think it adds up
when evaluating when to use a before or notify.
A notify for me says run this resource again, or schedule it to be run
again (it may be scheduled by other classes). I don't see why it
would also imply a before. If I don't mind i
> I'd expect that behaviour if using a before, but really think a notify
> shouldn't cause such a dependency, as i'm only asking for a
> restart/reload. That's just my two pence worth.
well a notify also implies a before on the notified resource. As you
want to manage a resource only once per
Apologies, I didn't notice the wiki had been updated.
I'd expect that behaviour if using a before, but really think a notify
shouldn't cause such a dependency, as i'm only asking for a
restart/reload. That's just my two pence worth.
I'll go back to using includes.
Thanks,
Matt
2009/11/2 Pete
> err: Could not apply complete catalog: Found dependency cycles in the
> following relationships: File[/etc/nginx/nginx.conf] =>
> Service[nginx], Service[nginx] => File[/etc/nginx/nginx.conf]; try
> using the '--graph' option and open the '.dot' files in OmniGraffle or
> GraphViz
>
> If I commen
Shouldn't this work?
class nginx {
package { "nginx" : ensure => present }
service { "nginx" :
ensure => running,
require => Package["nginx"];
}
}
class my-nginx {
require nginx
file { "/etc/nginx/nginx.conf" :
ensure
Peter Meier wrote :
> > Is this a known problem with 0.25 clients? Has anyone seem these
> > problems too?
>
> There have been some fixes for it in 0.25.1 [1] but I'm still
> encountering such issues as well. Especially as I'm connecting some
> clients over the internet, so I might encounter
Hi
> Is this a known problem with 0.25 clients? Has anyone seem these
> problems too?
There have been some fixes for it in 0.25.1 [1] but I'm still
encountering such issues as well. Especially as I'm connecting some
clients over the internet, so I might encounter high latency.
I'm in discus
Hi,
Since upgrading from 0.24 to 0.25, I've seen repeatedly puppetd clients
just stop when they're unable to reach the puppetmaster for a while.
With the normal logging level, they just seem to stop without writing
anything in their log.
I've seen this with 0.25.1rc1, rc2 and final, which are al
Hi all
Thanks for all the replies. I want to try to do the following:
I have two servers: server1 server2. /var/lib/puppet is shared via nas
and /etc/puppet is in a mercurial repository.
On server1 I have an ip for puppet-server1 and on server2 an ip for
puppet-server2. Those adresses will never
20 matches
Mail list logo