[Puppet Users] foreman 1.2 + puppet 3.0 + puppet module install erwbgy/system

[shyam sundar Keshari]

Hi Friends,

Kindly guide me in configuring the correct syntax of this module with
foreman 1.2


When executing puppet agent --test getting below error :


Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
config is not a hash or array when accessing it with servers at
/etc/puppet/environments/production/modules/system/manifests/ntp.pp:6 on
node icinga-test.synapse.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

ALso configuration is mention below for NTP also if anyone configure other
parameter of this module like system:files kindly provided syntax of it .

On foreman :

parameter type : string ( when changing to hash or array getting error from
foreman itself)

config box I put configuration like :

$ntp = {
  'servers' => ['ntp1.domain.com'],
}

class { 'system::ntp':
  config => $ntp,
}

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: remove node parameters with dashboard rake api?

[Jérémy JR]

Le mercredi 20 février 2013 22:55:11 UTC+1, Schofield a écrit :
>
> Is there a rake task for removing node parameters from the dashboard?  The 
> online dashboard manual is silent on the parameters related to rake tasks 
> altogether.
>

Hi,

I'm looking for the same thing.
Since your post, did you find a way to do that?

Regards,
Jérémy 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: hiera oddities

[Tom Hanstra]

Spot on!  Thanks for pointing this out.

Tom

On Friday, September 27, 2013 1:35:42 PM UTC-4, Ellison Marks wrote:
>
> Prefix doesn't return a string, it returns an array. I think this gets 
> stringified in the error message, but it screws up the lookup. Try 
> hiera($role_value[0]).
>
> On Friday, September 27, 2013 9:32:12 AM UTC-7, Tom Hanstra wrote:
>>
>> I'm having a real trouble getting hiera to work as expected.
>>
>> My current setup has a puppet master and an agent.  On both I have the 
>> same /etc/hiera.yaml file linked into the /etc/puppet directory.  I've also 
>> been able to confirm that hiera is seeing the right json files in 
>> /var/lib/hiera.
>>
>> What I'm seeing right now is that if I hard code a value (in my case a 
>> value called "role_puptest1").  In the class I'm working on, if I hardcode 
>> that value into the hiera lookup:
>>
>> $server_role = hiera('role_puptest1')
>>
>> then puppet  agent runs just fine.  However, if I build the value 
>> "role_puptest1" from other information, for instance like this:
>>
>>$role_value = prefix([$hostname],'role_')
>>$server_role = hiera($role_value)
>>
>> I get this error when running the puppet agent:
>>
>> Error: Could not retrieve catalog from remote server: Error 400 on 
>> SERVER: Could not find data item role_puptest1 in any Hiera data file and 
>> no default supplied at 
>> /etc/puppet/modules/server/iptables2/manifests/init.pp:9 on node 
>> puptest1.library.nd.edu
>>
>> Based on the error, it is parsing the role_value properly (still has 
>> "role_puptest1"), but it is not finding the value in the file.  At the same 
>> time, command line hiera on both my agent and my master find the file 
>> properly:
>>
>> puptest1 800$ hiera role_puptest1
>> role_LOCKSS
>>
>> So, why is the generated value which comes up with the same string of 
>> data not finding the record in the hiera data file?
>>
>> I'm using hiera 1.2.1 and puppet 3.2.4 on RHEL 6.
>>
>> Thanks,
>> Tom
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: How to deploy & excecute script remotely

[Raju Patil]

I didnt see  "file" resource to deploy the file and then "exec" option on 
Puppet master. Is there any plugin I have to installed on Master & then 
these two options will be
visible on Puppet master dashboard. Or I have to do the changes in 
commandline. 
Seriousely, not aware which file to edit & move ahead. Need your help. 
 
 

On Thursday, 19 September 2013 18:31:21 UTC+5:30, Raju Patil wrote:

>  JuanBrein,
>  
> Can you pls.mention here, what activites do I have to perform on Master & 
> nodes.
>  
> Will be very helpful.
>  
> Since I really dont know where this 
>  "file" resource to deploy the file and then "exec" to execute it:
>
>  
>
> On Monday, 16 September 2013 18:23:18 UTC+5:30, JuanBrein wrote:
>
>> Not hard at all...
>>
>> just use "file" resource to deploy the file and then "exec" to execute it:
>>
>> file{ "/path/to/my/script.sh"
>>   source => "puppet:///modules/${module_name}/script.sh",
>>   mode => 755,
>> } ~>
>>
>> exec { "/path/to/my/script.sh"
>>refreshonly => true,
>> }
>>
>> The important bit here is the ~> . That means notify and require. It 
>> basically means it will notify the exec when the file is deployed and that 
>> puppet will push the file before trying to execute it. The refreshonly true 
>> will assure you that the script will be executed only if it is notified.
>>
>> Cheers
>>
>> Juan
>>
>> On Monday, September 16, 2013 7:25:59 AM UTC+1, Raju Patil wrote: 
>>>
>>>  Hi,
>>>  
>>> I am new to Puppet & just had installed Puppet master on Centos.And 
>>> manging Linux & Windows nodes, now I would like to deploy and execute 
>>> script on one of my Linux Box Remotely from 
>>> Puppet Master.
>>>  
>>> Appriciate your help. Pls. share steps to be followed for achieving 
>>> above tast. 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: How to deploy & excecute script remotely

[Rob Reynolds]

Raju,
 Being new to puppet, allow me to suggest the Learning Workshop -
https://puppetlabs.com/learn.

In conjunection with that, we have a set of free tutorials with a learning
VM ( http://docs.puppetlabs.com/learning/ ) that I feel may help alleviate
some of these questions.

Give that a shot. Thanks!


On Mon, Sep 30, 2013 at 7:58 AM, Raju Patil  wrote:

> I didnt see  "file" resource to deploy the file and then "exec" option on
> Puppet master. Is there any plugin I have to installed on Master & then
> these two options will be
> visible on Puppet master dashboard. Or I have to do the changes in
> commandline.
> Seriousely, not aware which file to edit & move ahead. Need your help.
>
>
>
> On Thursday, 19 September 2013 18:31:21 UTC+5:30, Raju Patil wrote:
>
>>  JuanBrein,
>>
>> Can you pls.mention here, what activites do I have to perform on Master &
>> nodes.
>>
>> Will be very helpful.
>>
>> Since I really dont know where this
>>  "file" resource to deploy the file and then "exec" to execute it:
>>
>>
>>
>> On Monday, 16 September 2013 18:23:18 UTC+5:30, JuanBrein wrote:
>>
>>> Not hard at all...
>>>
>>> just use "file" resource to deploy the file and then "exec" to execute
>>> it:
>>>
>>> file{ "/path/to/my/script.sh"
>>>   source => "puppet:///modules/${module_**name}/script.sh",
>>>   mode => 755,
>>> } ~>
>>>
>>> exec { "/path/to/my/script.sh"
>>>refreshonly => true,
>>> }
>>>
>>> The important bit here is the ~> . That means notify and require. It
>>> basically means it will notify the exec when the file is deployed and that
>>> puppet will push the file before trying to execute it. The refreshonly true
>>> will assure you that the script will be executed only if it is notified.
>>>
>>> Cheers
>>>
>>> Juan
>>>
>>> On Monday, September 16, 2013 7:25:59 AM UTC+1, Raju Patil wrote:

  Hi,

 I am new to Puppet & just had installed Puppet master on Centos.And
 manging Linux & Windows nodes, now I would like to deploy and execute
 script on one of my Linux Box Remotely from
 Puppet Master.

 Appriciate your help. Pls. share steps to be followed for achieving
 above tast.

>>>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Error with Puppetlabs Dashboard module

[Chris McDermott]

I'm trying to use the Puppetlabs-dashboard module to install the dashboard
on a new host but I'm getting an error. I am using the latest versions of
the following Puppetlabs modules (as of 09/26/2013):

dashboard
mysql
passenger
apache
stdlib
concat

The other modules are not causing problems - I can "include mysql" or
whatever without issue. But when I "include dashboard" I get the following:

Error: Could not retrieve catalog from remote server: wrong header line
format Warning: Not using cache on failed catalog Error: Could not retrieve
catalog; skipping run

I have replicated this error on three different CentOS 6.x hosts at
slightly different patch levels. All were using puppet 3.2.x though.

Searching seems to indicate that this error usually indicates a faulty
template file. I found three templates in the dashboard module, but all of
them pass the syntax check. Likewise I ran "puppet parser validate" on all
.pp files but found no problems. I opened an Issue on the GitHub project,
but have not received any response, so I thought I would check on the
mailing list to see if anyone else has seen this issue, and if they have
any workarounds or solutions.

Thanks!

Chris

-- 
:wq

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] hiera config oddness

[Bret Wortman]

I'm trying to set up hiera for the first time, and something really odd is
happening.

I set up my hiera.yaml file in /etc/puppet/, and it was pretty simple:

---
:backends:
  - yaml
:hierarchy:
  - "%{hostname}"
  - common

:yaml:
  :datadir: /etc/puppet/data

So I added a "flag" class, which just has a manifest containing one
"notify" so I can see that it's getting loaded. I stuck it in
"data/common.yaml":

---
puppetserver : 'zgepetto.foo.net'
ipamaster : 'ipamaster'

classes:
  - role::base
  - flag

And lo and behold, the notify showed up when I ran puppet agent -t --noop.

Then I tried moving the flag mention into a file named for my test node,
zw129.yaml:

---
classes:
  - role::workstation
  - flag

But the flag never got picked up. Confused, I moved it back to common.yaml
and there it was again. Eventually, I got around to removing "common" from
my hiera.yaml file (leaving only the "{hostname}" in the hierarchy) and
still common is getting loaded, even after doing a "service puppetmaster
restart".

I've looked around for other instances of hiera.yaml but don't see any.
What else could be causing hiera to load a common.yaml that I'm not asking
for, and neglecting the zw129.yaml that I am asking for? It sure feels like
I'm picking up an incorrect config file somewhere, but I'm not sure where
to look or what logfile to examine next.

Thanks!

*
*
*Bret Wortman*

http://damascusgrp.com/
http://about.me/wortmanbret

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Problem retreiving catalog

[Binoy Daniel]

Hi Nikolay,

I too facing same issue, but i could not find external_node.rb, where as we 
have /etc/puppet/nodes.rb but that file does not have any database related 
info...

How to proceed..please help

(I think create mysql replica with different name and update the file which 
you specified ?)

Thanks in advance
Binoy

On Thursday, 11 July 2013 00:32:13 UTC+1, Nikolay Georgieff wrote:
>
> I solved my issue. Cloned the shared db for Foreman (emptied the type 
> column @ hosts table)  and updated the external_node.rb with the latest one.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] quiet exec script output

[Geoff Galitz]

Hi.

One of the scripts we run for systems management causes puppet to say:


notice:  /Stage[main]//Exec[script]/returns:  executed successfully


How can I suppress or quiet this output?

-G







-- 
---
Geoff Galitz, ggal...@shutterstock.com
WebOps
Shutterstock Images

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] facter behaves different for different users

[Bernd Weber]

Hey all,

I've been trying to get EC2 facts working with the open source edition. I 
changed the code for ec2.rb and util/ec2.rb according to the master branch 
on Github(https://github.com/puppetlabs/facter). And testing the code with 
a 'facter' call seems to work fine. I can see all the EC2 information. Now 
when I run Puppet and ask for the global variable (e.g. $::ec_ami_id) it is 
empty. Manual testing shows that running 'facter -d -p' as myself (non-root 
user) and as root results in different output. Has anybody observed this 
issue before and maybe an idea on what might be going wrong here?
Any help is greatly appreciated!

My Puppet version is 3.3.0
My Facter version is 1.7.3
Environment is Ubuntu 12.04 on an Amazon EC2 instance

Sensitive information has been ! ;)

Running 'facter -d -p' as root shows:
Relative directory ./facter removed from search path.
Found no suitable resolves of 1 for zonename
value for zonename is still nil
Found no suitable resolves of 1 for selinux_current_mode
value for selinux_current_mode is still nil
value for pe_version is still nil
value for puppi_projects is still nil
Found no suitable resolves of 2 for iphostnumber
value for iphostnumber is still nil
value for zfs_version is still nil
value for pe_version is still nil
Found no suitable resolves of 1 for pe_patch_version
value for pe_patch_version is still nil
Found no suitable resolves of 1 for selinux_policyversion
value for selinux_policyversion is still nil
Found no suitable resolves of 1 for operatingsystemmajrelease
value for operatingsystemmajrelease is still nil
value for pe_version is still nil
Found no suitable resolves of 1 for pe_minor_version
value for pe_minor_version is still nil
Found no suitable resolves of 1 for selinux_enforced
value for selinux_enforced is still nil
value for cfkey is still nil
Found no suitable resolves of 1 for xendomains
value for xendomains is still nil
Found no suitable resolves of 1 for selinux_mode
value for selinux_mode is still nil
value for pe_version is still nil
Found no suitable resolves of 1 for pe_major_version
value for pe_major_version is still nil
value for vlans is still nil
Found no suitable resolves of 1 for selinux_config_policy
value for selinux_config_policy is still nil
Found no suitable resolves of 2 for processor
value for processor is still nil
value for macaddress_lo is still nil
value for zpool_version is still nil
value for ipaddress6 is still nil
Found no suitable resolves of 1 for selinux_config_mode
value for selinux_config_mode is still nil
value for lsbrelease is still nil
value for pe_version is still nil
value for ipaddress6_lo is still nil
value for iptables_persistent_version is still nil
value for ipaddress6_eth0 is still nil
architecture => amd64
augeasversion => 0.10.0
blockdevice_xvda1_size => 8589934592
blockdevices => xvda1
concat_basedir => /var/lib/puppet/concat
domain => ec2.internal
facterversion => 1.7.3
filesystems => btrfs,ext2,ext3,ext4,iso9660,msdos,ufs,vfat,xfs
fqdn => ip-10-0-0-55.ec2.internal
getent_group => 
root:x:0:|daemon:x:1:|bin:x:2:|sys:x:3:|adm:x:4:ubuntu|tty:x:5:|disk:x:6:|lp:x:7:|mail:x:8:|news:x:9:|uucp:x:10:|man:x:12:|proxy:x:13:|kmem:x:15:|dialout:x:20:ubuntu|fax:x:21:|voice:x:22:|cdrom:x:24:ubuntu|floppy:x:25:ubuntu|tape:x:26:|sudo:x:27:|audio:x:29:ubuntu|dip:x:30:ubuntu|www-data:|backup:x:34:|operator:x:37:|list:x:38:|irc:x:39:|src:x:40:|gnats:x:41:|shadow:x:42:|utmp:x:43:|video:x:44:ubuntu|sasl:x:45:|plugdev:x:46:ubuntu|staff:x:50:bweber|games:x:60:|users:x:100:|nogroup:x:65534:|libuuid:x:101:|crontab:x:102:|syslog:x:103:|fuse:x:104:|messagebus:x:105:|whoopsie:x:106:|mlocate:x:107:|ssh:x:108:|landscape:x:109:|netdev:x:110:ubuntu|admin:x:111:ubuntu|ubuntu:x:1000:|puppet:x:112:|Debian-exim:x:113:|bweber:x:2001:|
getent_passwd => 
root:x:0:0:root:/root:/bin/bash|daemon:x:1:1:daemon:/usr/sbin:/bin/sh|bin:x:2:2:bin:/bin:/bin/sh|sys:x:3:3:sys:/dev:/bin/sh|sync:x:4:65534:sync:/bin:/bin/sync|games:x:5:60:games:/usr/games:/bin/sh|man:x:6:12:man:/var/cache/man:/bin/sh|lp:x:7:7:lp:/var/spool/lpd:/bin/sh|mail:x:8:8:mail:/var/mail:/bin/sh|news:x:9:9:news:/var/spool/news:/bin/sh|uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh|proxy:x:13:13:proxy:/bin:/bin/sh|www-data:x:33:33:www-data:/var/www:/bin/sh|backup:x:34:34:backup:/var/backups:/bin/sh|list:x:38:38:Mailing
 
List 
Manager:/var/list:/bin/sh|irc:x:39:39:ircd:/var/run/ircd:/bin/sh|gnats:x:41:41:Gnats
 
Bug-Reporting System 
(admin):/var/lib/gnats:/bin/sh|nobody:x:65534:65534:nobody:/nonexistent:/bin/sh|libuuid:x:100:101::/var/lib/libuuid:/bin/sh|syslog:x:101:103::/home/syslog:/bin/false|messagebus:x:102:105::/var/run/dbus:/bin/false|whoopsie:x:103:106::/nonexistent:/bin/false|landscape:x:104:109::/var/lib/landscape:/bin/false|sshd:x:105:65534::/var/run/sshd:/usr/sbin/nologin|ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash|puppet:x:106:112:Puppet
 
configuration management 
daemon,,,:/var/lib/puppet:/bin/false|Debian-exim:x:107:113::/var/spool/exim4:/bin/false|bweber:x:

[Puppet Users] Re: quiet exec script output

[Peter Bukowinski]

Puppet is doing what it is supposed to do: report changed resources. Puppet 
isn't aware of the content of your script, so it treats each run (that has 
an exit code of 0) as if something has changed. I'm guessing that your 
script is currently executing each time puppet runs?  Can you describe what 
this script is doing in general detail? If it's looking for a certain 
situation and doing something if it finds it (and doing nothing if it finds 
nothing), for example:

if [ "$(uptime | awk '{print $3}')" -gt 7 ]; then echo 'OMG! I have been up 
more than a week!'; fi

then I'd recommend putting the "looking for" portion of the script into the 
'onlyif' parameter of the exec and the "doing something" portion in the 
'command' parameter. For example:

exec { 'uptime_test':
command => "echo 'OMG! My uptime is abysmal!' > /etc/motd",
onlyif => '[ "$(uptime | awk \'{print $3}\')" -lt 7 ]',
}

Here, puppet will only report that the Exec[uptime_test] resource executed 
successfully if the computer has been up for less than 7 days. Once the 
uptime exceeds that condition, you'll see no notice from this resource on 
your puppet reports.

--
Peter


On Monday, September 30, 2013 1:52:55 PM UTC-4, Geoff Galitz wrote:
>
>
> Hi.
>
> One of the scripts we run for systems management causes puppet to say:
>
> 
> notice:  /Stage[main]//Exec[script]/returns:  executed successfully
> 
>
> How can I suppress or quiet this output?  
>
> -G
>
>
>
>
>
>
>
> -- 
> ---
> Geoff Galitz, gga...@shutterstock.com 
> WebOps 
> Shutterstock Images
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Installing LibreOffice 4 via wheezy-backports

[Gonéri Le Bouder]

On Wednesday, July 31, 2013 12:19:23 AM UTC+2, Jaap Winius wrote:
>
> Hi folks, 
>
> When my initial attempt to install libreoffice via wheezy-backports 
> didn't work, I decided to take a less elegant approach: 
>
Hi Jaap,

Did you try with:
provider => 'aptitude',

package { 'libreoffice':
ensure => installed,
provider => 'aptitude',
install_options => { '-t' => 'wheezy-backports' },
}

Best regards,
-- 
Gonéri

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] New release of fatmcgav-netapp module.

[fatmcgav]

Evening all,

Thought I'd drop a quick line through to say that I have just released
v0.4.0 of my Netapp network device module.

A full changelog can be found on the Forge [1] or Git [2], however the
highlights are:
 * Removed the need for a special config file to define username/password.
Now pulled from connect string.
N.B: This will not work with existing configuration, so will require config
tweaks before usage.
 * Support for NetApp Quotas
 * Re-factored a lot of code to use helper functions
 * Loads of new tests

Massive thanks to Stefan Schulte for a lot of the code changes that have
made it into this release.

As always, feel free to drop me a line or respond to this message with any
questions/issues.

Cheers again.
Gavin

[1] http://forge.puppetlabs.com/fatmcgav/netapp/0.4.0
[2] https://github.com/fatmcgav/fatmcgav-netapp/blob/v0.4-fixes/CHANGELOG

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet vs Oracle Enterprise Manager (cm pack)?

[Byron Miller]

We use both as they solve different problems.  I don't use any of the OS 
provisioning or metering in 12c as i use puppet for that but being that we 
run a lot of oracle stuff, i use the oracle management tool packs quite 
extensively.  We run puppet agents offline and use mcollective to 
orchestrate all changes, that way there isn't the burden of so many agents 
running on each host 100% of the time.. (Which was the biggest downfall of 
Puppet + 12c)

What features are you looking to implement? What are you trying to solve? 
do you already have 12c licensing? What is your vitalization or hardware 
layer?


On Saturday, September 28, 2013 6:40:11 PM UTC-5, dkoleary wrote:
>
> Hey;
>
> I'm still very new to puppet having *just* finished the pro puppet book. 
>  Going to have to go back to that a few times for re-reading, I suspect. 
>  Any rate, I have a client who's leaning very heavily towards OEM w/the 
> configuration management pack.  Despite some fairly exhaustive google 
> sessions, I haven't been able to find a direct comparison between these 
> two.  I have found a couple of troubling points (like cost); but, nothing 
> saying how well these two CM apps compare/contrast with each other.  Does 
> anyone here have any experience w/OEM and how it compares against puppet?
>
> Any info, stories, tips, or links would be greatly appreciated.
>
> Thanks.
>
> Doug O'Leary
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] hiera oddities

[Tom Hanstra]

Pete: Thanks for pointing this out as well.  It explains some things that 
were confusing me about how I was using hiera.  I appreciate the 
information.

Tom

On Saturday, September 28, 2013 7:16:00 AM UTC-4, Peter Meier wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> > My current setup has a puppet master and an agent.  On both I have 
> > the same /etc/hiera.yaml file linked into the /etc/puppet 
> > directory.  I've also been able to confirm that hiera is seeing the 
> > right json files in /var/lib/hiera. 
>
> Note: if you want to go with plain master/agent setup, there is no 
> need to setup hiera on the client. As the agent gets a compiled 
> catalog from the master that can be seen as kind of static, at least 
> all the hiera lookups are done when the agent receives the catalog. 
>
> ~pete 
>
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.14 (GNU/Linux) 
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ 
>
> iEYEARECAAYFAlJGumsACgkQbwltcAfKi394RgCfQ8+6+7uqJx02XO9wKux/Qb2k 
> W8QAoK/tCiEO3Q2w4gY1q/3GENSqrI07 
> =nmWj 
> -END PGP SIGNATURE- 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] best practice for managing multiple stanzas within a config file?

[Thomas]

What is the best way to manage multiple stanza within a config file?

For a splunk configuration file (inputs.conf) I need to manage some thing 
like

[monitor://var/log]
blacklist = someRegularExpression
whitelist = someOtherRegularExpression

[monitor://var/lib/ourApp]


There can be multiple monitor stanzas and each may or may not have a 
whitelist or blacklist.

I haven't found any thing on the forge or in this group regarding best 
practice for managing stanzas within a config file.

I've tried a few different combinations of templates, concat and define and 
haven't found a clean solution yet to construct the stanza. 

Any suggestions would be appreciated.

Thanks! Thomas

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] hiera config oddness

[Denmat]

Hi,

It isn't finding the file name declared as your hostname.

Two things here I would suggest.

1. Use certname instead of hostname. Hostname can easily be changed but 
certname a little harder.
2. Use puppet master --no-daemonize --debug (on the master) and look for the 
hiera log output.

In any case, point two will show you how hiera is performing its lookups and 
what files it is using.

Den

On 01/10/2013, at 3:43, Bret Wortman  wrote:

> I'm trying to set up hiera for the first time, and something really odd is 
> happening.
> 
> I set up my hiera.yaml file in /etc/puppet/, and it was pretty simple:
> 
> ---
> :backends:
>   - yaml
> :hierarchy:
>   - "%{hostname}"
>   - common
> 
> :yaml:
>   :datadir: /etc/puppet/data
> 
> So I added a "flag" class, which just has a manifest containing one "notify" 
> so I can see that it's getting loaded. I stuck it in "data/common.yaml":
> 
> ---
> puppetserver : 'zgepetto.foo.net'
> ipamaster : 'ipamaster'
> 
> classes:
>   - role::base
>   - flag
> 
> And lo and behold, the notify showed up when I ran puppet agent -t --noop.
> 
> Then I tried moving the flag mention into a file named for my test node, 
> zw129.yaml:
> 
> ---
> classes:
>   - role::workstation
>   - flag
> 
> But the flag never got picked up. Confused, I moved it back to common.yaml 
> and there it was again. Eventually, I got around to removing "common" from my 
> hiera.yaml file (leaving only the "{hostname}" in the hierarchy) and still 
> common is getting loaded, even after doing a "service puppetmaster restart".
> 
> I've looked around for other instances of hiera.yaml but don't see any. What 
> else could be causing hiera to load a common.yaml that I'm not asking for, 
> and neglecting the zw129.yaml that I am asking for? It sure feels like I'm 
> picking up an incorrect config file somewhere, but I'm not sure where to look 
> or what logfile to examine next.
> 
> Thanks!
> 
> 
> Bret Wortman
> 
> http://damascusgrp.com/
> http://about.me/wortmanbret
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Installing LibreOffice 4 via wheezy-backports

[Jaap]

On Mon, 30 Sep 2013 12:53:15 -0700, Gonéri Le Bouder wrote:

> Did you try with:
> provider => 'aptitude',
> 
> package { 'libreoffice':
> ensure => installed,
> provider => 'aptitude',
> install_options => { '-t' => 'wheezy-backports' },
> }

That works -- excellent! Thank you very much, Gonéri; that improves my 
puppet configuration considerably. :-)

Cheers,

Jaap

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Installing LibreOffice 4 via wheezy-backports

[Jaap]

On Mon, 30 Sep 2013 12:53:15 -0700, Gonéri Le Bouder wrote:

> provider => 'aptitude',
> 
> package { 'libreoffice':
> ensure => installed,
> provider => 'aptitude',
> install_options => { '-t' => 'wheezy-backports' },
> }

One small note. On subsequent runs of "puppet agent -t" the above 
configuration results in the following type of message for all of the 
wheezy-backports packages to install:

notice: /Package[libreoffice]/ensure: ensure changed '1:3.5.4+dfsg2-0
+deb7u2' to 'install'

This also slows down every single run of the Puppet client. Luckily, the 
fix is easy: just use "ensure => present," instead.

Cheers,

Jaap

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet vs Oracle Enterprise Manager (cm pack)?

[dkoleary]

Hey;

>>We use both as they solve different problems.

Thank you very much for responding!  All of the searching I've been doing 
has slowly lead me to that same conclusion, but I don't have any solid 
facts or sites to back it up.  

My client also has a lot of oracle stuff.  I'm sure they could start using 
rhel w/o issue, but it's almost exclusively OEL at this point.  They say 
they have the license for OEM 12c; but, so far, I've not been able to 
confirm the license for the CM pack - which, if I'm reading it right, is 
*not* cheap and does not come with the base OEM.

I've read about the mcollective but haven't had a chance to try it yet. 
 Good to know that there's a performance issue running both of puppet and 
OEM simultaneously.

As for the environment: as I mentioned, it's mostly OEL but they do have a 
smattering of rhel ver 4 and 5.  Most of the systems are now vmware guests; 
but, there are a few physicals - mostly the rhel4 systems, still running.  

>>What are you trying to solve? 

That, right there, is my core problem.  I haven't yet been able to hammer 
that down; but, I believe that the other admin (the one pushing for OEM) 
and I are trying to solve different problems.  She's looking for something 
that'll automate patching + some other nebulous things on which I haven't 
gotten a clear answer.  I'm looking for a tool through which I can nail 
down system configurations - ensuring that they're kept consistent across 
all environments - and help automate configuration change distributions. 
 I'm a UNIX admin but also a security guy at heart (CISSP/CISA).

So, short version: I need to figure out what my client's trying to solve 
(not as easy an investigation as one would hope) and, from there, I can 
figure out whether or not OEM will be sufficient.

At your convenience, any chance you could expand on the concept that they 
solve different problems?

Thanks again, very much, for your response.  It's nice getting at least a 
partial confirmation that what I was suspecting is accurate.

Doug O"Leary

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: PuppetDB 1.5.0 Available

[Chris Price]

PuppetDB 1.5.0 is now available for download!  This is a new feature
release that contains a few bug-fixes as well.

=
## Downloads ##
=

Available in native package format at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Puppet module:
http://forge.puppetlabs.com/puppetlabs/puppetdb

Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/

# Documentation (including how to install):
http://docs.puppetlabs.com/puppetdb/1.
5

# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues



##  PuppetDB 1.5.0 Release Notes  ##


Notable features and improvements:

* (#21520) Configuration for soft failure when PuppetDB is unavailable

  This feature adds a new option 'soft_write_failure' to the puppetdb
  configuration.  If enabled the terminus behavior is changed so that if a
  command or write fails, instead of throwing an exception and causing the
agent
  to stop it will simply log an error to the puppet master log.

* New v3 query API

  New `/v3` URLs are available for all query endpoints.  The `reports` and
  `events` endpoints, which were previously considered `experimental`, have
  been moved into `/v3`.  Most of the other endpoints are 100%
backwards-compatible
  with `/v2`, but now offer additional functionality.  There are few minor
  backwards-incompatible changes, detailed in the comments about individual
  endpoints below.

* Query paging

  This feature adds a set of new HTTP query parameters that can be used
with most
  of the query endpoints (`fact_names`, `facts`, `resources`, `nodes`,
`events`,
  `reports`, `event-counts`) to allow paging through large result sets over
  multiple queries.  The available HTTP query parameters are:

 * `limit`: an integer specifying the maximum number of results to
return.
 * `order-by`: a list of fields to sort by, in ascending or descending
order.
The legal set of fields varies by endpoint; see the documentation
for
individual endpoints for more info.
 * `offset`: an integer specifying the first result in the result set
that
should be returned.  This can be used in combination with `limit`
and `order-by` to page through a result set over multiple queries.
 * `include-total`: a boolean flag which, if set, will cause the HTTP
response
   to contain an `X-Records` header indicating the total number of
results that are
   available that match the query.  (Mainly useful in combination with
`limit`.)

* New features available on `events` endpoint

* The `events` data now contains `file` and `line` fields.  These
indicate
  the location in the manifests where the resource was declared.  They
can
  be used as input to an `events` query.
* Add new `configuration-version` field, which contains the value that
Puppet
  supplied during the agent run.
* New `containing-class` field: if the resource is declared inside of a
  Puppet class, this field will contain the name of that class.
* New `containment-path` field: this field is an array showing the full
  path to the resource from the root of the catalog (contains an ordered
  list of names of the classes/types that the resource is contained
within).
* New queryable timestamp fields:
* `run-start-time`: the time (on the agent node) that the run began
* `run-end-time`: the time (on the agent node) that the run
completed
* `report-receive-time`: the time (on the puppetdb node) that the
report was received by PuppetDB
* Restrict results to only include events that occurred in the latest
report
  for a given node: `["=", "latest-report?", true]`

* New `event-counts` endpoint

`v3` of the query API contains a new `event-counts` endpoint, which can
be
used to retrieve count data for an event query.  The basic input to the
endpoint is an event query, just as you'd provide to the `events`
endpoint,
but rather than returning the actual events, this endpoint returns
counts
of `successes`, `failures`, `skips`, and `noops` for the events that
match
the query.  The counts may be aggregated on a per-resource, per-class,
or per-node basis.

* New `aggregate-event-counts` endpoint

  This endpoint is similar to the `event-counts` endpoint, but rather than
  aggregating the counts on a per-node, per-resource, or per-class basis,
  it returns aggregate counts across your entire population.

* New `server-time` endpoint

  This endpoint simply returns a timestamp indicating the current time on
  the PuppetDB server.  This can be used as input to time-based queries
  against timestamp fields that are populated by PuppetDB.

* Minor changes to `resources` endpoint for `v3`

  The `sourcefile` and `sourceline` fields have been renamed to `file` and
`line`,
  for consistency with other parts of the API.

* Mi

[Puppet Users] Re: [Puppet-dev] Announce: PuppetDB 1.5.0 Available

[William Van Hevelingen]

No packages for precise/raring? Its missing debs for 1.5.0. Lucid seems fine

Thanks,
William


On Mon, Sep 30, 2013 at 4:56 PM, Chris Price  wrote:

> PuppetDB 1.5.0 is now available for download!  This is a new feature
> release that contains a few bug-fixes as well.
>
> =
> ## Downloads ##
> =
>
> Available in native package format at:
> http://yum.puppetlabs.com and http://apt.puppetlabs.com
>
> Puppet module:
> http://forge.puppetlabs.com/puppetlabs/puppetdb
>
> Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/
>
> # Documentation (including how to install):
> http://docs.puppetlabs.com/puppetdb/1.
> 5
>
> # Issues can be filed at:
> http://projects.puppetlabs.com/projects/puppetdb/issues
>
>
> 
> ##  PuppetDB 1.5.0 Release Notes  ##
> 
>
> Notable features and improvements:
>
> * (#21520) Configuration for soft failure when PuppetDB is unavailable
>
>   This feature adds a new option 'soft_write_failure' to the puppetdb
>   configuration.  If enabled the terminus behavior is changed so that if a
>   command or write fails, instead of throwing an exception and causing the
> agent
>   to stop it will simply log an error to the puppet master log.
>
> * New v3 query API
>
>   New `/v3` URLs are available for all query endpoints.  The `reports` and
>   `events` endpoints, which were previously considered `experimental`, have
>   been moved into `/v3`.  Most of the other endpoints are 100%
> backwards-compatible
>   with `/v2`, but now offer additional functionality.  There are few minor
>   backwards-incompatible changes, detailed in the comments about individual
>   endpoints below.
>
> * Query paging
>
>   This feature adds a set of new HTTP query parameters that can be used
> with most
>   of the query endpoints (`fact_names`, `facts`, `resources`, `nodes`,
> `events`,
>   `reports`, `event-counts`) to allow paging through large result sets over
>   multiple queries.  The available HTTP query parameters are:
>
>  * `limit`: an integer specifying the maximum number of results to
> return.
>  * `order-by`: a list of fields to sort by, in ascending or descending
> order.
> The legal set of fields varies by endpoint; see the documentation
> for
> individual endpoints for more info.
>  * `offset`: an integer specifying the first result in the result set
> that
> should be returned.  This can be used in combination with `limit`
> and `order-by` to page through a result set over multiple queries.
>  * `include-total`: a boolean flag which, if set, will cause the HTTP
> response
>to contain an `X-Records` header indicating the total number of
> results that are
>available that match the query.  (Mainly useful in combination with
> `limit`.)
>
> * New features available on `events` endpoint
>
> * The `events` data now contains `file` and `line` fields.  These
> indicate
>   the location in the manifests where the resource was declared.  They
> can
>   be used as input to an `events` query.
> * Add new `configuration-version` field, which contains the value that
> Puppet
>   supplied during the agent run.
> * New `containing-class` field: if the resource is declared inside of a
>   Puppet class, this field will contain the name of that class.
> * New `containment-path` field: this field is an array showing the full
>   path to the resource from the root of the catalog (contains an
> ordered
>   list of names of the classes/types that the resource is contained
> within).
> * New queryable timestamp fields:
> * `run-start-time`: the time (on the agent node) that the run began
> * `run-end-time`: the time (on the agent node) that the run
> completed
> * `report-receive-time`: the time (on the puppetdb node) that the
> report was received by PuppetDB
> * Restrict results to only include events that occurred in the latest
> report
>   for a given node: `["=", "latest-report?", true]`
>
> * New `event-counts` endpoint
>
> `v3` of the query API contains a new `event-counts` endpoint, which
> can be
> used to retrieve count data for an event query.  The basic input to the
> endpoint is an event query, just as you'd provide to the `events`
> endpoint,
> but rather than returning the actual events, this endpoint returns
> counts
> of `successes`, `failures`, `skips`, and `noops` for the events that
> match
> the query.  The counts may be aggregated on a per-resource, per-class,
> or per-node basis.
>
> * New `aggregate-event-counts` endpoint
>
>   This endpoint is similar to the `event-counts` endpoint, but rather than
>   aggregating the counts on a per-node, per-resource, or per-class basis,
>   it returns aggregate counts across your entire population.
>
> * New `server-time` endpoint
>
>   This endpoint s

[Puppet Users] Re: best practice for managing multiple stanzas within a config file?

[Rahul Khengare]

Hi Thomas,
   You can make use of *augeas* resource type of puppet yo manage the 
config files.

Refer following links for augeas resource type and project,
http://docs.puppetlabs.com/references/latest/type.html#augeas
http://projects.puppetlabs.com/projects/1/wiki/puppet_augeas

Thanks and Regards,
Rahul Khengare
NTT DATA OSS Center, Pune, India.

On Tuesday, October 1, 2013 4:05:20 AM UTC+5:30, Thomas wrote:
>
> What is the best way to manage multiple stanza within a config file?
>
> For a splunk configuration file (inputs.conf) I need to manage some thing 
> like
>
> [monitor://var/log]
> blacklist = someRegularExpression
> whitelist = someOtherRegularExpression
>
> [monitor://var/lib/ourApp]
>
>
> There can be multiple monitor stanzas and each may or may not have a 
> whitelist or blacklist.
>
> I haven't found any thing on the forge or in this group regarding best 
> practice for managing stanzas within a config file.
>
> I've tried a few different combinations of templates, concat and define 
> and haven't found a clean solution yet to construct the stanza. 
>
> Any suggestions would be appreciated.
>
> Thanks! Thomas
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.