Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Dan White]

http://docs.puppetlabs.com/dashboard/manual/1.2/using.html

On Dec 13, 2013, at 5:18 PM, Stuart Cracraft  wrote:

> Okay, now puppet-dashboard is installed on my Puppet Master and I am ready 
> and ripe.
> 
> How do I access the dashboard?

“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.” 
Bill Waterson (Calvin & Hobbes)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7350A19F-830C-467F-9204-6D7BA45BDEF3%40comcast.net.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppetlabs-firewall and Logging

[Jim Miller]

I forgot to add, yes the rules are being generated and outbound DNS logs 
are being generated.. AND I FOUND THE ISSUE.  You have to specify a 
protocol in ALL chains.  Or in the case where you specified it earlier (for 
LOG and custom chains 'proto => 'any').

with no protocol specified rules default to tcp

-A dns_out -p tcp -m comment --comment "024 dns_out" -j LOG --log-prefix 
"dns_out"
-A dns_out -p tcp -m comment --comment "025 dns_out" -j ACCEPT
---

with proto => 'any' 
--
-A dns_out -m comment --comment "024 dns_out" -j LOG --log-prefix "dns_out"
-A dns_out -m comment --comment "025 dns_out" -j ACCEPT
-
I get the desired results.



*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:dns_out - [0:0]
:ssh_in - [0:0]
-A INPUT -p icmp -m comment --comment "000 accept all icmp" -j ACCEPT
-A INPUT -i lo -m comment --comment "001 accept all to lo interface" -j 
ACCEPT
-A INPUT -m comment --comment "002 accept related established rules INPUT" 
-m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -s 10.xx.xx.0/23 -i eth0 -p tcp -m multiport --ports 22 -m comment 
--comment "005 fwd to ssh in" -m state --state NEW -j ssh_in
-A INPUT -m comment --comment "998 drop all INPUT" -j DROP
-A OUTPUT -m comment --comment "003 accept related established rules 
OUTPUT" -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -d 10.xx.xx.2X/32 -o eth0 -p tcp -m multiport --ports 53 -m 
comment --comment "015 fwd to dns_out" -m state --state NEW -j dns_out
-A OUTPUT -d 10.xx.X0.2x/32 -p udp -m multiport --ports 53 -m comment 
--comment "016 fwd to dns_out" -j dns_out
-A OUTPUT -d 10.xx.X.2x/32 -o eth0 -p tcp -m multiport --ports 53 -m 
comment --comment "018 fwd to dns_out" -m state --state NEW -j dns_out
-A OUTPUT -d 10.xx.X.2x/32 -p udp -m multiport --ports 53 -m comment 
--comment "026 fwd to dns_out" -j dns_out
-A OUTPUT -m comment --comment "999 drop all OUTPUT" -j DROP
-A dns_out -p tcp -m comment --comment "024 dns_out" -j LOG --log-prefix 
"dns_out"
-A dns_out -p tcp -m comment --comment "025 dns_out" -j ACCEPT
-A ssh_in -p tcp -m comment --comment "009 ssh_in" -j LOG --log-prefix 
"ssh_in"
-A ssh_in -p tcp -m comment --comment "011 ssh_in" -j ACCEPT
COMMIT


On Friday, December 13, 2013 6:15:25 PM UTC-6, Jim Miller wrote:
>
> These rules are being applied in the pre.pp so they run first.  Since 
> we're just testing this out the only rules we have are in pre.pp and 
> post.pp.  In pre.pp the rules are SSH and DNS, and post.pp drop everything 
> else.  
>
> I'm wondering how much traction this module has since it seems log and 
> drop is not supported.  Again, I ask if anyone can generically share some 
> working rules for tcp/udp.  Or if this isn't the module to use which one is?
>
>
> Thanks all,
>
>
> On Wednesday, December 11, 2013 10:02:08 PM UTC-6, Jeff Bachtel wrote:
>>
>>  Are you seeing the not-working rules generate iptables rules (verify 
>> with iptables-save after applying manifest)?
>>
>> Also, it's been a while since I dug into the ruby that generates the 
>> rules, you should probably use the before operator -> between rules to 
>> enforce ordering, like
>>
>>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
>> destination => '10.x8.x0.x5', proto => 'udp', port => '53', action => 
>> 'accept', } ->
>>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
>> destination => '10.x8.x0.x5', proto => 'tcp', state => 'NEW', port => '53', 
>> action => 'accept', }
>>
>> Jeff
>>
>> On 12/11/2013 10:24 PM, Jim Miller wrote:
>>  
>> We're testing out the Puppetlabs-Firewall module.  And it seems I'm 
>> either missing something fundamental or Logging/Accpet works/doesn't work 
>> in an irregular way.  I would be most grateful for some input.
>>
>> *COMMON:*
>>   firewall { '002 accept related established rules INPUT': proto => 
>> 'all', state => ['RELATED', 'ESTABLISHED'], action => 'accept' }
>>   firewall { '003 accept related established rules OUTPUT': chain => 
>> 'OUTPUT', proto => 'all', state => ['RELATED', 'ESTABLISHED'], action => 
>> 'accept' }
>>
>> *This works for new inbound SSH connections:*
>>   firewall { '007 fwd to ssh_in': chain => 'INPUT', iniface => 'eth0', 
>> source => '10.x8.xx1.0/24', proto => 'tcp', state => 'NEW', port => '22', 
>> action => 'accept' }
>>
>>
>> *This works for inbound SSH connections: *  firewallchain { 
>> 'ssh_in:filter:IPv4': ensure => present, }
>>
>>   firewall { '008 fwd to ssh_in': chain => 'INPUT', iniface => 'eth0', 
>> source => '10.x8.xx1.0/24', proto => 'tcp', state => 'NEW', port => '22', 
>> jump => 'ssh_in' }
>>   firewall { '009 ssh_in': chain => 'ssh_in', jump => 'LOG', log_prefix 
>> => 'ssh_in ' }
>>   firewall { '011 ssh_in': chain => 'ssh_in', action => 'accept' }
>>
>>
>> *This works for DNS:*
>>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
>> destination => '10.x8.x0.x5', proto => 'udp', port => '53', action => 
>> 'acce

[Puppet Users] Problem with runonce in Puppet Enterprise console

[Ken Weiss]

I am trying to use the Puppet Enterprise console to execute an on-demand 
Puppet agent run on a single managed node. If I don't set any options for 
the runonce command, it works fine. But if I try to set any options at all, 
I get this error:

Cannot specify any custom puppet options when the daemon is running


There are only two Puppet-related processes running on the managed node:


> ps -ef | grep puppet

root 10883 1  0 Oct21 ?00:03:11 /opt/puppet/bin/ruby 
/opt/puppet/bin/puppet agent

root 11810 1  0 Dec08 ?00:00:44 /opt/puppet/bin/ruby 
/opt/puppet/sbin/mcollectived --pid /var/run/pe-mcollective.pid
Which one do I need to kill in order to be able to specify 'noop=true' when 
I execute the runonce from the console? And, if I kill the 'daemon' on the 
managed node, will mcollective still periodically run a 'puppet apply' on 
that node? Or will I then have to run Puppet manually from the console (or 
periodically from a cron entry) to ensure that the node is compliant with 
the state defined in Puppet?

--Ken

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8b14229f-fa31-45e3-aca3-2355061f97c0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppetlabs-firewall and Logging

[Jim Miller]

These rules are being applied in the pre.pp so they run first.  Since we're 
just testing this out the only rules we have are in pre.pp and post.pp.  In 
pre.pp the rules are SSH and DNS, and post.pp drop everything else.  

I'm wondering how much traction this module has since it seems log and drop 
is not supported.  Again, I ask if anyone can generically share some 
working rules for tcp/udp.  Or if this isn't the module to use which one is?


Thanks all,


On Wednesday, December 11, 2013 10:02:08 PM UTC-6, Jeff Bachtel wrote:
>
>  Are you seeing the not-working rules generate iptables rules (verify with 
> iptables-save after applying manifest)?
>
> Also, it's been a while since I dug into the ruby that generates the 
> rules, you should probably use the before operator -> between rules to 
> enforce ordering, like
>
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x5', proto => 'udp', port => '53', action => 
> 'accept', } ->
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x5', proto => 'tcp', state => 'NEW', port => '53', 
> action => 'accept', }
>
> Jeff
>
> On 12/11/2013 10:24 PM, Jim Miller wrote:
>  
> We're testing out the Puppetlabs-Firewall module.  And it seems I'm either 
> missing something fundamental or Logging/Accpet works/doesn't work in an 
> irregular way.  I would be most grateful for some input.
>
> *COMMON:*
>   firewall { '002 accept related established rules INPUT': proto => 'all', 
> state => ['RELATED', 'ESTABLISHED'], action => 'accept' }
>   firewall { '003 accept related established rules OUTPUT': chain => 
> 'OUTPUT', proto => 'all', state => ['RELATED', 'ESTABLISHED'], action => 
> 'accept' }
>
> *This works for new inbound SSH connections:*
>   firewall { '007 fwd to ssh_in': chain => 'INPUT', iniface => 'eth0', 
> source => '10.x8.xx1.0/24', proto => 'tcp', state => 'NEW', port => '22', 
> action => 'accept' }
>
>
> *This works for inbound SSH connections: *  firewallchain { 
> 'ssh_in:filter:IPv4': ensure => present, }
>
>   firewall { '008 fwd to ssh_in': chain => 'INPUT', iniface => 'eth0', 
> source => '10.x8.xx1.0/24', proto => 'tcp', state => 'NEW', port => '22', 
> jump => 'ssh_in' }
>   firewall { '009 ssh_in': chain => 'ssh_in', jump => 'LOG', log_prefix => 
> 'ssh_in ' }
>   firewall { '011 ssh_in': chain => 'ssh_in', action => 'accept' }
>
>
> *This works for DNS:*
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x5', proto => 'udp', port => '53', action => 
> 'accept', }
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x5', proto => 'tcp', state => 'NEW', port => '53', 
> action => 'accept', }
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x6', proto => 'udp', port => '53', action => 
> 'accept', }
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x6', proto => 'tcp', state => 'NEW', port => '53', 
> action => 'accept', }
>
>
> *This does NOT work for DNS:*
>   firewallchain { 'dns_out:filter:IPv4': ensure => present, }
>
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x5', proto => 'udp', port => '53', jump => 
> 'dns_out', }
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x5', proto => 'tcp', state => 'NEW', port => '53', 
> jump => 'dns_out', }
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x6', proto => 'udp', port => '53', jump => 
> 'dns_out', }
>   firewall { '016 fwd to dns_out': chain => 'OUTPUT', outiface => 'eth0', 
> destination => '10.x8.x0.x6', proto => 'tcp', state => 'NEW', port => '53', 
> jump => 'dns_out', }
>
>   firewall { '024 dns_out': chain => 'dns_out', jump => 'LOG', log_prefix 
> => 'dns_out', }
>   firewall { '025 dns_out': chain => 'dns_out', action => 'accept', }
>
>
> None of the above rules generates any errors. 
> My understanding of reading the doc is the default policy is 'accept' when 
> not specified (not sure about custom chains).  When I try to connect to the 
> server, I don't see logs being generated.
>
> Thanks,
> Jim
>
>
>
>  -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/e12d97d9-2e43-482c-aa22-7bccaf6de17d%40googlegroups.com
> .
> 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 em

[Puppet Users] Re: Multiple runs needed to update configs?

[Jules]

A colleague of mine had a similar issue. When he ran it, the first time it 
failed and the second time it succeeds.
 
We noticed that his init.pp under modules/manifest doesn't contain a class. 
By adding an empty class, e.g. class xyz { }, solved the issue.

On Saturday, February 25, 2012 2:11:36 PM UTC-5, Mike Knell wrote:

> Hey folks,
>
> I've got a fairly basic out-of-the-box puppetmaster/puppet setup (out
> of the box on Ubuntu, that is), but am running into a bit of an odd
> problem with updating clients.
>
> The first time a host runs Puppet, and every time I change anything in
> the configs on the server, the agent has to run once and abort for
> each included class (module, thing..) on the machine I'm trying to
> configure before it finally just works after 'n' tries and everything
> works fine.
>
> I've tried to Google this, asked some colleagues with Puppet smarts,
> and not come up with any useful hints. Anyone got any idea what's
> going on here? See below for a sample run of (multiple) attempts.
>
> Cheers,
> Mike
>
> # puppet agent --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find class unix for hostname.uffish.net at
> /etc/puppet/manifests/templates.pp:2 on node hostname.uffish.net
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> # puppet agent --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find class users for hostname.uffish.net at
> /etc/puppet/manifests/templates.pp:3 on node hostname.uffish.net
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> # puppet agent --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find class ntp for hostname.uffish.net at
> /etc/puppet/manifests/templates.pp:8 on node hostname.uffish.net
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> # puppet agent --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find class bind for hostname.uffish.net at
> /etc/puppet/manifests/templates.pp:9 on node hostname.uffish.net
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> # puppet agent --test
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find class squid for hostname.uffish.net at
> /etc/puppet/manifests/templates.pp:24 on node hostname.uffish.net
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
> # puppet agent --test
> info: Caching catalog for hostname.uffish.net
> (from here on in, runs normally)
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b453e637-4067-4c0b-903a-907cb75a7973%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] New to puppet and recieving mcollective error

[Alan Renouf]

Im new to puppet and installed it in my home lab to mess with, when i 
installed it i used the hostname rather than FQDN so went back and changed 
puppet and reran the certificate tool to regenerate the certificates etc, 
the agent works fine now but i am getting an mccollective error i think, is 
there anything in the config i need to change for mccollective after 
altering the name to the FQDN?  My error is below..  Thanks!


root@testnix:~# puppet agent --test

Info: Retrieving plugin

Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/puppetdb_server_status.rb

Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/iptables_persistent_version.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/windows.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_version.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb

Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/postgres_default_version.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb

Info: Loading facts in 
/var/opt/lib/pe-puppet/lib/facter/ip6tables_version.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_version.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/staging_http_get.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb

Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb

Info: Caching catalog for testnix.home.lan

Info: Applying configuration version '1386955608'

Notice: 
/Stage[main]/Pe_mcollective::Server/File[/etc/puppetlabs/mcollective/server.cfg]/content:
 

--- /etc/puppetlabs/mcollective/server.cfg 2013-06-07 11:09:23.0 
-0700

+++ /tmp/puppet-file20131213-2681-oblovd 2013-12-13 09:24:46.579199297 -0800

@@ -1,22 +1,55 @@

-topicprefix = /topic/

+# Centrally managed by Puppet version 3.3.1 (Puppet Enterprise 3.1.0)

+topicprefix = /topic/

 main_collective = mcollective

-collectives = mcollective

-libdir = /opt/puppet/libexec/mcollective/

-logfile = /var/log/pe-mcollective/mcollective.log

-loglevel = info

-daemonize = 1

+collectives = mcollective

+libdir  = /opt/puppet/libexec/mcollective/

+logfile = /var/log/pe-mcollective/mcollective.log

+loglevel= info

+daemonize   = 1

 

+identity = testnix.home.lan

 # Plugins

-securityprovider = psk

-plugin.psk = unset

+securityprovider   = ssl

+plugin.ssl_server_private = 
/etc/puppetlabs/mcollective/ssl/mcollective-private.pem

+plugin.ssl_server_public = 
/etc/puppetlabs/mcollective/ssl/mcollective-public.pem

+plugin.ssl_client_cert_dir = /etc/puppetlabs/mcollective/ssl/clients/

+plugin.ssl_serializer = yaml

 

-connector = stomp

-plugin.stomp.host = localhost

-plugin.stomp.port = 61613

-plugin.stomp.user = mcollective

-plugin.stomp.password = secret

+connector = activemq

+plugin.activemq.pool.size = 1

+plugin.activemq.pool.1.host = puppetmaster.home.lan

+plugin.activemq.pool.1.port = 61613

+plugin.activemq.pool.1.user = mcollective

+plugin.activemq.pool.1.password = ngT4ya8aAEnWHaoEsLQl

+plugin.activemq.pool.1.ssl = true

+plugin.activemq.pool.1.ssl.ca = 
/etc/puppetlabs/mcollective/ssl/mcollective-cacert.pem

+plugin.activemq.pool.1.ssl.key = 
/etc/puppetlabs/mcollective/ssl/mcollective-private.pem

+plugin.activemq.pool.1.ssl.cert = 
/etc/puppetlabs/mcollective/ssl/mcollective-cert.pem

 

 # Facts

 factsource = yaml

 plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml

 

+# Puppet Classes

+classesfile = /var/opt/lib/pe-puppet/classes.txt

+

+# Puppet Agent plugin configuration

+plugin.puppet.command = /opt/puppet/bin/puppet agent

+plugin.puppet.config  = /etc/puppetlabs/puppet/puppet.conf

+

+plugin.puppet.splay = true

+plugin.puppet.splaylimit = 120

+

+# Periodcally broadcast metdata for registration purposes.

+# This registration plugin will broadcast current Facter fact values.

+registration = Meta

+# registerinterval is intentionally "long" to prevent systems from being 
overly

+# chatty on the message bus by default.  If you want a higher frequency, 
this

+# may be set to 300 (5 minutes)

+registerinterval = 600

+

+# authorization

+rpcauthorization = 1

+rpcauthprovider = action_policy

+plugin.actionpolicy.allow_unconfigured = 1

+direct_addressing = 1


*Error: Could not back up /etc/puppetlabs/mcollective/server.cfg: 
Connection refused - connect(2)*

*Error: Could not back up /etc/puppetlabs/mcollective/server.cfg: 
Connection refused - connect(2)*

*Error: 
/Stage[main]/Pe_mcollective::Server/File[/etc/puppetlabs/mcollective/server.cfg]/content:
 
change from {md5}a9c7335a83c5ac9f6a19bb195ea0c63e to 
{md5}32b98584ef48c0b099f43fd1f70e05fc failed: Could not back up 
/etc/puppetlabs/mcollective/server.cfg: Connection refused - connect(2)*

Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: 
Dependency File[/etc

[Puppet Users] Resource ordering only using Hiera?

[Joseph Swick]

Hello,
I'm trying to come up with a generic wrapper class for use with hiera so
that I can have a service that is completely managed and configured via
hiera and its own puppet module to be notified by Puppet of changes to a
file or other resource managed by a different class/module.  The example
I'm using here is the management of /etc/security/limits.conf for a
service account that only needs to be changed on certain systems.

[Yes, I could put the configuration of the limits.conf into the module
for this particular service, but I'm trying to keep the dependencies of
that module to a minimum so that it is portable.]

Picture the following yaml hiera data for a node (the basic::limits
class is a wrapper for the puppet-limits module):

---
classes:
  - foo
  - basic::limits
foo::option_1: true
basic::limits::instance:
  foo_limits:
user: 'foobar'
limit_type: 'nofile'
hard: '1'
soft: '1'


If I create a separate class, I can do the resource ordering normally as
expected:

class tmp {
  Limits::Limits['foo_limits'] ~> Service['foo']
}


This separate class ensures that changes to the limits configuration
properly notifies the service to restart.  However, I don't want to
clutter up our puppet configuration with a lot of singular
modules/classes just for resource ordering and would like to be able to
define it just in hiera.  Therefore, I attempted to create a generic
wrapper define for resource ordering (the following doesn't actually
work, will get to the error):

#Define for resource ordering or subscribing
define basic::order_resource::ordering (
  $resource1_type = undef,
  $resource1_name = undef,
  $resource2_type = undef,
  $resource2_name = undef,
  $notify = false,
){
  if $notify {
$resource1_type[$resource1_name] ~> $resource2_type[$resource2_name]
  } else {
$resource1_type[$resource1_name] -> $resource2_type[$resource2_name]
  }
}


And a wrapper class to use it via hiera:

#basic::order_resource
class basic::order_resource ($instance){
  $real_instance = hiera_hash(basic::order_resource::instance)
  create_resources(basic::order_resource::ordering, $real_instance)
}


Sample yaml in hieradata:

basic::order_resource::instance:
  foo_limits_sub:
resource1_type: Limits::Limits
resource1_name: foo_limits
resource2_type: Service
resource2_name: foo
notify: true


However, as I already stated, my generic define doesn't actually work
and returns the following error because Puppet can't/doesn't evaluate
the variable as an actual resource type:

Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: resource1_type is not a hash or array when accessing it with
foo_limits at
/etc/puppet/modules/basic/manifests/order_resource/ordering.pp:10 on
node vagrant-centos-6


What am I missing to get Puppet to evaluate the $resourceX_type
variables as a resource type [e.g: File, Service, etc.] to get this to
work?  I'd like to try do it this way so that I don't have to make a
very long, messy and hard to maintain class with a lot of nested case
statements to perform a similar function.  That is, unless there's some
other method that I haven't considered/found/thought of.

sample nested case code (this will get ugly fast and isn't very flexible):
case $resource1_type {
  'File': {
case $resource2_type {
  'Service': {
if $notify {
  File[$resource1_name] ~> Service[$resource2_name]
} else {
  File[$resource1_name] -> Service[$resource2_name]
}
  }
  default: {fail("Unknown resource type '${resource2_type}' for
\$resource2_type")}
}
  }
  default: {fail("Unknown resource type '${resource1_type}' for
\$resource1_type")}
}


Thank you for taking the time to wade through my lengthy question.
-- 
Joseph Swick 
Operations Engineer
Meltwater Group



signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] how to see which classes are assigned to a node?

[Mike Delaney]

On the client, the list of classes applied in the last successful puppet
run should be written to $vardir/state/classes.txt


On Fri, Dec 13, 2013 at 2:29 PM, Paul Archer  wrote:

> I'm trying to get my classes setup in hiera, but I'm having some issues,
> and having problems troubleshooting them.
> There doesn't seem to be any way to query either the puppetmaster or the
> client to get a list of the classes that the client actually gets.
>
> Running 'puppet node find my.node.example.com' should spit out a list of
> classes, but it doesn't.
>
> Any suggestions?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/afa1919b-8824-404c-ad10-1666dbaf682e%40googlegroups.com
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAELFvUmnNXQtpT2eMM6Jj8Y2rczBYjKZMFi4Mh_bgrSPR%2BCS3w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] get a *structured* version of the puppet agent output

[David Portabella]

wow, thanks for this very exhaustive answer!

is there a way to get the list of resources created when using a puppet 
apply (instead of puppet agent)?

the point is that we need this when refactoring puppet modules, in order to 
test the modules in a vagrant machine and check that there are not 
regression issues.
so, i run our current puppet modules in a vagrant machine, get the list of 
all puppet resources created,
then i refactor the puppet modules, i run again the refactored puppet 
modules in a new vagrant machine,
and i compare all the files and other resources.


On Friday, December 13, 2013 7:32:39 PM UTC+1, Charlie Sharpsteen wrote:
>
> On Friday, December 13, 2013 5:30:19 AM UTC-8, David Portabella wrote:
>
> Given this puppet manifest (test.pp):
>> $dir = '/tmp'
>> file {'myfile':
>>   path => "$dir/myfile.txt",
>>   content => 'hello'
>> }
>>
>> puppet produces this report:
>> [...]
>> File[myfile]: !ruby/object:Puppet::Resource::Status
>>   resource: File[myfile]
>>   file: /Users/david/test.pp
>>   line: 4
>>   evaluation_time: 0.001354
>>   change_count: 1
>>   out_of_sync_count: 1
>>   tags: 
>> - file
>> - myfile
>> - class
>>   time: 2013-12-13 11:44:59.092716 +01:00
>>   events: 
>> - !ruby/object:Puppet::Transaction::Event
>>   audited: false
>>   property: ensure
>>   previous_value: !ruby/sym absent
>>   desired_value: !ruby/sym file
>>   historical_value: 
>>   message: "defined content as 
>> '{md5}5d41402abc4b2a76b9719d911017c592'"
>>   name: !ruby/sym file_created
>>   status: success
>>   time: 2013-12-13 11:44:59.093067 +01:00
>>   out_of_sync: true
>>   changed: true
>>   resource_type: File
>>   title: myfile
>>   skipped: false
>>   failed: false
>>   containment_path: 
>> - Stage[main]
>> - ""
>> - File[myfile]
>> [...]
>>
>> so, the report tells that it has created File[myfile],
>> but it does not contain the path of the file /tmp/myfile.txt.
>>
>> that's a pity, because it means that I cannot get a list of all the files 
>> updated by puppet.
>>
>> is there a way to get the final path of all File resources created by 
>> puppet?
>> (not "$dir/myfile.txt", but "/tmp/myfile.txt")
>>
>  The report is focused on describing the changes that occurred during that 
> run. To that end, only the title is included as that information is 
> sufficient to uniquely identify the reporting resource when combined with 
> resource_type. Information concerning properties that were not changed 
> during the run is omitted as this data can be obtained from the catalog 
> that the agent was processing.
>
> In this specific situation, you can modify your file resource such that 
> the path is used as the title:
>
> $dir = '/tmp'
> file { "$dir/myfile.txt":
>   content => 'hello'
> }
>
> However, the general problem of matching changes to resources can be 
> solved by loading the report and then loading the catalog and joining the 
> two datasets using the resource_type and title. However, this particular 
> task is one of the problems PuppetDB was designed to solve. PuppetDB stores 
> both the catalogs and reports and provides an API that can be used to query 
> the data.
>
> For example, the changes related to myfile can be retrieved by querying 
> the events 
> endpointof 
> the PuppetDB API:
>
> curl -G 'http://localhost:8080/v3/events' --data-urlencode query=\'["and", 
> ["=", "resource-type", "File"],
>   ["=", "containing-class", "Testfile"],
>   ["=", "certname", "pe-310-agent.puppetdebug.vlan"]]'
>
> Which gives results similar to the following:
>
> [ {
>
>   "status" : "success",
>   "timestamp" : "2013-12-13T17:11:39.144Z",
>   "certname" : "pe-310-agent.puppetdebug.vlan",
>   "containing-class" : "Testfile",
>   "containment-path" : [ "Stage[main]", "Testfile", "File[myfile]" ],
>   "report" : "6bed5163b50b5857921b5ec27d9147b428c684f8",
>   "run-start-time" : "2013-12-13T17:11:29.382Z",
>   "resource-title" : "myfile",
>   "configuration-version" : "1386954691",
>   "run-end-time" : "2013-12-13T17:11:36.527Z",
>   "property" : "ensure",
>   "message" : "defined content as '{md5}5d41402abc4b2a76b9719d911017c592'",
>   "new-value" : "file",
>   "old-value" : "absent",
>   "line" : 44,
>   "file" : "/etc/puppetlabs/puppet/modules/testfile/manifests/init.pp",
>   "report-receive-time" : "2013-12-13T17:11:41.334Z",
>   "resource-type" : "File"} ]
>
> The resource contained in the catalog delivered to that node, which 
> contains properties such as the path, can be retrieved by passing the 
> resource Type and title to the resources 
> endpoint
> :
>
> curl -G 'http://localhost:8080/v3/resources/File/myfile' --data-urlencode 
> 'query=["=", "certname", "pe-310-a

[Puppet Users] how to see which classes are assigned to a node?

[Paul Archer]

I'm trying to get my classes setup in hiera, but I'm having some issues, 
and having problems troubleshooting them.
There doesn't seem to be any way to query either the puppetmaster or the 
client to get a list of the classes that the client actually gets.

Running 'puppet node find my.node.example.com' should spit out a list of 
classes, but it doesn't.

Any suggestions?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/afa1919b-8824-404c-ad10-1666dbaf682e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard: how to connect?

[Stuart Cracraft]

Okay, now puppet-dashboard is installed on my Puppet Master and I am ready 
and ripe.

How do I access the dashboard?


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0f180467-733b-4c4d-8dca-c919823cba27%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Stuart Cracraft]

Hey Ygor and Jeff.

I went to www.redhat.com, logged in, accessed the customer portal, went 
into the packages
and then searched for and found my rubygem-rake-0.8.7-2.1.el6.noarch.rpm, 
then rpm -i'd
then did a yum install puppet-dashboard and voila!!!

YEAH

Stuart

On Friday, December 13, 2013 2:00:20 PM UTC-8, Jeff Bachtel wrote:

>  yum-config-manager --enable rhel-6-server-optional-rpms
>
> Has worked on some RHEL machines, for me. It depends on how your system is 
> subscribed whether that will work or whether you'll need to use another 
> command.
>
> Jeff
>
>  On 12/13/2013 04:50 PM, Stuart Cracraft wrote:
>  
>  Great!
>
>  What is the .repo file format for the optional channel for rhel 6.
>
>  I would like to install puppet-dashboard using the above as soon as 
> possible.
>
>  Stuart
>
> On Friday, December 13, 2013 11:27:41 AM UTC-8, Matthaus Litteken wrote:
>
>> Stuart, 
>> rubygem(rake) is provided by the rubygem-rake package, available in 
>> centos 6 or in the optional channel for rhel 6. 
>>
>> On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft  
>> wrote: 
>> > yum install puppet-dashboard gives a requirement for dependency 
>> resolution: 
>> > 
>> >   Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs) 
>> >  Requires: rubygem(rake) 
>> > 
>> > My question is, how to install rubygem so that puppet-dashboard 
>> installs? 
>> > 
>> > Stuart 
>> > 
>> > 
>> > On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote: 
>> >> 
>> >> Hi - I run puppet 3.3.2 currently of Open Source Puppet. 
>> >> 
>> >> I am looking for anyone who has run Puppet Dashboard. 
>> >> 
>> >> How do I connect to the dashboard? 
>> >> 
>> >> Stuart 
>> >> 
>> > -- 
>> > 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...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com.
>>  
>>
>> > 
>> > For more options, visit https://groups.google.com/groups/opt_out. 
>>
>>
>>
>> -- 
>> Matthaus Owens 
>> Release Manager, 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/650e0e91-ff04-4eb8-aa2e-31aa2fe98add%40googlegroups.com
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5a0a26bb-b786-43d8-9257-5cc2956f14fa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Pass variable to class from hiera puppetlabs-apache

[Paul Archer]

The classes indicator/variable/key (whatever it's officially called) is 
only for classes. 
Then in the appropriate yaml file, specify:
apache::mpm_module: false
or whatever. It's that easy.

So your file should look like:

classes:
 - apache

apache::mpm_module: false
apache::mod::prefork: true
apache::mod::php: this
apache::mod::rewrite: that
apache::mod::ssl: "the other"



On Friday, December 13, 2013 5:03:17 AM UTC-6, Yuriy Gerasimov wrote:
>
> Hi,
>
> I am cleaning my manifest by moving things to hiera yaml config file.
>
> For the https://github.com/puppetlabs/puppetlabs-apache I need to 
> pass mpm_module variable as false like:
>
> class { 'apache':
>   mpm_module => false
> }
>
> But I can't figure out how to do this in hiera yaml file. I include 
> classes using hiera_include('classes').
>
> I tried 
>
> classes:
>  - apache
>  - apache::mpm_module: false
>  - apache::mod::prefork
>  - apache::mod::php
>  - apache::mod::rewrite
>  - apache::mod::ssl
>
> But I get error
>
> Error: undefined method `downcase' for {"apache::mpm_module"=>false}:Hash 
> at /tmp/vagrant-puppet/manifests/site.pp:13 on node precise64.asus
>
> Please advise how properly pass variables to classes in yaml files?
>
> Thank you a lot
>
> Yuriy
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/36e6635a-4508-4aa5-86d6-dd3ad3279c8e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet node find doesn't return classes and scope vars ?

[Paul Archer]

I see that puppet 3.3.2 has the problem as well. Worse, the documentation 
for 'puppet node' doesn't match the actual command.


On Friday, December 13, 2013 11:13:26 AM UTC-6, Jon McKenzie wrote:
>
> Re-upping this topic rather than creating a new one.
>
> I'm using Puppet 3.3.1 and am still having this problem.
>
>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/25ab52dd-6501-43f8-9cb3-d88da100d17d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Jeff Bachtel]

yum-config-manager --enable rhel-6-server-optional-rpms

Has worked on some RHEL machines, for me. It depends on how your system 
is subscribed whether that will work or whether you'll need to use 
another command.


Jeff

On 12/13/2013 04:50 PM, Stuart Cracraft wrote:

Great!

What is the .repo file format for the optional channel for rhel 6.

I would like to install puppet-dashboard using the above as soon as 
possible.


Stuart

On Friday, December 13, 2013 11:27:41 AM UTC-8, Matthaus Litteken wrote:

Stuart,
rubygem(rake) is provided by the rubygem-rake package, available in
centos 6 or in the optional channel for rhel 6.

On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft
> wrote:
> yum install puppet-dashboard gives a requirement for dependency
resolution:
>
>   Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs)
>  Requires: rubygem(rake)
>
> My question is, how to install rubygem so that puppet-dashboard
installs?
>
> Stuart
>
>
> On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft
wrote:
>>
>> Hi - I run puppet 3.3.2 currently of Open Source Puppet.
>>
>> I am looking for anyone who has run Puppet Dashboard.
>>
>> How do I connect to the dashboard?
>>
>> Stuart
>>
> --
> 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...@googlegroups.com .
> To view this discussion on the web visit
>

https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com

.

>
> For more options, visit https://groups.google.com/groups/opt_out
.



-- 
Matthaus Owens

Release Manager, 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/650e0e91-ff04-4eb8-aa2e-31aa2fe98add%40googlegroups.com.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52AB8374.1010500%40bericotechnologies.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Windows - MSI that shows up in Windows Features instead of Add/Remove Programs

[Josh D]

I assume you're referring to the DSIM module (
https://forge.puppetlabs.com/puppetlabs/dism )?

>From what I understand is that module is only good for installing existing 
features.  In other words, there doesn't appear to be a way to install a 
new feature from an MSI using that module.

On Friday, December 13, 2013 10:12:28 AM UTC-7, Rob Reynolds wrote:
>
> Josh, 
>  Have you tried using Windows-Features module that is on the forge to do 
> this instead?  As you are seeing, this is not currently a supported 
> scenario. It could be something we would add in the future though. I just 
> want to explore alternatives first.
>
>
> On Fri, Dec 13, 2013 at 1:06 AM, Josh D 
> > wrote:
>
>> I'm trying to deploy IE11 through puppet.  I've created a custom MSI 
>> using the IE Administration Kit that supports silent installs.  The problem 
>> is, IE is "built into" Windows, so rather than showing up in the installed 
>> programs list, it winds up in Windows Features.  I figured this would cause 
>> a problem, if I attempted to install it as a package since Puppet is 
>> checking the list of installed "programs" to see whether or not it needs to 
>> install the package.  As I expected, Puppet attempts to install the MSI 
>> everytime it's executed.  Is there any way to get it to check windows 
>> features in addition to installed programs?  In lieu of that, does anyone 
>> have any suggestions?
>>  
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/f1150eac-4100-4c6f-96b8-58531e53c84c%40googlegroups.com
>> .
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/29ee8eb0-eec1-4bc5-ac20-49b60b64ef8f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[ygor]

Check with your local admin with access to Red Hat Network. That is their job. 
"Sometimes I think the surest sign that intelligent life exists 
elsewhere in the universe is that none of it has tried to contact us."Bill Waterson (Calvin & Hobbes)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1601847732.31168.1386971790837.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Stuart Cracraft]

Great!

What is the .repo file format for the optional channel for rhel 6.

I would like to install puppet-dashboard using the above as soon as 
possible.

Stuart

On Friday, December 13, 2013 11:27:41 AM UTC-8, Matthaus Litteken wrote:

> Stuart, 
> rubygem(rake) is provided by the rubygem-rake package, available in 
> centos 6 or in the optional channel for rhel 6. 
>
> On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft 
> > 
> wrote: 
> > yum install puppet-dashboard gives a requirement for dependency 
> resolution: 
> > 
> >   Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs) 
> >  Requires: rubygem(rake) 
> > 
> > My question is, how to install rubygem so that puppet-dashboard 
> installs? 
> > 
> > Stuart 
> > 
> > 
> > On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote: 
> >> 
> >> Hi - I run puppet 3.3.2 currently of Open Source Puppet. 
> >> 
> >> I am looking for anyone who has run Puppet Dashboard. 
> >> 
> >> How do I connect to the dashboard? 
> >> 
> >> Stuart 
> >> 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com.
>  
>
> > 
> > For more options, visit https://groups.google.com/groups/opt_out. 
>
>
>
> -- 
> Matthaus Owens 
> Release Manager, 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/650e0e91-ff04-4eb8-aa2e-31aa2fe98add%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Interpolating hiera variables in hiera itself

[Guy Knights]

Well, wouldn't you know it but I just discovered the hiera() lookup 
function which does exactly what I want.

On Friday, 13 December 2013 11:39:27 UTC-8, Guy Knights wrote:
>
> Is it possible to reuse hiera variables within hiera itself? We have some 
> cases where we have a value that needs to be changed before we deploy some 
> code - it's not ideal, but for now it has to be done this way. The value is 
> used within a hash structure that is somewhat complex, and this value is 
> the only component of that hash that needs to change.
>
> What I was hoping is that I could do something like this:
>
> ---
> value: '1.1.0'
>
> haproxy_frontends:
>   http-in:
> ipaddress: '*'
> ports: '9000'
> options:
>   acl:
> - "review_path url_sub version=%{game_version}"
>   use_backend:
> - 'review if review_path'
>   default_backend: 'current'
>   
> However, it doesn't seem like this is possible. If I try to do this, when 
> 'haproxy_frontends' is used, nothing is output for %{game_version}.
>
> Is there a way to actually do this?
>
> Thanks,
> Guy
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c9ac272f-62be-483d-824a-46552dac69c3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Module team update: 2013-09-24 - 2013-12-12

[Ashley Penney]

I'd like to start by apologizing.  I went from weekly, to monthly to
apparently every 3 months.  It's been a really busy couple of months and
I've let these slide for too long.  I've made myself a calendar entry and
I'll try and be more diligent about these.


What have you guys been doing?!

We've been working primarily on some internal projects around testing over
the last few months, which has resulted in us being a little bit less
visible than previously.  We'll be ready to discuss more details of this
shortly, and will communicate extensively what we've been working on. In
the meantime we've been working on the following unrelated things that we
can talk about in the meantime:

Like what?


I've written a fairly large "Advanced Design Of Modules", an attempted
walkthrough to build an SSH module that includes everything from "best
practices" for manifests to types and providers as well as testing of all
these pieces.  We're still in the editing stage, but hopefully we'll be
able to get this out to the community eventually as a way of helping you
all build modules.  Once this is finished I’ll post an early preview here
on the lists and ask for early commentary (or just point out the bad bits
of my code, that’s fine too.)


Get to the modules!


We haven't been completely idle these last months, but the majority of the
work that's occurred has been due to the community.  We've had an amazing
outpouring of work, and I hesitate to mention names as I'll start
forgetting people and causing offense, but "blkperl", "igalic", and
"jhoblitt" have been very active, along with many other contributors.  In
the last three months there's been an amazing amount of work on apache,
mysql, and concat, amongst the other modules.


Apache has had *234* commits since 0.9.0.
Mysql has had *140* commits since 1.0.0.
Concat has had *87* (really complex) commits since the last list update.

So there's been a huge amount of work going on, almost all completely
community derived, which we love!

More specifically in terms of what's been going on:

Apache

A huge amount of work on bugfixes, polish, features, but the largest part
of this work introduced FreeBSD and Apache 2.4 support.  This is going to
be crucial for our support for RHEL7 (which is now in beta as of earlier
this week) as well as Debian as it hopefully moves to 2.4 also.  We
released 0.10.0 which rolled up all of this work and is available on the
forge.

MySQL

Most of the work for MySQL involved bugfixing.  There's more to do but
we've nailed down some of the more complex bugs in the providers as a
result of community testing, and we'd love to get more use cases from you
(in the form of chunks of manifest) to help us test this module more
extensively.  Some of the logic involved in parsing MySQL output is ..
hairy.. at the best of times, so this has been ongoing work.

Concat

Huge amounts of work have gone into concat, all driven by Josh Hoblitt.
 He's been focusing primarily on modernizing the manifest side of things,
deprecating unrequired parameters and writing volumes of awesome testing
code.

I just looked up his commit stats and in the last month or two he's:

33 
commits
 / 2,899 ++ / 1,775 --

We'll be looking to release this work shortly once we merge in some
documentation rewrites.  Oh, and it also supports Windows now, so that's
nice! :)

In terms of releases:


http://forge.puppetlabs.com/puppetlabs/activemq/0.2.0

http://forge.puppetlabs.com/puppetlabs/reboot/0.1.2

http://forge.puppetlabs.com/puppetlabs/ruby/0.1.0

http://forge.puppetlabs.com/puppetlabs/haproxy/0.4.1

http://forge.puppetlabs.com/puppetlabs/quantum/2.2.0

http://forge.puppetlabs.com/puppetlabs/razor/0.10.2

http://forge.puppetlabs.com/puppetlabs/pe_upgrade/2.1.0

http://forge.puppetlabs.com/puppetlabs/apt/1.4.0

http://forge.puppetlabs.com/puppetlabs/rabbitmq/3.1.0

http://forge.puppetlabs.com/puppetlabs/ntp/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/grizzly/1.0.0

http://forge.puppetlabs.com/puppetlabs/puppetdb/3.0.0

http://forge.puppetlabs.com/puppetlabs/gce_compute/0.2.0

http://forge.puppetlabs.com/puppetlabs/mongodb/0.3.0

http://forge.puppetlabs.com/puppetlabs/mysql/2.1.0

http://forge.puppetlabs.com/puppetlabs/vcsrepo/0.2.0

http://forge.puppetlabs.com/puppetlabs/mcollective/1.1.3

http://forge.puppetlabs.com/puppetlabs/openstack/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/keystone/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/glance/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/horizon/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/nova/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/cinder/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/swift/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/neutron/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/ceilometer/3.0.0-rc1

http://forge.puppetlabs.com/puppetlabs/passenger/0.2.0

http://forge.puppetlabs.com/puppetlabs/mssql/0.2.0

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Dan White]

http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-puppet-dashboard-1
 



“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.” 
Bill Waterson (Calvin & Hobbes) 

- Original Message -
From: "Stuart Cracraft"  
To: puppet-users@googlegroups.com 
Sent: Friday, December 13, 2013 12:44:58 PM 
Subject: [Puppet Users] Re: Puppet Dashboard: how to connect? 



yum install puppet-dashboard gives a requirement for dependency resolution: 


Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs) 
Requires: rubygem(rake) 


My question is, how to install rubygem so that puppet-dashboard installs? 


Stuart 

On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote: 



Hi - I run puppet 3.3.2 currently of Open Source Puppet. 


I am looking for anyone who has run Puppet Dashboard. 


How do I connect to the dashboard? 


Stuart 





-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com
 . 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/164590.29104.1386964097129.JavaMail.root%40sz0126a.westchester.pa.mail.comcast.net.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Interpolating hiera variables in hiera itself

[Guy Knights]

Is it possible to reuse hiera variables within hiera itself? We have some 
cases where we have a value that needs to be changed before we deploy some 
code - it's not ideal, but for now it has to be done this way. The value is 
used within a hash structure that is somewhat complex, and this value is 
the only component of that hash that needs to change.

What I was hoping is that I could do something like this:

---
value: '1.1.0'

haproxy_frontends:
  http-in:
ipaddress: '*'
ports: '9000'
options:
  acl:
- "review_path url_sub version=%{game_version}"
  use_backend:
- 'review if review_path'
  default_backend: 'current'
  
However, it doesn't seem like this is possible. If I try to do this, when 
'haproxy_frontends' is used, nothing is output for %{game_version}.

Is there a way to actually do this?

Thanks,
Guy

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3d877042-9c2f-4b2f-b613-5477e9339593%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet Dashboard: how to connect?

[Matthaus Owens]

Stuart,
rubygem(rake) is provided by the rubygem-rake package, available in
centos 6 or in the optional channel for rhel 6.

On Fri, Dec 13, 2013 at 9:44 AM, Stuart Cracraft  wrote:
> yum install puppet-dashboard gives a requirement for dependency resolution:
>
>   Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs)
>  Requires: rubygem(rake)
>
> My question is, how to install rubygem so that puppet-dashboard installs?
>
> Stuart
>
>
> On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote:
>>
>> Hi - I run puppet 3.3.2 currently of Open Source Puppet.
>>
>> I am looking for anyone who has run Puppet Dashboard.
>>
>> How do I connect to the dashboard?
>>
>> Stuart
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAd0RBdHtJ14tkBoStL5xrp-Xe1p1X_UQMovePAGnYSv9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

[Jon Yeargers]

Answer here: 
http://stackoverflow.com/questions/14607385/puppet-does-not-start-a-service-varnish-when-puppet-apply-is-run



On Friday, December 13, 2013 11:07:01 AM UTC-8, Jon Yeargers wrote:
>
> Just out of curiosity I created my own 'dmidecode' package with a trivial 
> (does nothing) dmidecode executable. Once this was installed the rest of 
> puppet v 3.3.2 installed fine.
>
> NOW: it's having trouble accepting that certain services are already 
> running and it's trying to restart them every time. Strangely enough it 
> doesn't happen with 'system' services (EG apache2, snmpd) but only with my 
> code. I can't imagine this is related to my fake dmidecode but I'll keep 
> looking into it.
>
> On Friday, December 13, 2013 4:08:10 AM UTC-8, Felix.Frank wrote:
>>
>> Ideally, there will be a newly released facter package that replaces 
>> this dependency by a suggestion or recommendation. It will Just Work for 
>> you then. 
>>
>> In the meantime, these are your options: 
>> a) fetch the facter source package and build a forked package without 
>> this dependency 
>> b) fetch all deb packages you require and install them in one go using 
>> dpkg -i --force-depends or similar. 
>>
>> Option (a) is simple if you're versed in the creation of Debian 
>> packages, and pretty difficult if you're not. 
>>
>> HTH, 
>> Felix 
>>
>> On 12/13/2013 12:39 PM, Jon Yeargers wrote: 
>> > So am I SOL on this? Is ARM considered an 'unsupported architecture' 
>> > until I can create a 'dmidecode' for this platform? 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0b3e34b1-e3e1-4e8d-8a3a-23ab6be1bf8d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

[Jon Yeargers]

Just out of curiosity I created my own 'dmidecode' package with a trivial 
(does nothing) dmidecode executable. Once this was installed the rest of 
puppet v 3.3.2 installed fine.

NOW: it's having trouble accepting that certain services are already 
running and it's trying to restart them every time. Strangely enough it 
doesn't happen with 'system' services (EG apache2, snmpd) but only with my 
code. I can't imagine this is related to my fake dmidecode but I'll keep 
looking into it.

On Friday, December 13, 2013 4:08:10 AM UTC-8, Felix.Frank wrote:
>
> Ideally, there will be a newly released facter package that replaces 
> this dependency by a suggestion or recommendation. It will Just Work for 
> you then. 
>
> In the meantime, these are your options: 
> a) fetch the facter source package and build a forked package without 
> this dependency 
> b) fetch all deb packages you require and install them in one go using 
> dpkg -i --force-depends or similar. 
>
> Option (a) is simple if you're versed in the creation of Debian 
> packages, and pretty difficult if you're not. 
>
> HTH, 
> Felix 
>
> On 12/13/2013 12:39 PM, Jon Yeargers wrote: 
> > So am I SOL on this? Is ARM considered an 'unsupported architecture' 
> > until I can create a 'dmidecode' for this platform? 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/40a9fd9d-127e-48b9-8c67-c284ca6bd694%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] get a *structured* version of the puppet agent output

[Charlie Sharpsteen]

On Friday, December 13, 2013 5:30:19 AM UTC-8, David Portabella wrote:

Given this puppet manifest (test.pp):
> $dir = '/tmp'
> file {'myfile':
>   path => "$dir/myfile.txt",
>   content => 'hello'
> }
>
> puppet produces this report:
> [...]
> File[myfile]: !ruby/object:Puppet::Resource::Status
>   resource: File[myfile]
>   file: /Users/david/test.pp
>   line: 4
>   evaluation_time: 0.001354
>   change_count: 1
>   out_of_sync_count: 1
>   tags: 
> - file
> - myfile
> - class
>   time: 2013-12-13 11:44:59.092716 +01:00
>   events: 
> - !ruby/object:Puppet::Transaction::Event
>   audited: false
>   property: ensure
>   previous_value: !ruby/sym absent
>   desired_value: !ruby/sym file
>   historical_value: 
>   message: "defined content as 
> '{md5}5d41402abc4b2a76b9719d911017c592'"
>   name: !ruby/sym file_created
>   status: success
>   time: 2013-12-13 11:44:59.093067 +01:00
>   out_of_sync: true
>   changed: true
>   resource_type: File
>   title: myfile
>   skipped: false
>   failed: false
>   containment_path: 
> - Stage[main]
> - ""
> - File[myfile]
> [...]
>
> so, the report tells that it has created File[myfile],
> but it does not contain the path of the file /tmp/myfile.txt.
>
> that's a pity, because it means that I cannot get a list of all the files 
> updated by puppet.
>
> is there a way to get the final path of all File resources created by 
> puppet?
> (not "$dir/myfile.txt", but "/tmp/myfile.txt")
>
 The report is focused on describing the changes that occurred during that 
run. To that end, only the title is included as that information is 
sufficient to uniquely identify the reporting resource when combined with 
resource_type. Information concerning properties that were not changed 
during the run is omitted as this data can be obtained from the catalog 
that the agent was processing.

In this specific situation, you can modify your file resource such that the 
path is used as the title:

$dir = '/tmp'
file { "$dir/myfile.txt":
  content => 'hello'
}

However, the general problem of matching changes to resources can be solved 
by loading the report and then loading the catalog and joining the two 
datasets using the resource_type and title. However, this particular task 
is one of the problems PuppetDB was designed to solve. PuppetDB stores both 
the catalogs and reports and provides an API that can be used to query the 
data.

For example, the changes related to myfile can be retrieved by querying the 
events 
endpoint of 
the PuppetDB API:

curl -G 'http://localhost:8080/v3/events' --data-urlencode query=\'["and", 
["=", "resource-type", "File"],
  ["=", "containing-class", "Testfile"],
  ["=", "certname", "pe-310-agent.puppetdebug.vlan"]]'

Which gives results similar to the following:

[ {

  "status" : "success",
  "timestamp" : "2013-12-13T17:11:39.144Z",
  "certname" : "pe-310-agent.puppetdebug.vlan",
  "containing-class" : "Testfile",
  "containment-path" : [ "Stage[main]", "Testfile", "File[myfile]" ],
  "report" : "6bed5163b50b5857921b5ec27d9147b428c684f8",
  "run-start-time" : "2013-12-13T17:11:29.382Z",
  "resource-title" : "myfile",
  "configuration-version" : "1386954691",
  "run-end-time" : "2013-12-13T17:11:36.527Z",
  "property" : "ensure",
  "message" : "defined content as '{md5}5d41402abc4b2a76b9719d911017c592'",
  "new-value" : "file",
  "old-value" : "absent",
  "line" : 44,
  "file" : "/etc/puppetlabs/puppet/modules/testfile/manifests/init.pp",
  "report-receive-time" : "2013-12-13T17:11:41.334Z",
  "resource-type" : "File"} ]

The resource contained in the catalog delivered to that node, which 
contains properties such as the path, can be retrieved by passing the 
resource Type and title to the resources 
endpoint
:

curl -G 'http://localhost:8080/v3/resources/File/myfile' --data-urlencode 
'query=["=", "certname", "pe-310-agent.puppetdebug.vlan"]'

This returns all the parameters of interest:

[ {
  "parameters" : {
"path" : "/tmp/myfile.txt",
"mode" : "0755",
"content" : "hello",
"backup" : "main",
"alias" : [ "/tmp/myfile.txt" ]
  },
  "line" : 45,
  "file" : "/etc/puppetlabs/puppet/modules/testfile/manifests/init.pp",
  "exported" : false,
  "tags" : [ "default", "node", "myfile", "testfile", "class", "file" ],
  "title" : "myfile",
  "type" : "File",
  "resource" : "93f90701c8f54a485246a9e3725040f1992fd90b",
  "certname" : "pe-310-agent.puppetdebug.vlan"} ]

The power of PuppetDB in this situation is that your reporting script can 
now focus on analyzing the data instead of finding and then filtering it.

Hope this helps!
-- 
Charlie Sharpsteen
Open Source Support Engineer
Puppet Labs

-- 
You received this me

Re: [Puppet Users] get a *structured* version of the puppet agent output

[Stuart Cracraft]

You ask a great question.

Also, it would be great if we could get the actual Unix cli equivalent of 
what Puppet is proposing to do.

On Friday, December 13, 2013 5:30:19 AM UTC-8, David Portabella wrote:

> Given this puppet manifest (test.pp):
> $dir = '/tmp'
> file {'myfile':
>   path => "$dir/myfile.txt",
>   content => 'hello'
> }
>
> puppet produces this report:
> [...]
> File[myfile]: !ruby/object:Puppet::Resource::Status
>   resource: File[myfile]
>   file: /Users/david/test.pp
>   line: 4
>   evaluation_time: 0.001354
>   change_count: 1
>   out_of_sync_count: 1
>   tags: 
> - file
> - myfile
> - class
>   time: 2013-12-13 11:44:59.092716 +01:00
>   events: 
> - !ruby/object:Puppet::Transaction::Event
>   audited: false
>   property: ensure
>   previous_value: !ruby/sym absent
>   desired_value: !ruby/sym file
>   historical_value: 
>   message: "defined content as 
> '{md5}5d41402abc4b2a76b9719d911017c592'"
>   name: !ruby/sym file_created
>   status: success
>   time: 2013-12-13 11:44:59.093067 +01:00
>   out_of_sync: true
>   changed: true
>   resource_type: File
>   title: myfile
>   skipped: false
>   failed: false
>   containment_path: 
> - Stage[main]
> - ""
> - File[myfile]
> [...]
>
> so, the report tells that it has created File[myfile],
> but it does not contain the path of the file /tmp/myfile.txt.
>
> that's a pity, because it means that I cannot get a list of all the files 
> updated by puppet.
>
> is there a way to get the final path of all File resources created by 
> puppet?
> (not "$dir/myfile.txt", but "/tmp/myfile.txt")
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8b0f3577-d5e4-4a55-abdb-cc15cbe949de%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet Dashboard: how to connect?

[Stuart Cracraft]

yum install puppet-dashboard gives a requirement for dependency resolution:

  Error: Package: puppet-dashboard-1.2.23-1.el6.noarch (puppetlabs)
 Requires: rubygem(rake)

My question is, how to install rubygem so that puppet-dashboard installs?

Stuart

On Friday, December 13, 2013 9:25:55 AM UTC-8, Stuart Cracraft wrote:

> Hi - I run puppet 3.3.2 currently of Open Source Puppet.
>
> I am looking for anyone who has run Puppet Dashboard.
>
> How do I connect to the dashboard?
>
> Stuart
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b501fed0-1922-4445-b577-1d212c70970d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] How best to distribute yaml file for custom fact?

[Bret Wortman]

That seems to do the trick (I went with the site.pp addition). Thanks for
your help!



*Bret Wortman*
http://about.me/wortmanbret



On Fri, Dec 13, 2013 at 11:17 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:

> Hi,
>
> I can at least supply a sensible workaround: In your templates, instead
> of relying on @factname being available, use
>
> has_variable?("@factname") ? @factname : 
>
> Untested, not sure if this works with the @varname syntax in templates.
>
> Alternatively, you can do this in site.pp:
>
> if ! $factname { $factname =  }
>
> Depending on circumstance, this won't address your issue. As yet another
> alternative, you can keep puppet from parsing the template at all when
> the fact is not yet present with the same syntax.
>
> HTH,
> Felix
>
> On 12/12/2013 08:25 PM, Bret Wortman wrote:
> > I have a yaml file I'd like to distribute to my systems, and it contains
> > some identifiers which help determine where that system is (this _can_
> > be determined from the IP address, but it's so much nicer to use a
> > custom fact -- we're basically assigning names to our various subnets
> > and storing those in these yaml files where we can use them in manifests
> > and templates).
> >
> > The problem is that we are using them in templates. So when I try to
> > distribute the file, the template fails to parse, and the whole puppet
> > run just aborts. If it were just an error, I could deal with it. But
> > this seems to be a show-stopper. I see that 3.4.0 will have a way to
> > distribute these files as part of pluginsync, but I need this sooner
> > than that (and since I'm in production, I'm hesitant to jump to a .0
> > release in any case).
> >
> > Any bright ideas?
> >
> >
> > Bret
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/zMDPDGg9Nbw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/52AB3325.5050200%40alumni.tu-berlin.de
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN9oxgRkrdqAzm2HTxMdsiVGg1em_pgnOizB04C4F4yZdyE5Fw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard: how to connect?

[Stuart Cracraft]

Hi - I run puppet 3.3.2 currently of Open Source Puppet.

I am looking for anyone who has run Puppet Dashboard.

How do I connect to the dashboard?

Stuart

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/270ebc67-7884-401b-8503-7823c6aa1624%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: puppet node find doesn't return classes and scope vars ?

[Jon McKenzie]

Re-upping this topic rather than creating a new one.

I'm using Puppet 3.3.1 and am still having this problem.

For example, if I run:

puppet node find $(puppet config print certname) --render-as yaml 

The resulting YAML is missing ENC-set parameters (among other things).

On the other hand, if I call the Puppet server's REST API (e.g. a GET to 
https://puppet:8140/production/node/), I *do* get the ENC-set 
parameters.

I'd like to use the provided command-line tool to do this, but it doesn't 
seem to be working correctly. Am I missing something?

Thanks!

On Friday, April 5, 2013 4:14:36 AM UTC-4, Mohit Chawla wrote:
>
> Hi, 
>
> I am trying to use the node subcommand like so: 
>
> puppet node find --terminus rest --render-as yaml --mode master foo.com
>
> This only shows facts, name, environment, expiration and time but not the 
> classes or node level variables. 
>
> Puppet version is 2.7.20. Any suggestions ? 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8441d5dd-8207-4f3a-9fce-6f8ab872b199%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Windows - MSI that shows up in Windows Features instead of Add/Remove Programs

[Rob Reynolds]

Josh,
 Have you tried using Windows-Features module that is on the forge to do
this instead?  As you are seeing, this is not currently a supported
scenario. It could be something we would add in the future though. I just
want to explore alternatives first.


On Fri, Dec 13, 2013 at 1:06 AM, Josh D  wrote:

> I'm trying to deploy IE11 through puppet.  I've created a custom MSI using
> the IE Administration Kit that supports silent installs.  The problem is,
> IE is "built into" Windows, so rather than showing up in the installed
> programs list, it winds up in Windows Features.  I figured this would cause
> a problem, if I attempted to install it as a package since Puppet is
> checking the list of installed "programs" to see whether or not it needs to
> install the package.  As I expected, Puppet attempts to install the MSI
> everytime it's executed.  Is there any way to get it to check windows
> features in addition to installed programs?  In lieu of that, does anyone
> have any suggestions?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/f1150eac-4100-4c6f-96b8-58531e53c84c%40googlegroups.com
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMJiBK6dNPaxs-CV6Lw2ioA7VEZeLTnG3fF3GfJg-sMnn%2BA%3D_A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] How best to distribute yaml file for custom fact?

[Felix Frank]

Hi,

I can at least supply a sensible workaround: In your templates, instead
of relying on @factname being available, use

has_variable?("@factname") ? @factname : 

Untested, not sure if this works with the @varname syntax in templates.

Alternatively, you can do this in site.pp:

if ! $factname { $factname =  }

Depending on circumstance, this won't address your issue. As yet another
alternative, you can keep puppet from parsing the template at all when
the fact is not yet present with the same syntax.

HTH,
Felix

On 12/12/2013 08:25 PM, Bret Wortman wrote:
> I have a yaml file I'd like to distribute to my systems, and it contains
> some identifiers which help determine where that system is (this _can_
> be determined from the IP address, but it's so much nicer to use a
> custom fact -- we're basically assigning names to our various subnets
> and storing those in these yaml files where we can use them in manifests
> and templates).
> 
> The problem is that we are using them in templates. So when I try to
> distribute the file, the template fails to parse, and the whole puppet
> run just aborts. If it were just an error, I could deal with it. But
> this seems to be a show-stopper. I see that 3.4.0 will have a way to
> distribute these files as part of pluginsync, but I need this sooner
> than that (and since I'm in production, I'm hesitant to jump to a .0
> release in any case).
> 
> Any bright ideas? 
> 
> 
> Bret

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52AB3325.5050200%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Error: Puppet::Parser::AST::Resource failed with error Hiera::InterpolationLoop: Detected in [::environment]

[Roman Shiryaev]

Hello,

just upgraded Hiera from ver. 1.2.1 to 1.3.0 and broke our puppet 
environment. :)
It seems that there are sizeable changes related to variable interpolation

Here is an error during Puppet run:


Error: Puppet::Parser::AST::Resource failed with error 
Hiera::InterpolationLoop: Detected in [::environment] at 
/home/ubuntu/environments/project_dev/manifests/site.pp:35 on node 
project-dev.novalocal
Wrapped exception:
Detected in [::environment]
Error: Puppet::Parser::AST::Resource failed with error 
Hiera::InterpolationLoop: Detected in [::environment] at 
/home/ubuntu/environments/project_dev/manifests/site.pp:35 on node 
project-dev.novalocal
Error: Puppet::Parser::AST::Resource failed with error 
Hiera::InterpolationLoop: Detected in [::environment] at 
/home/ubuntu/environments/project_dev/manifests/site.pp:35 on node 
project-dev.novalocal


Line 35 in the above manifest contains the line

class { "apache": }

as we're using a standard module apache from Puppetlabs to manage an 
installation of Apache.

And here is our hiera.yaml
---
:backends:
  - yaml
:hierarchy:
  - private/%{::environment}/%{::clientcert}
  - public/%{::environment}/%{::clientcert}
  - private/%{::environment}/%{::environment}
  - public/%{::environment}/%{::environment}
  - public/%{::environment}/%{::operatingsystem}
  - public/%{::environment}/common
:yaml:
  :datadir: '/etc/puppet/hieradata/'


Any ideas how to fix the issue? Thanks.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/108d2c80-cf30-4599-80da-f70aaddb0cd1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Pass variable to class from hiera puppetlabs-apache

[Yuriy Gerasimov]

Hi,

I am cleaning my manifest by moving things to hiera yaml config file.

For the https://github.com/puppetlabs/puppetlabs-apache I need to 
pass mpm_module variable as false like:

class { 'apache':
  mpm_module => false
}

But I can't figure out how to do this in hiera yaml file. I include classes 
using hiera_include('classes').

I tried 

classes:
 - apache
 - apache::mpm_module: false
 - apache::mod::prefork
 - apache::mod::php
 - apache::mod::rewrite
 - apache::mod::ssl

But I get error

Error: undefined method `downcase' for {"apache::mpm_module"=>false}:Hash 
at /tmp/vagrant-puppet/manifests/site.pp:13 on node precise64.asus

Please advise how properly pass variables to classes in yaml files?

Thank you a lot

Yuriy

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/53358b67-e54d-4d4a-988f-3f8139bbf830%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Stdlib and Defined Types

[Trevor Vaughan]

William,

Thanks for the response. Ironically, I was trying to figure out how to
change it in production.

I had a case where all of my tests passed but production was failing. It
turned out to be some strange hiera-fu but it would have been *much* easier
to be able to just get the file path directly.

Thanks,

Trevor


On Fri, Dec 13, 2013 at 2:22 AM, William Leese
wrote:

> On Friday, December 13, 2013 5:30:26 AM UTC+9, Trevor Vaughan wrote:
>>
>> Does anyone know of a way to add a file-centric backtrace to the validate
>> functions in the Stdlib?
>>
>> If you use a validator in a defined type, you end up not having any idea
>> what actually threw the error.
>>
>
>  Annoying indeed - had this issue quite often as well. What you want is to
> change this in your checkout of stdlib (modules/stdlib):
>
> For spec/unit/puppet/parser/functions/validate_*_spec.rb
>
> Change all:
> expect { scope.compiler.compile }.to raise_error(Puppet::ParseError
>
> to:
> expect { scope.compiler.compile }.to raise_error(Puppet::Error
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/6fec71ff-df7c-4f66-a2a5-21be0e68d587%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANs%2BFoWndH6v%3Ddw4Wme1GfoJGwGBhtOjUFeWVWQ196T71O%2BrWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] get a *structured* version of the puppet agent output

[David Portabella]

Given this puppet manifest (test.pp):
$dir = '/tmp'
file {'myfile':
  path => "$dir/myfile.txt",
  content => 'hello'
}

puppet produces this report:
[...]
File[myfile]: !ruby/object:Puppet::Resource::Status
  resource: File[myfile]
  file: /Users/david/test.pp
  line: 4
  evaluation_time: 0.001354
  change_count: 1
  out_of_sync_count: 1
  tags: 
- file
- myfile
- class
  time: 2013-12-13 11:44:59.092716 +01:00
  events: 
- !ruby/object:Puppet::Transaction::Event
  audited: false
  property: ensure
  previous_value: !ruby/sym absent
  desired_value: !ruby/sym file
  historical_value: 
  message: "defined content as 
'{md5}5d41402abc4b2a76b9719d911017c592'"
  name: !ruby/sym file_created
  status: success
  time: 2013-12-13 11:44:59.093067 +01:00
  out_of_sync: true
  changed: true
  resource_type: File
  title: myfile
  skipped: false
  failed: false
  containment_path: 
- Stage[main]
- ""
- File[myfile]
[...]

so, the report tells that it has created File[myfile],
but it does not contain the path of the file /tmp/myfile.txt.

that's a pity, because it means that I cannot get a list of all the files 
updated by puppet.

is there a way to get the final path of all File resources created by 
puppet?
(not "$dir/myfile.txt", but "/tmp/myfile.txt")

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ff8d4db1-29b2-4c0e-aca8-a9d9faf4e02f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] [SOLVED] Re: puppet dashboard & ssl database connection

[Juan Sierra Pons]

fixed, it was a ca file permissions issue.

Regards

--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
--


2013/12/13 Juan Sierra Pons :
> Hi,
>
> I am configuring my puppet-dasbboard to connect to a ssl encrypted
> mysql DB server
>
> The mysql server is configured OK as using the mysql client with the
> --ssl-ca works ok
>
> mysql -u dashboard -p -h mysql.example.org --ssl-ca=/etc/mysql/ca.pem
> Enter password:
> Welcome to the MySQL monitor.  Commands end with ; or \g.
> Your MySQL connection id is 103
>
> But modifying the /etc/puppet-dashboard/database.yml and adding the
> sslca line doesn't work:
> host: mysql.example.org
> sslca: /etc/mysql/ROOTCA-eltorete.com-cacert.pem
>
> Any idea what am I missing?
>
> Best regards
>
> --
> Juan Sierra Pons j...@elsotanillo.net
> Linux User Registered: #257202
> Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
> GPG key = 0xA110F4FE
> Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
> --

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9t%3DaU0ukcSeoffWx2xa8Zeht5DAbB8xF-RcK7O68TSWvg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

[Felix Frank]

Ideally, there will be a newly released facter package that replaces
this dependency by a suggestion or recommendation. It will Just Work for
you then.

In the meantime, these are your options:
a) fetch the facter source package and build a forked package without
this dependency
b) fetch all deb packages you require and install them in one go using
dpkg -i --force-depends or similar.

Option (a) is simple if you're versed in the creation of Debian
packages, and pretty difficult if you're not.

HTH,
Felix

On 12/13/2013 12:39 PM, Jon Yeargers wrote:
> So am I SOL on this? Is ARM considered an 'unsupported architecture'
> until I can create a 'dmidecode' for this platform?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52AAF8AA.2070107%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet and MCollective

[Jason Antman]

It's great that you're using Puppet and MCollective and trying to get 
them setup everywhere, and there are some really easy ways to do that 
when provisioning a new VM - either through templates or the build 
process. Personally, I have Puppet baked in to our base installs (we 
actually don't use templates, we kickstart each machine via Cobbler) and 
use Puppet to install MCollective.


If you're wondering about *existing* VMs that for some reason you can't 
just rebuild... what about a good, old-fashioned ssh-in-a-for-loop?


-jantman

On 12/12/2013 11:54 AM, ro001 wrote:



Hi,

I am writing scripts for deployment of our software and I am also 
using MCollective on linux.


I hope to use MCollective in order to reduce the requirement of 
opening a putty session to each VM and running the puppet agent 
manually the first time (when its registers/ creates keys etc). The 
problem I see with this is that I need to log in to each machine and 
install/configure mcollective (server.cfg & client.cfg), so for this 
reason I do not save myself very much effort by using mcollective.


I am using vms so I can add mcollective to the vm template, but I wont 
know the name of mcollective/activemq machine nor would I know the 
name of the machine at that point.


How do you guys deploy mcollective?  It seems abit like a chicken/egg 
scenario!




--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d1e0fc41-6558-4abf-bcc3-1a19e418d6f5%40googlegroups.com.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52AAF890.7010706%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet dashboard & ssl database connection

[Juan Sierra Pons]

Hi,

I am configuring my puppet-dasbboard to connect to a ssl encrypted
mysql DB server

The mysql server is configured OK as using the mysql client with the
--ssl-ca works ok

mysql -u dashboard -p -h mysql.example.org --ssl-ca=/etc/mysql/ca.pem
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 103

But modifying the /etc/puppet-dashboard/database.yml and adding the
sslca line doesn't work:
host: mysql.example.org
sslca: /etc/mysql/ROOTCA-eltorete.com-cacert.pem

Any idea what am I missing?

Best regards

--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
--

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9va61b4W4T15gvfXaKO-4b75TqS8B9v1e9PcRsxf2bqXA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Getting latest agent on debian for ARM?

[Jon Yeargers]

So am I SOL on this? Is ARM considered an 'unsupported architecture' until 
I can create a 'dmidecode' for this platform?

On Wednesday, December 11, 2013 10:55:11 AM UTC-8, Jon Yeargers wrote:
>
> I can wget and install facter but the issues continue:
>
> root@plugpc-005:/tmp# apt-get install puppet
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> You might want to run 'apt-get -f install' to correct these:
> The following packages have unmet dependencies:
>  facter : Depends: dmidecode but it is not installable
>  puppet : Depends: puppet-common (= 3.3.2-1puppetlabs1) but it is not 
> going to be installed
> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or 
> specify a solution).
>
>
> root@plugpc-005:/tmp# apt-get install puppet-common
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> You might want to run 'apt-get -f install' to correct these:
> The following packages have unmet dependencies:
>  facter : Depends: dmidecode but it is not installable
>  puppet-common : Depends: ruby-shadow but it is not installable or
>   libshadow-ruby1.8 but it is not going to be 
> installed
>  Depends: libaugeas-ruby but it is not going to be 
> installed or
>   libaugeas-ruby1.9.1 but it is not going to be 
> installed or
>   libaugeas-ruby1.8 but it is not going to be 
> installed
>  Depends: hiera (>= 1.0.0) but it is not going to be 
> installed
>  Depends: ruby-rgen (>= 0.6.5) but it is not going to be 
> installed
>  Recommends: lsb-release but it is not going to be 
> installed
>  Recommends: debconf-utils but it is not going to be 
> installed
> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or 
> specify a solution).
>
>
> Attempts to install any of these packages gives me similar errors.
>
> On Wednesday, December 11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote:
>>
>>  You can fetch it directly (wget, curl, whatever) from
>>
>>
>> http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb
>>
>> Jeff
>>
>> On 12/11/2013 12:39 PM, Jon Yeargers wrote:
>>  
>>  root@plugpc-005:~# apt-get install ruby libopenssl-ruby pciutils
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Note, selecting 'libruby' instead of 'libopenssl-ruby'
>> pciutils is already the newest version.
>> libruby is already the newest version.
>> ruby is already the newest version.
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>
>>  There isn't a 'download' option for apt-get on this system so I tried 
>> '--download-only':
>>
>>  root@plugpc-005:~# apt-get --download-only install  facter
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>>  The following packages have unmet dependencies:
>>  facter : Depends: dmidecode but it is not installable
>> E: Broken packages
>>  
>>  I added '--ignore-missing' but the result was the same. 
>>
>> On Wednesday, December 11, 2013 7:47:02 AM UTC-8, Jeff Bachtel wrote: 
>>>
>>>  demidecode (which is a hard dependency for facter) is not available for 
>>> armel in Debian's repository. I have confirmed that facter will not fail 
>>> outright when dmidecode is missing.
>>>
>>> The following facter variables will not be created, however:
>>> bios_release_date
>>> bios_vendor
>>> bios_version
>>> boardmanufacturer
>>> boardproductname
>>> boardserialnumber
>>> manufacturer
>>> productname
>>> serialnumber
>>> type
>>> uuid
>>>
>>> If that's acceptable for you, you can try
>>>
>>> apt-get install ruby libopenssl-ruby pciutils
>>> apt-get download facter
>>> dpkg -i --force-depends facter*.deb
>>> apt-get install puppet
>>>
>>> This will manually install the other facter dependencies (which should 
>>> exist for armel), download the facter .deb file, then do an install of it 
>>> without checking depends. The puppet install should succeed after that.
>>>
>>> I think facter's dmidecode dependency should be a Suggests vice a 
>>> Depends, and it might be worth filing a bugrep to get it changed.
>>>
>>> Jeff
>>>
>>>
>>> On 12/11/2013 10:31 AM, Jon Yeargers wrote:
>>>  
>>> I also tried 'apt-get dist-upgrade'. This brought down 'hiera' (along 
>>> with a few other things). 
>>>
>>>  Then tried 'apt-get install puppet-common' - this failed as 'facter' 
>>> needed a higher version.
>>>
>>>  .. so tried 'facter' but this failed with:
>>>
>>>  facter : Depends : dmidecode but it is not instal

Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd

[Felix Frank]

On 12/12/2013 08:25 PM, Jeff Bachtel wrote:
> Sprang to mind, anyway. Probably cargo cult.

No, that's actually a neat idea.

So John, you may want to see if the latest RC master works better for
you, that would pretty much confirm this.

Thanks,
Felix

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52AAD8C5.8050400%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.