date:20140506

Re: [Puppet Users] Re: temp dir fact

2014-05-06 Thread Cristian Falcas

I have now something like this in one of my modules:

require 'facter'
Facter.add("temp_dir") { setcode { Dir::tmpdir } }


Why I was asking about a standard fact: I wanted to contribute to some
external module and I needed to download a file on Windows.machines.
And I realized there is now standard location where any user can
download files.

Thank you all for your answers.

Best regards,
Cristian Falcas




On Mon, May 5, 2014 at 8:21 PM, jcbollinger  wrote:
>
>
> On Saturday, May 3, 2014 12:50:11 PM UTC-5, Cristian Falcas wrote:
>>
>> Hello,
>>
>> Does puppet have a variable for temporary directories for each os, or
>> I need to write a custom fact with this?
>>
>
>
> You can get the complete list of facts that any node will provide to Puppet
> by running "facter -p" on that node.  I don't see a standard fact naming a
> designated temporary directory when I try it on CentOS 5 or 6.
>
>
> John
>
> --
> 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/4a312035-105f-4d2f-9788-d9841f9900a0%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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/CAMo7R_eHPZNRfFfrPcUxd%3D8Yd8Be5tEoRubtgPSpJNyuT5UcDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dism

2014-05-06 Thread Helen Paterson

It seems that you should be using the switch /Featurename OR 
/Apply-Unattend NOT both, yet the puppet example is
 

dism { 'IIS-WebServer':
  ensure => present,
  answer => 'C:\answer\iis.xml',
}
https://forge.puppetlabs.com/puppetlabs/dism
 
 
I can see how to use this puppet module with the answer file, so i am going 
to try:
 
dism { 'NetFx3':
  ensure => present,
}
dism { 'IIS-WebServer':
ensure => present,
 
etc.
 

On Friday, May 2, 2014 6:51:51 PM UTC+1, Rob Reynolds wrote:

> Can you verify /Apply-Unattend is a proper switch for that particular 
> feature? The error you are getting indicates it should not be used.
>
>
> On Fri, May 2, 2014 at 10:26 AM, Helen Paterson 
> 
> > wrote:
>
>> Hi,
>>  
>> I'm getting the below error, when using an answer file with the forge 
>> puppet dism module
>>  
>>
>> Error: Execution of 'C:\Windows\sysnative\Dism.exe /online 
>> /Enable-Feature /Fea
>> ureName:IIS-WebServerRole /Apply-Unattend:c:\answer\iis_net.xml 
>> /NoRestart' ret
>> rned 87:
>> Deployment Image Servicing and Management tool
>> Version: 6.1.7600.16385
>> Image Version: 6.1.7600.16385
>> Error: 87
>> The apply-unattend option is not recognized in this context.
>> For more information, refer to the help.
>>
>>  
>>  
>> *This is my module*
>>  
>>
>> * class win7roles {  require win7roles::params  file {  
>> $win7roles::params::answer:  ensure  => directory,  recurse => 
>> true,   source  => "puppet:///modules/win7roles/answer",  force   
>> => true,  #copy files from puppet module to the local folder created 
>> above } dism { 'IIS-WebServerRole':  ensure => present,  answer 
>> => "${win7roles::params::answer}\\iis_net.xml",  require => 
>> File["${win7roles::params::answer}"],#answer file create with windows 
>> system image manager(windows AIK) & windows 7 iso} }  
>>   class win7roles::params {   $answer ="c:\\answer"}  *
>>
>>  
>>
>>  -- 
>> 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/36c555a6-4c93-42f5-adba-416ddbaa715c%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Rob Reynolds
> Developer, Puppet Labs
>
> *Join us at **PuppetConf 2014 **, September 
> 23-24 in San Francisco*
> *Register by May 30th to take advantage of the Early Adopter discount 
>  **—**save $349!*
>  

-- 
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/40258a43-89fe-48d4-a7f1-ca590a0c8492%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Setting quotes using augeas type

2014-05-06 Thread zerozerounouno

On Wednesday, April 30, 2014 11:21:47 PM UTC+2, kbrede wrote:

But when using the augeas type with the following:
> changes => 'set \$database_password "\"test\""',
>
> The file entry looks like:
> $database_password = \"test\";
>

Try this (pay attention to what is a single quote and what is a double!):

changes => 'set \$database_password \'"test"\'',

Marco

-- 
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/f1b5d685-0549-4660-b098-25af0b52441a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Could not find class

2014-05-06 Thread devaki prabhu

Hi everybody,

i have to install keystone package on puppet client :
i have some module  in puppet master 
/etc/puppet/modules/keystone/manifests/init.pp
and when i include it in client ,getting an class not found.
any help is accepted.
Thank you.


   
152,5 34%


On Thursday, 16 December 2010 07:18:47 UTC+5:30, Dmytro Bablinyuk wrote:
>
> Hi Everybody, 
>
> I am sure that I am missing something very obvious, 
>
> I have installed rsync package 
>
> git clone https://github.com/camptocamp/puppet-rsyncd.git rsync 
>
> The path 
>
> root@puppet-master:/etc/puppet/modules/rsync/manifests/classes# ls -l 
> total 4 
> -rw-r--r-- 1 root root 1078 2010-12-16 09:54 rsyncd.pp 
>
> The manifest file 
>
> package { ["rsync", "xinetd"]: ensure => present } 
> service { "xinetd": ensure => running } 
>
> include rsyncd 
>
> rsyncd::export { "etc": 
> path => "/etc", 
> chroot => true, 
> gid => "staff", 
> allow => ["172.16.50.4", "172.16.41.10"], 
> } 
>
> I have error on the client 
>
> root@puppet-client-ubuntu:~# puppetd --test 
> info: Retrieving plugin 
> err: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: Could not find class rsyncd at /etc/puppet/manifests/site.pp: 
> 33 on node puppet-client-ubuntu.harbour 
> warning: Not using cache on failed catalog 
> err: Could not retrieve catalog; skipping run 
>
> How do I specify path to the rsyncd class? 
>
> Thank you 
> Dmytro 
>

-- 
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/0df3c085-bdba-4b44-a9d4-f4477274b49f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Delete a clients certificate with curl no longer working?

2014-05-06 Thread Thomas

When deploying openvz images, we use a init-script to delete puppets ssl 
directory and then run a curl that deletes the certificate from the puppet 
server:
curl -k -X DELETE -H "Accept: pson" 
"https://puppet.example.com:8140/production/certificate_status/client.examle.com";.

After upgrading to puppet 3.5.1 this stopped working, I have read that I 
need to revoke the certificate first and that works:
curl -k -X PUT -H "Content-Type: text/pson" --data 
'{"desired_state":"revoked"}' 
https://puppet.example.com:8140/production/certificate_status/client.example.com

I have verified that the certificate gets revoked on the server:
[root@puppet ~]# puppet cert list client.example.com
- "client.example.com" (SHA256) 
A9:FD:2D:C3:E4:7C:84:12:9C:D0:B2:4C:F2:81:AB:A0:BE:9C:A4:40:A7:8E:4A:6A:D8:E0:A4:D7:10:A9:4B:E2
 
(certificate revoked)

After this, the documentation says that I should run the DELETE command 
described above but that fails (using | sed for readability):
curl -k -X DELETE -H "Accept: pson" 
https://puppet.example.com:8140/production/certificate_status/work-reduce203.trioptima.com
 
| sed 's/,/\n/g'
{"issue_kind":"RUNTIME_ERROR"
"message":"Server Error: undefined method `each' for nil:NilClass"
"stacktrace":["/usr/lib/ruby/site_ruby/1.8/puppet/network/http/route.rb:72:in 
`process'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:63:in `process'"
"/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler/none.rb:6:in `profile'"
"/usr/lib/ruby/site_ruby/1.8/puppet/util/profiler.rb:43:in `profile'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:61:in `process'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:31:in 
`service'"
"/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'"
"/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:36:in `listen'"
"/usr/lib/ruby/1.8/webrick/server.rb:173:in `call'"
"/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'"
"/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'"
"/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'"
"/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'"
"/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'"
"/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'"
"/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'"
"/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:30:in `listen'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in 
`initialize'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `new'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `listen'"
"/usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:27:in `start'"
"/usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:139:in `start'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:284:in 
`start_webrick_master'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:200:in `main'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:160:in 
`run_command'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:372:in `run'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:479:in `plugin_hook'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:372:in `run'"
"/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:479:in `exit_on_fail'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:372:in `run'"
"/usr/lib/ruby/site_ruby/1.8/puppet/context.rb:51:in `override'"
"/usr/lib/ruby/site_ruby/1.8/puppet.rb:233:in `override'"
"/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:362:in `run'"
"/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:137:in `run'"
"/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:91:in `execute'"
"/usr/bin/puppet:4"]}

Running the puppet master in debug:
[root@puppet ~]# puppet master --no-daemonize --debug --verbose
[...]
Notice: Starting Puppet master version 3.5.1
[...]
Debug: Routes Registered:
Debug: Route /^\/v2\.0/
Debug: Route /.*/
Debug: Evaluating match for Route /^\/v2\.0/
Debug: Did not match path 
("/production/certificate_status/client.example.com")
Debug: Evaluating match for Route /.*/
Error: Server Error: undefined method `each' for nil:NilClass

Any hints?

-- 
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/9d8aef00-8855-4190-a32d-3ae897217c22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "puppet apply --noop -e" and overiding facter values for testing

2014-05-06 Thread Jakov Sosic


On 05/06/2014 12:29 AM, Brian Mathis wrote:

The problem is that your variable names are being returned from the
$(cat...) after bash has already evaluated the environment, so it's
taking it as a literal string and trying to execute the command.

To get bash to interpret it as a variable, use 'eval':
eval $(cat test_values | tr '\n' ' ' ) puppet apply --noop -e
'notice("${fqdn}")'

Also, on modern versions of facter you can place facts in
/etc/facter/facts.d and they will override the detected versions.


Can you show an example how to override facter value with file in 
/etc/facter/facts.d/ ? For example, how to override hostname?


--
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/5368CAD9.1030302%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] rubygems.org broken for puppet < 3.5

2014-05-06 Thread Martin Alfke

Hi,

at the moment there is only one factor version available on rubygems.org:

facter - 2.0.1

Is there a reason why older facter versions have disappeared?

Older puppet versions are still on ruby gems.org.. but they are useless due to 
missing dependencies.

- Martin

-- 
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/6D3B150A-CED6-426A-8467-CC0E2206A542%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: rubygems.org broken for puppet < 3.5

2014-05-06 Thread Martin Alfke



Sorry. My mistake.
Everything is working fine.
I just did not check properly my logs.


Am Dienstag, 6. Mai 2014 14:18:47 UTC+2 schrieb Martin Alfke:
>
> Hi, 
>
> at the moment there is only one factor version available on rubygems.org: 
>
> facter - 2.0.1 
>
> Is there a reason why older facter versions have disappeared? 
>
> Older puppet versions are still on ruby gems.org.. but they are useless 
> due to missing dependencies. 
>
> - Martin 
>
>

-- 
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/e0046834-767a-46c3-94fd-8be98f24712d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "puppet apply --noop -e" and overiding facter values for testing

2014-05-06 Thread Brian Mathis

This applies to facter version 1.7 and above.  See docs:
http://docs.puppetlabs.com/guides/custom_facts.html#external-facts

You can create a file like this (the name does not matter):
/etc/facter/facts.d/myfacts.txt:
hostname=value

Then when you run 'facter hostname', "value" will be returned.


❧ Brian Mathis


On Tue, May 6, 2014 at 7:43 AM, Jakov Sosic  wrote:

> On 05/06/2014 12:29 AM, Brian Mathis wrote:
>
>> The problem is that your variable names are being returned from the
>> $(cat...) after bash has already evaluated the environment, so it's
>> taking it as a literal string and trying to execute the command.
>>
>> To get bash to interpret it as a variable, use 'eval':
>> eval $(cat test_values | tr '\n' ' ' ) puppet apply --noop -e
>> 'notice("${fqdn}")'
>>
>> Also, on modern versions of facter you can place facts in
>> /etc/facter/facts.d and they will override the detected versions.
>>
>
> Can you show an example how to override facter value with file in
> /etc/facter/facts.d/ ? For example, how to override hostname?
>
>
> --
> 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/5368CAD9.1030302%40gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALKwpEwyEaGx_AtpXxc%2B8%3DCxa1Nh0M8y78zq6P4ArebZp1P3Eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] [JOB] - Senior Systems Administrator; 3-6 Month Contract; Deploy Linux Desktop Environment

2014-05-06 Thread Georgien Dimis

Hi Guys,
I am currently looking for a a Senior Systems Administrator with very
strong Puppet knowledge and skills to provide a full Proof of Concept and
roll-out of Linux Desktop (Ubuntu) to a Contact Centre located in Melbourne
and the Philippines. Initially this is for a 3-6 month contract however I
have been advise this year is time to innovate so there is a good chance,
it could turn into something on going for the right person.

We currently use Puppet to manage over 200 servers. The setup was
implemented by a very strong System Administrator that didn't have much
Puppet knowledge and unfortunately looking back over his work looks like
there are many improvements that can be made, no love lost, he did the best
with the knowledge he had.

The immediate project is to investigate the possibility of replacing some
of our existing Windows Desktop environment with a Linux environment,
whether Ubuntu or other.
The current scope of work, will be split over the following stages:
1. Provide a POC
2. Signed off for POC by myself and GM
3. Deploy 800 machines to replace ageing existing infrastructure
4. Deploy two new sites the required Linux Desktop environment
Total deployment is over 2,000 Desktops.

*Technology considerations so far:*
- Puppet to control each machine based on OU through Active Directory or
OpenLDAP
- TFTP to be deployed on boot (not ideal but has been suggested,
as something to investigate)
- Maybe require Landscape Canonical for the management aspect
The above are purely considerations and I am open to all suggestions as to
what we can do to have this rolled out successfully and obviously what is
best for the business needs, from deployment to management.

As a Contact Centre, like many other businesses, we have many critical
systems that are shared amongst many different verticals for our clients,
guaranteeing business continuity for them is key, so this will need to be
rolled out in parallel with current operations.

Future projects on the cards:
- New Asterix PBX
- Rebuild Postfix Mail Servers to include redundancy
- Rebuild Puppet Server
- Improve on existing monitoring in place

Hopefully this covers most queries anyone may have although if anyone
thinks of anything, is interested in more information or knows someone that
can assist please feel free to drop me a message.

Georgien Dimis
georgien.di...@acquireap.com
+61 413 555 699

--
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/26a7e0b2-d0d3-45aa-bd13-5f429343385b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Could not find class

2014-05-06 Thread jcbollinger

On Tuesday, May 6, 2014 5:44:39 AM UTC-5, devaki prabhu wrote:
>
> Hi everybody,
>
> i have to install keystone package on puppet client :
> i have some module  in puppet master 
> /etc/puppet/modules/keystone/manifests/init.pp
> and when i include it in client ,getting an class not found.
> any help is accepted.
>
>

Step 1.  Avoid disturbing the dead.  This thread died three and a half 
years ago!  Start your own thread for your own question.

Step 2.  In the new thread where you are going to pose your question, post 
the specific error message and the relevant code.  The relevant code 
includes the node block (or other means) by which you are assigning the 
class to the node, and the fully-qualified name and contents of the 
manifest file containing the definition of the class in question.  The 
Puppet code can be abbreviated if it is long -- the class declaration and 
the beginning of the class definition or the most important parts.

John

-- 
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/901c384e-fb07-4bd6-b909-a0fbe2a9846b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dism

2014-05-06 Thread Helen Paterson

I didn't get the answer file working but this works instead

class windowsfeaturedesktop::iis {
 dism { 'IIS-WebServerRole':
 ensure => present,
   }
dism { 'IIS-WebServer':
 ensure => present,
 require => Dism['IIS-WebServerRole'],
   }
dism { 'IIS-CommonHttpFeatures':
 ensure => present,
 require => Dism['IIS-WebServerRole'],
   }
dism { 'IIS-StaticContent':
 ensure => present,
 require => Dism['IIS-CommonHttpFeatures'],
   }
 dism { 'IIS-DefaultDocument':
 ensure => present,
 require => Dism['IIS-CommonHttpFeatures'],
   }
 dism { 'IIS-HttpErrors':
 ensure => present,
 require => Dism['IIS-CommonHttpFeatures'],
   }
   dism { 'IIS-ApplicationDevelopment':
 ensure => present,
 require => Dism['IIS-WebServerRole'],
   }
dism { 'IIS-NetFxExtensibility':
 ensure => present,
 require => Dism['IIS-ApplicationDevelopment'],
   }
dism { 'IIS-ISAPIExtensions':
 ensure => present,
 require => Dism['IIS-ApplicationDevelopment'],
   }
dism { 'IIS-ISAPIFilter':
 ensure => present,
 require => Dism['IIS-ApplicationDevelopment'],
   }
dism { 'IIS-ASPNET':
 ensure => present,
 require => Dism['IIS-ISAPIExtensions','IIS-ISAPIFilter'],
   }
dism { 'IIS-Security':
 ensure => present,
 require => Dism['IIS-WebServerRole'],
   }
dism { 'IIS-WindowsAuthentication':
 ensure => present,
 require => Dism['IIS-Security'],
   }
dism { 'IIS-RequestFiltering':
 ensure => present,
 require => Dism['IIS-Security'],
   }
dism { 'IIS-Performance':
 ensure => present,
 require => Dism['IIS-WebServerRole'],
  }
   dism { 'IIS-HttpCompressionDynamic':
 ensure => present,
 require => Dism['IIS-Performance'],
  }
dism { 'IIS-HttpCompressionStatic':
 ensure => present,
 require => Dism['IIS-Performance'],
  }
dism { 'IIS-HealthAndDiagnostics':
 ensure => present,
 require => Dism['IIS-WebServerRole'],
  }
dism { 'IIS-CustomLogging':
 ensure => present,
 require => Dism['IIS-HealthAndDiagnostics'],
  }
dism { 'IIS-HttpLogging':
 ensure => present,
 require => Dism['IIS-HealthAndDiagnostics'],
  }
dism { 'IIS-RequestMonitor':
 ensure => present,
 require => Dism['IIS-HealthAndDiagnostics'],
  }
dism { 'IIS-WebServerManagementTools':
 ensure => present,
 require => Dism['IIS-WebServer'],
 }
dism { 'IIS-ManagementConsole':
 ensure => present,
 require => Dism['IIS-WebServerManagementTools'],
 }   
  dism { 'IIS-ManagementScriptingTools':
 ensure => present,
 require => Dism['IIS-WebServerManagementTools'],
 }
   dism { 'IIS-ManagementService':
 ensure => present,
 require => Dism['IIS-WebServerManagementTools'],
 }
  }


On Tuesday, May 6, 2014 9:27:52 AM UTC+1, Helen Paterson wrote:
>
> It seems that you should be using the switch /Featurename OR 
> /Apply-Unattend NOT both, yet the puppet example is
>  
>
> dism { 'IIS-WebServer':
>   ensure => present,
>   answer => 'C:\answer\iis.xml',
> }
> https://forge.puppetlabs.com/puppetlabs/dism
>  
>  
> I can see how to use this puppet module with the answer file, so i am 
> going to try:
>  
> dism { 'NetFx3':
>   ensure => present,
> }
> dism { 'IIS-WebServer':
> ensure => present,
>  
> etc.
>  
>
> On Friday, May 2, 2014 6:51:51 PM UTC+1, Rob Reynolds wrote:
>
>> Can you verify /Apply-Unattend is a proper switch for that particular 
>> feature? The error you are getting indicates it should not be used.
>>
>>
>> On Fri, May 2, 2014 at 10:26 AM, Helen Paterson wrote:
>>
>>> Hi,
>>>  
>>> I'm getting the below error, when using an answer file with the forge 
>>> puppet dism module
>>>  
>>>
>>> Error: Execution of 'C:\Windows\sysnative\Dism.exe /online 
>>> /Enable-Feature /Fea
>>> ureName:IIS-WebServerRole /Apply-Unattend:c:\answer\iis_net.xml 
>>> /NoRestart' ret
>>> rned 87:
>>> Deployment Image Servicing and Management tool
>>> Version: 6.1.7600.16385
>>> Image Version: 6.1.7600.16385
>>> Error: 87
>>> The apply-unattend option is not recognized in this context.
>>> For more information, refer to the help.
>>>
>>>  
>>>  
>>> *This is my module*
>>>  
>>>
>>> * class win7roles {  require win7roles::params  file {  
>>> $win7roles::params::answer:  ensure  => directory,  recurse => 
>>> true,   source  => "puppet:///modules/win7roles/answer",  force   
>>> => true,  #copy files from puppet module to the local folder created 
>>> above } dism { 'IIS-WebServerRole':  ensure => present,  answer 
>>> => "${win7roles::params::answer}\\iis_net.xml",  require => 
>>> File["${win7roles::params::answer}"],#answer file create with windows 
>>> system image manager(windows AIK) & windows 7 iso} }  
>>>   class win7roles::params {   $answer ="c:\\answer"}  *
>>>
>>>  
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet

[Puppet Users] Re: Hiera question: Nested hash

2014-05-06 Thread jcbollinger

On Monday, May 5, 2014 12:44:59 PM UTC-5, Sans wrote:
>
> Thanks John for showing me a way to do it. I haven't tried that yet but 
> meanwhile, I was also trying the "define type" but different way. Do you 
> think this is a better data structure?
>
> rpm_mon_base_pack:
>> base-pkg1:
>> rep: mon-repo-test
>> rpm: rpm-mon-ntp
>> ver: latest
>> base-pkg2:  
>> rep: mon-utils-test:
>> rpm: rpm-mon-utils
>> ver: latest
>>
>
>

Yes, I think that's a better data structure.  The import criterion here is 
that the desired per-package data be selectable directly, without scanning 
the whole top-level hash.

> then, in my .pp:
>
> class packages::rpm::monitoring-utils {
>>
>> $rpm_pkgs_list = hiera_array('rpm_mon_base_pack', undef) 
>
>

Using hiera_array() does ensure that the value retrieved is an array, but 
it's not at all what you want for this job or for either data structure.  
In this case, the returned array will contain one element -- the same hash 
that would be returned by the ordinary hiera() function.  If the 
'rpm_mon_base_pack' key appeared at multiple levels of your hierarchy, then 
the array returned by hiera_array() would contain the values from the other 
levels, too -- *that's* the main purpose of the funciton.

> define monitoring_utils_pkgs() {
>>
>> $i_rpm = $rpm_pkgs_list[$name]
>> $u_rpm = inline_template("<%= @i_rpm['rpm'].to_s.chomp %>")
>> $u_ver = inline_template("<%= @i_rpm['ver'].to_s.chomp %>")
>> $u_rep = inline_template("<%= @i_rpm['rep'].to_s.chomp %>")
>> 
>> package { "$u_rpm":
>> ensure   => $u_ver,
>> require  => [
>>   Yumrepo[ "$u_rep" ],
>>   Package[ 'mon-tools', 'patch-utils' ],
>> ];
>> }
>> }
>> monitoring_utils_pkgs { $rpm_pkgs_list: }
>> }
>>
>
> But I end up with the error:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
>> Resource title must be a String, not Hash 
>>
>
>
>  What's doing wrong here? I'll try your suggestion to night as well. Best!
>

The error message pretty much says it.  Resource titles must be strings, 
but the one element of $rpm_pkgs_list is a hash. Under slightly different 
circumstances, the hash might have been automatically flattened to a 
string, which would fail a bit more interestingly.  An approach along those 
lines could be made to work, however, by making two main changes:

1. Look up the data via hiera() rather than hiera_array(), so that the hash 
is not needlessly wrapped in an array.
2. Use use just the keys of the hash as your resource titles.  You can 
extract an array of the keys via the stdlib's keys() function, and that's 
exactly what you would want to use in your declaration:

$package_names = keys($rpm_pkgs_list)
monitoring_utils_pkgs { $package_names: }

John

-- 
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/ef0af391-2de0-49ea-a891-441f819496e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Hiera question: Nested hash

2014-05-06 Thread Sans

Hi John,

I haven't use create_resources() before, so following the puppetlab docs. After 
having the data structure in my default.yaml, I have this  in the nodes.pp:

$hr_mon_base_pkgs = hiera_hash('rpm_mon_base_pack', undef)
>

and then in my utils.pp, I have this:

class monitoring::mon-utils {
>
> define mon_pkgs($pkgs_pack) {
> $repo = inline_template("<%= @pkgs_pack.values.each { |repo| if 
> repo.has_key?(@name) { repo; break } } %>")
>
> if $repo == '' {
> fail("No package '@name' defined in the provided pack")
> }
> package { $name:
> ensure   => $pkgs_pack[$repo][$name],
> require  => Yumrepo[ $repo ],
> }
> }
> create_resources(  monitoring::mon-utils::mon_pkgs, $hr_mon_base_pkgs )
> }
>


but ends up with the error:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Invalid parameter rpm-mon-ntp on node mon105.back.local
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>

which is one of the packages in the hiera hash. Am I doing it right at all??

Best,
San


On Monday, May 5, 2014 6:13:13 PM UTC+1, jcbollinger wrote:
>
>
>
> You can use the create_resources() function to declare resources based on 
> hashes similar in form to those you present.  You cannot, however, express 
> resource references in hiera data, and you need resource references to 
> express your resource relationships.  That can be worked around.  In this 
> case, you also structure your data in a form that is not particularly 
> conducive to the lookups you want to perform, but that, too can be worked 
> around.
>
> As is often the case in Puppet DSL, a suitable defined type can serve here 
> as an adaptor, and suitable templates can do the needed processing.  I 
> might do something like this:
>
> define site::hiera_package($package_pack) {
>   $repo = inline_template("<%= @package_pack.values.each { |repo| if 
> repo.has_key?(@name) { repo; break } } %>")
>   if $repo == '' {
> fail("No package '@name' defined in the provided pack")
>   }
>   package { $name:
> ensure => $package_pack[$repo][$name]
> require => Yumrepo[$repo]
>   }
>
}
>
> That will work with the data structure you presented, but will not provide 
> relationships on other Packages.  However, since you are assuming the Yum 
> package provider, you should not need to define package relationships to 
> Puppet.  These should already be adequately described in your packages' 
> internal metadata, which Yum uses to install any needed dependencies 
> automatically.
>
> If you nevertheless want data-driven explicit dependencies between 
> packages, then you can probably obtain that.  One approach would involve 
> making the values of the inner hashes be a third level of hash wherein you 
> describe possibly-multiple properties of the package named by the key.  One 
> of those properties would be the state to ensure, and another could be an 
> array of the names of packages it should depend on.  You could then use an 
> additional define to process the array and declare appropriate resource 
> relationships via a chain operator.  Alternatively, the iteration 
> facilities of the Future parser might provide a more direct route to 
> expressing the needed chain operations.
>
>
> John
>
>

-- 
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/ccebd1f8-d760-4f64-8e2a-9968f20bdda0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Setting quotes using augeas type

2014-05-06 Thread Kenton Brede

That's one combination I hadn't tried but it works!
Thanks,
Kent


On Tue, May 6, 2014 at 4:52 AM,  wrote:

> On Wednesday, April 30, 2014 11:21:47 PM UTC+2, kbrede wrote:
>
> But when using the augeas type with the following:
>> changes => 'set \$database_password "\"test\""',
>>
>> The file entry looks like:
>> $database_password = \"test\";
>>
>
> Try this (pay attention to what is a single quote and what is a double!):
>
> changes => 'set \$database_password \'"test"\'',
>
> Marco
>
> --
> 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/f1b5d685-0549-4660-b098-25af0b52441a%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Kent Brede

-- 
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/CA%2BnSE38iQnzNOMQ7CaYW%3D7YMxo%2B8dzYjDWvJp7Bp5ktvy%3DO6aA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "The certificate retrieved from the master does not match the agent's private key." The master and agent in this case are on the same machine.

2014-05-06 Thread jcbollinger

On Monday, May 5, 2014 10:25:50 AM UTC-5, Felix.Frank wrote:
>
> Ah, so you're running the master from an unprivileged user. That makes a 
> lot of sense now. 
>
>

Maybe.  It is normal to run the *master* as an unprivileged user.  The 
master does not store anything in its home directory in that case, unless 
its home directory is set to something like /var/lib/puppet.  Or am I stuck 
in the past?

It is *ab*normal to run the agent as an unprivileged user, because that 
prevents the agent from applying most of the kinds of system changes that 
Puppet is typically wanted for.  It is perhaps more common to run 'puppet 
apply' as a normal user, but the same limitations apply.  Under these 
circumstances, however, it is my understanding that agent or apply will use 
$HOME/.puppet.

> And yes, this is most disturbing. 
>
> Would it be feasible to renew all your certificates? Because the current 
> state looks messed up beyond reason :-) 
>
>

Again, maybe.  If the agents have in the past run successfully as root (as 
is more usual), then they will have certificates signed by the master and 
living in Puppet's normal system directory.  If one then tries to run the 
agent on one or more of those machines, however, then just such a problem 
as is reported might arise.

Specifically, when running as an ordinary user, the agent cannot use the 
certificate that puppet-as-root uses, because it cannot access the 
corresponding private key.  Instead, it creates its own key pair, and 
issues a certificate request to the master based on that public key.  The 
master, on the other hand, already has a signed certificate for the node, 
which it returns to the agent (this is a feature).  That certificate is 
indeed not based on the same key pair as the cert request, so the agent 
would emit exactly the message described.

John

-- 
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/fdb1c58d-9003-45d2-b742-a096339d8af6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Looking for a better way to use hiera hashes than create_resources

2014-05-06 Thread jcbollinger

On Monday, May 5, 2014 9:32:05 AM UTC-5, Alex Scoble wrote:
>
> If you are trying to follow Puppet Labs recommended best practices, it's 
> definitely a moving target.
>
>

Obviously, "best practices" are not at all the same thing as the DSL itself.

Still, I'm curious what you define as "PuppetLabs recommended best 
practices".  PL has indeed at times published various best practices guides 
on their site, but the current one is so high-level as to hardly recommend 
anything close enough to the DSL as to lead anyone to confuse the two.  The 
guides they have published in the past have come and gone as Puppet has 
grown and experience with it has grown, both at PL and in the community.

PL is indeed a fast-moving company, though, and Puppet is a faster-moving 
product than many.  Nevertheless, Felix is right: the Puppet core is pretty 
stable.  The key to best practices, whether with Puppet or any other 
complex system, is to understand the system well enough to know why one 
practice is better than another.  That's something we can help you with 
here, though you will have to contend with a plurality of opinions.

Best,

John

-- 
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/30a0ffe0-a86b-4464-9951-c05507588b6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "The certificate retrieved from the master does not match the agent's private key." The master and agent in this case are on the same machine.

2014-05-06 Thread Felix Frank

On 05/06/2014 04:56 PM, jcbollinger wrote:
> Ah, so you're running the master from an unprivileged user. That
> makes a
> lot of sense now.
> 
> 
> 
> Maybe.  It is normal to run the /master/ as an unprivileged user.  The
> master does not store anything in its home directory in that case,
> unless its home directory is set to something like /var/lib/puppet.  Or
> am I stuck in the past?

More or less. Hence my awkward wording of "running *from* an
unprivileged user". Sure, you normally want the master to drop root
privileges after initialization, and run as the puppet user.

Since Puppet 3 it is surpassingly easy to run independent master
processes with webrick, though, by just exclaiming `puppet master` from
a terminal, which will (just as the agent) use ~/.puppet as its base of
operation/configuration. (Of course, care must be taken if the master
port is already in use, but that should be it.)

> It is /ab/normal to run the agent as an unprivileged user, because that
> prevents the agent from applying most of the kinds of system changes
> that Puppet is typically wanted for.  It is perhaps more common to run
> 'puppet apply' as a normal user, but the same limitations apply.  Under
> these circumstances, however, it is my understanding that agent or apply
> will use $HOME/.puppet.

Right.

> Again, maybe.  If the agents have in the past run successfully as root
> (as is more usual), then they will have certificates signed by the
> master and living in Puppet's normal system directory.  If one then
> tries to run the agent on one or more of those machines, however, then
> just such a problem as is reported might arise.
>
> Specifically, when running as an ordinary user, the agent cannot use the
> certificate that puppet-as-root uses, because it cannot access the
> corresponding private key.  Instead, it creates its own key pair, and
> issues a certificate request to the master based on that public key.
> The master, on the other hand, already has a signed certificate for the
> node, which it returns to the agent (this is a feature).  That
> certificate is indeed not based on the same key pair as the cert
> request, so the agent would emit exactly the message described.

Very true. Specifically, I have found during last night's debugging
session that the $ssldir contents are very prone to fall off balance if
they are ever used by an agent that has the wrong permissions.

Sadly, bottom line likely remains: If an intact copy of the certs and
keys cannot be secured, it will be necessary to certify from scratch.

Regards,
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/5368FDF7.5080702%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Problem with deploying Hiera hashes in order

2014-05-06 Thread Marcin

 

I got the following lines in Hiera:

 

  # My hash array

  somehash::somevalues:

  # NODE1 - ukdc1-c1-pscn01 -- 172.19.128.2 - below

FIRSTARTEFACT1:

  artefact: FIRSTARTEFACT

  order: ??

SECONDARTEFACT:

  artefact: SECONDARTEFACT

  order: FIRSTARTEFACT1

THIRDARTEFACT:

  artefact: THIRDARTEFACT

  order: SECONDARTEFACT

 

and from those I have created  resources:

create_resources(something, $ransomething)

 

When I try to deploy this in order (from top to bottom – although this may 
not be clear from the listing here), I use something like:

 

I use exec of course – sample of this is below:

exec { " something _${name}":

  command => $some_command_here,

  require => something [$order],

  creates => some entry here

}

 

but what do I need to put in Hiera file, on the FIRST hash – where the 
question marks are in my example?


If I put the name of the first component - in this case: FIRSTARTEFACT1 - I 
got an error message like this:

Error: Could not apply complete catalog: Found 1 dependency cycle:


If I leave this field empty, it also causes an error 

 

Hope I have presented the problem clearly….


Can you help me out with this issue? 


-- 
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/3351c9d6-397a-4a56-b3ee-06b7a29d321a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dism

2014-05-06 Thread Rob Reynolds

On Tue, May 6, 2014 at 9:27 AM, Helen Paterson wrote:

> I didn't get the answer file working but this works instead
>
> class windowsfeaturedesktop::iis {
>  dism { 'IIS-WebServerRole':
>  ensure => present,
>}
> dism { 'IIS-WebServer':
>  ensure => present,
>  require => Dism['IIS-WebServerRole'],
>}
> dism { 'IIS-CommonHttpFeatures':
>  ensure => present,
>  require => Dism['IIS-WebServerRole'],
>}
> dism { 'IIS-StaticContent':
>  ensure => present,
>  require => Dism['IIS-CommonHttpFeatures'],
>}
>  dism { 'IIS-DefaultDocument':
>  ensure => present,
>  require => Dism['IIS-CommonHttpFeatures'],
>}
>  dism { 'IIS-HttpErrors':
>  ensure => present,
>  require => Dism['IIS-CommonHttpFeatures'],
>}
>dism { 'IIS-ApplicationDevelopment':
>  ensure => present,
>  require => Dism['IIS-WebServerRole'],
>}
> dism { 'IIS-NetFxExtensibility':
>  ensure => present,
>  require => Dism['IIS-ApplicationDevelopment'],
>}
> dism { 'IIS-ISAPIExtensions':
>  ensure => present,
>  require => Dism['IIS-ApplicationDevelopment'],
>}
> dism { 'IIS-ISAPIFilter':
>  ensure => present,
>  require => Dism['IIS-ApplicationDevelopment'],
>}
> dism { 'IIS-ASPNET':
>  ensure => present,
>  require => Dism['IIS-ISAPIExtensions','IIS-ISAPIFilter'],
>}
> dism { 'IIS-Security':
>  ensure => present,
>  require => Dism['IIS-WebServerRole'],
>}
> dism { 'IIS-WindowsAuthentication':
>  ensure => present,
>  require => Dism['IIS-Security'],
>}
> dism { 'IIS-RequestFiltering':
>  ensure => present,
>  require => Dism['IIS-Security'],
>}
> dism { 'IIS-Performance':
>  ensure => present,
>  require => Dism['IIS-WebServerRole'],
>   }
>dism { 'IIS-HttpCompressionDynamic':
>  ensure => present,
>  require => Dism['IIS-Performance'],
>   }
> dism { 'IIS-HttpCompressionStatic':
>  ensure => present,
>  require => Dism['IIS-Performance'],
>   }
> dism { 'IIS-HealthAndDiagnostics':
>  ensure => present,
>  require => Dism['IIS-WebServerRole'],
>   }
> dism { 'IIS-CustomLogging':
>  ensure => present,
>  require => Dism['IIS-HealthAndDiagnostics'],
>   }
> dism { 'IIS-HttpLogging':
>  ensure => present,
>  require => Dism['IIS-HealthAndDiagnostics'],
>   }
> dism { 'IIS-RequestMonitor':
>  ensure => present,
>  require => Dism['IIS-HealthAndDiagnostics'],
>   }
> dism { 'IIS-WebServerManagementTools':
>  ensure => present,
>  require => Dism['IIS-WebServer'],
>  }
> dism { 'IIS-ManagementConsole':
>  ensure => present,
>  require => Dism['IIS-WebServerManagementTools'],
>  }
>   dism { 'IIS-ManagementScriptingTools':
>  ensure => present,
>  require => Dism['IIS-WebServerManagementTools'],
>  }
>dism { 'IIS-ManagementService':
>  ensure => present,
>  require => Dism['IIS-WebServerManagementTools'],
>  }
>   }
>

Awesome! If you have order dependencies, it may be best to add the chaining
arrows as well. Depending on whether you have manifest ordering turned on
or not
http://docs.puppetlabs.com/learning/ordering.html#unrelated-resources-and-the-ordering-setting


>
>
> On Tuesday, May 6, 2014 9:27:52 AM UTC+1, Helen Paterson wrote:
>>
>> It seems that you should be using the switch /Featurename OR
>> /Apply-Unattend NOT both, yet the puppet example is
>>
>>
>> dism { 'IIS-WebServer':
>>   ensure => present,
>>   answer => 'C:\answer\iis.xml',
>> }
>> https://forge.puppetlabs.com/puppetlabs/dism
>>
>>
>> I can see how to use this puppet module with the answer file, so i am
>> going to try:
>>
>> dism { 'NetFx3':
>>   ensure => present,
>> }
>> dism { 'IIS-WebServer':
>> ensure => present,
>>
>> etc.
>>
>>
>> On Friday, May 2, 2014 6:51:51 PM UTC+1, Rob Reynolds wrote:
>>
>>> Can you verify /Apply-Unattend is a proper switch for that particular
>>> feature? The error you are getting indicates it should not be used.
>>>
>>>
>>> On Fri, May 2, 2014 at 10:26 AM, Helen Paterson wrote:
>>>
 Hi,

 I'm getting the below error, when using an answer file with the forge
 puppet dism module


 Error: Execution of 'C:\Windows\sysnative\Dism.exe /online
 /Enable-Feature /Fea
 ureName:IIS-WebServerRole /Apply-Unattend:c:\answer\iis_net.xml
 /NoRestart' ret
 rned 87:
 Deployment Image Servicing and Management tool
 Version: 6.1.7600.16385
 Image Version: 6.1.7600.16385
 Error: 87
 The apply-unattend option is not recognized in this context.
 For more information, refer to the help.



 *This is my module*


 * class win7roles {  require win7roles::params  file {
 $win7roles::params::answer:  ensure  => directory,  recurse =>
 true,   source  => "puppet:///modules/win7roles/answer",  force
 => true,

[Puppet Users] Ignore resource in provider if not defined?

2014-05-06 Thread Gavin Williams

Afternoon all,

I'm trying to update my Glassfish module [1] to support some additional
functionality, such as clustering.

I've done most of the code changes, and they all seem to work fine from a
usage POV. However several of my tests [2] are failing with the following
error:
1) Puppet::Type::Application::ProviderAsadmin when asking exists? should
return true if resource is present
Failure/Error: application.provider.should be_exists
Puppet::Error:
Invalid parameter dashost(:dashost)
# ./lib/puppet/provider/asadmin.rb:6:in `asadmin_exec'
# ./lib/puppet/provider/application/asadmin.rb:22:in `exists?'
# ./spec/unit/puppet/provider/application/asadmin_spec.rb:34:in `block
(3 levels) in '

I suspect this is related to some changes I made to
Puppet::Provider::Asadmin [3] in order to support running asadmin commands
against a host other than localhost.
Effectively, I'm just trying to only use the 'dashost' resource value if
it's defined and not null.
This works fine for actual usage, but seems to fail horribly for RSpec
testing :(

Cheers in advance for any replies.

Regards
Gavin

[1] https://github.com/fatmcgav/puppet-glassfish/tree/develop
[2] https://travis-ci.org/fatmcgav/puppet-glassfish/jobs/24549377#L505-L511
[3]
https://github.com/fatmcgav/puppet-glassfish/blob/develop/lib/puppet/provider/asadmin.rb#L6-L8

--
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/c111d1e0-a988-49ec-aa6e-9d67680602af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet enterprise console, all nodes 'unresponsive'.

2014-05-06 Thread Jay Benner

I had some corruption in my puppetdb and had to rebuild my KahaDB 
directory.  After doing so I restarted everything, but all of the puppet 
nodes still show 'unresponsive', even after a successful puppet run.  Looks 
like things are running smoothely now, only the console isn't updating 
properly. 

-- 
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/8d568cc9-962b-4b83-af8c-8947bb9e3513%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Eugene Oregon Puppet User Group?

2014-05-06 Thread Spencer Krum

Hi Jon,

I'm based in portland but would be happy to come down for the first meeting.

Thanks,
Spencer
On May 1, 2014 8:53 PM, "Jon Sawyer"  wrote:

> I am interested in starting one if one does not yet exist.
> I'd like to talk about and collaborate on usage of puppet.
>
> Anyone can hit me up if there is such a group here in town, I know there
> is one in Portland but I won't be going any time soon.
>
> --
> 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/981c1dbd-7df7-4401-839a-c1e50e1fa2e4%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CADt6FWO-Rv%3DF1n%2BgYo3C5Avh-81C_LXztaRFMvEXe0KLXW45mA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet module to install and configure libvirt on hosts and webvirtmgr on a separate server

2014-05-06 Thread Alex Scoble

Hi All,

I got this fully working yesterday on CentOS 6.5 and uploaded it to github 
today:

https://github.com/ITBlogger/puppet-kvm

It's very crude, doesn't have any parameter validation or testing and 
requires hiera as written, but you may find it useful.

At some point it would be interesting to create a custom type to do all of 
this, but I'm just not there yet.

I ended up going this route because I couldn't get the Carla Souza based 
libvirt modules to work. They seem to be too far out of date at this point.

None of them set up webvirtmgr for you either.

Anyhow, use it, add to it, edit it, fork it, or do whatever you want with 
it. If you print it out, would also make for good kindling for a fire, or 
perhaps once shredded, good to use for the bottom of a hamster cage.

Thanks,

Alex

-- 
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/13823d0d-fb11-4854-a847-c96dd2f3525e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Hiera question: Nested hash

2014-05-06 Thread Sans



On Tuesday, May 6, 2014 3:36:13 PM UTC+1, jcbollinger wrote:
>
>
>
>
> Using hiera_array() does ensure that the value retrieved is an array, but 
> it's not at all what you want for this job or for either data structure.  
> In this case, the returned array will contain one element -- the same hash 
> that would be returned by the ordinary hiera() function.  If the 
> 'rpm_mon_base_pack' key appeared at multiple levels of your hierarchy, then 
> the array returned by hiera_array() would contain the values from the other 
> levels, too -- *that's* the main purpose of the funciton.
>
>
Just noticed the typo: I was actually using hiera_hash() in stead of 
hiera_array(). This is for reason - I have four environments and the idea 
is override the default values from the environment specific yaml. Using 
:merge_behavior: 
deeper to merge  the values levels.

Best,
San


-- 
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/e7a27cbe-9843-46f7-9ae7-bf29ccdd6ed6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet 3.6.0-RC1 available!

2014-05-06 Thread Eric Sorenson

Puppet 3.6.0 is a backward-compatible features and fixes release in the Puppet 
3 series. The biggest things in this release are:

* Improvements to directory environments, and the deprecation of config 
file environments
* Support for purging unmanaged ssh_authorized_key resources
* Support for installing gems for a custom provider as part of a Puppet 
run
* A configurable global logging level
* A configurable hashing algorithm (for FIPS compliance and other 
purposes)
* Improvements to the experimental future parser

Read the full release notes here: 
http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#puppet-360
Get the downloads by following the directions here: 
http://docs.puppetlabs.com/guides/installation.html
Since this is a Release Candidate, you'll need to enable the pre-release 
repositories as described here:
  
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos


Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

-- 
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/5D25350D-5685-4F2A-8019-6F62D5BEA6AC%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Master not responding

2014-05-06 Thread Sean Keery

I just had this happen to me today.  Turns out that I had pasted some 
database settings into the puppet.conf instead of the database.ini while 
using *screen* and having too many windows open.  Luckily I had some cert 
warnings so I ran *puppet cert list --all *and got an error about the 
puppet.conf file having an invalid line.  There you go,

Sean

On Monday, December 9, 2013 9:45:17 PM UTC-7, Naveen Desu wrote:
>
> Hi,
>
> While I was trying to access Puppet REST API [
> https://:8140/production/facts/], getting the 
> below error.
>
> I am not sure the issue here & could not find any specific log to further 
> troubleshoot. Any help will be appreciated.
>
>
> Web application could not be started
>
> exit (SystemExit)
>   /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util.rb:525:in `exit'
>   /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util.rb:525:in `rescue in 
> exit_on_fail'
>   /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util.rb:511:in `exit_on_fail'
>   /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/application.rb:364:in `run'
>   /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/command_line.rb:132:in 
> `run'
>   /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/command_line.rb:86:in 
> `execute'
>   config.ru:28:in `block in '
>   /opt/puppet/lib/ruby/gems/1.9.1/gems/rack-1.4.5/lib/rack/builder.rb:51:in 
> `instance_eval'
>   /opt/puppet/lib/ruby/gems/1.9.1/gems/rack-1.4.5/lib/rack/builder.rb:51:in 
> `initialize'
>   config.ru:1:in `new'
>   config.ru:1:in `'
>   /opt/puppet/share/phusion_passenger/helper-scripts/rack-preloader.rb:105:in 
> `eval'
>   /opt/puppet/share/phusion_passenger/helper-scripts/rack-preloader.rb:105:in 
> `preload_app'
>   /opt/puppet/share/phusion_passenger/helper-scripts/rack-preloader.rb:150:in 
> `'
>   /opt/puppet/share/phusion_passenger/helper-scripts/rack-preloader.rb:29:in 
> `'
>   /opt/puppet/share/phusion_passenger/helper-scripts/rack-preloader.rb:28:in 
> `'
>
>
> Application root/var/opt/lib/pe-puppetmasterEnvironment (value of RAILS_ENV, 
> RACK_ENV, WSGI_ENV and PASSENGER_ENV)production
>
> PS: The server was working fine until the REST API DELETE 
> https://:8140/production/certificate_status/{hostname} was 
> run.
>
> Thanks,
> Naveen.
>

-- 
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/b132068d-c699-40c3-b5f0-4a64d336bce7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppetmaster Logrotate isn't working

2014-05-06 Thread Joachim Schrod

On 04/29/14 18:13, willi.feh...@home24.de wrote:
> Hello,
> 
> we have an issue that the Puppetmaster logrotate isn't working.
> 
> We are using the following default Logrotate:
> 
> /var/log/puppet/*log {
>   missingok
>   sharedscripts
>   create 0644 puppet puppet
>   compress
>   rotate 4
> 
>   postrotate
> pkill -USR2 -u puppet -f 'puppet master' || true
> [ -e /etc/init.d/puppet ] && /etc/init.d/puppet reload > /dev/null 2>&1 
> || true
>   endscript
> }
> 
> After running the logrotate script we have this message in syslog:
> 
> Apr 29 09:36:12 puppet1 puppet-master[3109]: Caught USR2; calling reopen_logs
> Apr 29 09:36:12 puppet1 puppet-master[3109]: Reopening log files
> 
> The problem is that the logrotate does not create a new masterhttp.log. We 
> tried it with Puppet-3.4.2, 3.4.3 and 3.5.1.

I can add that it doesn't work in 3.3.1 on openSUSE 12.x either.
Signal USR2 doesn't work there, log files are not reopened. (I
can't upgrade to 3.5 yet, am waiting for that to check if the
problem is still there.)

I resorted to restart the puppet service, instead of reloading it.

Cheers,
Joachim

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod, Roedermark, Germany
Email: jsch...@acm.org

-- 
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/lk994f%24s18%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB 2.0.0 final now available

2014-05-06 Thread Ken Barber

** Final Release **

PuppetDB 2.0.0 final - May 6, 2014.

PuppetDB 2.0.0 Downloads


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

For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories

Binary tarball: http://downloads.puppetlabs.com/puppetdb/

Source: http://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site, using an
affected PuppetDB version of 2.0.0:
https://tickets.puppetlabs.com/browse/PDB

Documentation: http://docs.puppetlabs.com/puppetdb/2.0

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

PuppetDB 2.0.0 Release Notes


PuppetDB 2.0.0 is a major release focusing on environments support.
Note that *this is a major version bump* and there are several
breaking changes, including dropping support for versions of
PostgreSQL prior to version 8.4 and Java 1.6. See the "Deprecations
and potentially breaking changes" section below for more information.

Things to take note of before upgrading:

* There is a known issue in Puppet 3.4.0, 3.4.1 and 3.4.2 with
duplicate failed events being tracked here:
https://tickets.puppetlabs.com/browse/PUP-1524. This is being fixed in
an upcoming release of Puppet. Since 1.6.0 this error will become more
obvious as we are now raising full stack traces, so you may notice it
more readily after the upgrade.

* If you receive the error “Could not open
/etc/puppet/log4j.properties”, this is because we have changed the
packaged config.ini to point at a new logging configuration file:
logback.xml. However during package installation some package managers
will cowardly refuse to just update config.ini, this in particular
affects RPM. After upgrading you should ensure any .rpmnew files are
reviewed and that changes to our vendored version are now merged with
your version of config.ini on disk. See this ticket for more
information: https://tickets.puppetlabs.com/browse/PDB-656

* Make sure all your PuppetDB instances are shut down and only upgrade
one at a time.

* As usual, don’t forget to upgrade your puppetdb-terminus package
also (on the host where your Puppet Master lives), and restart your
master service.

New features:

* (PDB-452,453,454,456,457,526,557) Adding support for storing,
querying and importing/exporting environments

  This change forced a new revision of the `replace facts`,
  `replace catalog` and `store report` commands. The PuppetDB terminus
  also needed to be updated to support new environment information
  being sent to PuppetDB. USERS MUST ALSO UPDATE THE PUPPETDB
  TERMINUS. Previous versions of those commands (and wire formats) are
  now deprecated. See the PuppetDB API docs for more information.
  Environments support has been added to the new v4 (currently
  experimental) query API. The following query endpoints now include
  environment in the response:

  - facts
  - resources
  - nodes
  - catalogs
  - reports
  - events
  - event counts
  - aggregate event counts

  The below query endpoints now allow query/filtering by environment:

  - facts
  - resources
  - nodes
  - catalogs
  - reports
  - events

  This release also includes a new environments query endpoint to list
  all known environments and allow an easy filtering based on
  environment for things like events, facts reports and resources. See
  the query API docs for more information. PuppetDB
  import/export/anonymization and benchmark tools also now have
  environment support. Storeconfigs export does not include
  environments as that information is not being stored in the old
  storeconfigs module. Environments that are no longer associated with
  a fact set, report or catalog will be "garbage collected" by being
  removed from the database.

* (PDB-581) Add subqueries to events query endpoint

  The events endpoint now supports select-resources and select-facts

* (PDB-234) Add v4 query API, deprecate v2 query API

  This patch adds the new code relevant for doing any future v4 work.
It has been
  raised as an experimental end-point only so there are no commitments to its
  interface yet. Once stable we will need another patch to declare it as so.

  This patch also deprecates the v2 end-point in documentation and by adding the
  same headers we used to use for the v1 end-point.

* (PDB-470) Provide new db setting 'statements-cache-size' with a
default of 1000

  This setting adjusts how many SQL prepared statements get cached via BoneCP.

  By using this setting we've seen an almost 40% decrease in wall clock time it
  takes to store a new catalog.

  This patch adds the new configuration item as a user configurable one, with a
  default set to 1000 for now. Documentation has also been added for this
  setting.

* (PDB-221) Add facts to import/export

  This commit imports/exports facts similar t

[Puppet Users] Re: Directory Environments Patch

2014-05-06 Thread Joshua Partlow

If you were unable to test from source previously, there is a 3.6.0-rc1
available now that you can use to test environment slow down issues.

You can obtain it from the pre-release repos as documented here:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos

Please see Eric's 3.6.0-rc1 announcement for more details.


On Tue, Apr 22, 2014 at 7:56 PM, Joshua Partlow <
joshua.part...@puppetlabs.com> wrote:

> Hi,
>
> We have a pull request on the Puppet master branch which provides caching
> support for directory environments, and which we think addresses the
> slowdowns people are seeing using directory environments with their
> production instances.
>
> https://github.com/puppetlabs/puppet/pull/2566
>
> This PR relies on code slated for 3.6.0 (current master head), so you
> can't simply apply the patch to a 3.5.1 install.  If you are comfortable
> doing a test run from a source checkout of the PR, it would be great to
> hear if this patch speeds up a run with directory environments enabled.
>
> There should be instructions at the bottom of the PR for how to get the
> branch (There is a link: 'you can also merge branches on the command
> line').  If you don't see that link, this is the important part:
>
> git checkout -b hlindberg-pup-1699_cache-environments master
> git pull g...@github.com:hlindberg/puppet.git pup-1699_cache-environments
>
> Don't do this unless you know how to run Puppet from source.
>
> There is a five second cache timeout set by default.  You can adjust this
> by adding an 'environment_timeout' setting in your directory environment's
> environment.conf file.  The possible values are '0' (no cacheing),
> 'unlimited' (cache forever), or a time value such as '5s', '5m', '5h', '5d'
> and so forth.
>
> Thanks!
>
>
> --
> Josh Partlow
> jpart...@puppetlabs.com
> Developer, Puppet Labs
>
> Join us at PuppetConf 2014, September 22-24 in San Francisco -
> http://puppetconf.com
> Register by May 30th to take advantage of the Early Adopter discount —save
> $349!
>



-- 
Josh Partlow
jpart...@puppetlabs.com
Developer, Puppet Labs

Join us at PuppetConf 2014, September 22-24 in San Francisco -
http://puppetconf.com
Register by May 30th to take advantage of the Early Adopter discount —save
$349!

-- 
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/CADxAQ5pG9Xr-aQbWrVuR%2By%2Bb5ofUQaH73_JwYKna3vXoM4fa0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Serious performance issues with Puppet 3.5.x when using Directory Environments

2014-05-06 Thread Josh Partlow

Hi Antoine,

There is a Puppet 3.6.0-rc1 available in the pre-release repos which has 
environment cacheing that we think will take care of the slowdown you are 
seeing with directory environments.  Would you be able to test that?  (See 
Eric's 3.6.0-rc1 announcement for details on obtaining the packages)

thanks,
Josh

On Tuesday, April 22, 2014 11:26:47 AM UTC-7, Eric Sorenson wrote:
>
>
>
> On Tuesday, April 22, 2014 5:25:55 AM UTC-7, Antoine Cotten wrote:
>>
>> Hi Eric,
>> thank you for pointing me to this feature, and sorry for the answer time. 
>>
>> I managed to outline the problematic parts in the Puppet run: the final 
>> POST method takes forever when Directory Environments is enabled (1) and 
>> the catalog compilation is overall much slower (1.3./4|5|6/)
>>
>> I triggered a run on the same node, with and without the feature enabled. 
>> Here are the corresponding profiling logs:
>>
>>
> Thanks, this is great information.
>
> The reason the POST looks slow is because it's an aggregate of all the 
> steps that came before it, as you see the profile step numbers pop out a 
> level, that line aggregates the times of everything inside it.  So the POST 
> is the aggregate of all the steps to compilation.
>
> I am looking at this more closely and I have opened 
> https://tickets.puppetlabs.com/browse/PUP-2337 to track it.
>
> --eric0
>

-- 
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/33f1c4fd-4a11-41fb-974c-e3cfd0337156%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppetmaster Logrotate isn't working

2014-05-06 Thread Chris


On 30/04/14 02:13, willi.feh...@home24.de wrote:

Hello,

we have an issue that the Puppetmaster logrotate isn't working.

We are using the following default Logrotate:

/var/log/puppet/*log {
   missingok
   sharedscripts
   create 0644 puppet puppet
   compress
   rotate 4

   postrotate
 pkill -USR2 -u puppet -f 'puppet master' || true
 [ -e /etc/init.d/puppet ] && /etc/init.d/puppet reload > /dev/null 2>&1 || 
true
   endscript
}

After running the logrotate script we have this message in syslog:

Apr 29 09:36:12 puppet1 puppet-master[3109]: Caught USR2; calling reopen_logs
Apr 29 09:36:12 puppet1 puppet-master[3109]: Reopening log files

The problem is that the logrotate does not create a new masterhttp.log. We 
tried it with Puppet-3.4.2, 3.4.3 and 3.5.1.


I can't help with the puppet side of things, but try 'copytruncate' in 
your logrotate conf instead, and remove the postrotate section.


--
Postgresql & php tutorials
http://www.designmagick.com/

--
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/5369577A.1010105%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "puppet apply --noop -e" and overiding facter values for testing

2014-05-06 Thread Jakov Sosic


On 05/06/2014 02:38 PM, Brian Mathis wrote:

This applies to facter version 1.7 and above.  See docs:
http://docs.puppetlabs.com/guides/custom_facts.html#external-facts

You can create a file like this (the name does not matter):
 /etc/facter/facts.d/myfacts.txt:
 hostname=value

Then when you run 'facter hostname', "value" will be returned.


Thank you!

--
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/53695BD5.3080704%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] ploperations modules/releases

2014-05-06 Thread Jeff Bachtel

The ploperations Forge user (and associated puppetlabs-operations GitHub 
account) have some very useful modules that are kept up-to-date on 
GitHub, but haven't been seeing releases to Forge (in more than a year, 
actually).


Is this a matter of lack of time or interest by the PL ops team on 
pushing out releases, or is there a more technical reason that these 
modules haven't seen releases cut and pushed to Forge?


Jeff

--
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/53695C10.1010803%40bericotechnologies.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Looking for a better way to use hiera hashes than create_resources

2014-05-06 Thread Ramin K


On 5/5/2014 7:32 AM, Alex Scoble wrote:

If you are trying to follow Puppet Labs recommended best practices, it's
definitely a moving target.


	I find it best not to change my workflow or methodology until it makes 
sense on my system regardless of what the community or even Puppet Labs 
has said.


A few of the things I have completely ignored,
 - inheriting params.pp class to get local variables
 - ENC
 - parameterized classes
 - 99.8% of Forge modules
 - data bindings

A few of the things I do/have done that Puppet no longer recommends or 
has never recommended,

 - use stages
 - include subclasses to change behavior of modules, class 
postfix::config::relay inherits postfix::config {

 - specific hiera calls
 - used RVM to run my Puppet master

	On the flip side I did have a 2000+ line commit last year when I 
switched over to role/profile. However the massive benefits in 
organization (at least for me) were worth the time investment. At some 
point I'll probably bite the parameterized classes/data binding bullet 
as well.


	I ran across a paper recently with the following quote. I think keeping 
this definition of Engineering in mind would be a good thing for the 
Puppet community instead of searching for the elusive best solution.


http://www.lunduniversity.lu.se/o.o.i.s?id=24965&postid=2968043
"Engineering has no hint of the absolute, the deterministic, the 
guaranteed, the true. Instead it fairly reeks of the uncertain, the 
provisional and the doubtful. The engineer instinctively recognizes this 
and calls his ad hoc method “doing the best you can with what you’ve 
got,” “finding a seat-of-the-pants solution,” or just “muddling 
through”. (Koen, 1985, p. 23)."


Ramin

--
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/536967B4.7000303%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 3.3: Signal USR2 doesn't work

2014-05-06 Thread Joachim Schrod


Hi,

On some systems, I use Puppet 3.3.1 for openSUSE 12.2. (We plan to
upgrade, but some external dependencies cause problems.) No newer
Puppet version is available from OBS.

On that systems, signal USR2 doesn't work. The man page tells that
it shall "Close file descriptors for log files and reopen them.
Used with logrotate." When "puppet agent" is called with "--logdest
FILE", that file is not reopened.

Can somebody confirm that signal USR2 works with Puppet 3.5.x or
3.6.0-RC1? I'd like to know if our workaround to restart Puppet
services on logrotate is a temporary issue, gone after upgrade, or
if I should incorporate according changes into all Puppet
installations.

TIA for any recommendation,

Joachim

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod, Roedermark, Germany
Email: jsch...@acm.org

-- 
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/lkbvuq%24vpk%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: temp dir fact

Re: [Puppet Users] puppet dism

[Puppet Users] Re: Setting quotes using augeas type

[Puppet Users] Re: Could not find class

[Puppet Users] Delete a clients certificate with curl no longer working?

Re: [Puppet Users] "puppet apply --noop -e" and overiding facter values for testing

[Puppet Users] rubygems.org broken for puppet < 3.5

[Puppet Users] Re: rubygems.org broken for puppet < 3.5

Re: [Puppet Users] "puppet apply --noop -e" and overiding facter values for testing

[Puppet Users] [JOB] - Senior Systems Administrator; 3-6 Month Contract; Deploy Linux Desktop Environment

[Puppet Users] Re: Could not find class

Re: [Puppet Users] puppet dism

[Puppet Users] Re: Hiera question: Nested hash

[Puppet Users] Re: Hiera question: Nested hash

Re: [Puppet Users] Re: Setting quotes using augeas type

Re: [Puppet Users] "The certificate retrieved from the master does not match the agent's private key." The master and agent in this case are on the same machine.

Re: [Puppet Users] Re: Looking for a better way to use hiera hashes than create_resources

Re: [Puppet Users] "The certificate retrieved from the master does not match the agent's private key." The master and agent in this case are on the same machine.

[Puppet Users] Problem with deploying Hiera hashes in order

Re: [Puppet Users] puppet dism

[Puppet Users] Ignore resource in provider if not defined?

[Puppet Users] Puppet enterprise console, all nodes 'unresponsive'.

Re: [Puppet Users] Eugene Oregon Puppet User Group?

[Puppet Users] Puppet module to install and configure libvirt on hosts and webvirtmgr on a separate server

[Puppet Users] Re: Hiera question: Nested hash

[Puppet Users] Announce: Puppet 3.6.0-RC1 available!

[Puppet Users] Re: Puppet Master not responding

Re: [Puppet Users] Puppetmaster Logrotate isn't working

[Puppet Users] PuppetDB 2.0.0 final now available

[Puppet Users] Re: Directory Environments Patch

[Puppet Users] Re: Serious performance issues with Puppet 3.5.x when using Directory Environments

Re: [Puppet Users] Puppetmaster Logrotate isn't working

Re: [Puppet Users] "puppet apply --noop -e" and overiding facter values for testing

[Puppet Users] ploperations modules/releases

Re: [Puppet Users] Re: Looking for a better way to use hiera hashes than create_resources

[Puppet Users] Puppet 3.3: Signal USR2 doesn't work

36 matches

Site Navigation

Mail list logo

Footer information