Hi,
For every server, I would like to have add some extra data - facts as:
indate (date in service)
asset,
location, and a few others
First I was thinking about adding custom facts, that are read from a
file on the server (ks)
The benefit: all data is available on the host.
With all facts I can
I would like to delegate access to puppet to other teams in our company.
It has to be possible for them to:
- create new recipes
- doing some sort of check if their recipes / templates work.
How should I do this without giving other teams the ability to create havoc?
--
You received this messag
r/abstract_server.rb:196:in
`start_synchronously'
Jan 10 15:46:38 puppetm puppet-master[2476]: >
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.11/bin/passenger-spawn-server:61
Jan 10 15:47:29 puppetm puppet-master[2476]: Compiled catalog for
puppetclient.replaced.domain in environment production
On Tue, Dec 14, 2010 at 08:28, Pieter Baele wrote:
>
> With a web browser:
> An error occurred during a connection to server_fqdn:8140.
>
> SSL received a record that exceeded the maximum permissible length.
>
> (Error code: ssl_error_rx_record_too_long)
If I change the v
On Mon, Dec 13, 2010 at 19:56, Patrick wrote:
>
> On Dec 13, 2010, at 4:55 AM, PieterB wrote:
>
> Puppet is working perfectly with WEBRick,
> but not with my passenger setup.
>
> The error I receive:
> Could not retrieve catalog from remote server: unknown protocol
>
> But the puppet client on the
lijke groeten,
Pieter Baele
www.pieterb.be
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@google
ates (I may have a typo in the
>>> path.)
>>>
>>> Also, what's the full path to puppet.conf.erb?
>>>
>>> On Jun 28, 2010, at 1:04 AM, Pieter Baele wrote:
>>>
>>>> Hello,
>>>>
>>>> I did make a stupid fault: not commit
These are in /etc/puppet/manifests/templates
|-- classes
| |-- motd.pp
| |-- puppet.pp
|-- nodes
| |-- default.pp
|-- site.pp
`-- templates
`-- etc
|-- motd.erb
|-- puppet
| `-- puppet.conf.erb
Met vriendelijke groeten,
Pieter Baele
www.pieterb.be
On Mon
roup => root,
mode=> 0644,
content => template("etc/puppet/puppet.conf.erb");
}
service {
"puppet":
ensure => running,
enable => true;
}
}
Met vriendelijke groeten,
hange it.
>
> chattr +i /etc/sudoers
>
> When you want puppet to start managing the file again, remove the
> attribute.
>
> chattr -i /etc/sudoers
>
>
> I hadn't thought about that possibility. I will try it.
Met vriendelijke groeten,
Pieter Baele
www.pieterb.be
On Fri, May 7, 2010 at 19:51, Adam Crews wrote:
> On Fri, May 7, 2010 at 6:45 AM, Pieter Baele
> wrote:
> > We use a script to edit /etc/sudoers temporarily to provide sudo access
> to
> > clients for a limited time.
> > A cron job checks for a var and after a defin
as a solution to this problem?
Met vriendelijke groeten,
Pieter Baele
www.pieterb.be
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group
12 matches
Mail list logo
