I've uploaded version 0.3 of ssh::auth to
http://reductivelabs.com/trac/puppet/wiki/Recipes/ModuleSSHAuth . Changes in
this release:
* Regenerate key if $keytype or $length changes
* Update authorized_keys if $options changes
* Use ssh_authorized_keys to manage authorized_keys
* Remove comment pa
Thanks for the comments Silviu, here what I found:
I ran:
/usr/sbin/puppetd -vdt --fqdn `hostname` --environment=development --test
This is the excerpt of the output:
debug:
//Node[puppetclient.example.com]/common/common::nagios/Package[nrpe_custom]:
Changing ensure
debug:
//Node[puppetclient.e
>
> Sounds like mongrel or nginx might be generating an error message. Try
> pointing a web browser at https://:8140 and see if you get
> anything helpful.
The error I get is:
Peer's certificate has an invalid signature.
It would seem rather odd that the certificate has suddenly become inval
On 12/21/2009 10:05 PM, Matthew Delves wrote:
> Hey All, This is probably a gotcha of some kind. That is to say I've missed
> a configuration somewhere. I've recently moved over to using mongrel as the
> puppet server type and having nginx proxy to one of four mongrel
> instances.
>
> What I'm seei
Hey All,
This is probably a gotcha of some kind. That is to say I've missed a
configuration somewhere. I've recently moved over to using mongrel as the
puppet server type and having nginx proxy to one of four mongrel instances.
What I'm seeing though is that when I try to run a new node (one tha
>>
> Doug, I am not a version control expert but I think you might be
> confusing svn branches with cvs branches.
> As soon as you do:
>
> svn cp production development:
>
> you've not only made a new puppet environment, you've 'branched'
> production into development.
I'd also recommend using a m
Legrave wrote:
> I'm on Gentoo.
> I've created /etc/env.d/99facter
> with FACTER_test=infof
> and in console : env_update && source /etc/profile
>
If you want puppetd to inherit environment variables, set them in the puppetd
init script.
I really don't see any value to gain by setting facts thi
I'm on Gentoo.
I've created /etc/env.d/99facter
with FACTER_test=infof
and in console : env_update && source /etc/profile
All my custom facts works when I run puppetd with -vt --factsync
If I start it normally, only the fact with ENV['HOME'] works.
I run puppet 0.24.8
thanks
On 21 déc, 23:41, S
Legrave wrote:
> Facter.add("salle") do
> setcode do
> ENV['FACTER_test']
> end
> end
>
> Puppet refuse to synchronize my own environments variables unless I
> run the deamon manually :
> #puppetd -vt --factsync
>
Where are you setting `FACTER_test'?
=scott
--
You received this me
Douglas Garstang wrote:
> On Mon, Dec 21, 2009 at 8:32 AM, R.I.Pienaar wrote:
>
>> hello,
>>
>>
>> - "Douglas Garstang" wrote:
>>
>>
>>> http://www.devco.net/archives/2009/10/10/puppet_environments.php
>>>
[staging]
modulepath =
>>> /e
Q1: Ohad, I has not understood your assumption. You consider that in
my options there is an error?
Just in case I have edited options ServerName:
ServerName puppet -> ServerName puppet:3000
And I see that Foreman listen only 3000 port.
[u...@puppet foreman]$ netstat -an | grep 80
udp0
On Dec 19, 2009, at 11:54 PM, Douglas Garstang wrote:
> I'd like to be able to split out my puppet production and test
> environments so that I can continue to develop puppet
> modules/manifests without breaking production. How are people doing
> this?
My setup is pretty simple and doesn't requir
On Dec 19, 2009, at 9:46 AM, Al @ Lab42 wrote:
> On 18 Dic, 20:46, Luke Kanies wrote:
>> On Dec 17, 2009, at 8:15 AM, Al @ Lab42 wrote:
>>
>>> Hallo *,
>>> at the Puppet Camp there has been some discussion about modules
>>> standards and naming conventions.
>>> I might have missed some relevant b
Douglas Garstang wrote:
> But... how do you serve up those multiple puppet environments? Are you
> running multiple versions of the puppetmaster? I'm using passenger so
> it would seem like it would be fairly easy to run additional
> puppetmasters on different ports, except that I can't find where
Hello,
I'm trying to add an environment variable as fact like this :
#export $FACTER_test="infof"
#facter | grep test
test => infof
But my fact don't synchronize with puppet master. I don't see it in /
var/puppet/yaml/clientfile.yaml
If I want this works, I've need to start puppet like this :
#pu
hello,
> >>> puppet.conf contains (in addition to the standard stuff):
> >>>
> >>> [staging]
> >>> modulepath =
> /etc/puppet-staging/modules:/etc/puppet-staging/services
> >>> manifest = /etc/puppet-staging/manifests/site.pp
> >>>
> >>> [development]
> >>> modulepath =
> >>> /etc/puppet-
On Mon, Dec 21, 2009 at 11:45 AM, Douglas Garstang
wrote:
> On Mon, Dec 21, 2009 at 8:36 AM, Matthew Hyclak wrote:
>> On Mon, Dec 21, 2009 at 11:27 AM, Douglas Garstang
>> wrote:
>>> On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
>>
hello,
'lo,
> I did read the reductive labs documentation (which is unclear as
> usual), and the devco site before posting here, and again after
> someone referenced it. I understand the concept of multiple
> environments quite well, and that's not the issue. The issue is how I
> integrate this fu
On Mon, Dec 21, 2009 at 8:36 AM, Matthew Hyclak wrote:
> On Mon, Dec 21, 2009 at 11:27 AM, Douglas Garstang
> wrote:
>> On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
>>> On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
>>> wrote:
On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
On Mon, Dec 21, 2009 at 8:32 AM, R.I.Pienaar wrote:
> hello,
>
>
> - "Douglas Garstang" wrote:
>
>> http://www.devco.net/archives/2009/10/10/puppet_environments.php
>
>> > [staging]
>> > modulepath =
>> /etc/puppet-staging/modules:/etc/puppet-staging/services
>> > manifest = /etc/p
On Mon, Dec 21, 2009 at 11:27 AM, Douglas Garstang
wrote:
> On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
>> On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
>> wrote:
>>> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
>>> wrote:
On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar w
hello,
- "Douglas Garstang" wrote:
> http://www.devco.net/archives/2009/10/10/puppet_environments.php
> > [staging]
> > modulepath =
> /etc/puppet-staging/modules:/etc/puppet-staging/services
> > manifest = /etc/puppet-staging/manifests/site.pp
> >
> > [development]
> > modul
On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
> On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
> wrote:
>> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
>> wrote:
>>> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
hello,
- "Douglas Garstang" wrote:
On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
wrote:
> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
> wrote:
>> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
>>> hello,
>>>
>>> - "Douglas Garstang" wrote:
>>>
I'd like to be able to split out my puppet production and test
Douglas Garstang wrote:
> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
> wrote:
>
>> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
>>
>>> hello,
>>>
>>> - "Douglas Garstang" wrote:
>>>
>>>
I'd like to be able to split out my puppet production and test
envi
My guess is that you have pluginsync enabled, and as such, you need to
put the custom functions in your modules plugins (or lib) path.
cheers,
Ohad
On Mon, 2009-12-21 at 14:19 +0100, Kenneth Holter wrote:
> Hi.
>
>
> I've downloaded the exlookup.rb script, and put it in
> the /var/lib/puppet/l
Hi.
I've downloaded the exlookup.rb script, and put it in the
/var/lib/puppet/lib/puppet/parser/functions folder like this:
-- snip --
[r...@puppetmaster /]# ll /var/lib/puppet/lib/puppet/parser/functions/|grep
-i extlookup
-rw-r--r-- 1 root root 7103 Dec 21 13:41 extlookup.rb
-- snip --
After
27 matches
Mail list logo
