gt;
> > The final step is to set the topscope variable 'globalvars_noop'
> somewhere
> > (for example hiera, or Puppet console) and your node will be run with
> noop.
> > No need to touch any puppet config on the clients, and very easy to
> manage
>
Yeah but then when we push out noop = true in puppet.conf how do we then
push out noop = false via puppet if they're all in noop.
Managing on the server is the only way to do it in a safe and scalable way
(we have 500+ nodes)
On Thu, Jul 25, 2013 at 10:18 PM, Klavs Klavsen wrote:
> well - p
On Wednesday, 24 July 2013 03:12:10 UTC+10, Ellison Marks wrote:
>
> How are you running puppet? If cron or mcollective, you can add a --noop
> flag to the command line somewhere.
>
We're just using it the standard way running it as a daemon
--
You received this message because you are subsc
I'm trying to set a global noop but it doesn't seem possible,
There are 2 bugs open about this which to me look pretty serious as the
expected behaviour isn't the case.
http://projects.puppetlabs.com/issues/21286
http://projects.puppetlabs.com/issues/6549
If anyone has a work around (that doesn
On Saturday, 23 March 2013 00:50:11 UTC+11, jcbollinger wrote:
>
>
>
> On Thursday, March 21, 2013 6:16:07 PM UTC-5, Sam Morrison wrote:
>>
>> Hi,
>>
>> I've been battling with trying to get our puppet to do the following:
>>
>> Install
Hi,
I've been battling with trying to get our puppet to do the following:
Install all sources.list, apt-keys
then:
Run an apt-get update
then:
install Packages
I've tried a few ways.
1. Set a default requires
Package {
require => Exec['apt_update']
}
This doesn't work, I think because som
Hi,
I'm wanting to restrict hosts to a certain environment.
Eg only hosts in the range 192.168.0.0/24 can use the production environment
Similar with test env etc.
Is this possible with auth.conf?
Thanks,
Sam
--
You received this message because you are subscribed to the Google Groups
"Pupp
gt;
> Hi Sam,
>
> I would rather suggest uninstalling mod-passenger and then do a fresh
> install, rather going into all this mess..
>
> Regards,
> System Admin
> Ashish Jaiswal
>
> On Monday 20 August 2012 07:03:54 AM IST, Sam Morrison wrote:
> > Hi Danie
.
>
> If not, then it's getting interesting...
>
> --
> Daniele Sluijters
>
> On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote:
>>
>> Hi,
>>
>> I'm trying to install dashboard on precise and I get the below error.
>> I'm using the
gem install rack -v=1.1.0
But I still get exactly the same error:
root@admin:/usr/share/puppet-dashboard# gem list
*** LOCAL GEMS ***
rack (1.1.0)
Something else I'm missing?
Thanks,
Sam
On Friday, 17 August 2012 09:58:06 UTC+10, Sam Morrison wrote:
>
> Hi Daniele,
>
> Tha
icket.
>
> --
> Daniele Sluijters
>
> On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote:
>>
>> Hi,
>>
>> I'm trying to install dashboard on precise and I get the below error.
>> I'm using the latest version that is available in
=1.1.0
>
>
> server:/usr/share/puppet-dashboard/script# gem list
>
> *** LOCAL GEMS ***
>
> daemon_controller (1.0.0)
> fastthread (1.0.7)
> passenger (3.0.15)
> rack (1.1.2, 1.1.0)
> rake (0.9.2.2)
>
>
> Regards,
> System Admin
> Ashish Ja
Hi,
I'm trying to install dashboard on precise and I get the below error.
I'm using the latest version that is available in the puppet apt
repository. The package rdoc is installed (it's just a virtual package
pointing to ruby)
Are there some other missing dependencies that the package doesn't
I seem to have a weird error when trying to collect ssh keys and installing
them on our backup server.
On all hosts I have:
@@ssh_authorized_key { "root@$fqdn":
type => ssh-rsa,
key => $rootsshkey,
tag => 'host',
user => backups,
}
Then on my backup server I have:
Ssh_au
Thanks Wolf,
This works perfectly.
Cheers,
Sam
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/oayiKvapyZUJ.
To post to this group, send email to puppet-
Hi,
In a file resource I want to be able to specify multiple template contents.
If the 1st template doesn't exist use the 2nd listed and so on. Much like
how the source attribute works.
Basically this:
file { "/tmp/somefile.txt":
ensure => present,
content => [
16 matches
Mail list logo
