On 6/16/2010 8:27 PM, Silviu Paragina wrote:
This is somewhat related to an older thread. The topic was how to
install some perquisite packages for puppet, like augeas, lsb-release,
cron to name just a few. Puppet is required to reinstall this packages
if they are accidentally uninstalled. Becaus
On 6/17/2010 8:15 AM, Mathijs wrote:
Thanks for all answers,
I indeed want unmanaged resources to remove themselves (in some cases,
I know it's somewhat dangerous).
So the ensure => absent (in the package example) is not what I'm
after, because that only works on managed resources.
Packages tha
- "Daniel Pittman" wrote:
> >>
> >> # The puppet version of rm -rf /*
> >> Package { ensure => absent, noop => true }
> >> User { ensure => absent, noop => true }
> >>
> >> # These override the defaults
> >> package { "foo": ensure => present }
> >
> > How does this mee
"R.I.Pienaar" writes:
> - "Daniel Pittman" wrote:
>
>> >>
>> >> # The puppet version of rm -rf /*
>> >> Package { ensure => absent, noop => true }
>> >> User { ensure => absent, noop => true }
>> >>
>> >> # These override the defaults
>> >> package { "foo": ensure => pre
- "Daniel Pittman" wrote:
> "R.I.Pienaar" writes:
> > - "Daniel Pittman" wrote:
> >
> >> >>
> >> >> # The puppet version of rm -rf /*
> >> >> Package { ensure => absent, noop => true }
> >> >> User { ensure => absent, noop => true }
> >> >>
> >> >> # These override th
I'm troubled with a node-definition not able to resolve a class:
Could not find class rhnsd::common at /etc/puppet/manifests/nodes.pp:
8 on node X
Content of manifest/site.pp:
import "nodes.pp"
[...]
The layout of modules/rhnsd/ is:
|-- files
| `-- up2date-rhn
|-- manifests
| |-- client.pp
|
On 17.06.2010 10:53, David Schmitt wrote:
On 6/16/2010 8:27 PM, Silviu Paragina wrote:
This is somewhat related to an older thread. The topic was how to
install some perquisite packages for puppet, like augeas, lsb-release,
cron to name just a few. Puppet is required to reinstall this packages
i
On 17.06.2010 13:31, Tore wrote:
I'm troubled with a node-definition not able to resolve a class:
Could not find class rhnsd::common at /etc/puppet/manifests/nodes.pp:
8 on node X
Content of manifest/site.pp:
import "nodes.pp"
[...]
The layout of modules/rhnsd/ is:
|-- files
| `-- up2date-r
Hm, I thought that puppet would search for filname X in module Y
manifestdir when you included a class like include "Y::X", guess I'm
wrong there.
On the other hand, adding the import statement in the beginning of
rhnsd/manifests/init.pp yeilds the same error.
On 17 Jun, 13:10, Silviu Paragina w
On 6/17/2010 1:02 PM, Silviu Paragina wrote:
On 17.06.2010 10:53, David Schmitt wrote:
On 6/16/2010 8:27 PM, Silviu Paragina wrote:
This is somewhat related to an older thread. The topic was how to
install some perquisite packages for puppet, like augeas, lsb-release,
cron to name just a few. P
On Jun 16, 2010, at 5:42 PM, Silviu Paragina wrote:
>> set /files/etc/aliases/*[name = ‘ftp’]/name ftp
>>
> I've actually tried this in augtool and puppet and it didn't work. In puppet
> it fails silently and on first sight you would believe everything went ok. In
> augtool it simply fails.
Hello All,
I'm trying to start using external nodes under foreman, and I'm
running into some issues. I have the entries in puppet.conf:
[main]
external_nodes = /etc/puppet/external_node.rb
node_terminus = exec
The enternal_node.rb script is the one that came with foreman:
Just to be on the safe side, does it work if you use it with http (instead
of https)?
additionally, you should be using it with fqdn as the parameter (e.g.
/etc/puppet/external_node.rb fqdn )
Ohad
On Thu, Jun 17, 2010 at 10:48 PM, CraftyTech wrote:
> Hello All,
>
> I'm trying to start using
> We're going to set up Puppetmaster and Dashboard, and would like to
> automate the installation process. Have anyone made scripts or puppet
> manifests for installing these and would like to share?
I'm not aware of any specific examples, but do a search at
http://github.com/ if you haven't alrea
I was never able to get this working properly for /etc/services, there is
support in augeas now to do the matches properly but I think the ruby
bindings are not up to date with the new changes which ended up making
puppet fail.
On Thu, Jun 17, 2010 at 9:06 AM, Rob McBroom wrote:
> On Jun 16, 20
Forrie wrote:
> What is the disadvantage of using the puppet gem vs. installing from
> source (install.rb)?
Well, I wouldn't recommend that either. I much prefer a proper
packaging system like dpkg or rpm. But that's just my opinion. :)
--
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.po
Hello Ohad,
I started it with webrick on port 80, and it appears to work.
This what I get when I run the command /etc/puppet/external_node.rb
host:
---
parameters:
puppetmaster: puppet
classes: []
environment: ""
Does that mean it works on webrick but not on apache/passenger:443?
On Jun
Todd Zullinger wrote:
> Forrie wrote:
>> What is the disadvantage of using the puppet gem vs. installing from
>> source (install.rb)?
>
> Well, I wouldn't recommend that either. I much prefer a proper
> packaging system like dpkg or rpm. But that's just my opinion. :)
>
+1.
Regards
James Tur
I have been working with the Augeas resource command and having a
difficult time. At this point I am perplexed as to why the following
code doesn't work. I have the following rule for updating the main.cf
file to change an existing value and to add a new element with
comments:
augeas { "
On 2010-06-17 06:31, Tore wrote:
> I'm troubled with a node-definition not able to resolve a class:
> Could not find class rhnsd::common at /etc/puppet/manifests/nodes.pp:
> 8 on node X
>
> Content of manifest/site.pp:
> import "nodes.pp"
> [...]
>
> The layout of modules/rhnsd/ is:
> |-- files
* Ohad Levy [06/15/2010 22:38]:
>The ip address does not really matter, if you want to force your own
>certificate names, you can use the certname option instead on relaying on
>facter to resolve the fqdn fact for you.
ah... that's even better. I didn't notice that option on the manua
I have done some further experimenting and found things even more
perplexing. The rule is now just adding the new values that I need. The
rule is:
augeas { "dkim-postfix-settings":
require => Package["postfix"],
context => "/files/etc/postfix/main.cf",
Just to be sure we're on the same page. It doesn't work like this?
init.pp::
import "*"
class rhnsd {
}
Is the module path in puppet set to your module path? Other than this I
can't spot any other errors. Also make sure you have restarted
puppetmasterd, in many cases when developing puppet code
Hi Bryan,
I was just looking over your puppet-puppet recipe and I was curious on
how you are managing your different target environments. I see that
you have defined different trees for each environment:
[development]
manifest = /etc/puppet/environments/development/site.pp
modulepath = /e
I'm getting the following errors in the module I'm writing to maintain my
snmpd configurations (this is a mis of verbose and normal errors):
err: //snmp/File[/etc/sysconfig/snmpd.options]: Failed to retrieve current
state of resource: Could not retrieve information from source(s)
puppet:///snmp/sn
On Thu, Jun 17, 2010 at 4:23 PM, PBWebGuy wrote:
> Hi Bryan,
>
> I was just looking over your puppet-puppet recipe and I was curious on
> how you are managing your different target environments. I see that
> you have defined different trees for each environment:
> [development]
> manifest = /e
I think I have the same problem the scripts bundled with foreman,
those that talk to the web interface, do not seem to support https...
I set up an apache virtual on localhost with ssl disabled and
configured these scripts to speak to that. that seems to do it.
Can someone confirm this limitat
Well I got foreman.rb to work with https. Look at this thread:
http://groups.google.com/group/puppet-users/browse_thread/thread/1d2b5814a73300d/5907d3697c63853c?lnk=gst&q=foreman.rb#5907d3697c63853c
I'd like to know what the deal is with node.rb I hope I'm doing
something wrong, and that th
that is not a limitation, and usually actually works :)
can you check that you get the right output with curl/wget - e.g.?
curl -k https://foreman/node/fqdn?format=yml (add -x "" to disable curl
using a proxy)
Ohad
On Fri, Jun 18, 2010 at 9:28 AM, CraftyTech wrote:
> Well I got foreman.rb t
Hello
Is there any way to have a user with two different passwords.
I have a user that is present in our prod and non prod environments.
However the password for non-prod is different than prod. Anyway I can
arrange that in puppet?
--
You received this message because you are subscribed to
Hi,
I'm trying to develop a manifest to setup a new puppet master. To solve
the SSL certificates I've created a root CA outside of puppet, and have
generated an intermediate CA for the new puppet master to use. I've also
configured my puppetmaster daemon to use it's own ssl directory. So the
On Fri, Jun 18, 2010 at 1:07 PM, Geoff Crompton <
geo...@trinity.unimelb.edu.au> wrote:
>
> Anyone know how I can arrange for the puppet client to successfully trust
> the masters certificate?
>
you need to add the top level ca pub key to it to
/var/lib/puppet/ssl/certs/ca.pem
you might still fai
On Jun 17, 2010, at 11:04 AM, John Martin wrote:
> I have done some further experimenting and found things even more perplexing.
> The rule is now just adding the new values that I need. The rule is:
>
> augeas { "dkim-postfix-settings":
> require => Package["postfix"]
33 matches
Mail list logo
