[Puppet Users] minor change in inkling/postgresql – PostgreSQL
Hi, When running the Postgresql module the database installed by default is 8.4 what we need is 9.1 where do i define the version to be installed by puppet. If i edit the params,pp like; $client_package_name = 'postgresql91' $server_package_name = 'postgresql91' The 9.1 is being installed but i get some errors like these; Execution of '/sbin/service postgresql start' returned 1 Thanks in forward for you help. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/2456wjmHE2oJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: minor change in inkling/postgresql – PostgreSQL
On more thing the postgresql-9.1 is installed but when you run service postgresql-9.1 start you get /var/lib/pgsql/9.1/data is missing, Use service postgresql-9.1.4 initdb to initialize the cluster first. Any idea ? Op woensdag 29 augustus 2012 02:14:54 UTC-4 schreef OXS007 het volgende: Hi, When running the Postgresql module the database installed by default is 8.4 what we need is 9.1 where do i define the version to be installed by puppet. If i edit the params,pp like; $client_package_name = 'postgresql91' $server_package_name = 'postgresql91' The 9.1 is being installed but i get some errors like these; Execution of '/sbin/service postgresql start' returned 1 Thanks in forward for you help. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/nUDK3yg3Mb0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] dmz network configuration
On 12-08-29 01:51 AM, Andrei-Florian Staicu wrote: I need to install puppet agent on some DMZ hosts, so I need to have all TCP ports. Can anyone tell me what the data flow is between agents and the master? Also, what would be the case when using MCollective, inseatad of puppet kick? If I'm not mistaken, in the simplest scenario where your puppetmaster is not interacting with external filebuckets, puppetDBs, schedulers and whatnot, puppet clients pretty much only need to be able to establish a TCP connection with the puppet master on port 8140. As long as you let established connections out of the DMZ, then connection both ways should be assured. -- Gabriel Filion -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: minor change in inkling/postgresql – PostgreSQL
I think i figured it out in the Postgresql module edit the params.pp so
that it looks like this;
case $::osfamily {
'RedHat': {
$service_name = 'postgresql-9.1'
$client_package_name = 'postgresql91'
$server_package_name = 'postgresql91-server'
$needs_initdb = true
$initdb_path = '/usr/pgsql-9.1/bin/initdb'
$createdb_path= '/usr/pgsql-9.1/bin/createdb'
$psql_path= '/usr/pgsql-9.1/bin/psql'
$datadir = '/var/lib/pgsql/9.1/data/'
$pg_hba_conf_path = '/var/lib/pgsql/9.1/data/pg_hba.conf'
$postgresql_conf_path = '/var/lib/pgsql/9.1/data/postgresql.conf'
$firewall_supported = true
$persist_firewall_command = '/sbin/iptables-save
/etc/sysconfig/iptables'
}
Op woensdag 29 augustus 2012 02:14:54 UTC-4 schreef OXS007 het volgende:
Hi,
When running the Postgresql module the database installed by default is
8.4 what we need is 9.1 where do i define the version to be installed by
puppet.
If i edit the params,pp like;
$client_package_name = 'postgresql91'
$server_package_name = 'postgresql91'
The 9.1 is being installed but i get some errors like these;
Execution of '/sbin/service postgresql start' returned 1
Thanks in forward for you help.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/0oZAJXRvTRgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] troubleshooting resource collection
Hi,
I'm new to Puppet. And I'm trying out an ssh module:
https://github.com/saz/puppet-ssh.
It collects ssh keys like this:
class ssh::knownhosts {
Sshkey | | {
ensure = present,
}
notify{knownhosts class: $fqdn $hostname $ipaddress :}
}
I can see it echoes the host key of the host the puppet agent runs on. But
the /etc/ssh/ssh_known_hosts file isn't actually written - I can add an
sshkey resource manually in a manifest somewhere and then puppet does
write the file though.
I reckon when compiling the catalog, Puppet doesn't actually use the
collected resource to include in another host's configuration. But why not?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/xIajfCY6vaYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Managing Eclipse with Puppet
perjantai, 24. elokuuta 2012 0.43.19 UTC+3 Jeff Sussna kirjoitti: Does anyone know if there's a Puppet module available for managing Eclipse plugins? I'm also interested in this. Anyone using puppet for setting up eclipse? (with or without plugins) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/PIArMUWCZ8EJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] How to purge network-manager (requires reboot) ?
Hi all =) I would like to purge the following packages network-manager network-manager-gnome network-manager-pptp network-manager-pptp-gnome but the problem is, that I suppose a reboot is required for the NIC's no longer to be manged by network-manager? How would you work around this? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ZrmngeNkZCcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] The rewritten Puppet 2.7 language reference is live
https://github.com/puppetlabs/puppet/commit/193e19eb14ff640a68f2a21fd525ef6c8825dbf2 Don't think that was in the language guide. And the new 'unless' statement in 3.0. - henrik -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: How to purge network-manager (requires reboot) ?
Hi Sandra, [...] but the problem is, that I suppose a reboot is required for the NIC's no longer to be manged by network-manager? I am not sure why would it require a restart, hm... I am used to making sure that the service is stopped, packaged purged and then you only need to make sure that static IP configuration is in place. Sometimes you need to get rid of the udev rules file, but not often. KW -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Vr_-k9qbXUEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Managing plugins
Hi all,
We are configuring Jenkins and Sonar with puppet and both systems use
plugins. What is the preferred way of managing plugin-like resources
with puppet?
I am looking at two options but if you have a better idea let me know!
1. Create plugin::installed and plugin::uninstalled definitions:
define plugin::installed {
$plugin_url = ${name}
exec {
download-jenkins-plugin-${name} :
command = wget -O `basename ${plugin_url}` ${plugin_url}
--no-check-certificate,
cwd = ${jenkins::plugin_dir},
path = '/usr/bin',
user = ${jenkins::user},
group = ${jenkins::group},
creates = ${jenkins::plugin_dir}/${plugin}
}
}
define plugin::uninstalled {
$plugin_url = ${name}
exec {
uninstall-jenkins-plugin ${name} :
command = rm ${plugin_url},
cwd = ${jenkins::plugin_dir},
path= ['/usr/bin', '/bin'],
user= ${jenkins::user},
onlyif = test -e `basename ${plugin_url}`
}
}
and define an array of installed and uninstalled plugins on which the
definitions are applied.
OR
2. On every puppet run, clear the plugin directory and then download
every plugin via a plugin definition and an array of installed
plugins.
Option 2 is more compact and easier to use but the downside is that
plugins are downloaded every time.
What do you think?
Cheers,
Frank
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/7BEGHYCw9ugJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Managing plugins
Hi, [...] I'd get rid of wget altogether, then make nice packages for each plugin using https://github.com/jordansissel/fpm and then just use Puppet's package to install relevant ones. KW -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ZB8kcy1Xcu4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Don't touch non-default config files
Hi folks, I'd like to say puppet. If the standart config file, delivered by dpkg, is changed and has also not the same md5sum as the file I want to deliver with puppet. Do nothing :) OK guys.. that was not my idea! I say everything has to be changed in puppet and not by hand. Or Maybe there is a way to use facter for it?! Thank's for your recommendations! Jonesi -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/n2Gl5nwHdY8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Announce: Hiera-Puppet 1.0.0 available
On Tuesday, August 28, 2012 5:32:56 PM UTC-5, Matthaus Litteken wrote:
We are happy to announce Hiera-Puppet 1.0.0.
That is good news, however, doesn't this rely on hiera 1.0.0?
Any word on when that will be out of RC and a final release will be ready?
It includes Puppet functions for hiera and also the puppet backend for
hiera lookups.
Downloads are available:
* Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0.tar.gz
* Apt and yum repositories
* Apple package
http://puppetlabs.com/downloads/mac/hiera-puppet-1.0.0.dmg
* Rubygems https://rubygems.org/downloads/hiera-puppet-1.0.0.gem
It includes contributions from the following people:
Andrew Parker, Gary Larizza, Hunter Haugen, Jeff McCune, Kelsey
Hightower, Ken Barber, Matthaus Litteken, Nan Liu, Patrick Carlisle,
and Will Hopper
See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.0.0:
http://projects.puppetlabs.com/projects/hiera-puppet
## Hiera-Puppet 1.0.0 Changelog ##
Andrew Parker (1):
89cde8d (Maint) Create a test for the puppet backend
Gary Larizza (2):
894a7a4 Fail if a lookup key isn't passed
927de1f Add test coverage for hiera_hash()
Hunter Haugen (1):
632457e Rubygems is not required to use hiera
Jeff McCune (5):
def41d5 Add watchr script
d840325 (Maint) Use PuppetlabsSpec::PuppetSeams.parser_scope
88c5f9a (Maint) Fix mock error with hiera module
7ac4a54 (Maint) Fix missing spec_helper lines in some tests
84b4d11 (Maint) Rename PuppetlabsSpec::Puppet{Seams,Internals}
Kelsey Hightower (8):
48bfccb (#14461) Remove Puppet parser functions
a042de4 Revert (#14461) Remove Puppet parser functions
01e9122 (maint) Follow Puppet Labs style guide + code cleanup
95d7058 (maint) parser functions do not require hiera.yaml
8a49eab (maint) Add acceptance tests
bdb8563 (#15184) Refactor parser functions
9ab901f (maint) Hiera Puppet now has a LICENSE file
44bc7cb (#15105) Update README YAML examples
Ken Barber (1):
2df319a (#14124) Load rake tasks directly to fix tests for Ruby
1.9.x
Matthaus Litteken (17):
cb721c5 Add mac packaging to hiera-puppet
64b7375 Move conf to ext directory
4101d02 Add debian packaging for hiera-puppet
470c5c8 Add Redhat packaging to hiera-puppet
5adc454 Add package task to tasks
1138e65 Updating CHANGELOG for hiera-puppet 1.0.0rc1
378a1a2 Tweak debian packaging
9c23e9d Remove puppetlabs_spec_helper require from root Rakefile
8e4e76a (maint) Replace .should on blocks with .to
2fa4251 Update hiera-puppet package tasks
c686adb Update debian package task to handle orig version
properly and use the correct directory name when building.
416f098 Update hiera-puppet hiera dependency to ~ 1.0
1b2a5d1 Update CHANGELOG for 1.0.0rc2
0fbdd62 (#15291) Add Vendor tag to Hiera-Puppet spec file
fd3fe17 Add hiera_puppet.rb to debian, redhat packages, fix gem
version dependency
962453f Updating CHANGELOG for 1.0.0rc3
62492ba Updating CHANGELOG for 1.0.0, changing hiera dependency to
~ 1.0
Nan Liu (1):
eb800e4 (#12037) hiera-puppet should support hash values.
Patrick Carlisle (4):
dbdda00 (#12122) Use nil as default answer in lookup
7a458a4 (#14841) Give useful error for array or hash lookup failure
d76a9d8 (#14841) Add test for hiera_hash parser function
b166328 (#14841) Add test coverage for remaining hiera parser
functions
Will Hopper (1):
5e516ee Update Debian packaging rake task to correctly create
the orig.tar.gz
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/gjEFHekb_U0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Managing Eclipse with Puppet
Eclipse itself is straightfoward, since it's just a matter of download/unzip/set env vars.I wrote my own manifest to do that. In at least one case I tried, installing a plugin by manually placing files into /plugins and /features wasn't enough to activate the plugin. Wondering if it was because of the need to accept the license? On Wednesday, August 29, 2012 2:38:49 AM UTC-5, Juha Vainikka wrote: perjantai, 24. elokuuta 2012 0.43.19 UTC+3 Jeff Sussna kirjoitti: Does anyone know if there's a Puppet module available for managing Eclipse plugins? I'm also interested in this. Anyone using puppet for setting up eclipse? (with or without plugins) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5MJ7AWKU7MsJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: How to purge network-manager (requires reboot) ?
Hi Krzysztof I am not sure why would it require a restart, hm... I am used to making sure that the service is stopped, packaged purged and then you only need to make sure that static IP configuration is in place. Sometimes you need to get rid of the udev rules file, but not often. Great. Then that problem is solved. Thanks =) Hugs, Sandra =) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/L1MZfP_loJoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: How to purge network-manager (requires reboot) ?
On Wednesday, August 29, 2012 6:48:04 AM UTC-5, Sandra Schlichting wrote:
Hi all =)
I would like to purge the following packages
network-manager
network-manager-gnome
network-manager-pptp
network-manager-pptp-gnome
but the problem is, that I suppose a reboot is required for the NIC's no
longer to be manged by network-manager?
How would you work around this?
Like Krzysztof, I'm not certain that a reboot is required. On the other
hand, Network Manager is a tricky and sometimes pesky little beast, so
maybe a reboot really is required. I can't advise you on avoiding a
reboot, but if you really do need one, then you can probably make Puppet
schedule one using something along these lines:
exec { 'reboot-soon':
command = '/usr/bin/nohup /sbin/shutdown -r +5 ',
provider = 'sh',
subscribe = Package['network-manager'],
refreshonly = true,
}
That will reboot the system whenever Puppet changes the 'network-manager'
package (which must already have been declared elsewhere). The five-minute
delay designated by the +5 argument serves two purposes:
1. To allow the Puppet run to complete before the reboot (see also below)
2. To give an admin who happens to be logged in a chance to cancel the
restart
With respect to the delay time, there is an unavoidable race condition
here, because you can't really predict how much longer Puppet will take to
finish up, especially if the system is heavily loaded. You can largely
mitigate that, however, by ensuring that Exec['reboot-soon'] is applied
after all other resources. Although I'm not a great fan of run stages,
this looks like a good use case for them.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/ZtpVMqFw7G8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Managing Eclipse with Puppet
To install additional plugins into Eclipse, you want to use the p2 director application. It is embedded inside the Eclipse IDE itself so once the IDE is unzipped and Java is installed, it is possible to run the director. The director app can install new things, update, and uninstall. There is also a separately packaged smaller headless p2 director available for download. (This director is often used in headless/CI builds). The main complications regarding Eclipse installations is if you install it in one of the shared modes. Regards - henrik On 2012-29-08 15:49, Jeff Sussna wrote: Eclipse itself is straightfoward, since it's just a matter of download/unzip/set env vars.I wrote my own manifest to do that. In at least one case I tried, installing a plugin by manually placing files into /plugins and /features wasn't enough to activate the plugin. Wondering if it was because of the need to accept the license? On Wednesday, August 29, 2012 2:38:49 AM UTC-5, Juha Vainikka wrote: perjantai, 24. elokuuta 2012 0.43.19 UTC+3 Jeff Sussna kirjoitti: Does anyone know if there's a Puppet module available for managing Eclipse plugins? I'm also interested in this. Anyone using puppet for setting up eclipse? (with or without plugins) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5MJ7AWKU7MsJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: troubleshooting resource collection
On Wednesday, August 29, 2012 6:25:35 AM UTC-5, Frank Van Damme wrote:
Hi,
I'm new to Puppet. And I'm trying out an ssh module:
https://github.com/saz/puppet-ssh.
It collects ssh keys like this:
class ssh::knownhosts {
Sshkey | | {
ensure = present,
}
notify{knownhosts class: $fqdn $hostname $ipaddress :}
}
I can see it echoes the host key of the host the puppet agent runs on. But
the /etc/ssh/ssh_known_hosts file isn't actually written - I can add an
sshkey resource manually in a manifest somewhere and then puppet does
write the file though.
I reckon when compiling the catalog, Puppet doesn't actually use the
collected resource to include in another host's configuration. But why not?
The code you present collects all available exported resources of type
'sshkey', but it does not declare any such resources. If you're not
managing your nodes' ssh host keys, then Puppet knows nothing about them.
For this to work, therefore, in addition to the above your manifest should
contain something like
@@sshkey { ${hostname}:
key = 'the-key',
type = 'probably-dsa-or-rsa'
}
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/SIJ1apuqsu0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Don't touch non-default config files
On 29/08/12 15:10, Jones wrote: I'd like to say puppet. If the standart config file, delivered by dpkg, is changed and has also not the same md5sum as the file I want to deliver with puppet. Do nothing :) OK guys.. that was not my idea! I say everything has to be changed in puppet and not by hand. Just for the sake of curiosity: why don't you just prepare your puppet conf to be like the default conf for that package? It's easier and saner IMO. -- Davide Ferrari Senior System Administrator Trovit Search http://www.trovit.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet not picking up manifests
On Tuesday, August 28, 2012 10:39:01 PM UTC-5, Anatoliy Lisovskiy (Wavebourn) wrote: On Tue, Aug 28, 2012 at 3:55 PM, Nick Fagerlund nick.fa...@puppetlabs.comjavascript: wrote: Could you please link me to these tutorials, so I may destroy them. It is easy to destroy incomplete tutorials, but harder to offer something good instead! When I started using Puppet it took long time until I suddenly found somewhere that the starting point is site.pp After that all went flawlessly. But this first step was very hard to understand. It would be nice to have a working scenario that describes basic details, how Puppet works, step by step, instead of long explanations of syntax, variables, and tricks with code optimization that are not needed to start running it. I have always found PuppetLabs's Puppet Language Guide to be a great resource. It was easy to find on PL's (then called Reductive Labs) web site when I first started with Puppet about three years ago, and it still is. It covers this point, among many others. There are also some good books about Puppet available. Additionally, there are a number of third-party tutorials spread around the web, of varying quality and thoroughness. Is there something else specific that you would have liked to see? John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/rjHuDUJ3UucJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Don't touch non-default config files
If it's default it should use the puppet version... but if someone changed it puppet should do nothing. That's the little issue :/ Am 29.08.2012 16:21 schrieb Davide Ferrari dav...@trovit.com: On 29/08/12 15:10, Jones wrote: I'd like to say puppet. If the standart config file, delivered by dpkg, is changed and has also not the same md5sum as the file I want to deliver with puppet. Do nothing :) OK guys.. that was not my idea! I say everything has to be changed in puppet and not by hand. Just for the sake of curiosity: why don't you just prepare your puppet conf to be like the default conf for that package? It's easier and saner IMO. -- Davide Ferrari Senior System Administrator Trovit Search http://www.trovit.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: thoughts on puppet 2.7 vs 3.0
Please see this post. https://groups.google.com/forum/#!topic/puppet-users/8AwzWv2-Qeo -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/mlKC53-C9e4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] augeas and cron.allow
Hi.
I am having a few problems with augeas and need some help.
What I am trying to use is augeas to update the cron.allow file. I can get
augeas to add the required name but I am having problems with getting it to add
the name once.
augeas { check_mk_cron.allow :
context = /files/etc/cron.allow,
# changes = set line[last()+1] $name,
changes = set 1[last()+1] $name,
# onlyif = match /files/etc/cron.allow/* include ALL,
onlyif = match *[.='$name'] not_include $name,
# onlyif = get 1[.='ALL'] == ALL,
}
The line ' changes = set 1[last()+1] $name,' works like a charm but I am
unable to get any onlyif to work.
If I use the onlyif in augtool I get this output, if this helps.
augtool match /files/etc/cron.allow/*[.='ALL']
/files/etc/cron.allow/4 = ALL
Cheers
Mark
This email has been sent from Gala Coral Group Limited (GCG) or a subsidiary
or associated company. GCG is registered in England with company number
07254686. Registered office address: 71 Queensway, London W2 4QH, United
Kingdom; website: www.galacoral.com.
This e-mail message (and any attachments) is confidential and may contain
privileged and/or proprietorial information protected by legal rules. It is for
use by the intended addressee only. If you believe you are not the intended
recipient or that the sender is not authorised to send you the email, please
return it to the sender (and please copy it to h...@galacoral.com) and then
delete it from your computer. You should not otherwise copy or disclose its
contents to anyone.
Except where this email is sent in the usual course of business, the views
expressed are those of the sender and not necessarily ours. We reserve the
right to monitor all emails sent to and from our businesses, to protect the
businesses and to ensure compliance with internal policies.
Emails are not secure and cannot be guaranteed to be error-free, as they can be
intercepted, amended, lost or destroyed, and may contain viruses; anyone who
communicates with us by email is taken to accept these risks. GCG accepts no
liability for any loss or damage which may be caused by software viruses.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Don't touch non-default config files
On 29/08/12 16:57, Johannes Reichhardt wrote: If it's default it should use the puppet version... but if someone changed it puppet should do nothing. That's the wrong approach. if you are managing a resource through puppet, then ALL changes go through puppet, otherwise it's a mess, and then puppet it's not what you want. You probably want some system deploy application like FAI and then manual resource management. -- Davide Ferrari Senior System Administrator Trovit Search http://www.trovit.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet not picking up manifests
This is the tutorial I was using.
http://bitfieldconsulting.com/puppet-tutorial
Once I changed nodes.pp to site.pp Puppet saw it. Now I just have to
change the rest of the manifests.
Thanks.
On Tue, Aug 28, 2012 at 6:55 PM, Nick Fagerlund
nick.fagerl...@puppetlabs.com wrote:
Could you please link me to these tutorials, so I may destroy them.
Okay, anyway, here's how Puppet works:
The master has ONE manifest file that it ALWAYS reads, called
/etc/puppet/manifests/site.pp. (use puppet master --configprint manifest to
confirm its location. You can set the 'manifest' setting to change that.)
It also OPTIONALLY can have an external node classifier; don't worry about
that right now.
The main manifest and the ENC can declare classes. Puppet will AUTOLOAD
classes from MODULES. See here:
http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html
If you use an IMPORT statement in site.pp, you can also load arbitrary
files like nodes.pp or nodes/somethingelse.pp. See here:
http://docs.puppetlabs.com/puppet/2.7/reference/lang_import.html But you
don't need to do this right now.
So to get your simple thing working now:
* rename nodes.pp to site.pp so puppet master will use it
* move ntp.pp to /etc/puppet/modules/ntp/manifests/init.pp
On Tuesday, August 28, 2012 1:19:23 PM UTC-7, Bai Shen wrote:
I created some manifest files, but my client doesn't seem to be picking
them up. According to all of the tutorials, I'm doing this right, so I'm
not sure what the issue is.
nodes.pp:
node default {
include ntp
}
ntp.pp:
class ntp {
package {
ntp:
ensure = installed
}
service {
ntpd:
ensure = running,
}
}
puppetd --test:
dnsdomainname: Unknown host
dnsdomainname: Unknown host
info: Caching catalog for testserver
info: Applying configuration version '1346184997'
notice: Finished catalog run in 0.01 seconds
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/ABbfMKE7JkgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] What is wrong with mu class?
Hi, If I write the following in a template directories=% backupDirList.each do |dir| -%%= dir % % end -% then it will output directories=/appl /etc /usr/local Question How do I print the backupDirList array, so it doesn't end with a blank space? Best regards, Sandra =) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/crWCaGLzqAIJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: thoughts on puppet 2.7 vs 3.0
I saw that, thanks. I'm looking for more of an opinion on what route other people would take... On Wednesday, August 29, 2012 10:57:40 AM UTC-4, Sandra Schlichting wrote: Please see this post. https://groups.google.com/forum/#!topic/puppet-users/8AwzWv2-Qeo -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/q5AdWIPVEw8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: thoughts on puppet 2.7 vs 3.0
On 08/29/2012 06:01 PM, Jason Antman wrote: I saw that, thanks. I'm looking for more of an opinion on what route other people would take... Considering the long term lock-in, I would try to postpone deployment till 3.0 stable gets out. PS. This new addon of parametrized classes getting info from hiera auto-magicly really sounds great :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: What is wrong with mu class?
Solved. directories=%= backupDirList.join( ) % Of course =) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/yJvpD1K7AiQJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: minor change in inkling/postgresql – PostgreSQL
Hello OSX007,
You are on the right track, for sure. The goal of the params.pp is to set
default values for those things and allow you to override them in your own
manifests. It's definitely OK for you to edit params.pp directly if you
know for sure that the settings you've specified will always be the ones
that you want, but otherwise you should be able to override them in your
own manifests and pass them in without modifying the module's params.pp
directly. This would allow you to potentially use the module to manage
both 8.x and 9.x instances.
I'd love to put together a test manifest that illustrates how to do what
you're doing w/o modifying params.pp directly, and submit a pull request to
the module so that it will be easier for other folks to figure out how to
do it in the future. I'd also love to provide a single parameter like
postgres_version that you could just set to 9.1 and then add code to
the module that would switch all of those path variables to the correct
values for you. I hope to continue submitting pull requests with features
like that over time, but if you have any such submissions you'd like to
make yourself, I'm sure they'd be welcomed!
On Wednesday, August 29, 2012 12:15:13 AM UTC-7, OXS007 wrote:
I think i figured it out in the Postgresql module edit the params.pp so
that it looks like this;
case $::osfamily {
'RedHat': {
$service_name = 'postgresql-9.1'
$client_package_name = 'postgresql91'
$server_package_name = 'postgresql91-server'
$needs_initdb = true
$initdb_path = '/usr/pgsql-9.1/bin/initdb'
$createdb_path= '/usr/pgsql-9.1/bin/createdb'
$psql_path= '/usr/pgsql-9.1/bin/psql'
$datadir = '/var/lib/pgsql/9.1/data/'
$pg_hba_conf_path = '/var/lib/pgsql/9.1/data/pg_hba.conf'
$postgresql_conf_path = '/var/lib/pgsql/9.1/data/postgresql.conf'
$firewall_supported = true
$persist_firewall_command = '/sbin/iptables-save
/etc/sysconfig/iptables'
}
Op woensdag 29 augustus 2012 02:14:54 UTC-4 schreef OXS007 het volgende:
Hi,
When running the Postgresql module the database installed by default is
8.4 what we need is 9.1 where do i define the version to be installed by
puppet.
If i edit the params,pp like;
$client_package_name = 'postgresql91'
$server_package_name = 'postgresql91'
The 9.1 is being installed but i get some errors like these;
Execution of '/sbin/service postgresql start' returned 1
Thanks in forward for you help.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/ewViWOoG3kIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] hiera-puppet no longer installs
Once Hiera-Puppet moved out of rc, it seemed best to move its hiera dependency from 1.0.0rc to 1.0, to ensure that those using Hiera-puppet get the non-RC version of hiera when it's available. Until Hiera 1.0.0 is released, you can install Hiera-puppet alongside hiera using the --pre flag to gems. `gem install --pre hiera-puppet`. Currently this will bring in Hiera 1.0.0rc4 and Hiera-puppet 1.0.0rc3 (which is identical to Hiera-puppet 1.0.0 except for the dependency change). If you want Hiera-puppet 1.0.0 still, you can then run `gem install --force hiera-puppet -v 1.0.0`. Hiera-puppet 1.0.0 requires changes that were made to Hiera prior to and during the 1.0.0 rc series, so running hiera-puppet 1.0.0 alongside hiera 0.3.0 will not behave as expected. This should only affect gem installs, if you are installing hiera-puppet using our yum or apt repos with our development repositories enabled hiera-puppet should install fine. On Tue, Aug 28, 2012 at 9:26 PM, Thomas Hallgren tho...@tada.se wrote: I'm unable to install hiera-puppet. Seems it requires hiera ~ 1.0. $ gem install hiera-puppet ERROR: While executing gem ... (Gem::DependencyError) Unable to resolve dependencies: hiera-puppet requires hiera (~ 1.0) Hiera installs, but version 0.3.0 $ gem install hiera Fetching: hiera-0.3.0.gem (100%) Successfully installed hiera-0.3.0 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/cKz0pYFMxKIJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Matthaus Litteken Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppetlabs-stdlib
I'm confused about this... https://github.com/puppetlabs/puppetlabs-stdlib/ I see a lot of functions there that are the same as the ones that come standard with puppet. If I create a module and dump this stuff in there, what happens to the existing stuff? How does puppet know which one to use? Doug -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Announce: Hiera-Puppet 1.0.0 available
It does rely on Hiera 1.0.0. We'll be cutting one more rc of Hiera
this week and if that goes well, Hiera 1.0.0 will follow the week
after.
On Wed, Aug 29, 2012 at 6:12 AM, llowder llowde...@gmail.com wrote:
On Tuesday, August 28, 2012 5:32:56 PM UTC-5, Matthaus Litteken wrote:
We are happy to announce Hiera-Puppet 1.0.0.
That is good news, however, doesn't this rely on hiera 1.0.0?
Any word on when that will be out of RC and a final release will be ready?
It includes Puppet functions for hiera and also the puppet backend for
hiera lookups.
Downloads are available:
* Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0.tar.gz
* Apt and yum repositories
* Apple package
http://puppetlabs.com/downloads/mac/hiera-puppet-1.0.0.dmg
* Rubygems https://rubygems.org/downloads/hiera-puppet-1.0.0.gem
It includes contributions from the following people:
Andrew Parker, Gary Larizza, Hunter Haugen, Jeff McCune, Kelsey
Hightower, Ken Barber, Matthaus Litteken, Nan Liu, Patrick Carlisle,
and Will Hopper
See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.0.0:
http://projects.puppetlabs.com/projects/hiera-puppet
## Hiera-Puppet 1.0.0 Changelog ##
Andrew Parker (1):
89cde8d (Maint) Create a test for the puppet backend
Gary Larizza (2):
894a7a4 Fail if a lookup key isn't passed
927de1f Add test coverage for hiera_hash()
Hunter Haugen (1):
632457e Rubygems is not required to use hiera
Jeff McCune (5):
def41d5 Add watchr script
d840325 (Maint) Use PuppetlabsSpec::PuppetSeams.parser_scope
88c5f9a (Maint) Fix mock error with hiera module
7ac4a54 (Maint) Fix missing spec_helper lines in some tests
84b4d11 (Maint) Rename PuppetlabsSpec::Puppet{Seams,Internals}
Kelsey Hightower (8):
48bfccb (#14461) Remove Puppet parser functions
a042de4 Revert (#14461) Remove Puppet parser functions
01e9122 (maint) Follow Puppet Labs style guide + code cleanup
95d7058 (maint) parser functions do not require hiera.yaml
8a49eab (maint) Add acceptance tests
bdb8563 (#15184) Refactor parser functions
9ab901f (maint) Hiera Puppet now has a LICENSE file
44bc7cb (#15105) Update README YAML examples
Ken Barber (1):
2df319a (#14124) Load rake tasks directly to fix tests for Ruby
1.9.x
Matthaus Litteken (17):
cb721c5 Add mac packaging to hiera-puppet
64b7375 Move conf to ext directory
4101d02 Add debian packaging for hiera-puppet
470c5c8 Add Redhat packaging to hiera-puppet
5adc454 Add package task to tasks
1138e65 Updating CHANGELOG for hiera-puppet 1.0.0rc1
378a1a2 Tweak debian packaging
9c23e9d Remove puppetlabs_spec_helper require from root Rakefile
8e4e76a (maint) Replace .should on blocks with .to
2fa4251 Update hiera-puppet package tasks
c686adb Update debian package task to handle orig version
properly and use the correct directory name when building.
416f098 Update hiera-puppet hiera dependency to ~ 1.0
1b2a5d1 Update CHANGELOG for 1.0.0rc2
0fbdd62 (#15291) Add Vendor tag to Hiera-Puppet spec file
fd3fe17 Add hiera_puppet.rb to debian, redhat packages, fix gem
version dependency
962453f Updating CHANGELOG for 1.0.0rc3
62492ba Updating CHANGELOG for 1.0.0, changing hiera dependency to
~ 1.0
Nan Liu (1):
eb800e4 (#12037) hiera-puppet should support hash values.
Patrick Carlisle (4):
dbdda00 (#12122) Use nil as default answer in lookup
7a458a4 (#14841) Give useful error for array or hash lookup failure
d76a9d8 (#14841) Add test for hiera_hash parser function
b166328 (#14841) Add test coverage for remaining hiera parser
functions
Will Hopper (1):
5e516ee Update Debian packaging rake task to correctly create
the orig.tar.gz
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/gjEFHekb_U0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Matthaus Litteken
Release Manager, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] hiera-puppet no longer installs
Thanks for the info.
In our case it affected our puppet manifests where we had:
package { 'hiera-puppet':
ensure = installed,
provider = $gem_provider,
}
We prefer to use the latest release when possible.
On 2012-08-29 18:56, Matthaus Owens wrote:
Once Hiera-Puppet moved out of rc, it seemed best to move its hiera
dependency from 1.0.0rc to 1.0, to ensure that those using
Hiera-puppet get the non-RC version of hiera when it's available.
Until Hiera 1.0.0 is released, you can install Hiera-puppet alongside
hiera using the --pre flag to gems.
`gem install --pre hiera-puppet`. Currently this will bring in Hiera
1.0.0rc4 and Hiera-puppet 1.0.0rc3 (which is identical to Hiera-puppet
1.0.0 except for the dependency change). If you want Hiera-puppet
1.0.0 still, you can then run `gem install --force hiera-puppet -v
1.0.0`.
Hiera-puppet 1.0.0 requires changes that were made to Hiera prior to
and during the 1.0.0 rc series, so running hiera-puppet 1.0.0
alongside hiera 0.3.0 will not behave as expected.
This should only affect gem installs, if you are installing
hiera-puppet using our yum or apt repos with our development
repositories enabled hiera-puppet should install fine.
On Tue, Aug 28, 2012 at 9:26 PM, Thomas Hallgren tho...@tada.se wrote:
I'm unable to install hiera-puppet. Seems it requires hiera ~ 1.0.
$ gem install hiera-puppet
ERROR: While executing gem ... (Gem::DependencyError)
Unable to resolve dependencies: hiera-puppet requires hiera (~ 1.0)
Hiera installs, but version 0.3.0
$ gem install hiera
Fetching: hiera-0.3.0.gem (100%)
Successfully installed hiera-0.3.0
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/cKz0pYFMxKIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: thoughts on puppet 2.7 vs 3.0
Chris Jakov, That's my tentative feeling right now, but given the way things work around here, and that puppet is really a lower-level project (i.e. experimentation, failure, and bugs aren't tolerated well because we only have management support for the end result, not puppet itself) I'll probably have to wait for community adoption of 3.0 and then see how it goes. A slightly complicating factor is that I need RHEL4 and SLES9... I just built ruby-1.8.7 and deps and haven't tested puppet 2.7.18 on them yet, so the 2.0 switch might be a bit of a pain... Thanks for the input. -Jason On 08/29/2012 12:24 PM, Christopher Wood wrote: In your position I would consider it well worth waiting for puppet 3. On Wed, Aug 29, 2012 at 09:01:05AM -0700, Jason Antman wrote: I saw that, thanks. I'm looking for more of an opinion on what route other people would take... On Wednesday, August 29, 2012 10:57:40 AM UTC-4, Sandra Schlichting wrote: Please see this post. [1]https://groups.google.com/forum/#!topic/puppet-users/8AwzWv2-Qeo -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit [2]https://groups.google.com/d/msg/puppet-users/-/q5AdWIPVEw8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. References Visible links 1. https://groups.google.com/forum/#%21topic/puppet-users/8AwzWv2-Qeo 2. https://groups.google.com/d/msg/puppet-users/-/q5AdWIPVEw8J -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet java module
I'm trying to install the java module using puppet. http://forge.puppetlabs.com/puppetlabs/java I think I'm supposed to download the oracle rpm and extract it somewhere. But where does it go? Thanks. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet visudo/ sudoers help
Hi,
I am trying to get puppet going on CentOS 6.3 and I got it installed and
running. I want to create good manifests for basic stuff. I know I will learn
more as I go but I am new to programming in general and puppet code. I have
puppet master install on 1 cloud server and a client test puppet on another
cloud server. I was able to run this code correctly. Now I want to make it
better.
Here is what I have so far for my Push to add users to my nodes.
site.pp: (I know its short lol)
node 'puppet-client' {
import classes/adduser.pp
}
adduser.pp located in /etc/puppet/manifests/classes/
define custom_user($passwd) {
user { ${name}:
ensure = present,
password = $passwd,
shell = /bin/bash,
managehome = true,
}
}
custom_user {
anthony:
passwd = 'Removed real hash here',
}
custom_user {
admin:
passwd = 'Hash for password gone',
}
custom_user {
luca:
passwd = 'My Password Hash Here',
}
So I am testing on a test-only server till I get the hang of it. So I have many
cloud servers and need to be able to add my admin users. I need help now to
modify /etc/sudoers or visudo and add these people to the doc with ALL=(ALL)
ALL
Please help me. I know I need to add a template and also a module of my own. I
mainly need help with code and learning to build off this for future system
changes. Please help me keep this simple and dumb-down lol. FYI - After this I
want to start on Apache and editing the config and setting up new servers from
an image. This is more practical and important to start with.
Thanks all.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/k7r-BpgI4s4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Agent on Windows
Hi , I am trying to run puppet agent on windows. The Master is running on Linux RHEL6.2. Puppet Version : 2.7.12. The puppet agent service starts properly and the client is able to fetch its catalouge evry 30 mins. My requirement is to reduce this interval to 2 mins. I tried changing the puppet.conf and restarted the service on the agent (via start-services.msc). But somehow this does not work for me. Still the client continues to fetch the catalogue at default time(30 mins). puppet.conf: [agent] server=puppet pluginsync=true report=true runinterval=60 listen=true certname=hawkeye.kodiak-internal.com tags=job-schedular please let me know if i am missing something. regards Neemish -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] issues with puppetdoc and missing symlink
I have a module with its files/ directory symlinked to a SVN checkout outside of the module path (specifically, to /shared_svn). (explanation below) in a few places within that directory structure, there are some dead symlinks. When I run puppetdoc on my modules and manifests, it dies with Could not generate documentation: No such file or directory because the file it's looking for is a symlink to a non-existent file. I know that the actual error is being generated in rdoc itself, specifically an Errno::ENOENT (no such file or directory) in rdoc.rb (for 1.8.7-p299, on line 177). Is there any way to get puppetdoc to ignore a specified path, or paths? Aside from patching puppetdoc itself, can anyone think of a way to work around this? Anything better than doing a second checkout of my configs without the offending SVN directory and running puppetdoc against that? Thanks, Jason PS - The reason for this is a bit of a pain, but it's a set of configuration files which are managed by puppet on new machines, and managed via a cron'ed svn update on older machines. The symlinks are for the older machines, and refer to local paths on them... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: thoughts on puppet 2.7 vs 3.0
On 08/29/2012 07:34 PM, Jason Antman wrote: but given the way things work around here, and that puppet is really a lower-level project (i.e. experimentation, failure, and bugs aren't tolerated well because we only have management support for the end result, not puppet itself) I'll I don't see why the fuss around it, even if puppet itself breaks, it shouldn't affect anything else on the system. Also, you should consider having dev/test environments if your management is so itchy :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Agent on Windows
Hi Nimish, On Wed, Aug 29, 2012 at 10:52 AM, Nimish Vidyarthi nimish.v...@gmail.com wrote: I tried changing the puppet.conf Likely the file you are editing is not the same one that the service is looking at. Since the puppet agent service runs under the LocalSystem account, make sure you are editing the puppet.conf within the CommonAppData directory[1]. Also follow these directions[2] for starting a command prompt (running as an administrator) and run `puppet agent --configprint runinterval` But somehow this does not work for me. Still the client continues to fetch the catalogue at default time(30 mins). puppet.conf: [agent] server=puppet pluginsync=true report=true runinterval=60 This says to run every 60 seconds (not 2 mins). See[3] listen=true certname=hawkeye.kodiak-internal.com tags=job-schedular Josh [1] http://docs.puppetlabs.com/windows/installing.html#data-directory [2] http://docs.puppetlabs.com/windows/running.html#running-other-puppet-tasks [3] http://docs.puppetlabs.com/references/latest/configuration.html#runinterval -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Agent on Windows
Yes i know i was trying out things to make it work. it does not work for 60 sec also. Ok i fetched the values from puppet config print all | find config. the puppet.conf is showing to be correct( as the file i changed) But the runinterval is showing as 1800. I presume this is the issue , how can i change this time setting. and why it is not being read from puppet.conf Regards Neemish On Wed, Aug 29, 2012 at 11:16 AM, Josh Cooper j...@puppetlabs.com wrote: Hi Nimish, On Wed, Aug 29, 2012 at 10:52 AM, Nimish Vidyarthi nimish.v...@gmail.com wrote: I tried changing the puppet.conf Likely the file you are editing is not the same one that the service is looking at. Since the puppet agent service runs under the LocalSystem account, make sure you are editing the puppet.conf within the CommonAppData directory[1]. Also follow these directions[2] for starting a command prompt (running as an administrator) and run `puppet agent --configprint runinterval` But somehow this does not work for me. Still the client continues to fetch the catalogue at default time(30 mins). puppet.conf: [agent] server=puppet pluginsync=true report=true runinterval=60 This says to run every 60 seconds (not 2 mins). See[3] listen=true certname=hawkeye.kodiak-internal.com tags=job-schedular Josh [1] http://docs.puppetlabs.com/windows/installing.html#data-directory [2] http://docs.puppetlabs.com/windows/running.html#running-other-puppet-tasks [3] http://docs.puppetlabs.com/references/latest/configuration.html#runinterval -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Managing Eclipse with Puppet
On 2012-29-08 16:04, Henrik Lindberg wrote: To install additional plugins into Eclipse, you want to use the p2 director application. It is embedded inside the Eclipse IDE itself so once the IDE is unzipped and Java is installed, it is possible to run the director. The director app can install new things, update, and uninstall. There is also a separately packaged smaller headless p2 director available for download. (This director is often used in headless/CI builds). The main complications regarding Eclipse installations is if you install it in one of the shared modes. And if you are behind a proxy, you probably need to read this as well: http://wiki.eclipse.org/Hudson#Configuring_a_proxy_for_the_p2_director - henrik -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppetlabs-stdlib
On Wednesday, August 29, 2012 11:58:13 AM UTC-5, Douglas wrote: I'm confused about this... https://github.com/puppetlabs/puppetlabs-stdlib/ I see a lot of functions there that are the same as the ones that come standard with puppet. If I create a module and dump this stuff in there, what happens to the existing stuff? How does puppet know which one to use? That's odd. I don't see *anything* in there that comes standard with Puppet. Would you care to give some examples? Maybe I'm just missing the obvious. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/dTHHvPBQFwMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Don't touch non-default config files
On Wednesday, August 29, 2012 9:57:13 AM UTC-5, Jones wrote: If it's default it should use the puppet version... but if someone changed it puppet should do nothing. That's the little issue :/ It sounds like you want Puppet to manage the file content under some circumstances, but not under others. If that's so, then how do you expect Puppet to discern which case applies? How would you determine that manually? John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Ua3LwUasd-MJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppetlabs-stdlib
Really? From the function reference at: http://docs.puppetlabs.com/references/latest/function.html Common ones seem to be create_resources, crit, defined, err, extlookup, fail, file and so on. Doug. On Wed, Aug 29, 2012 at 11:57 AM, jcbollinger john.bollin...@stjude.org wrote: On Wednesday, August 29, 2012 11:58:13 AM UTC-5, Douglas wrote: I'm confused about this... https://github.com/puppetlabs/puppetlabs-stdlib/ I see a lot of functions there that are the same as the ones that come standard with puppet. If I create a module and dump this stuff in there, what happens to the existing stuff? How does puppet know which one to use? That's odd. I don't see anything in there that comes standard with Puppet. Would you care to give some examples? Maybe I'm just missing the obvious. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/dTHHvPBQFwMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garst...@gmail.com Cell: +1-805-340-5627 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppetlabs-stdlib
- Original Message - From: Douglas Garstang doug.garst...@gmail.com To: puppet-users@googlegroups.com Sent: Wednesday, August 29, 2012 8:20:19 PM Subject: Re: [Puppet Users] Re: puppetlabs-stdlib Really? From the function reference at: http://docs.puppetlabs.com/references/latest/function.html Common ones seem to be create_resources, crit, defined, err, extlookup, fail, file and so on. none of the ones you mentioned are also in stdlib: https://github.com/puppetlabs/puppetlabs-stdlib/tree/master/lib/puppet/parser/functions -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppetlabs-stdlib
Hi, For some reason these are in README.markdown, perhaps a copy-paste mistake. Look inside the directory :) KW On Wednesday, August 29, 2012 5:58:13 PM UTC+1, Douglas wrote: I'm confused about this... https://github.com/puppetlabs/puppetlabs-stdlib/ I see a lot of functions there that are the same as the ones that come standard with puppet. If I create a module and dump this stuff in there, what happens to the existing stuff? How does puppet know which one to use? Doug -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WQXlCyrEMoQJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?
My puppet has been created in isolation on an island at top of scotland over a period of 2 weeks nonstop working on her mismatched outfit. sure youve probwho hsn't . Flattery will get u know where..no.Know we're he're..wh'at i'd on't knowdumf... dumf humfrey'yes m'lady.why do I love you so'.HumPhrey... YesM'lady. remember w is an upside down vivisection h is r 1 leaning again movemenf ..espanyolrythme and movemenf... what ya gonna do about the below bell .ow...!! stay team ent you wrote it its your scrip.crypt.whose hose hh .Mortgage coming to a show home near lend an ear...Job coming to a show you how Billed the perfect invoice guaranteed to be presentable F9, Puppet, the honor you dont want to be without...Michele xX On Wednesday, August 15, 2012 3:41:32 PM UTC+1, Jason Antman wrote: I'm in the process of building out a new puppet master and pulling our existing/legacy infrastructure into Puppet control for the basic system-level stuff (mail, syslog, sudo, ssh, etc.). Unfortunately, the directive from on high is that all of our hosts need to be managed by the same system. That list is about 95% RHEL/Cent 5 or 6, but there's a few RHEL4 and SLES9 machines on the must have list. As upgrades are very unlikely, I'd like to be on the newest version possible - ideally, 2.7.12+ on the master so I can leverage puppetDB. Is anyone out there running new-ish puppet (2.7, or else 2.6) on such ancient beasts? If so, can anyone point me at sources for the packages, and dependencies? Or perhaps have spec files to share? I'd like to say I can spend the time to build and test puppet and all the dependencies, but alas, that is very far from the case. Thanks for any assistance, Jason PS - If you happen to be a competent generalist Linux admin in the Boston, MA or Atlanta, GA area, feel free pass along your resume... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/0DM356VV6JYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet-Dashboard nodes showing up as unreported
Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch2.7.19-1.el6 SERVER: -bash-4.1$ cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl [master] reports = store, http reporturl = http://us3sm2ppt001.comp.prod.local:3000/reports/upload [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig certname = us3sm2ppt001.comp.prod.local server = us3sm2ppt001.comp.prod.local report = true AGENT -bash-4.1$ cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig server = us3sm2ppt001.comp.prod.local certname = us3sm2nn010r07.comp.prod.local report = true I am uncertain about where the master should be configured to send reports to. reports/upload doesn't seem to exist and I just followed the default location in the documentation. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/xNNacEjU660J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?
Who's got the ban hammer? :P On Wed, Aug 29, 2012 at 3:44 PM, shell Nor norenmich...@gmail.com wrote: My puppet has been created in isolation on an island at top of scotland over a period of 2 weeks nonstop working on her mismatched outfit. sure youve probwho hsn't . Flattery will get u know where..no.Know we're he're..wh'at i'd on't knowdumf... dumf humfrey'yes m'lady.why do I love you so'.HumPhrey... YesM'lady. remember w is an upside down vivisection h is r 1 leaning again movemenf ..espanyolrythme and movemenf... what ya gonna do about the below bell .ow...!! stay team ent you wrote it its your scrip.crypt.whose hose hh .Mortgage coming to a show home near lend an ear...Job coming to a show you how Billed the perfect invoice guaranteed to be presentable F9, Puppet, the honor you dont want to be without...Michele xX On Wednesday, August 15, 2012 3:41:32 PM UTC+1, Jason Antman wrote: I'm in the process of building out a new puppet master and pulling our existing/legacy infrastructure into Puppet control for the basic system-level stuff (mail, syslog, sudo, ssh, etc.). Unfortunately, the directive from on high is that all of our hosts need to be managed by the same system. That list is about 95% RHEL/Cent 5 or 6, but there's a few RHEL4 and SLES9 machines on the must have list. As upgrades are very unlikely, I'd like to be on the newest version possible - ideally, 2.7.12+ on the master so I can leverage puppetDB. Is anyone out there running new-ish puppet (2.7, or else 2.6) on such ancient beasts? If so, can anyone point me at sources for the packages, and dependencies? Or perhaps have spec files to share? I'd like to say I can spend the time to build and test puppet and all the dependencies, but alas, that is very far from the case. Thanks for any assistance, Jason PS - If you happen to be a competent generalist Linux admin in the Boston, MA or Atlanta, GA area, feel free pass along your resume... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/0DM356VV6JYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet visudo/ sudoers help
First suggestion:
Use a group name ( like wheel ) and declare the sudo privileges to the group.
Then all you need do is add that group in the groups parameter for puppet
type user.
On Aug 29, 2012, at 11:31 AM, Tony Caffe wrote:
Hi,
I am trying to get puppet going on CentOS 6.3 and I got it installed and
running. I want to create good manifests for basic stuff. I know I will learn
more as I go but I am new to programming in general and puppet code. I have
puppet master install on 1 cloud server and a client test puppet on another
cloud server. I was able to run this code correctly. Now I want to make it
better.
Here is what I have so far for my Push to add users to my nodes.
site.pp: (I know its short lol)
node 'puppet-client' {
import classes/adduser.pp
}
adduser.pp located in /etc/puppet/manifests/classes/
define custom_user($passwd) {
user { ${name}:
ensure = present,
password = $passwd,
shell = /bin/bash,
managehome = true,
}
}
custom_user {
anthony:
passwd = 'Removed real hash here',
}
custom_user {
admin:
passwd = 'Hash for password gone',
}
custom_user {
luca:
passwd = 'My Password Hash Here',
}
So I am testing on a test-only server till I get the hang of it. So I have
many cloud servers and need to be able to add my admin users. I need help
now to modify /etc/sudoers or visudo and add these people to the doc with
ALL=(ALL) ALL
Please help me. I know I need to add a template and also a module of my own.
I mainly need help with code and learning to build off this for future system
changes. Please help me keep this simple and dumb-down lol. FYI - After this
I want to start on Apache and editing the config and setting up new servers
from an image. This is more practical and important to start with.
Thanks all.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/k7r-BpgI4s4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: puppetlabs-stdlib
On Wed, Aug 29, 2012 at 12:54 PM, Krzysztof Wilczynski krzysztof.wilczyn...@linux.com wrote: Hi, For some reason these are in README.markdown, perhaps a copy-paste mistake. Look inside the directory :) Ah this was my fault. I thought I filtered out the function documentation for core functions but I clearly didn't. -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Managing Eclipse with Puppet
Thanks! Will give it a shot and let you know how it works. On Wednesday, August 29, 2012 1:25:17 PM UTC-5, Henrik Lindberg wrote: On 2012-29-08 16:04, Henrik Lindberg wrote: To install additional plugins into Eclipse, you want to use the p2 director application. It is embedded inside the Eclipse IDE itself so once the IDE is unzipped and Java is installed, it is possible to run the director. The director app can install new things, update, and uninstall. There is also a separately packaged smaller headless p2 director available for download. (This director is often used in headless/CI builds). The main complications regarding Eclipse installations is if you install it in one of the shared modes. And if you are behind a proxy, you probably need to read this as well: http://wiki.eclipse.org/Hudson#Configuring_a_proxy_for_the_p2_director - henrik -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/rZCc2ZQD8ywJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppetlabs-stdlib
On Wednesday, August 29, 2012 2:54:48 PM UTC-5, Krzysztof Wilczynski wrote: Hi, For some reason these are in README.markdown, perhaps a copy-paste mistake. Look inside the directory :) Ah, that explains it. Silly me, I ignored the README and went straight to the actual sources :) John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/bJ-MYeUb9JQJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?
About to unsubscribe this account as it was set to no email and looks like a spam account. On Wed, Aug 29, 2012 at 1:25 PM, Sam Kottler s...@kottlerdevelopment.com wrote: Who's got the ban hammer? :P On Wed, Aug 29, 2012 at 3:44 PM, shell Nor norenmich...@gmail.com wrote: My puppet has been created in isolation on an island at top of scotland over a period of 2 weeks nonstop working on her mismatched outfit. sure youve probwho hsn't . Flattery will get u know where..no.Know we're he're..wh'at i'd on't knowdumf... dumf humfrey'yes m'lady.why do I love you so'.HumPhrey... YesM'lady. remember w is an upside down vivisection h is r 1 leaning again movemenf ..espanyolrythme and movemenf... what ya gonna do about the below bell .ow...!! stay team ent you wrote it its your scrip.crypt.whose hose hh .Mortgage coming to a show home near lend an ear...Job coming to a show you how Billed the perfect invoice guaranteed to be presentable F9, Puppet, the honor you dont want to be without...Michele xX On Wednesday, August 15, 2012 3:41:32 PM UTC+1, Jason Antman wrote: I'm in the process of building out a new puppet master and pulling our existing/legacy infrastructure into Puppet control for the basic system-level stuff (mail, syslog, sudo, ssh, etc.). Unfortunately, the directive from on high is that all of our hosts need to be managed by the same system. That list is about 95% RHEL/Cent 5 or 6, but there's a few RHEL4 and SLES9 machines on the must have list. As upgrades are very unlikely, I'd like to be on the newest version possible - ideally, 2.7.12+ on the master so I can leverage puppetDB. Is anyone out there running new-ish puppet (2.7, or else 2.6) on such ancient beasts? If so, can anyone point me at sources for the packages, and dependencies? Or perhaps have spec files to share? I'd like to say I can spend the time to build and test puppet and all the dependencies, but alas, that is very far from the case. Thanks for any assistance, Jason PS - If you happen to be a competent generalist Linux admin in the Boston, MA or Atlanta, GA area, feel free pass along your resume... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/0DM356VV6JYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Come to PuppetConf 2012! Sep 27/28 - San Francisco http://puppetconf.com/ Nigel Kersten | http://puppetlabs.com | @nigelkersten Schedule Meetings at: http://tungle.me/nigelkersten -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: troubleshooting resource collection
On Wednesday, August 29, 2012 9:34:24 AM UTC-5, Frank Van Damme wrote:
On Wednesday, August 29, 2012 4:14:27 PM UTC+2, jcbollinger wrote:
On Wednesday, August 29, 2012 6:25:35 AM UTC-5, Frank Van Damme wrote:
Hi,
I'm new to Puppet. And I'm trying out an ssh module:
https://github.com/saz/puppet-ssh.
It collects ssh keys like this:
class ssh::knownhosts {
Sshkey | | {
ensure = present,
}
notify{knownhosts class: $fqdn $hostname $ipaddress :}
}
I can see it echoes the host key of the host the puppet agent runs on.
But the /etc/ssh/ssh_known_hosts file isn't actually written - I can add an
sshkey resource manually in a manifest somewhere and then puppet does
write the file though.
I reckon when compiling the catalog, Puppet doesn't actually use the
collected resource to include in another host's configuration. But why not?
The code you present collects all available exported resources of type
'sshkey', but it does not declare any such resources. If you're not
managing your nodes' ssh host keys, then Puppet knows nothing about them.
For this to work, therefore, in addition to the above your manifest should
contain something like
@@sshkey { ${hostname}:
key = 'the-key',
type = 'probably-dsa-or-rsa'
}
John
There is, in another class (and as I wrote, the collection sort of works
because I see the output of the 'notify{knownhosts class: $fqdn $hostname
$ipaddress :}' above)
That you see the output of your 'notify' proves only that class
'ssh::knownhosts' is included in the target node's catalog. It therefore
compiled successfully, but that says nothing about what resources were
actually collected.
If nothing is showing up in /etc/ssh/ssh_known_hosts, then that almost
certainly means that no Sshkey resources are being collected. The most
likely explanations then are that your class 'ssh:hostkeys' is not being
included in your nodes' catalogs, or else that you do not have
[thin]storeconfigs configured.
If the target node's key is showing up but no other nodes' are, then the
most likely explanations are that your other nodes are not getting class
'ssh::hostkeys' in their catalogs, that they have not checked in with the
Puppetmaster since that class was assigned to them, or that you do not have
[thin]storeconfigs configured.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/-ZWQiLll4nkJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet visudo/ sudoers help
I understand but that is not what I asked for help. I would like some help
on making or writing the code needed to add users to visudo.
On Wednesday, August 29, 2012 1:34:35 PM UTC-7, Ygor wrote:
First suggestion:
Use a group name ( like wheel ) and declare the sudo privileges to the
group.
Then all you need do is add that group in the groups parameter for
puppet type user.
On Aug 29, 2012, at 11:31 AM, Tony Caffe wrote:
Hi,
I am trying to get puppet going on CentOS 6.3 and I got it installed and
running. I want to create good manifests for basic stuff. I know I will
learn more as I go but I am new to programming in general and puppet code.
I have puppet master install on 1 cloud server and a client test puppet on
another cloud server. I was able to run this code correctly. Now I want to
make it better.
Here is what I have so far for my Push to add users to my nodes.
site.pp: (I know its short lol)
node 'puppet-client' {
import classes/adduser.pp
}
adduser.pp located in /etc/puppet/manifests/classes/
define custom_user($passwd) {
user { ${name}:
ensure = present,
password = $passwd,
shell = /bin/bash,
managehome = true,
}
}
custom_user {
anthony:
passwd = 'Removed real hash here',
}
custom_user {
admin:
passwd = 'Hash for password gone',
}
custom_user {
luca:
passwd = 'My Password Hash Here',
}
So I am testing on a test-only server till I get the hang of it. So I
have many cloud servers and need to be able to add my admin users. I need
help now to modify /etc/sudoers or visudo and add these people to the doc
with ALL=(ALL) ALL
Please help me. I know I need to add a template and also a module of my
own. I mainly need help with code and learning to build off this for future
system changes. Please help me keep this simple and dumb-down lol. FYI -
After this I want to start on Apache and editing the config and setting up
new servers from an image. This is more practical and important to start
with.
Thanks all.
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/k7r-BpgI4s4J.
To post to this group, send email to
puppet...@googlegroups.comjavascript:.
To unsubscribe from this group, send email to
puppet-users...@googlegroups.com javascript:.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/ebP58zFazv0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet visudo/ sudoers help
You learn from use one of these:
http://forge.puppetlabs.com/modules?q=sudo
On Wed, Aug 29, 2012 at 02:13:34PM -0700, Tony Caffe wrote:
I understand but that is not what I asked for help. I would like some help
on making or writing the code needed to add users to visudo.
On Wednesday, August 29, 2012 1:34:35 PM UTC-7, Ygor wrote:
First suggestion:
Use a group name ( like wheel ) and declare the sudo privileges to the
group.
Then all you need do is add that group in the groups parameter for
puppet type user.
On Aug 29, 2012, at 11:31 AM, Tony Caffe wrote:
Hi,
I am trying to get puppet going on CentOS 6.3 and I got it installed
and running. I want to create good manifests for basic stuff. I know I
will learn more as I go but I am new to programming in general and
puppet code. I have puppet master install on 1 cloud server and a client
test puppet on another cloud server. I was able to run this code
correctly. Now I want to make it better.
Here is what I have so far for my Push to add users to my nodes.
site.pp: (I know its short lol)
node 'puppet-client' {
import classes/adduser.pp
}
adduser.pp located in /etc/puppet/manifests/classes/
define custom_user($passwd) {
user { ${name}:
ensure = present,
password = $passwd,
shell = /bin/bash,
managehome = true,
}
}
custom_user {
anthony:
passwd = 'Removed real hash here',
}
custom_user {
admin:
passwd = 'Hash for password gone',
}
custom_user {
luca:
passwd = 'My Password Hash Here',
}
So I am testing on a test-only server till I get the hang of it. So I
have many cloud servers and need to be able to add my admin users. I
need help now to modify /etc/sudoers or visudo and add these people to
the doc with ALL=(ALL) ALL
Please help me. I know I need to add a template and also a module of
my own. I mainly need help with code and learning to build off this for
future system changes. Please help me keep this simple and dumb-down
lol. FYI - After this I want to start on Apache and editing the config
and setting up new servers from an image. This is more practical and
important to start with.
Thanks all.
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To view this discussion on the web visit
[1]https://groups.google.com/d/msg/puppet-users/-/k7r-BpgI4s4J.
To post to this group, send email to [2]puppet...@googlegroups.com.
To unsubscribe from this group, send email to
[3]puppet-users...@googlegroups.com.
For more options, visit this group at
[4]http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
[5]https://groups.google.com/d/msg/puppet-users/-/ebP58zFazv0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
References
Visible links
1. https://groups.google.com/d/msg/puppet-users/-/k7r-BpgI4s4J
2. javascript:
3. javascript:
4. http://groups.google.com/group/puppet-users?hl=en
5. https://groups.google.com/d/msg/puppet-users/-/ebP58zFazv0J
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet visudo/ sudoers help
On 8/29/2012 8:31 AM, Tony Caffe wrote:
Hi,
I am trying to get puppet going on CentOS 6.3 and I got it installed and
running. I want to create good manifests for basic stuff. I know I will learn
more as I go but I am new to programming in general and puppet code. I have
puppet master install on 1 cloud server and a client test puppet on another
cloud server. I was able to run this code correctly. Now I want to make it
better.
Here is what I have so far for my Push to add users to my nodes.
site.pp: (I know its short lol)
node 'puppet-client' {
import classes/adduser.pp
}
adduser.pp located in /etc/puppet/manifests/classes/
define custom_user($passwd) {
user { ${name}:
ensure = present,
password = $passwd,
shell = /bin/bash,
managehome = true,
}
}
custom_user {
anthony:
passwd = 'Removed real hash here',
}
custom_user {
admin:
passwd = 'Hash for password gone',
}
custom_user {
luca:
passwd = 'My Password Hash Here',
}
So I am testing on a test-only server till I get the hang of it. So I have many
cloud servers and need to be able to add my admin users. I need help now to
modify /etc/sudoers or visudo and add these people to the doc with ALL=(ALL)
ALL
Please help me. I know I need to add a template and also a module of my own. I
mainly need help with code and learning to build off this for future system
changes. Please help me keep this simple and dumb-down lol. FYI - After this I
want to start on Apache and editing the config and setting up new servers from
an image. This is more practical and important to start with.
Your sudo should be new enough to support /etc/sudoers.d/ which means
you can just drop a file per user into that dir. Make Puppet manage the
whole dir and purge anything it doesn't recognize and you're all set.
Ramin
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet visudo/ sudoers help
Would I still need to write ruby code? I dont know ruby or really any other programming language. So I would create a duplicate of the sudoers file in /etc/sudoers.d/ that adds a user to it and it will work? I am not to sure of how sudoers.d works. Thanks. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/be_1FNEoI8kJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet-Dashboard nodes showing up as unreported
Adam, in dashboard's upper-left corner, do you see any pending tasks listed in the Background Tasks section? If so, then you simply need to start the delayed job workers (http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#starting-and-managing-delayed-job-workers) and they will start processing the backlogged puppet reports. -- Peter Bukowinski On Aug 29, 2012, at 1:19 PM, Adam Hamner adamhamne...@gmail.com wrote: Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch2.7.19-1.el6 SERVER: -bash-4.1$ cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl [master] reports = store, http reporturl = http://us3sm2ppt001.comp.prod.local:3000/reports/upload [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig certname = us3sm2ppt001.comp.prod.local server = us3sm2ppt001.comp.prod.local report = true AGENT -bash-4.1$ cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig server = us3sm2ppt001.comp.prod.local certname = us3sm2nn010r07.comp.prod.local report = true I am uncertain about where the master should be configured to send reports to. reports/upload doesn't seem to exist and I just followed the default location in the documentation. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/xNNacEjU660J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet visudo/ sudoers help
In regard to: Re: [Puppet Users] Puppet visudo/ sudoers help, Tony Caffe...:
I understand but that is not what I asked for help. I would like some help
on making or writing the code needed to add users to visudo.
$ cat puppet/modules/sudo/manifests/config.pp
define sudo::config($content='', $source='') {
case $content {
'': {
file {/etc/sudoers.d/${name}:
ensure = file,
owner = 'root',
group = 'root',
mode = '0440',
source = $source,
}
}
default: {
file {/etc/sudoers.d/${name}:
ensure = file,
owner = 'root',
group = 'root',
mode= '0440',
content = $content,
}
}
}
}
# vim:sm:ts=2:expandtab
Example usage for source:
sudo::config{ 'networker-jukebox':
source = 'puppet:///networker/networker_jb_sudoers',
}
Example usage for contents:
sudo::config{ 'myuser':
content = myuser ALL = (ALL) ALL\n
}
Note that both RHEL 5.x and 6.x have a sudo that supports the include
mechanism, but only RHEL 6.x ships with an /etc/sudoers.d and an
/etc/sudoers that has the include /etc/sudoers.d/* pre-populated.
Since both flavors support it, we just have our sudo init.pp make sure
the directory is present and make certain that the /etc/sudoers has the
necessary include statement. From then on, it's just puppet dropping
files into /etc/sudoers.d via the sudo::config() define.
The bad part about our current implementation is that there's no syntax
checking for the contents/source, so a bad entry can sneak in and cause
sudo to completely not work until it's fixed. There are ways around this
but it's more complicated than we felt like getting for now.
If you need to support systems where sudo is old enough that include
isn't even an option, then I highly recommend you look at the concat
module, and build up your sudoers file from file fragments.
Another option for older sudo versions that don't support including
fragments is using file_line from puppetlabs-stdlib.
Tim
On Wednesday, August 29, 2012 1:34:35 PM UTC-7, Ygor wrote:
First suggestion:
Use a group name ( like wheel ) and declare the sudo privileges to the
group.
Then all you need do is add that group in the groups parameter for
puppet type user.
On Aug 29, 2012, at 11:31 AM, Tony Caffe wrote:
Hi,
I am trying to get puppet going on CentOS 6.3 and I got it installed and
running. I want to create good manifests for basic stuff. I know I will
learn more as I go but I am new to programming in general and puppet code.
I have puppet master install on 1 cloud server and a client test puppet on
another cloud server. I was able to run this code correctly. Now I want to
make it better.
Here is what I have so far for my Push to add users to my nodes.
site.pp: (I know its short lol)
node 'puppet-client' {
import classes/adduser.pp
}
adduser.pp located in /etc/puppet/manifests/classes/
define custom_user($passwd) {
user { ${name}:
ensure = present,
password = $passwd,
shell = /bin/bash,
managehome = true,
}
}
custom_user {
anthony:
passwd = 'Removed real hash here',
}
custom_user {
admin:
passwd = 'Hash for password gone',
}
custom_user {
luca:
passwd = 'My Password Hash Here',
}
So I am testing on a test-only server till I get the hang of it. So I
have many cloud servers and need to be able to add my admin users. I need
help now to modify /etc/sudoers or visudo and add these people to the doc
with ALL=(ALL) ALL
Please help me. I know I need to add a template and also a module of my
own. I mainly need help with code and learning to build off this for future
system changes. Please help me keep this simple and dumb-down lol. FYI -
After this I want to start on Apache and editing the config and setting up
new servers from an image. This is more practical and important to start
with.
Thanks all.
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/k7r-BpgI4s4J.
To post to this group, send email to puppet...@googlegroups.comjavascript:.
To unsubscribe from this group, send email to
puppet-users...@googlegroups.com javascript:.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
Re: [Puppet Users] Puppet visudo/ sudoers help
Thanks. I used this:
file {'puppet_sudo':
ensure = present,
path = '/tmp/puppet_sudo',
source = 'puppet:///files/puppet_sudo',
owner = 'root',
group = 'root',
mode = 0440,
}
file {'move_puppet_sudo':
ensure = present,
path = '/etc/sudoers.d/',
source = '/tmp/puppet_sudo',
owner = 'root',
group = 'root',
mode = 0440,
require= file['puppet_sudo'],
}
but My Puppet master is 6.3 and all my puppet clients are all 5.8. 5.8
doesnt have the line
#includedir /etc/sudoers.d
nor does it have a DIRECTORY /etc/sudoers.d/, just a file called
/etc/sudoers.d
Any Idea about that? I am avoiding writing code since I dont know how.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/G3ZQJhWgM1QJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?
Sam Kottler wrote: Who's got the ban hammer? :P The address appears to be now banned. Apologies for the spam. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?
Thanks! -Sam On Wed, Aug 29, 2012 at 7:10 PM, James Turnbull ja...@puppetlabs.comwrote: Sam Kottler wrote: Who's got the ban hammer? :P The address appears to be now banned. Apologies for the spam. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] thoughts on puppet 2.7 vs 3.0
On 30 August 2012 00:52, Jason Antman ja...@jasonantman.com wrote: For anyone in the know, given this situation, would you recommend building on puppet 2.7.18, or trying to draw things out as much as possible and wait for a stable 3.x release? Does anyone have any general idea of when one might be forthcoming (weeks? months? next year?) I'm in a similar position with 1000 hosts, 100 odd modules, 2K+ resources managed by puppet on 2.6.x. Given the deprecation warnings, and changes in 2.7, then 3.x, I'm using 2.7 both as a stepping stone to 3 (code cleanup) and added functionality (puppet DB) Seeing how 2.7 wasn't suitable *for me* until 2.7.10 due to some specific bugs, I think you should move to 2.7 unless you have a simple setup and prepared to wait for 3 John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] thoughts on puppet 2.7 vs 3.0
From what I have seen there is a big difference between 2.6+ and 3.0+. I would be setting up a completely separate environment with 2.7 to test if your code works. 2.7 apparently let you know which things will stop working in 3.0 so it will be a better idea to use that in the dev environment and iron out the obvious things first and then switch to 3.0+ There will likely be a bunch of things you will need to fix with your code before you switch your environment to 3.0 so by the time it's stable enough you will have your code ported and ready to roll out. I am currently running 2.7+ and plan on setting up my dev environment to 3.0 once i finish a few more important modules i need to write for a big project. (yes i write most of my modules from scratch) Just my opinion but it seems like the best way to make sure everything works and avoid breaking your production environment and spending way too long fixing it. Hope that helps. Pete. On 30 August 2012 09:16, John Warburton jwarbur...@gmail.com wrote: On 30 August 2012 00:52, Jason Antman ja...@jasonantman.com wrote: For anyone in the know, given this situation, would you recommend building on puppet 2.7.18, or trying to draw things out as much as possible and wait for a stable 3.x release? Does anyone have any general idea of when one might be forthcoming (weeks? months? next year?) I'm in a similar position with 1000 hosts, 100 odd modules, 2K+ resources managed by puppet on 2.6.x. Given the deprecation warnings, and changes in 2.7, then 3.x, I'm using 2.7 both as a stepping stone to 3 (code cleanup) and added functionality (puppet DB) Seeing how 2.7 wasn't suitable *for me* until 2.7.10 due to some specific bugs, I think you should move to 2.7 unless you have a simple setup and prepared to wait for 3 John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet-3.0.0-rc5 Available
Puppet 3.0.0-rc5 is a feature release candidate for the 3.x series of Puppet. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc5.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available at http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.0.rc5.gem or by using `gem install --pre puppet` Mac packages are available at http://downloads.puppetlabs.com/mac/puppet-3.0.0-rc5.dmg Windows packages are available at http://downloads.puppetlabs.com/windows/puppet-3.0.0-rc5.msi See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.0-rc5: http://projects.puppetlabs.com/projects/puppet/ Puppet 3.0.0-rc5 (Telly) Release Notes = Numbers in parentheses like `(#7788)` indicate a Redmine ticket at http://projects.puppetlabs.com/issues/7788 Notation like `(puppet/pull/998)` indicate a github pull request at https://github.com/puppetlabs/puppet/pull/998 # Summary of Changes This is not an exhaustive summary, but rather an editorialized list of the biggest changes. See the Git changelog for the full monty. ## Cool New Stuff * Performance Improvements - substantial improvements to performance, particularly around catalog compilation. Agent supports JSON serialization for catalog cache, which can be dramatically faster for large catalogs (#16058, #2892) * Data Bindings - hiera will be automatically consulted for values of parameterized classes so you don't need the parser functions. (#11608) * Improved OS/Platform Support - Full Ruby 1.9 support; vastly improved Windows package support; yumrepo now supports ssl options (#3324); better upstart support; better Solaris zone, package and service support; * Loading Plugins from Rubygems - you can now install and use puppet extension code (faces, types, providers) via rubygems. (#7788) * Server Auto-Discovery - Puppet agents can use SRV records in DNS to find CA, master, report, and file servers (#3669) # DSL/Config Changes * Variable Scoping - Dynamic scoping has been removed. http://docs.puppetlabs.com/guides/scope_and_puppet.html * Auth.conf differentiates between names and IPs - There's a new `allow_ip` keyword in auth.conf if you want to permit IP addresses. (PR991) * `unless` is available as a synonym for `if !` (#7762) * Pluginsync now defaults to true - Yep, it's true. (#5521) * Updated `config.ru` syntax -- When running the master under Rack, make sure you update your config.ru to follow the example from ext/rack/files/config.ru in the source distribution. (#15337) # Changed Code Behaviour * External Node Classifier and Environments - If there's a conflict between the environment requested by a client and what's set in the external node classifier, the ENC wins. (#3910) * When running puppet as root, the system-wide `confdir` and `vardir` settings will be used. When running as a non-root user, `confdir` will be `~/.puppet/` and `vardir` will be `~/.puppet/var`. You can override these on the command line or via `config.ru` for rack setups. (#16137, PR#1080) ## Changelog Josh Cooper (3) 88171aa Maint: Use pending block 33bf085 Maint: Make paths absolute on Windows 54acfba (#16137) Delay evaluation of config and var directories Andrew Parker (2) b53e600 (#16137) Tilde expansion should only occur for normal users 43590bd (Maint) Remove trailing whitespace Curtis Ruck (1) c0ff98d (#16137) Ensure HOME is set before attempting ~ expansion Genadi Samokovarov (1) 224d380 Move singleton require to puppet/util/storage.rb Eric Sorenson (1) 605e34d (#15739) Bump report_version since #10064 change its format Rahul (1) d834e76 (#6143) ensure that destroy works for zpools -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Announce: Puppet-3.0.0-rc5 Available
The chkconfig change that was implmented is breaking the puppet service function on Red Hat based systems. http://projects.puppetlabs.com/issues/15797 chkconfig reset looks like it is meant to set the service back to how it was set during initial package installation. Most services are not enabled by default and use a - instead of the actual run levels in their init scripts. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WkObl9pnVcMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: [Puppet-dev] Re: Announce: Puppet-3.0.0-rc5 Available
Ack, thanks for the catch. I can't believe we regressed on a sub-1000 bug number; this exact change was applied in redmine #528 and reverted in March 2007! https://github.com/puppetlabs/puppet/commit/41e1285553870f0b425b88a6209fab8733b421b2 On Aug 29, 2012, at 5:54 PM, Chuck wrote: The chkconfig change that was implmented is breaking the puppet service function on Red Hat based systems. http://projects.puppetlabs.com/issues/15797 chkconfig reset looks like it is meant to set the service back to how it was set during initial package installation. Most services are not enabled by default and use a - instead of the actual run levels in their init scripts. -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/WkObl9pnVcMJ. To post to this group, send email to puppet-...@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en. Eric Sorenson - eric.soren...@puppetlabs.com PuppetConf'12 - 27-28 Sep in SF - http://bit.ly/pcsig12 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Autosign frequency
Hi Puppet Gurus I am running puppet 2.6.16, ruby 1.8.7-p249, on puppet server with passenger on Apache. These are my gems: builder (2.1.2) fastthread (1.0.7) mysql (2.8.1) passenger (2.2.14) rack (1.1.0) rake (0.8.7) We manually manage autosign.conf to allow new builds to continue so certificates can be signed automatically. This has been working well for a couple of years, but I've always wondered what triggers the puppet master to sign the certificate. We can wait 5-10 minutes for a signing request to be fulfilled. We made a change last week to now use short names as the certificate names (not FQDN) and now we're looking closer to 30 minutes for a request to be signed :-( The only correlation I can see in the logs is that just before a request is signed, a new puppetmasterd is spawned by passenger: Aug 28 22:15:09 engnadm010 puppet-master[26047]: [ID 702911 daemon.notice] labcsvr004 has a waiting certificate request Aug 28 22:24:06 engnadm010 puppet-master[26031]: [ID 702911 daemon.notice] Compiled catalog for engnadm010.bfm.com in environment lab in 19.65 seconds Aug 28 22:37:11 engnadm010 puppet-master[26031]: [ID 702911 daemon.notice] labcsvr004 has a waiting certificate request Aug 28 22:39:47 engnadm010 puppet-master[27717]: [ID 702911 daemon.notice] Starting Puppet master version 2.6.16 Aug 28 22:40:52 engnadm010 puppet-master[26047]: [ID 702911 daemon.notice] Signed certificate request for labcsvr004 Here are my passenger Apache config entries: PassengerHighPerformance on PassengerMaxPoolSize 15 PassengerPoolIdleTime 300 PassengerUseGlobalQueue on PassengerStatThrottleRate 120 RackAutoDetect Off RailsAutoDetect Off Is there any way I can speed up things so that puppet signs the request immediately? Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Autosign frequency
How many nodes is your puppetmaster currently servicing? I have one servicing about 700 nodes, splayed over an hour check-in interval, and any new nodes I add (that fall into my autosign subdomain) get signed immediately on their first puppet run. -- Peter Bukowinski On Aug 29, 2012, at 8:50 PM, John Warburton jwarbur...@gmail.com wrote: Hi Puppet Gurus I am running puppet 2.6.16, ruby 1.8.7-p249, on puppet server with passenger on Apache. These are my gems: builder (2.1.2) fastthread (1.0.7) mysql (2.8.1) passenger (2.2.14) rack (1.1.0) rake (0.8.7) We manually manage autosign.conf to allow new builds to continue so certificates can be signed automatically. This has been working well for a couple of years, but I've always wondered what triggers the puppet master to sign the certificate. We can wait 5-10 minutes for a signing request to be fulfilled. We made a change last week to now use short names as the certificate names (not FQDN) and now we're looking closer to 30 minutes for a request to be signed :-( The only correlation I can see in the logs is that just before a request is signed, a new puppetmasterd is spawned by passenger: Aug 28 22:15:09 engnadm010 puppet-master[26047]: [ID 702911 daemon.notice] labcsvr004 has a waiting certificate request Aug 28 22:24:06 engnadm010 puppet-master[26031]: [ID 702911 daemon.notice] Compiled catalog for engnadm010.bfm.com in environment lab in 19.65 seconds Aug 28 22:37:11 engnadm010 puppet-master[26031]: [ID 702911 daemon.notice] labcsvr004 has a waiting certificate request Aug 28 22:39:47 engnadm010 puppet-master[27717]: [ID 702911 daemon.notice] Starting Puppet master version 2.6.16 Aug 28 22:40:52 engnadm010 puppet-master[26047]: [ID 702911 daemon.notice] Signed certificate request for labcsvr004 Here are my passenger Apache config entries: PassengerHighPerformance on PassengerMaxPoolSize 15 PassengerPoolIdleTime 300 PassengerUseGlobalQueue on PassengerStatThrottleRate 120 RackAutoDetect Off RailsAutoDetect Off Is there any way I can speed up things so that puppet signs the request immediately? Thanks John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Autosign frequency
On 30 August 2012 14:03, Peter Bukowinski pmb...@gmail.com wrote: How many nodes is your puppetmaster currently servicing? I have one servicing about 700 nodes, splayed over an hour check-in interval, and any new nodes I add (that fall into my autosign subdomain) get signed immediately on their first puppet run. We run puppet twice daily (6am 6pm splayed over an hour), and most builds are done outside of that time frame so the puppet server is pretty idle as you can see in my example - just one catalog compile to do in between request signing Here's an example of a signing request on an idle server last week before the short name certificates (no correlation to restarting the daemon here...) Aug 23 10:37:43 cornadm010 puppet-master[25783]: [ID 702911 daemon.notice] blkasec001.domain.com has a waiting certificate request Aug 23 10:44:24 cornadm010 puppet-master[25783]: [ID 702911 daemon.notice] Signed certificate request for blkasec001.domain.com Thanks for taking a look John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Debugging Custom Stuff
So... how can I debug ruby code for custom functions? Putting a 'puts' in the ruby script doesn't actually cause anything to go anywhere. Doug -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Uber Frustration with Puppet.
Boy, am I frustrated. I'm about ready to throw puppet out the window
here. I'm trying to configure glusterfs, and you know, it kinda made
sense to separate the data from the manifests, so I went ahead and put
this into a YAML file, which hiera loads...
glusterfs_volumes:
gfsvol01:
volume_name: gfsvol01
master_node: gfs01.us1.xxx.com # Make sure only one node
runs the gluster commands.
nodes:
- name: gfs01.us1.xxx.com
bricks:
- device: /dev/bcvg/disk1
brick_name: /var/bricks/gfsvol01-0
- device: /dev/bcvg/disk2
brick_name: /var/bricks/gfsvol01-1
- name: gfs02.us1.xxx.com
bricks:
- device: /dev/bcvg/disk3
brick_name: /var/bricks/gfsvol01-0
- device: /dev/bcvg/disk4
brick_name: /var/bricks/gfsvol01-1
For the last couple of days I have been dealing with the inadequacies
of puppet in dealing with working with this kind of data structure.
You can't easily iterate through it, and every time you do, you have
to write a new definition that takes an array. The whole thing ends up
turning into a giant complicated mess.
I tried writing some custom functions in ruby that do things like,
return a list of nodes for a volume, or return a list of bricks for a
node, but it really irks me that I have to keep writing ruby scripts
for this (since ruby makes my eyes bleed).
So... what are my options here? Aren't we supposed to strive for
separating the manifest from the data? I could probably get away with
a few definitions that take a set of parameters. However, when the
time comes to say, add a new node to the cluster, we have to modify
the manifest. At one point, I had this working so that all you had to
do was add a node to the yaml file, make ZERO changes to the manifest
file, and after running puppet, it would add the node to the cluster.
It may make my life easier if I flatten the yaml file, but then I'm
changing the data to suit the limitations of the DSL.
At this point, I'm very close to simply sticking with the yaml file,
have puppet push that out to the clients, write some python scripts to
do all the magic (reading the yaml file), and have puppet run those
scripts with Exec {}.
Is proper array/hash iteration ever going to be added to puppet?
Doug.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
