similar to: Simple config question

Hi I am trying to configure hosts.allow using augeas with puppet. I can add a ip range if process exists with this code augeas { "Add ${name} to ${process}": context => "/files/etc/hosts.allow", changes => "set *[process=''${process}'']/client[last()+1] ${name}", onlyif => "match

Hi folks, when I try to do something like: define railsproject($name, $uid, $gid, $userpass, $sqlpass) { mysql_database { "$name_staging": ensure => present } mysql_database { "$name_production": ensure => present} ....more stuff... } I get: Puppet::Parser::AST::Resource failed with error ArgumentError: Duplicate definition: Mysql_database[] is already

Hi, are there any good ways of scripting an inventory of managed resources on all nodes? I''ve found the inventory script by R.I.Pienaar ( http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php) which does what I want but only locally on each client. Is there any native way of syncing the client_yaml data centrally or any other way of doing this? I need a

Why doesn''t puppet autoload modules with capitals in the class names? Jul 5 09:55:54 s_sys@test01.sjc.xxx.com puppetd[6527]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class repo::centOSBase in namespaces repo::common at /etc/puppet/modules/repo/manifests/common.pp:8 on node test01.sjc.xxx.com Change ''centOSBase'' to

G''day. I am wondering what the current best practice for building a single file out of distributed fragments is with puppet. Specifically, my problem: 1. Install munin-node on arbitrary machines. 2. Install ''munin.conf'' as a single file on one machine, containing a configuration stanza for every machine that munin-node is installed on. The current best practice

Hi everyone, Just wanted to tell you a little story. We''ve been enthusiastic puppet users since about a year ago here at the Geographic Institute of the University of Zürich. But we won''t use the zpool type ever again. Its just not worth it. Here''s what happened: . one of our servers lost knowledge about one of its zfs pools . puppet didn''t find the pool

(apologies in advance for the line wrap) I have the following tidbit of augeas code, which inserts a rule into /etc/sysconfig/iptables as the first rule of a specifically named chain; # augtool> insert append before "/files/etc/sysconfig/iptables/table/append[. = ''Mayo-Firewall-INPUT''][1]" # augtool> match /files/etc/sysconfig/iptables/table/append[. =

Hi! I using Augeas to handle dump and passno for certain mount points in /etc/fstab. Each mount point is defined as it''s own augeas block: augeas { ''homeLV'': context => ''/files/etc/fstab'', changes => [

Having just spent about 2 hours trying to work out how to add a password --md5 $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1 line to my grub.conf I thought it would be worth sharing how I finally got it to work. augeas {"/boot/grub/grub.conf": context => "/files/boot/grub/grub.conf", changes => [ "set timeout 15",

Hi all, I''m trying to come up with a lens for the zabbix agent config files. I find the lens language untransparent at best, so I''m struggeling to figure out what''s up. The debugging possibilities are extremely limited. Here''s what I have now: zabbix.aug: ==== (** An adjusted copy of the postfix_main module **) module Zabbix_agent = autoload xfm

On Monday 22 September 2014 13:50:18 Richard W.M. Jones wrote: > On Mon, Sep 22, 2014 at 10:49:42AM +0200, Pino Toscano wrote: > > The lenses in our custom path need the system lens for base > > definitions. Disabling the system path was worthless anyway, since > > our API does not allow user-specified custom paths. > > > > The only possible use for AUG_NO_STDINC

We were previously forcing the augeas Modprobe lens to match modules.conf and conf.modules. It turns out that the contents of these files are quite different to modprobe.conf, requiring a new lens. This change keeps the logic which looks for where modules should go, but doesn't update the augeas configuration. If there is no augeas lens for /etc/modules.conf, any attempt to parse or modify it

Hi, Can puppet autosign work by giving vlan IP instead of domain? For example, in the autosign.conf file, instead of using *.mydomain.org, I want to give 172.18.133.* But it does not seem to work if I give the IP address. But I don''t want to limit the client from *.mydomain.org by only allow certain vlan client not all the are in the same domain. Thanks, -Haiyan -- You received this

Hello, I am trying to use augeas via puppet, augeas { "mailops": context => "/files/etc/sudoers", changes => [ "set spec[user = ''%mail-ops'']/user %mail-ops", "set spec[user = ''%mail-ops'']/host_group/host ALL", "set spec[user = ''%mail-ops'']/host_group/command[1] \"/bin/su

Hi, currently /etc/shadow is edited manually when needed (i.e. when setting the password for an user), and it is not changed when removing users. Import the upstream shadow.aug (currently in their development serie, but not part of any released version yet), and use it only when the augeas version is less than a potential 1.2.1 (covering also the case when the new version is just 1.3.0). Pino

Hi David, We have a general problem using Augeas in libguestfs and I wonder if you have any advice. The problem is that we often -- as with yesterday's patch -- add new config file paths to lenses. Or we want to parse config files which are not necessarily in the exact paths that Augeas is expecting. Now it's easy enough to parse such files using an arbitrary lens by calling

I would like to use puppet classes to inject and/or replace xml elements into an existing xml configuration file. This seems to me to be a common problem already solved. Can anyone suggest the easiest way to do this? An example use case would look like something like this. Given xml file: <host> <server name="one"/> <server name="two"/>

v3: - Don't remove the LVM transform.

The lenses in our custom path need the system lens for base definitions. Disabling the system path was worthless anyway, since our API does not allow user-specified custom paths. The only possible use for AUG_NO_STDINC to aug-init could have been to not load the lenses right at init time loading them later; however, this is what the AUG_NO_LOAD flag (= 32) does already. --- daemon/augeas.c | 5

Hello, As I''ve been building up my puppet infrastructure, I''ve started using puppet certs for all of my services that require ssl. Usually this is in the form of links: file { "/opt/syslog-ng/etc/ca.d/b2457b50.0": require => Package["syslog-ng"], ensure => link, target =>