Re: [Puppet Users] Re: Perform action when exported resources change
On 22.07.2013 08:58, George Brown wrote: Hi Sneha, This is for a GPFS (IBM parallel file system) cluster. When a new client is added it needs to be added by an node that is already part of the cluster. I'm trying to automate this through puppet E.g. node80 has just been provisioned After installing the client packages I need to add the node from a server already in the cluster by running the following two commands mmaddnode -N node80 mmchlicense client --accept -N node80 Obviously I only want to have this exec run when a new host is added but I also only want it to execute for the newly added host (I don’t want it to run though nodes01-79 also). Unfortunately I have to run the above commands as it appears GPFS does not perform this config through plain text files. Yes, GPFS is a pain. I've protected those calls by onlyif checks that read the gpfs state whether the node is already added/licensed. It works out pretty well, except that it takes ages to apply a catalog. I'm really thinking about redoing that as a native type with prefetching/pruning. Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Installing MSI failed with errror: The network name cannot be found.
Hi Tinu, On Thu, Jul 25, 2013 at 11:33 PM, tinu tinu.walt...@gmail.com wrote: Hello Josh Here the output from puppet agent --test --debug --trace: ruby 1.8.7 (2012-02-08 patchlevel 358) [i386-mingw32] C:\Program Files (x86)\Puppet Labs\Puppet\binpuppet agent --test --debug --trace ... debug: Package[System Center Operations Manager 2007 R2 Agent](provider=msi): Executing 'msiexec.exe /qn /nore start /i C:\\Install\\MOMAgent.msi INSTALLDIR=C:\Program Files\System Center Operations Manager 2007' ... err: /Stage[main]/Services::Scomagent/Package[System Center Operations Manager 2007 R2 Agent]/ensure: change from absent to present failed: Failed to install: The network name cannot be found. I think you have extra backslashes in the MOMAgent.msi path, which is consistent with the error message The network name cannot be found. msiexec thinks the double backslashes are a UNC path. Make sure you either use single quotes and single backslashes, or if you need to interpolate the string, double quotes with double backslashes, but not single quotes with double backslashes[1]. Josh [1] https://projects.puppetlabs.com/issues/16246 -- Josh Cooper Developer, Puppet Labs *Join us at PuppetConf 2013, August 22-23 in San Francisco - * http://bit.ly/pupconf13* **Register now and take advantage of the Final Countdown discount - save 15%!* -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet, Yum, Cassandra, openjdk and --nodeps
On 30 Jul 2013 18:57, Paul Pham m...@paulpham.net wrote: Do most folks who use puppet not use yum? Or are most people okay with letting puppet install dependencies automagically? Puppet has different package providers and I use the appropriate one depending on what I want it to do. If I want Puppet to just install a package and fail if it's dependencies are not met I use the rpm provider and specify the location of the rpm file. If I want Puppet to install a package with all its dependencies then I use the yum provider (the default) usually with a local repository so I can make local changes - try fpm, pulp and similar tools. Of course there are similar providers for non-RHEL systems. Paul - Keith On Monday, July 29, 2013 10:58:11 AM UTC-7, jcbollinger wrote: On Wednesday, July 24, 2013 4:29:44 PM UTC-5, Paul Pham wrote: Hello, puppet n00b here. Trying to install cassandra via puppet. Works great, only caveat is cassandra (dsc12 package) lists openjdk as a dependency. Ironically enough, the datastax guys themselves recommend using Oracle JRE instead of openjdk, and there is even a bug that prevents cassandra from starting if it's using openjdk. Anyway, I fixed it by adding an exec to my puppet-java module that sets the Oracle JRE runtime as the defaults via alternatives, and it works fine. However, I still end up with two different java runtimes installed which I find to be a bit unclean. The root of the problem to me, though, is that by having puppet install dsc12, I lose visibility into what all those dependencies were that got installed along with it (I didn't realize openjdk was even installing until I started investigating why cassandra wasn't starting). So what I'd prefer to do is add each individual package dependency into my cassandra module itself, thereby explicitly installing only what I intend to install, and nothing else. The only way this works, though, is if I can somehow pass the --nodeps option into yum during puppet apply time. Otherwise, regardless of whether I already installed Oracle JRE, using yum to install dsc12 will automatically install openjdk. How have you guys handled scenarios like this? I tried searching through the topics here for yum nodeps but it seems people found different ways of solving their individual problems rather than sending flags to the yum provider itself. I also noticed this puppet feature request which unfortunately has remained open(?) for 3 years. I've also seen people suggest that nodeps should never be used with yum since the purpose of yum is to handle dependencies... but we also like some of the other features of yum, like being able to pull packages down by name automatically from our yum repo (which we manage in-house). Anyway, any insights would be great! Thanks, The best solution to the immediate problem would be to rebuild the RPM to correct the dependency information. There are even tools available by which you could edit your existing RPM without rebuilding it from scratch. As far as --nodeps goes, I am not aware that yum implements it, or anything similar. I find explicit documentation to the contrary, in fact. If you want to go that direction (very unwise) then you need to use rpm directly. If you use rpm directly, however, (including by explicitly telling Puppet to use the 'rpm' Package provider) then you probably still don't want --nodeps. Instead, you want rpm to fail when a package's dependencies are not satisfied, so that you can fix the problem. This is the route to take if you want to explicitly specify every package and avoid any others being installed. You do not then get automatic package downloads, but rpm understands http: URLs, so you can still pull packages from your local repository (or external ones) by specifying their complete URLs. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Support for Windows
Hi Damian, On Sun, Jul 28, 2013 at 1:03 PM, damian.folw...@gmail.com wrote: Hi Josh, Did PuppetLabs ever get anywhere with ticket 13249. I'm guessing not as it hasn't been updated for months. I see that PE 3 is now available and that there has been plenty of activity on the Windows side of things (we are about to start a trial with it on some of our Windows estate as Windows support especially MCollective is much better). Yes, mcollective is fully supported on windows now! Do you have any sort of timescale for this ticket. I'd like to vote on it but the gatekeepers of our PE login details are not letting me near it (the sysadmins own it, we're an app development department and having some fun and games with them trying to do continuous deployment type stuff!). I don't have a time estimate, other than to say that we are working on a set of improvements to file system management, including NTFS ACLs, symlinks, and some bug fixes, and it's one of our top priorities, along with powershell and reboot support. If you have any early release type versions of this I might be able to help out with some testing etc. That'd be great! Managing the ACL via Win32 API's is not hard (we do much of it today). The hard part is deciding how best to model the ACL in puppet. Should it be a separate resource type or a property of the file type? Do we create a new file acl type with multiple providers, e.g. windows, solaris, etc? If so, what parameters and properties are common, and which are unique to a specific provider, e.g. protected on windows? Josh -- Josh Cooper Developer, Puppet Labs *Join us at PuppetConf 2013, August 22-23 in San Francisco - * http://bit.ly/pupconf13* **Register now and take advantage of the Final Countdown discount - save 15%!* -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] file_line assistance
Hi,
do you have pluginsync enabled?
During the first puppet agent run (after you have added std lib module) you
will see many files synced to the agent.
hth,
Martin
On Jul 30, 2013, at 11:24 PM, Tom Hanstra t...@miwoods.net wrote:
I'm running puppet 3.2.3 with the current (4.1.0) stdlib set from puppetlabs.
I'm attempting to use file_line to add a line to a file. I've dumbed this
down to basically the test script:
class hs_puptest1 {
file { '/tmp/testfile':
ensure = present
}-
file_line { 'test_line':
line = 'Some data',
path = '/tmp/testfile',
}
}
The puppet agent puptest1 creates /tmp/testfile, but it does not add the line
to the file. I don't even see file_line executed:
puptest1.library.nd.edu|root no_ora /etc/puppet 673$ puppet agent --test
Info: Caching catalog for puptest1.library.nd.edu
Info: Applying configuration version '1375219378'
Notice: /Stage[main]/Hs_puptest1/File[/tmp/testfile]/ensure: created
Notice: Finished catalog run in 1.86 seconds
puptest1.library.nd.edu|root no_ora /etc/puppet 674$ cat /tmp/testfile
puptest1.library.nd.edu|root no_ora /etc/puppet 675$
What am I doing wrong? What might be missing?
Thanks,
Tom
hans...@nd.edu
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: file_line assistance
On Tuesday, July 30, 2013 10:24:41 PM UTC+1, Tom Hanstra wrote:
I'm running puppet 3.2.3 with the current (4.1.0) stdlib set from
puppetlabs.
I'm attempting to use file_line to add a line to a file. I've dumbed this
down to basically the test script:
class hs_puptest1 {
file { '/tmp/testfile':
ensure = present
}-
file_line { 'test_line':
line = 'Some data',
path = '/tmp/testfile',
}
}
Add
ensure = present
To the file_line resource as well.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: file_line assistance
No, I don't have pluginsync enabled, but when I attempt to do so I get this
error:
Info: Retrieving plugin
Error: Could not retrieve plugin: Parameter source failed on
File[/var/lib/puppet/lib]: Could not understand source
puppet://lib_puppet2.library.nd.edu/plugins: the scheme puppet does not
accept registry part: lib_puppet2.library.nd.edu (or bad hostname?)
I've been searching the web, but have not found the combination to get past
this. Documentation only suggests enabling pluginsync on both master and
agent, which is not enough. What else am I missing?
Thanks,
Tom
On Tuesday, July 30, 2013 5:24:41 PM UTC-4, Tom Hanstra wrote:
I'm running puppet 3.2.3 with the current (4.1.0) stdlib set from
puppetlabs.
I'm attempting to use file_line to add a line to a file. I've dumbed this
down to basically the test script:
class hs_puptest1 {
file { '/tmp/testfile':
ensure = present
}-
file_line { 'test_line':
line = 'Some data',
path = '/tmp/testfile',
}
}
The puppet agent puptest1 creates /tmp/testfile, but it does not add the
line to the file. I don't even see file_line executed:
puptest1.library.nd.edu|root no_ora /etc/puppet 673$ puppet agent --test
Info: Caching catalog for puptest1.library.nd.edu
Info: Applying configuration version '1375219378'
Notice: /Stage[main]/Hs_puptest1/File[/tmp/testfile]/ensure: created
Notice: Finished catalog run in 1.86 seconds
puptest1.library.nd.edu|root no_ora /etc/puppet 674$ cat /tmp/testfile
puptest1.library.nd.edu|root no_ora /etc/puppet 675$
What am I doing wrong? What might be missing?
Thanks,
Tom
hans...@nd.edu
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: file_line assistance
http://projects.puppetlabs.com/issues/3504
factsync doesn't work when puppetmaster has _ in hostname
Updated by Patrick Carlisle over 1 year ago
• Status changed from Needs More Information to Closed
This is an error raised by ruby’s URI library. Unfortunately the error is not
more specific, but the string does correctly suggest bad hostname as a cause. I
think we’re unlikely to do anything more about this, and it’s nearly two years
old, so I’m closing it.
Please have a look at RFC952 (http://tools.ietf.org/html/rfc952) Hostnames
should not contain an ‘_’!
On Jul 31, 2013, at 2:46 PM, Tom Hanstra t...@miwoods.net wrote:
No, I don't have pluginsync enabled, but when I attempt to do so I get this
error:
Info: Retrieving plugin
Error: Could not retrieve plugin: Parameter source failed on
File[/var/lib/puppet/lib]: Could not understand source
puppet://lib_puppet2.library.nd.edu/plugins: the scheme puppet does not
accept registry part: lib_puppet2.library.nd.edu (or bad hostname?)
I've been searching the web, but have not found the combination to get past
this. Documentation only suggests enabling pluginsync on both master and
agent, which is not enough. What else am I missing?
Thanks,
Tom
On Tuesday, July 30, 2013 5:24:41 PM UTC-4, Tom Hanstra wrote:
I'm running puppet 3.2.3 with the current (4.1.0) stdlib set from puppetlabs.
I'm attempting to use file_line to add a line to a file. I've dumbed this
down to basically the test script:
class hs_puptest1 {
file { '/tmp/testfile':
ensure = present
}-
file_line { 'test_line':
line = 'Some data',
path = '/tmp/testfile',
}
}
The puppet agent puptest1 creates /tmp/testfile, but it does not add the line
to the file. I don't even see file_line executed:
puptest1.library.nd.edu|root no_ora /etc/puppet 673$ puppet agent --test
Info: Caching catalog for puptest1.library.nd.edu
Info: Applying configuration version '1375219378'
Notice: /Stage[main]/Hs_puptest1/File[/tmp/testfile]/ensure: created
Notice: Finished catalog run in 1.86 seconds
puptest1.library.nd.edu|root no_ora /etc/puppet 674$ cat /tmp/testfile
puptest1.library.nd.edu|root no_ora /etc/puppet 675$
What am I doing wrong? What might be missing?
Thanks,
Tom
hans...@nd.edu
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet, Yum, Cassandra, openjdk and --nodeps
On Tuesday, July 30, 2013 12:56:56 PM UTC-5, Paul Pham wrote: Appreciate the input guys. You're right about the --nodeps flag being an RPM thing, I was hoping there might be something similar I could leverage from the yum provider, but it looks like the yum provider does not currently support install_options anyway, so it's kind of moot. It seems like there's a bug/feature request in here somewhere, but I still can't put my finger on it. I'm talking about Java, but in general if you have some type of runtime that has multiple vendors/providers, and you're using Alternatives to configure your default provider for that type of runtime, how does/should puppet handle it? Or should I not be relying on alternatives to set defaults? Is the main problem that the cassandra RPM requires openjdk, or is that standard practice (and I should learn to deal with it?) Do most folks who use puppet not use yum? Or are most people okay with letting puppet install dependencies automagically? I suspect that most people who use Puppet with yum-based clients let Puppet install dependencies automagically via yum, at least in most cases. I certainly do. If you need finer control then that's what the 'rpm' command and Puppet's direct rpm provider are for. I exercise a measure of control by configuring yum to use local mirrors of most of the repositories we rely on. In principle, that affords me the opportunity to audit all packages available for installation, but in practice I do very little of that. It also allows me to control when package updates become available for installation, which I make much less frequent than the upstream providers do. Additionally, it allows me to pick and choose what versions of what packages from upstream are available at all, but I exercise that capability only very rarely. The careful among us may go so far as to maintain test environments that encompass repository updates in addition to Puppet manifest and data updates. I think you should give a bit of thought to *why* you are uncomfortable with using yum via Puppet (and that's really what you're saying, since yum doesn't offer any form of nodeps operation, Puppet notwithstanding). There may be a way to mitigate your concerns without greatly complicating your Puppet manifests by explicitly declaring all dependencies, recursively, of every package you want Puppet to manage. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Augeas, fstab and duplicate lines: How to test ? (onlyif ? not_include ?) ... Examples ?
On Monday, July 29, 2013 4:26:59 PM UTC-5, haral...@gmail.com wrote: Hi, I am trying to define a new type that will insert a new filesystem line into /etc/fstab. This is a large part of what the built-in Mount type is for. Do you need something it does not provide? However, no matter what I tried, it will insert a new line each time. I can't really help you with Augeas details, but for what little it's worth, I don't see what's wrong with what you've attempted so far. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] updating puppet with puppet on windows node (msi)
The windows package provider doesn't have this information. You could
alternatively try the chocolatey package provider. It's available on the
forge: http://forge.puppetlabs.com/rismoney/chocolatey
--
Rob Reynolds
Developer, Puppet Labs
*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*
On Thu, Jul 4, 2013 at 5:17 PM, Dan White y...@comcast.net wrote:
On Linux, you would do this:
install.pp:
class base_puppet_agent::install {
case $::operatingsystem {
windows : {
package { 'PuppetWindows':
name= 'Puppet',
ensure = installed,
source =
'puppet:\\\modules\base_puppet_agent\puppet-3.2.3-rc1.msi',
provider = windows
}
}
centos, redhat: {
package { 'puppet':
ensure = latest, #
}
}
}
}
And the Linux package provider would know when a new version is available.
I am not sure if Windows can do that.
From http://docs.puppetlabs.com/references/3.2.latest/type.html#package,
it says:
ensure
What state the package should be in. On packaging systems that can
retrieve new packages on their own, you can choose which package to
retrieve by specifying a version number or latest as the ensure value. On
packaging systems that manage configuration files separately from “normal”
system files, you can uninstall config files by specifying purged as the
ensure value. Valid values are present (also
calledinstalled), absent, purged, held, latest. Values can match /./.
You might find these links of help:
http://docs.puppetlabs.com/windows/writing.html#packagepackage
http://docs.puppetlabs.com/windows/troubleshooting.html#package
On Jul 4, 2013, at 3:09 PM, cko wrote:
hi, im trying to update the puppet windows agent on my windows server 2008
r2 node.
i installed puppet-3.2.2 manually. my goal is to update the puppet agent
to puppet-3.2.3-rc1
i tried that with the following manifest:
init.pp:
class base_puppet_agent {
include base_puppet_agent::install,
base_puppet_agent::service,
base_puppet_agent::config
}
install.pp:
class base_puppet_agent::install {
case $::operatingsystem {
windows : {
package { 'PuppetWindows':
name= 'Puppet',
ensure = installed,
source =
'puppet:\\\modules\base_puppet_agent\puppet-3.2.3-rc1.msi',
provider = windows
}
}
centos, redhat: {
package { 'puppet':
ensure = installed,
}
}
}
}
service.pp:
class base_puppet_agent::service {
service { 'puppet':
ensure = running,
enable = true,
hasstatus = true,
hasrestart = true
}
}
config.pp:
class base_puppet_agent::config {
case $::operatingsystem {
windows: {
#Windows
file { 'C:\ProgramData\PuppetLabs\puppet\etc\puppet.conf':
source =
puppet:///modules/base_puppet_agent/puppet_windows.conf,
notify = Service['puppet'],
require = Package ['PuppetWindows']
}
}
centos, redhat: {
#Linux
file { '/etc/puppet/puppet.conf':
source = puppet:///modules/base_puppet_agent/puppet.conf,
owner = 'root',
group = 'root',
mode = '0644',
notify = Service['puppet'],
require = Package ['puppet']
}
}
}
}
the puppet run works perfectly. no errors whatsoever. the problem is, that
it doesn't update to the desired version. it just checks, if a package
named puppet is installed, but ignores the current version.
thoughts?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send
[Puppet Users] Node Classifications
Hi Everyone, I am struggling a bit with the order of precedence of node classifications. When using .pp files to classify nodes, what happens if a node corresponds to two different manifests. For example, if I have .pp files that select nodes based on hostnames and I have another .pp file that selects hosts based in data center location, will both manifests be applied accordingly? Also, is the default manifest applied to ALL hosts, complimentary of any manifests that explicitly apply to the host? Or, is the default applied ONLY if no other manifests apply to that host? Thank you very much! Bee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Version number and full name of the installed modules on a node
Hi @all, as the name of the topic describes already i am looking for a way to get some more information about the installed modules on a node. I know i can get the installed classes/modules on a node via mcollective inventory HOSTNAME. But actually the version of the module is not included neither the author like puppetlabs-mysql. Is there any way to get these information? Thanks in advance Dave -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Ruby Error Encountered when Installing Dashboard for Puppet Open Source
Maybe you figured it out already... and yes, it has something to do with the gem version :) This is the fix for me: $ rake RAILS_ENV=production db:migrate rake aborted! undefined method `source_index' for Gem:Module(See full trace by running task with --trace)$ gem -v 2.0.3$ gem update --system 1.8.25$ gem -v 1.8.25 I got it here: http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror On Tuesday, April 16, 2013 12:04:40 PM UTC+8, Cary Czichon wrote: I've installed Puppet and am installing Dashboard on CentOS 6. I'm running into an 'undefined method' when installing the dashboard. To install Puppet Open Source, I ran: rpm -ivh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpmhttps://webmail.battelle.org/owa/redir.aspx?C=49d16157280e4bac838fdb9a9a3f5644URL=http%3a%2f%2fyum.puppetlabs.com%2fel%2f6%2fproducts%2fi386%2fpuppetlabs-release-6-6.noarch.rpm rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-7.noarch.rpmhttps://webmail.battelle.org/owa/redir.aspx?C=49d16157280e4bac838fdb9a9a3f5644URL=http%3a%2f%2fdownload.fedoraproject.org%2fpub%2fepel%2f6%2fx86_64%2fepel-release-6-7.noarch.rpm yum install puppet-server yum install puppet I created the /etc/puppet/manifests/site.pp and /etc/puppet/manifests/classes/sudo.pp files and ran: service puppetmaster start chkconfig puppetmaster on I created the /etc/sysconfig/puppet file and then ran service puppet start chkconfig puppet on To install dashboard I followed the steps in the Dashboard Manual. First I installed: * RubyGems * Rake * MySQL * Ruby-MySQL Then I ran: yum install puppet-dashboard I updated the database.yml and settings.yml files and created a puppet DB in MySQL by running the following in MySQL's workbench. CREATE DATABASE dashboard CHARACTER SET utf8; CREATE USER 'dashboard'@'localhost' IDENTIFIED BY 'dbpassword'; GRANT ALL PRIVILEGES ON dashboard.* TO 'dashboard'@'localhost'; I've added the following line to the /etc/mysql/my.cnf file. max_allowed_packet = 32M And executed 'set max_allowed_packet = 33554432;' in the MySQL workbench. I then ran the following within the /usr/share/puppet-dashboard/ directory. rake RAILS_ENV=production db:migrate I got the following error message. rake aborted! undefined method `source_index' for Gem:Module (See full trace by running task with --trace) So I ran it again with trace turned on and got the following. rake aborted! undefined method `source_index' for Gem:Module /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21:in `add_frozen_gem_path' /usr/share/puppet-dashboard/config/boot.rb:50:in `load_initializer' /usr/share/puppet-dashboard/config/boot.rb:41:in `run' /usr/share/puppet-dashboard/config/boot.rb:14:in `boot!' /usr/share/puppet-dashboard/config/boot.rb:113 /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in `gem_original_require' /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:45:in `require' /usr/share/puppet-dashboard/Rakefile:4 /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/rake_module.rb:25:in `load' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/rake_module.rb:25:in `load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:589:in `raw_load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:89:in `load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:88:in `load_rakefile' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:72:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:70:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.4/bin/rake:33 /usr/bin/rake:23:in `load' /usr/bin/rake:23 Has this problem been encountered before. Is a solution known? Could it be a RubyGem version problem (version 1.8.1 needed?). I'm using the 2.0.3 version. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Support for Windows
Hi Josh, On Sun, Jul 28, 2013 at 1:03 PM, damian@gmail.com javascript: wrote: snip I don't have a time estimate, other than to say that we are working on a set of improvements to file system management, including NTFS ACLs, symlinks, and some bug fixes, and it's one of our top priorities, along with powershell and reboot support. That's amazing news. Powershell support alone would be killer - I had to wrap nearly my entire universe with cmd.exe to make like easier - to the point of writing a shared module for this pain. Powershell can't come fast enough :) snip That'd be great! Managing the ACL via Win32 API's is not hard (we do much of it today). The hard part is deciding how best to model the ACL in puppet. Should it be a separate resource type or a property of the file type? Do we create a new file acl type with multiple providers, e.g. windows, solaris, etc? If so, what parameters and properties are common, and which are unique to a specific provider, e.g. protected on windows? Hopefully my $0.02 can we worth something here ;) I'd argue that it's really a separate resource type - since the ACL is related to the user space. If you're going to extend it to multiple providers (solaris as per your example) it's really similar in idea to RBAC. In fact, if you look at Windows ACLs, RBAC, and set/get facl you pretty much have a new type. Or at least that's what I'd hope :) Josh -- Josh Cooper Developer, Puppet Labs *Join us at PuppetConf 2013, August 22-23 in San Francisco - * http://bit.ly/pupconf13* **Register now and take advantage of the Final Countdown discount - save 15%!* --c Chayim Kirshen Founder, Lyrical Software @lyricaldevops | http://www.lyricaldevops.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Windows puppet service
Hello,
Even with the service set to stopped, I have a windows puppet agent
that seems to be applying its catalog trying to install
puppet-3.2.3.msi over and over every minute. There are ruby processes
in tasklist, and killing them helps, but the problem persists if the
service restarts.
Where might I look to troubleshoot? I originally installed puppet
3.2.2 on this machine, then thought I upgraded successfully to 3.2.3.
The manifest is trivial:
class puppet_client_win {
package { 'puppet':
ensure = installed,
source = 'http://sv-mgmt6/windows/puppet-3.2.3.msi',
notify = Service['puppet'],
}
service { 'puppet':
ensure= 'running',
#enabled = true,
subscribe = File['C:\ProgramData\PuppetLabs\puppet\etc\puppet.conf'],
}
file { 'C:\ProgramData\PuppetLabs\puppet\etc\puppet.conf':
ensure = present,
content = template('puppet_client_win/puppet.conf.erb'),
}
}
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] excessive hiera logging
(puppet 3.1.1, hiera 1.2.1, redhat 6.x) My puppetmaster is filling up it's logs filesystem every other day because of hiera debug logging that I cannot seem to get rid of. I have a pretty large hierarchy (18 levels) and about 30 modules that I deploy out to 1900 servers. Every time I have an agent run the master logs thousands of lines such as: Jul 31 12:55:21 rv-mg-xppm-08 puppet-master[17966]: (Scope(Class[Samba::Params])) Could not look up qualified variable 'data::osfamily/Solaris/10_u8/samba::samba::params::service'; class data::osfamily/Solaris/10_u8/samba::samba::params could not be found Basically one for every permutation of module and hierarchy level where I don't define values for that module. This comes out to thousands and thousands of lines a minute. According to the hiera docs, I should be able to put :logging: noop in the /etc/hiera.yaml file but then puppet automatically sets it to puppet no matter what I put. Is there some way I can shut down this logging?? Right now I have had to stop ALL puppet master logging by changing the rack configuration (putting --logdest /dev/null in my config.ru file) Thanks Bill -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: file_line assistance
Well, the hostname was the problem. That never tripped me up before, but
I'll keep it in mind for future reference!
Thanks,
Tom
On Tuesday, July 30, 2013 5:24:41 PM UTC-4, Tom Hanstra wrote:
I'm running puppet 3.2.3 with the current (4.1.0) stdlib set from
puppetlabs.
I'm attempting to use file_line to add a line to a file. I've dumbed this
down to basically the test script:
class hs_puptest1 {
file { '/tmp/testfile':
ensure = present
}-
file_line { 'test_line':
line = 'Some data',
path = '/tmp/testfile',
}
}
The puppet agent puptest1 creates /tmp/testfile, but it does not add the
line to the file. I don't even see file_line executed:
puptest1.library.nd.edu|root no_ora /etc/puppet 673$ puppet agent --test
Info: Caching catalog for puptest1.library.nd.edu
Info: Applying configuration version '1375219378'
Notice: /Stage[main]/Hs_puptest1/File[/tmp/testfile]/ensure: created
Notice: Finished catalog run in 1.86 seconds
puptest1.library.nd.edu|root no_ora /etc/puppet 674$ cat /tmp/testfile
puptest1.library.nd.edu|root no_ora /etc/puppet 675$
What am I doing wrong? What might be missing?
Thanks,
Tom
hans...@nd.edu
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Node Classifications
http://docs.puppetlabs.com/puppet/3/reference/lang_node_definitions.html According to that, default only applies if nothing else matches. For your other question, how are you doing multiple manifests? With imports? On Wednesday, July 31, 2013 9:53:13 AM UTC-7, Worker Bee wrote: Hi Everyone, I am struggling a bit with the order of precedence of node classifications. When using .pp files to classify nodes, what happens if a node corresponds to two different manifests. For example, if I have .pp files that select nodes based on hostnames and I have another .pp file that selects hosts based in data center location, will both manifests be applied accordingly? Also, is the default manifest applied to ALL hosts, complimentary of any manifests that explicitly apply to the host? Or, is the default applied ONLY if no other manifests apply to that host? Thank you very much! Bee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Fedora 17 leaving yum.puppetlabs.com
Fedora 17 reached end of life on 2013-07-30 [1], so we are no longer building new packages for it and will remove it from our yum repository on Monday, October 28. [1] - https://lists.fedoraproject.org/pipermail/announce/2013-July/003169.html -- Matthaus Owens Release Manager, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Final Countdown discount - save 15%! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Version number and full name of the installed modules on a node
Hi Dave, You may try `puppet module list` which provides information like this: [root@dhcp100 ~]# puppet module list /etc/puppetlabs/puppet/modules ├── adrien-filemapper (v1.1.2) ├── garethr-cube (v0.1.0) ├── nanliu-staging (v0.3.1) ├── puppetlabs-mongodb (v0.1.0) ├── puppetlabs-nodejs (v0.2.1) ├── puppetlabs-pe_upgrade (v1.0.0) ├── razorsedge-vmwaretools (v4.5.0) └── reidmv-yamlfile (v0.0.2) You can pass `--render-as json` to get json back though unfortunately, this does not include version information. Regards, --Ryan On Wed, Jul 31, 2013 at 2:16 AM, David Gillet gillet.david@gmail.comwrote: Hi @all, as the name of the topic describes already i am looking for a way to get some more information about the installed modules on a node. I know i can get the installed classes/modules on a node via mcollective inventory HOSTNAME. But actually the version of the module is not included neither the author like puppetlabs-mysql. Is there any way to get these information? Thanks in advance Dave -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- Ryan Coleman | Modules Forge | ryanycoleman on twitter #puppet IRC -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Augeas, fstab and duplicate lines: How to test ? (onlyif ? not_include ?) ... Examples ?
Many thanks to all for your replies. Yeah, I finally got it. Something like: onlyif = match */spec[ . = '$fs_spec' ] size == 0 for fstab entries and onlyif = match */spec[ . = '$fs_spec' ]/../opt[ . = '$fs_opt'] size == 0 for handling options Cheers. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Augeas, fstab and duplicate lines: How to test ? (onlyif ? not_include ?) ... Examples ?
On Wed, Jul 31, 2013 at 4:57 PM, haraldch...@gmail.com wrote: Many thanks to all for your replies. Yeah, I finally got it. It looks like I'm too late to really help, but I wanted to offer an alternative. domcleal/augeasproviders on the Forge offers a new provider to the built-in mounttab type that relies on the power of augeas while allowing you to use the Puppet DSL to express the configuration. Here are a few code examples: http://augeasproviders.com/documentation/examples.html#mounttab_provider http://forge.puppetlabs.com/domcleal/augeasproviders Even if you don't use that module for this, check it out. It also provides a number of awesome resource types like sshd_config and sysctl. Regards, -- Ryan Coleman | Modules Forge | ryanycoleman on twitter #puppet IRC -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Augeas, fstab and duplicate lines: How to test ? (onlyif ? not_include ?) ... Examples ?
On Wednesday, July 31, 2013 11:58:47 PM UTC+10, jcbollinger wrote: This is a large part of what the built-in Mount type is for. Do you need something it does not provide? AFAIK Mount does not provide support for encrypted filesystems (/etc/crypttab) There are some good basic reasons for using encrypted filesystems: - if I have to return a failed disk to factory (warranty) - if it gets stolen - if I need to discard an old disk etc. Cheers, -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] evaluating vCloud and OpenStack (and ?), was wondering about experiences / stability, etc.
We are looking at vCloud and OpenStack for our University Cloud offering (research and education). I'm curious what anyone's experiences have been. We have an OpenStack (Essex) installation now, but we are looking to upgrade to Grizzly or move to vCloud. Other than that cloud instance, we are a vmWare shop so moving to vCloud may be easier for us in terms of training. Both I understand rely heavily on Puppet so I think that this is relevant to this list, but if not, let me know. Anyway, any experience / thoughts on this? Thanks, Nathan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Getting the following error with repo key authentication on puppet client
I am getting the following error while running puppet agent -t on client side..how do I enable repository keys on puppet master to get rid off this error. info: Applying configuration version '1375302925' err: /Stage[main]/Nrpe/Package[nagios-plugins-basic]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--forc. Building dependency tree... Reading state information... The following extra packages will be installed: nagios-plugins-common Suggested packages: nagios3 icinga The following NEW packages will be installed: nagios-plugins-basic nagios-plugins-common 0 upgraded, 2 newly installed, 0 to remove and 44 not upgraded. Need to get 1204 kB of archives. After this operation, 2654 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! nagios-plugins-common nagios-plugins-basic E: There are problems and -y was used without --force-yes Regards, Chittaranjan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet environments not working
Does anyone know how I can troubleshoot this? surely someone's seen this before? On Monday, July 29, 2013 3:34:39 PM UTC-4, me 1 wrote: I have a surprising problem with environments not working, i'm using rhel 6.3 with puppet-3.2.3-1.el6.noarch and here is the puppet.conf on the master: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl server = puppet.local reports = store, http reporturl = http://localhost:80/reports/upload modulepath = $confdir/modules manifest = $confdir/manifests/site.pp [preprod] modulepath = $confdir/environments/preprod/modules manifest = $confdir/environments/preprod/manifests/site.pp [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig When I make a change to 1 of the modules in the preprod modulepath, all I ever see is this on the client: $ puppet agent --test --noop --environment preprod --configprint environment preprod $ puppet agent --test --noop --environment preprod Info: Retrieving plugin Info: Caching catalog for testvm.local Info: Applying configuration version '1375125121' Notice: Finished catalog run in 0.01 seconds -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet Support for Windows
On Wed, Jul 31, 2013 at 6:22 AM, cha...@lyricalsoftware.com wrote:
Hi Josh,
On Sun, Jul 28, 2013 at 1:03 PM, damian@gmail.com wrote:
snip
I don't have a time estimate, other than to say that we are working on a
set of improvements to file system management, including NTFS ACLs,
symlinks, and some bug fixes, and it's one of our top priorities, along
with powershell and reboot support.
That's amazing news. Powershell support alone would be killer - I had to
wrap nearly my entire universe with cmd.exe to make like easier - to the
point of writing a shared module for this pain. Powershell can't come fast
enough :)
I have a powershell provider here:
http://forge.puppetlabs.com/joshcooper/powershell. And as of puppet 3.2,
that the module tool supports windows, so you can do:
C:\puppet module install joshcooper-powershell
C:\puppet apply -e exec { 'Write-Host hello': provider= powershell,
logoutput = true }
Notice: /Stage[main]//Exec[Write-Host hello]/returns: hello
Notice: /Stage[main]//Exec[Write-Host hello]/returns: executed successfully
We've recently made some improvements around powershell invocation. See
https://github.com/joshcooper/puppetlabs-powershell/issues for more info.
Josh
--
Josh Cooper
Developer, Puppet Labs
*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
