Re: [Puppet Users] Re: Using Mcollective with Enterprise Ruby
- Original Message - not sure if there's a way to tell rpmbuild to do that, but you can just comment them out in the spec file. or when you install you can do rpm -ivh --nodeps to skip them. There's a ticket open to make this kind of thing easier - being able to rebuild the rpms for different rubies installed in weird places but I havnt really had any good thoughts about how to achieve that. -- R.I.Pienaar This allowed me to get the product installed; however, it failed with the /usr/bin/env -- so when I ran the commands, the 'require' for mcollective didn't work (presumably because the installation wasn't done properly, as it would have installed into the Enterprise Ruby directory. The Enterprise Ruby executable is in my $PATH -- though the PATH variable points to a symlink that goes to the full version named directory -- shouldn't make a difference here. This is exactly why we use /usr/bin/env and not a hard coded path to your ruby since everyone's ruby is different. /usr/bin/env will search your PATH and use the first one, I suspect you have a local setup problem. Shouldn't the mcollective tarball have a script to facilitate a manual install? That would be a good place to override/set some variables. No I dont think we should have an install script that edit every ruby script on install since this doesnt solve the problem - you will also be installing other scripts from the plugins repo or what you found on github etc. Set your environment up correctly so that /usr/bin/env does what its supposed to do and it will work fine. If I add a custom ruby to the beginning of my PATH environment the mcollective scrips all just use that ruby without a problem. -- 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] puppetd by cron using cached config , does it expire ?
hi, since my puppet CA expired the nodes cannot connect to the server because of ssl issue. I have recreated a CA and removed/resigned all the certs i could find for the node. However i just saw that the node not having ssl connexion right are still running puppet using cached configuration. Jun 16 03:35:08 xxx puppetd[9503]: Could not get config; using cached copy Jun 16 03:35:10 xxx puppetd[9503]: Starting configuration run is there a moment they will stop doing this , is the cache expiring in xx days ? How i can detect the nodes that are failling from the master the logs does seems to only report succesful connections (i am on an old version 0.22.4). regards, Jean. -- 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: puppet dashboard performance issue
no other solution ? Where this query is used in the code ? Can we disable the query ? On Apr 18, 12:49 am, Andrew Forgue andrew.for...@gmail.com wrote: I also tried to look at this; since it was causing me issues as well. I had 800,000 rows or so in the reports table but I accidentally corrupted it (kill -9) so I won't have that many for a few more days. I created the separate indexex for kind and status but MySQL didn't use them. It uses indexes for everything except the report.status != failed and then it switches to a full table scan, even if the query is a simple select with only the where and no join. The documentation for MySQL indexes says that if MySQL thinks not using an index will be better it will not use indexes. mysql explain select * from reports WHERE reports.status = 'failed'; *** 1. row *** id: 1 select_type: SIMPLE table: reports type: ref possible_keys: index_reports_on_status key: index_reports_on_status key_len: 258 ref: const rows: 274 Extra: Using where 1 row in set (0.00 sec) mysql explain select * from reports WHERE reports.status != 'failed'; *** 1. row *** id: 1 select_type: SIMPLE table: reports type: ALL possible_keys: index_reports_on_status key: NULL key_len: NULL ref: NULL rows: 108828 Extra: Using where 1 row in set (0.00 sec) Presumably it's doing this because the number of rows that are != failed are the vast majority so a full table scan is actually faster. It looks like it's selecting all the reports, and then grouping so we get the latest one. Doing a cartesian join and then grouping seems extremely slow. I re-wrote the query to use a sub-select: select reports.*,nodes.* from nodes, (select node_id,max(time) from reports where reports.kind = 'apply' and reports.status != 'failed' GROUP by node_id) as reports WHERE reports.node_id = nodes.id; 1424 rows in set (0.12 sec). So you're only getting the latest report and then the nodes for each. How fast does that query run? -Andrew -- 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] puppetd by cron using cached config , does it expire ?
On Thu, Jun 16, 2011 at 1:02 PM, j...@squirk.org j...@squirk.org wrote: ** hi, since my puppet CA expired the nodes cannot connect to the server because of ssl issue. 5 years? nice! :) Ohad I have recreated a CA and removed/resigned all the certs i could find for the node. However i just saw that the node not having ssl connexion right are still running puppet using cached configuration. Jun 16 03:35:08 xxx puppetd[9503]: Could not get config; using cached copy Jun 16 03:35:10 xxx puppetd[9503]: Starting configuration run is there a moment they will stop doing this , is the cache expiring in xx days ? How i can detect the nodes that are failling from the master the logs does seems to only report succesful connections (i am on an old version 0.22.4). regards, Jean. -- 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] Concat Module posted to Onyx Point Github.
On 12 June 2011 20:21, Markus Falb markus.f...@fasel.at wrote:
I also tried with 0.25.5 and noticed that your module does not work.
All autorequire stuff does not work. It seems like things like
if catalog.resources.find_all { ... }.empty?
is always true. I have no clue why.
It's because catalog.resources() only returns an array of strings on
0.25.x
There might be another way to construct the autorequires. Not sure though.
--
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] Problem with usage of arrays
Hi there, i can't use array in puppet. Here is my codesnipplet: $callapidata = [ 'wert1','wert2'] notice $callapidata[1] A puppetrun results in: Could not retrieve catalog from remote server: Error 400 on SERVER: can't convert String into Integer at /etc/puppet/myenv/modules/ uc4client/manifests/init.pp:41 on node testnode Thanks for your help. Greetings Roband -- 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] Passing an array to a chained provider
Afternoon all,
I am looking to do the following using Puppet to simplify
relationships for our AD class. I've stripped it down to the basic
relation I'd like to work.
$kerberos_packages = [winbind, krb5-config, libpam-krb5,
portmap, krb5-user, samba-common]
$kerberos_dependencies = [/etc/nsswitch.conf, /etc/samba/smb.conf,
/etc/pam.d/common-account, /etc/pam.d/common-auth, /etc/pam.d/
common-session]
package { $kerberos_packages: ensure = installed }
Package[$kerberos_packages] - File[$kerberos_dependencies]
file { files listed here with various options }
This does not generate an error for the puppet parser however the
puppet master fails to compile modules with an error.
Jun 16 14:29:25 puppetmaster puppet-master[9820]: Could not find
resource 'Package[winbind]Package[krb5-config]Package[libpam-
krb5]Package[portmap]Package[krb5-user]Package[samba-common]' for
relationship on 'File[/etc/nsswitch.conf]File[/etc/samba/
smb.conf]File[/etc/pam.d/common-account]File[/etc/pam.d/common-
auth]File[/etc/pam.d/common-session]]' on node example.domain
Please note the issue isn't in sending the array, Package[one,
two] - File[a,b] still fails.
The documentation on chaining is literally the brief post by the guy
who wrote the patch that added this functionality. There is also
mention of the | | relationship operator however I cannot figure out
how to limit its actions to the items in my arrays.
So I'd like to know if I've made a mistake in my syntax or if the
chaining is limited to one-to-one relations? If it is limited to one-
to-one relations is there already a bug asking for many-to-many passed
via array?
Thanks,
Edward Savage
--
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 repository from puppetlabs
I installed using gem instead of Lucid packages - not exactly for that reason (we are using ruby-enterprise and not Lucid ruby packages). Craig On Jun 15, 2011, at 8:56 PM, Asif Iqbal wrote: Hi All, Is there a ubuntu repository managed by puppetlabs? I am using lucid and latest puppet package it offers is 0.25.4. I could of course just download source, or a deb from debian or newer ubuntu, or get it using gem. But would be nice if there is a PPA available for lucid, cuz it would work nicely with routine upgrade. puppetdashboard worked nicely with the puppet labs ppa deb http://apt.puppetlabs.com/ubuntu lucid main and deb-src deb-src http://apt.puppetlabs.com/ubuntu lucid main Please advise. -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- 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. -- Craig White ~~ craig.wh...@ttiltd.com 1.800.869.6908 ~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! -- 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] OpenBSD default packages
Hello all,
I'm new to this great tool.
In our enviroment, we use different linux/unix flavors (CentOS/Ubuntu/
OpenBSD).
Everything works fine, but in OpenBSD we have some issues.
Some packages that are installed by the default installation on
OpenBSD, like snmpd and ntpd, also need to be installed in CentOS and
Ubuntu.
So, we created a module that handle these services.
Like this one:
class snmp {
include snmp::params
package { $snmp::params::snmp_package:
ensure = present,
}
file { snmp.conf:
owner= root,
group= root,
mode = '0644',
path = $snmp::params::snmp_config_path,
content = template(snmp/etc/snmp/snmpd.conf.erb),
require = Package[snmpd],
}
service { snmpd:
ensure = running,
start = $operatingsystem ? {
'OpenBSD' = /usr/sbin/snmpd,
default = undef,
},
stop = $operatingsystem ? {
'OpenBSD' = pkill snmpd,
default = undef,
},
enable = true,
}
}
class snmp::params {
case $operatingsystem {
OpenBSD: {
$snmp_package = snmpd
$snmp_config_path = /etc/snmpd.conf
}
/(Ubuntu|Debian)/: {
$snmp_package = snmpd
$snmp_config_path = /etc/snmp/snmpd.conf
}
CentOS: {
$snmp_package = net-snmp
$snmp_config_path = /etc/snmp/snmpd.conf
}
}
}
When we wanna assure that package is present in our OpenBSD box, the
puppet agent try to execute pkg_info -I snmpd.
If we set PKG_PATH to our internal mirror this command freezes, if we
unset our PKG_PATH we recieve this message:
info: Applying configuration version '1308232496'
debug: Service[snmpd](provider=bsd): Executing 'ps auxwww'
debug: Service[snmpd](provider=bsd): PID is 993
debug: Puppet::Type::Package::ProviderOpenbsd: Executing '/usr/sbin/
pkg_info snmpd'
err: /Stage[main]/Snmp/Package[snmpd]/ensure: change from absent to
present failed: You must specify a package source for BSD packages
Is a better way to handle this issue? Has anyone use OpenBSD box?
Best Regards,
Sidarta Oliveira
--
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] Problems with puppetlabs yum repo
Hi folks, I'm having a couple of problem with the puppetlabs base repo: First problem - puppet dashboard 1.1.1 is missing from the repo (latest there is 1.1.0). This is pretty straightforward. My second problem is weirder. I use the reposync utility (from the yum-utils RPM) to locally mirror yum repositories. For some strange reason, when I reposync against puppetlabs, the mcollective 1.3.0 version RPMs all end up being 0-length files, despite the fact that I can correctly download them manually. This is very easy to test on any RedHat-style system with the puppetlabs repo, just try this: cd /var/tmp reposync -r puppetlabs You see things like: [puppetlabs: 5 of 48] Downloading mcollective-1.3.0-6.noarch.rpm Could not retrieve package mcollective-1.3.0-6.noarch. Error was failure: mcollective-1.3.0-6.noarch.rpm from puppetlabs: [Errno 256] No more mirrors to try. Is this an odd bug in reposync or is there something malformed in the puppetlabs repodata? I'm using yum-utils-1.1.30-6.el6 on an RHEL6 system. 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] Re: Using Mcollective with Enterprise Ruby
My PATH is set with the /opt/ruby/bin pointer in the front. When I run /usr/bin/env on *any* of the many RHEL5 systems I have, it just hangs. Some of these I didn't set up, some are just stock RHEL installs. So I don't know whether this is a configuration problem or not. By install script, I meant one that actually installs mcollective. Regardless of /usr/bin/env I think this makes some sense for people that want to do a manual install vs. RPM. As for the PATH issue with ruby, I suppose that's everyone's personal choice. I could use 'alternatives' to create links in standard locations to help mitigate PATH issues, of course. Thanks. This allowed me to get the product installed; however, it failed with the /usr/bin/env -- so when I ran the commands, the 'require' for mcollective didn't work (presumably because the installation wasn't done properly, as it would have installed into the Enterprise Ruby directory. The Enterprise Ruby executable is in my $PATH -- though the PATH variable points to a symlink that goes to the full version named directory -- shouldn't make a difference here. This is exactly why we use /usr/bin/env and not a hard coded path to your ruby since everyone's ruby is different. /usr/bin/env will search your PATH and use the first one, I suspect you have a local setup problem. Shouldn't the mcollective tarball have a script to facilitate a manual install? That would be a good place to override/set some variables. No I dont think we should have an install script that edit every ruby script on install since this doesnt solve the problem - you will also be installing other scripts from the plugins repo or what you found on github etc. Set your environment up correctly so that /usr/bin/env does what its supposed to do and it will work fine. If I add a custom ruby to the beginning of my PATH environment the mcollective scrips all just use that ruby without a problem. -- 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: Using Mcollective with Enterprise Ruby
- Original Message - My PATH is set with the /opt/ruby/bin pointer in the front. When I run /usr/bin/env on *any* of the many RHEL5 systems I have, it just hangs. Some of these I didn't set up, some are just stock RHEL installs. So I don't know whether this is a configuration problem or not. this all sounds like you have local configuration errors to be honest. By install script, I meant one that actually installs mcollective. Regardless of /usr/bin/env I think this makes some sense for people that want to do a manual install vs. RPM. As for the PATH issue with ruby, I suppose that's everyone's personal choice. I could use 'alternatives' to create links in standard locations to help mitigate PATH issues, of course. Would you also expect this install script to be able to uninstall or upgrade? Because generally they do not. There's a Makefile in ext/ that you can use with the normal unix tool set to install it wherever you want. It supports the usual DESTDIR variables etc. It still cant make your broken 'env' work though. -- 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: Using Mcollective with Enterprise Ruby
I think I presumed /usr/bin/env returned something. It turns out, it just executes the ruby binary. So that part is working. I now need to sort out the installation issue, mentioned above. Would it be feasible to have an install.rb that you could pass flags to for: * common * server * client * all (all of the above) ? This would make it easy to manually install. Failing that, I suppose directions about where to copy the files to, init scripts, etc. Something I think should be scripted. 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.
Re: [Puppet Users] Re: Using Mcollective with Enterprise Ruby
- Original Message - I think I presumed /usr/bin/env returned something. It turns out, it just executes the ruby binary. So that part is working. I now need to sort out the installation issue, mentioned above. Would it be feasible to have an install.rb that you could pass flags to for: * common * server * client * all (all of the above) ? This would make it easy to manually install. Failing that, I suppose directions about where to copy the files to, init scripts, etc. Something I think should be scripted. it really sounds like you want to reinvent the packaging wheel, thats fine by me - we accept contributed code and we have a public ticketing system where you can file tickets and let us know where to find contributions. I believe packaged sofware solve your problems much better than a script could - since they take in mind things like your distributions rc system etc so I dont think this is going to be a priority for us to script. But you're welcome to contribute. -- R.I.Pienaar -- 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: Problems with puppetlabs yum repo
Hi, I've a similar problem when I try to make a local copy of the repository with mrepo from Dag Wiers. My conf file for mrepo use the name vmware41 for the repository and that's the content of the file : [vmware41] name = VMWare Tools $release release = 41 arch = i686 x86_64 vmware = http://packages.vmware.com/tools/esx/4.1latest/rhel5/$arch when I launch the command it says: blahblablahblah... vmware41-i686: Updating VMWare Tools 41 vmware41-i686: Mirror packages from http://packages.vmware.com/tools/esx/4.1latest/rhel5/i686 to /var/mrepo/vmware41-i686/vmware Execute: exec /usr/bin/lftp -c '; mirror --ignore-time --ignore-size - v -v -v -e -I *.rpm -X openoffice* -X thunderbird* -X tetex* -X /headers/ -X /repodata/ -X *.src.rpm -X /SRPMS/ -X *- debuginfo-*.rpm -X /debug/ http://packages.vmware.com/tools/esx/4.1latest/rhel5/i686 /var/mrepo/vmware41-i686/vmware' mirror: File moved: 302 Moved Temporarily (/tools/esx/4.1latest/rhel5/ i686 - /tools/esx/4.1latest/rhel5/i686/index.html) mrepo: Mirroring failed for http://packages.vmware.com/tools/esx/4.1latest/rhel5/i686 with message: Failed with return code: 256 and it doesn't download anything, naturally I'm using mrepo with success to mirror a bunch of other repositories and I can also manually download files from puppetlabs repo (even with that strange redirection). Any Clues? By the way I have to say that Puppet is a masterpiece of software like few others keep on with that good job guys! On Jun 16, 4:58 pm, Pheran phe...@gmail.com wrote: Hi folks, I'm having a couple of problem with the puppetlabs base repo: First problem - puppet dashboard 1.1.1 is missing from the repo (latest there is 1.1.0). This is pretty straightforward. My second problem is weirder. I use the reposync utility (from the yum-utils RPM) to locally mirror yum repositories. For some strange reason, when I reposync against puppetlabs, the mcollective 1.3.0 version RPMs all end up being 0-length files, despite the fact that I can correctly download them manually. This is very easy to test on any RedHat-style system with the puppetlabs repo, just try this: cd /var/tmp reposync -r puppetlabs You see things like: [puppetlabs: 5 of 48 ] Downloading mcollective-1.3.0-6.noarch.rpm Could not retrieve package mcollective-1.3.0-6.noarch. Error was failure: mcollective-1.3.0-6.noarch.rpm from puppetlabs: [Errno 256] No more mirrors to try. Is this an odd bug in reposync or is there something malformed in the puppetlabs repodata? I'm using yum-utils-1.1.30-6.el6 on an RHEL6 system. 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] special handling for template file with XML?
hi, i get the following error when trying to use a template with XML in it: Could not parse for environment production: Syntax error at '' So I tried using the HTML codes for special chars but now get: Could not parse for environment production: Could not match lt;?xml anyone know if I need to specially handle XML templates? thanks a lot, Guy -- 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] is ruby code allowed in puppet manifest?
Hi,
I'm trying to get the following to work:
class cluster {
$cluster_name = hostname.slice(0..-2)
.
.
} # class
hoping that if I have a server called appfarmserver1 (obtained from facter,
can I use a fact like this!?), cluster_name will get set to appfarmserver .
. .
puppet --parseonly init.pp says:
err: Could not parse for environment production: Syntax error at '.';
expected '}'
Is there some way to get this to work? Is there a better, more puppetty way
to do what I want to do, i.e. based on the hostname from fatcer, set the
variable cluster_name for use in a template.
Thanks so much,
Guy Matz
--
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] is ruby code allowed in puppet manifest?
On Thu, 16 Jun 2011 11:56:59 -0400, Guy Matz wrote:
Hi,
I'm trying to get the following to work:
class cluster {
$cluster_name = hostname.slice(0..-2)
.
.
} # class
hoping that if I have a server called appfarmserver1 (obtained from facter,
can I use a fact like this!?), cluster_name will get set to appfarmserver .
. .
puppet --parseonly init.pp says:
err: Could not parse for environment production: Syntax error at '.';
expected '}'
Is there some way to get this to work? Is there a better, more puppetty way
to do what I want to do, i.e. based on the hostname from fatcer, set the
variable cluster_name for use in a template.
Thanks so much,
Guy Matz
The most puppety way to do it is to create a custom fact that will
return this for you, instead of doing it in the manifest.
You could do it in the manifest using an inline ERB template, but it's
rather hacky.
I definitely recommend going the custom fact route instead.
--
Jacob Helwig
signature.asc
Description: Digital signature
Re: [Puppet Users] is ruby code allowed in puppet manifest?
You have the choice of either a Puppet DSL manifest or a Ruby DSL manifest.
You cannot mix the two within a single file.
On Thu, Jun 16, 2011 at 8:56 AM, Guy Matz gm...@matz.org wrote:
Hi,
I'm trying to get the following to work:
class cluster {
$cluster_name = hostname.slice(0..-2)
.
.
} # class
hoping that if I have a server called appfarmserver1 (obtained from facter,
can I use a fact like this!?), cluster_name will get set to appfarmserver .
. .
puppet --parseonly init.pp says:
err: Could not parse for environment production: Syntax error at '.';
expected '}'
Is there some way to get this to work? Is there a better, more puppetty
way to do what I want to do, i.e. based on the hostname from fatcer, set the
variable cluster_name for use in a template.
Thanks so much,
Guy Matz
--
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: Using Mcollective with Enterprise Ruby
Point taken. Back to the RPM issue. For those of us that do not use a standard system-provided ruby installation, such as Enterprise Ruby, how can we mitigate the installation so that it works? As I mentioned earlier, I tried this with --nodeps and the ruby script could not require the mcollective bit. Given that I just verified that /usr/bin/env is working properly, I think we can safely eliminate that. What would be the best approach to get this working properly? Enterprise Puppet also uses Enterprise Ruby, so I wonder how they've handled it. 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.
Re: [Puppet Users] Re: Using Mcollective with Enterprise Ruby
- Original Message - Point taken. Back to the RPM issue. For those of us that do not use a standard system-provided ruby installation, such as Enterprise Ruby, how can we mitigate the installation so that it works? As I mentioned earlier, I tried this with --nodeps and the ruby script could not require the mcollective bit. Given that I just verified that /usr/bin/env is working properly, I think we can safely eliminate that. What would be the best approach to get this working properly? Enterprise Puppet also uses Enterprise Ruby, so I wonder how they've handled it. Did you rebuild the RPMs like I said yesterday with the ruby in your path correctly setup? Then the resulting RPMs will install into your enterprise directory. I also showed you how to install rpms bypassing the dependency checks and also told you that you could just edit the requirements from the spec files. -- R.I.Pienaar -- 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: Using Mcollective with Enterprise Ruby
Here's the output from the mcollective rpm install: # rpm -ihv --nodeps *.rpm Preparing... ### [100%] 1:mcollective-common ### [ 33%] 2:mcollective ### [ 67%] 3:mcollective-client ### [100%] note the 33% and 67% -- there's an error somewhere? Forrest -- 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: Using Mcollective with Enterprise Ruby
- Original Message - Here's the output from the mcollective rpm install: # rpm -ihv --nodeps *.rpm Preparing... ### [100%] 1:mcollective-common ### [ 33%] 2:mcollective ### [ 67%] 3:mcollective-client ### [100%] note the 33% and 67% -- there's an error somewhere? No, it installed 3 rpms. The first was a 1/3 of the progress the 2nd 2/3 and so forth. -- 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 CA expired
On Tue, 14 Jun 2011 17:01:20 +0200, j...@squirk.org wrote: hi, my puppet CA expired. Anyone knows how to solve the problem and extend the validity of the CA ? I mean without recreating one and going on each node to change the certs (that is what puppet is made to prevent, going to each node ^^) regards, Jean. Pretty sure you can't actually extend the validity of the CA cert. Unfortunately, I don't think there's much that can be done at this point without touching each node. I did open up #7962[1] so we can work out exactly what the safety net should look like to help prevent this from happening to other people. [1] http://projects.puppetlabs.com/issues/7962 -- Jacob Helwig signature.asc Description: Digital signature
Re: [Puppet Users] Problem with usage of arrays
Talking a bit through my hat here.. but:
On 11-06-16 05:36 AM, Roband wrote:
i can't use array in puppet. Here is my codesnipplet:
$callapidata = [ 'wert1','wert2']
notice $callapidata[1]
try something like the following instead of the second line:
notice { $callapidata[1]: }
--
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.
Re: [Puppet Users] puppet CA expired
What's the length of time on the CA cert? -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Thu, Jun 16, 2011 at 10:40 AM, Jacob Helwig ja...@puppetlabs.com wrote: On Tue, 14 Jun 2011 17:01:20 +0200, j...@squirk.org wrote: hi, my puppet CA expired. Anyone knows how to solve the problem and extend the validity of the CA ? I mean without recreating one and going on each node to change the certs (that is what puppet is made to prevent, going to each node ^^) regards, Jean. Pretty sure you can't actually extend the validity of the CA cert. Unfortunately, I don't think there's much that can be done at this point without touching each node. I did open up #7962[1] so we can work out exactly what the safety net should look like to help prevent this from happening to other people. [1] http://projects.puppetlabs.com/issues/7962 -- Jacob Helwig -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQGcBAEBAgAGBQJN+kAOAAoJEHJabXWGiqEBAQ8L/RVhorA/f49gilPW26X82BID aGYWFajNg5oBI1OtrieA9J//qNe9HRUUy8xWhq+S+B69FoQ4hU6ocfTH1eXDB8BN NM1rwuuqLpTvn1Gguxs3qTMPNyUEqMwugesH1XE7MOUH7XE10SgWqZwBpVpiJBPe cMctwUbgN6CfLD1F+wWKfuv9n1L4NvS5AcXj2WjgHbAjAAZx50m3gGIni5U6gF4+ GTRRxABtAEv0atsvUUO8kxecBhR1N+ZCbQAhk5PcJnKD5CW+7vqxxoC+K0D7BZNZ bRKk69IyG/ZFZnMbnzPNdYY2Ol9HE4ClnyydUq7r4uNdG5DbLg5sCPSgZXgAJRzt l5N3k4uNSWmnRco5zFmRAxV7YfzSu6o8ZueC07yiu8EeGDpEVWPg29esqUSm7Uqw 47s2uENGJ2mRr/NfN96YsMjPm2+leKUa37/YcQTdfswdQdkCNGyt/kt5fmncSnYX n2DwQ1CmHNQp1gf3wUzSqsIJmlEBKfgSQnTbIyAHBQ== =oopZ -END PGP SIGNATURE- -- 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 CA expired
5 years, IIRC. -- Jacob Helwig On Thu, 16 Jun 2011 11:03:49 -0700, Nathan Clemons wrote: What's the length of time on the CA cert? On Thu, Jun 16, 2011 at 10:40 AM, Jacob Helwig ja...@puppetlabs.com wrote: On Tue, 14 Jun 2011 17:01:20 +0200, j...@squirk.org wrote: hi, my puppet CA expired. Anyone knows how to solve the problem and extend the validity of the CA ? I mean without recreating one and going on each node to change the certs (that is what puppet is made to prevent, going to each node ^^) Pretty sure you can't actually extend the validity of the CA cert. Unfortunately, I don't think there's much that can be done at this point without touching each node. I did open up #7962[1] so we can work out exactly what the safety net should look like to help prevent this from happening to other people. [1] http://projects.puppetlabs.com/issues/7962 signature.asc Description: Digital signature
Re: [Puppet Users] puppet CA expired
Thanks. I think having to go out across the board once every 5 years is quite acceptable, although advance warning from the master that it's going to happen would definitely be a good thing. Jean: Kudos to running Puppet for 5 years! :) -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Thu, Jun 16, 2011 at 11:09 AM, Jacob Helwig ja...@puppetlabs.com wrote: 5 years, IIRC. -- Jacob Helwig On Thu, 16 Jun 2011 11:03:49 -0700, Nathan Clemons wrote: What's the length of time on the CA cert? On Thu, Jun 16, 2011 at 10:40 AM, Jacob Helwig ja...@puppetlabs.com wrote: On Tue, 14 Jun 2011 17:01:20 +0200, j...@squirk.org wrote: hi, my puppet CA expired. Anyone knows how to solve the problem and extend the validity of the CA ? I mean without recreating one and going on each node to change the certs (that is what puppet is made to prevent, going to each node ^^) Pretty sure you can't actually extend the validity of the CA cert. Unfortunately, I don't think there's much that can be done at this point without touching each node. I did open up #7962[1] so we can work out exactly what the safety net should look like to help prevent this from happening to other people. [1] http://projects.puppetlabs.com/issues/7962 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQGcBAEBAgAGBQJN+kbcAAoJEHJabXWGiqEBIgAL/0RX6X/eUll4EZCCZWWaEdby +fL9LQvyEPV/IiKeafpbn3Kct3FKIFEgMWOH7xubgp0x36u7jMCmDh4MXiFGOEPL BzNyLxPhkTQPG6Ml44INaiQ6wshdIlqFe3HfjtxlQZP/CSVBbPMBIcVwpgaAA6n8 sJidtfSYPfltbaRB2XMKpIg+ltMG4SEJvCndPBumPZjbrOKsOd4HHcL4MGdp7ump ryPj2E9+PXFZ/TZ+oNPSn30v0fX1om/UCHqUelkr6/SJls9P68VWsM7hVIB5Jc4P 3MwhBWHOzKV+8C7KZsQcUW3qywRCIF3Rb/APM8Ikol7A/fMYQJYvD5QgeVBygoPx jwoPoIZAVaxuCXMyOvvaPegsoc0qAk09RlYQXX8EhzwM7NyiatTVojQCZTfecEnO diDRs5U/rpjZ2gxrMIGkJMImRKGIDl9e7D+ez1IwY0XyR6b2vYbroeKP8PTG/L/C PU6U6MQnzLQ6Eovl+JOifRVZA3+U1nCxNK3ErAopvw== =mnf2 -END PGP SIGNATURE- -- 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 CA expired
On Thu, Jun 16, 2011 at 11:12 AM, Nathan Clemons nat...@livemocha.comwrote: Thanks. I think having to go out across the board once every 5 years is quite acceptable, although advance warning from the master that it's going to happen would definitely be a good thing. Jean: Kudos to running Puppet for 5 years! :) As an FYI, 5years is the default. When you initially create a CA, you may use the ca_ttl setting to extend this longer. [master] ca_ttl = 20y -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.
[Puppet Users] sshd service enable on Ubuntu
Hello,
Could someone tell me how to use 'enable' on Ubuntu? I am not too
familiar with this OS, as I usually use CentOS. I am using Puppet
2.6.8.
The problem is that every time I try to use enable it causes the node to
appear as yellow on the puppet-dashboard:
notice enable changed 'false' to 'true'
/Stage[main]/Ssh::Service/Service[ssh]/enable
/etc/puppet/modules/ssh/manifests/service.pp11 2011-06-16 13:32
CDT
My CentOS systems don't have this problem when using the same module.
Here is my service.pp class:
class ssh::service {
if $operatingsystem == Ubuntu {
$daemonname = ssh
} else {
$daemonname = sshd
}
service { $daemonname:
ensure = running,
enable = true,
require = Class[ssh::config],
}
}
Thanks,
Matt
--
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 recipe to copy and execute a shell file
Hi all, I am new to puppet. I need a sample recipe to write/copy a shell file on puppet client. The shell file exists on puppet server. Once the file is written, I also want to execute it. I have tried using file resource with ensure command to copy at /etc but permission was denied and moreover with a different directory path (\tmp) it just created an empty file. Can anyone please help? Regards, A. -- 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: Using Mcollective with Enterprise Ruby
Alright, so when I install it this way, I still get errors, which indicates the installation may not be correct. Here's a log: # rpm -ihv --nodeps *.rpm warning: mcollective-1.2.0-5.el5.noarch.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 4bd6ec30 Preparing... ### [100%] 1:mcollective-common ### [ 33%] 2:mcollective ### [ 67%] 3:mcollective-client ### [100%] # mc-facts /usr/sbin/mc-facts:3:in `require': no such file to load -- mcollective (LoadError) from /usr/sbin/mc-facts:3 # head /usr/sbin/mc-facts == /usr/sbin/mc-facts == #!/usr/bin/env ruby require 'mcollective' if $0 =~ /mc\-(.+)$/ app_name = $1 if MCollective::Applications.list.include?(app_name) MCollective::Applications.run(app_name) else No, it installed 3 rpms. The first was a 1/3 of the progress the 2nd 2/3 and so forth. -- 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: Using Mcollective with Enterprise Ruby
- Original Message - Alright, so when I install it this way, I still get errors, which indicates the installation may not be correct. Here's a log: are these RPMs you built like I said you should build them yesterday? I dont think so. signature: NOKEY, key ID 4bd6ec30 -- 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: Using Mcollective with Enterprise Ruby
I verified that this is not getting confused with /usr/bin/ruby, which I removed also as a part of that test and removed/reinstalled mcollective. A gem would fit within the ruby paradigm. -- 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: Using Mcollective with Enterprise Ruby
Indeed, i was using the supplied RPMs. The ones I built seem to be
doing something, tho I need to get RabbitMQ running first before I can
test it. This error came up in the RPM build:
lib/mcollective/log.rb:83:79: Skipping require of dynamic string:
mcollective/logger/#{logger_type.downcase}_logger
Thanks.
On Jun 16, 3:22 pm, R.I.Pienaar r...@devco.net wrote:
- Original Message -
Alright, so when I install it this way, I still get errors, which
indicates the installation may not be correct. Here's a log:
are these RPMs you built like I said you should build them yesterday?
I dont think so.
signature: NOKEY, key ID 4bd6ec30
--
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] functions and environments
I got further into the problem thanks to your help.. but there's something else now. On 11-06-15 12:36 PM, Nigel Kersten wrote: Functions get executed master side, so even though they get delivered to the node, they need to be accessible on the master. oh, ok.. so I'd need to have that new plugin used by the master first? What version of Puppet are you running on the master and nodes? master: 0.25.4 node: 0.25.4 Ah. For that version, you'll need to make sure the function is in the libdir of the puppet master, as I believe that functions from environments weren't accessible to the master in 0.25.x that seems to have worked. I copied the files in the master's lib dir and it got further. However, I'm now stuck on another weirdness between environments: I get an error about some resource that gets redefined between the init.pp from the production environment and another manifest from the development environment called moduledir.pp in the puppet master's config I have: [main] logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run/puppet ssldir=/var/lib/puppet/ssl environment=production [...] [development] modulepath=/etc/puppet/modules-development:/etc/puppet/modules:/usr/share/puppet/modules I was expecting the declaration in the [development] section to mean that if modules are found in the first directory, then the other dirs are not inspected.. But apparently this is not the case. This could lead to some nasty bugs when testing things out with such a mixed environment. Is there a work around to make the other module of the same name in the /etc/puppet/modules directory not influence the development environment? -- 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.
Re: [Puppet Users] functions and environments
If you want your environments to never be able to affect one another then your module paths should not contain any common directories. On Thu, Jun 16, 2011 at 12:33 PM, Gabriel Filion lelu...@gmail.com wrote: I got further into the problem thanks to your help.. but there's something else now. On 11-06-15 12:36 PM, Nigel Kersten wrote: Functions get executed master side, so even though they get delivered to the node, they need to be accessible on the master. oh, ok.. so I'd need to have that new plugin used by the master first? What version of Puppet are you running on the master and nodes? master: 0.25.4 node: 0.25.4 Ah. For that version, you'll need to make sure the function is in the libdir of the puppet master, as I believe that functions from environments weren't accessible to the master in 0.25.x that seems to have worked. I copied the files in the master's lib dir and it got further. However, I'm now stuck on another weirdness between environments: I get an error about some resource that gets redefined between the init.pp from the production environment and another manifest from the development environment called moduledir.pp in the puppet master's config I have: [main] logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run/puppet ssldir=/var/lib/puppet/ssl environment=production [...] [development] modulepath=/etc/puppet/modules-development:/etc/puppet/modules:/usr/share/puppet/modules I was expecting the declaration in the [development] section to mean that if modules are found in the first directory, then the other dirs are not inspected.. But apparently this is not the case. This could lead to some nasty bugs when testing things out with such a mixed environment. Is there a work around to make the other module of the same name in the /etc/puppet/modules directory not influence the development environment? -- 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. -- 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 recipe to copy and execute a shell file
It sounds like you haven't set up the puppet fileserver yet. Choose a directory
that will hold files you want to copy to clients. I use /opt/files, so that's
what is in my example. Create fileserver.conf in the same directory as
puppet.conf and add these lines:
[files]
path /opt/files
allow *.client.domain
Put your shell file in the path you specified. Now you just need to set up a
file and exec resource. Note the source item in the file resource and the
require item in exec.
file { '/etc/shell_file':
ensure = present,
owner = 'root',
group = 'root',
mode = '0755',
source = 'puppet://puppet/files/shell_file',
}
exec { '/etc/shell_file': require = File['/etc/shell_file'] }
--
Peter M. Bukowinski
Systems Engineer
Janelia Farm Research Campus, HHMI
On Thursday, June 16, 2011 at 3:17 PM, annierana wrote:
Hi all, I am new to puppet. I need a sample recipe to write/copy a
shell file on puppet client. The shell file exists on puppet server.
Once the file is written, I also want to execute it. I have tried
using file resource with ensure command to copy at /etc but permission
was denied and moreover with a different directory path (\tmp) it just
created an empty file. Can anyone please help?
Regards,
A.
--
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
(mailto:puppet-users@googlegroups.com).
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
(mailto: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] functions and environments
Or what you might want to do is to create a specific common directory for code that should be shared, and per-environment directories which contain code that should not be shared. If you find that something should no longer be common, you then move it into the per-env directories as appropriate. -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Thu, Jun 16, 2011 at 12:42 PM, Aaron Grewell aaron.grew...@gmail.comwrote: If you want your environments to never be able to affect one another then your module paths should not contain any common directories. On Thu, Jun 16, 2011 at 12:33 PM, Gabriel Filion lelu...@gmail.comwrote: I got further into the problem thanks to your help.. but there's something else now. On 11-06-15 12:36 PM, Nigel Kersten wrote: Functions get executed master side, so even though they get delivered to the node, they need to be accessible on the master. oh, ok.. so I'd need to have that new plugin used by the master first? What version of Puppet are you running on the master and nodes? master: 0.25.4 node: 0.25.4 Ah. For that version, you'll need to make sure the function is in the libdir of the puppet master, as I believe that functions from environments weren't accessible to the master in 0.25.x that seems to have worked. I copied the files in the master's lib dir and it got further. However, I'm now stuck on another weirdness between environments: I get an error about some resource that gets redefined between the init.pp from the production environment and another manifest from the development environment called moduledir.pp in the puppet master's config I have: [main] logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run/puppet ssldir=/var/lib/puppet/ssl environment=production [...] [development] modulepath=/etc/puppet/modules-development:/etc/puppet/modules:/usr/share/puppet/modules I was expecting the declaration in the [development] section to mean that if modules are found in the first directory, then the other dirs are not inspected.. But apparently this is not the case. This could lead to some nasty bugs when testing things out with such a mixed environment. Is there a work around to make the other module of the same name in the /etc/puppet/modules directory not influence the development environment? -- 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. -- 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] Problem with usage of arrays
What version of puppet are you using? kbarber:~ ken$ puppet --version 2.6.8 kbarber:~ ken$ puppet -e '$callapidata = [ 'wert1','wert2'] notice $callapidata[1]' notice: Scope(Class[main]): wert2 notice: Finished catalog run in 0.01 seconds kbarber:~ ken$ ken. On Thu, Jun 16, 2011 at 10:36 AM, Roband andreas.hac...@universa.de wrote: Hi there, i can't use array in puppet. Here is my codesnipplet: $callapidata = [ 'wert1','wert2'] notice $callapidata[1] A puppetrun results in: Could not retrieve catalog from remote server: Error 400 on SERVER: can't convert String into Integer at /etc/puppet/myenv/modules/ uc4client/manifests/init.pp:41 on node testnode Thanks for your help. Greetings Roband -- 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: Facter 1.6.0rc1 -- License Change Included
Facter 1.6.0rc1 is a feature release containing fixes, updates and refactoring. This release is available for download at: http://puppetlabs.com/downloads/facter/facter-1.6.0rc1.tar.gz 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.6.0rc1: http://projects.puppetlabs.com/projects/facter/ Full Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki Text version included: -- # Facter 1.6.0rc1 Release Notes ## License Change Facter has moved to Apache 2.0 license This is in line with our proposed plan to change from the GPL license to Apache 2.0 for Puppet in 2.7.0 and Facter in 1.6.0. Please see this link for further explanation: https://groups.google.com/d/topic/puppet-users/NuspYhMpE5o/discussion ## Speed Improvements (#7670) Stop preloading all facts in the application If a requested fact isn't found in the same location as its name, we want to load all of the facts to find it. However, to simplify that, we were previously just preloading all the facts every time. Because requesting a fact now implicitly loads all facts if necessary, we can rely on that, providing results much more quickly in the case where facts do match their filenames. ## Fact Detection Improvements (#6728) Facter improperly detects openvzve on CloudLinux systems Make the openvz check for more than just the vz directory to be sure it's OpenVZ. Update the OpenVZ fact to be slightly more resilient in it's checking of OpenVZ, so it doesn't clash with CloudLinux's LVE container system. (#6740) facter doesn't always respect facts in environment variables On an OSX host: $ facter operatingsystem Darwin $ facter_operatingsystem=Not_Darwin facter operatingsystem Not_Darwin But on a linux/solaris host: $ facter operatingsystem CentOS $ facter_operatingsystem=Not_CentOS facter operatingsystem CentOS As the operatingsystem fact resolution for linux-based kernels has higher precedence than the environment variable as it has more matching confines than the value from the environment variable. This patch adds from_environment to the resolution mechanism, which makes the resolution have an artificially high weight by claiming the length of its confines array is 1 billion. ## Documentation (#5394) Document each Facter fact. Document all the builtin Facter facts in puppetdoc/rdoc format. This is laying the ground work for using a tool like puppet doc, or puppet describe but for facter, so you can see what a fact is for and how it resolves this. This is the leg work of documenting the actual facts, and the syntax of them may change in future. ## CHANGELOG Highlights 926e912 (#7670) Stop preloading all facts in the application 2255abe (#7670) Never fail to find a fact that is present 6b1cd16 (#6614) Update ipaddress6 fact to work with Ruby 1.9 21fe217 (#6612) Changed uptime spec to be endian agnostic 19f96b5 (#6728) Facter improperly detects openvzve on CloudLinux systems 5b10173 (#5135) Fix faulty logic in physicalprocessorcount 53cd946 Ensures that ARP facts are returned only on EC2 hosts bfa038d Fixed #6974 - Moved to Apache 2.0 license d56bca8 refactor the mechanism for allowing for resolution ordering to be influenced 9f4c5c6 (#6740) facter doesn't always respect facts in environment variables bfc16f6 (#2714) Added timeout to prtdiag resulution 3efa9d7 (#3856) Add virtualbox detection via lspci (graphics card), dmidecode, and prtdiag for Solaris and corresponding tests. Darwin case is not handled yet. 7c80172 (#6883) Update Facter install.rb to be slightly more informative. d31e3f9 (#5394) Document each Facter fact. d6967a0 (#6613) Switch solaris macaddress fact to netstat -- 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] functions and environments
On 11-06-16 03:47 PM, Nathan Clemons wrote: Or what you might want to do is to create a specific common directory for code that should be shared, and per-environment directories which contain code that should not be shared. If you find that something should no longer be common, you then move it into the per-env directories as appropriate. Oh ok ... I'll have to work something out then.. this is more complicated to use than I thought. Thanks everyone for all the help. -- 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.
Re: [Puppet Users] sshd service enable on Ubuntu
Hi,
You're probably hitting this bug or similar:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573551
Cheers,
Den
On 17/06/2011, at 4:52, Cashdollar, Matthew mcashdol...@randmcnally.com
wrote:
Hello,
Could someone tell me how to use 'enable' on Ubuntu? I am not too
familiar with this OS, as I usually use CentOS. I am using Puppet
2.6.8.
The problem is that every time I try to use enable it causes the node to
appear as yellow on the puppet-dashboard:
noticeenable changed 'false' to 'true'
/Stage[main]/Ssh::Service/Service[ssh]/enable
/etc/puppet/modules/ssh/manifests/service.pp112011-06-16 13:32
CDT
My CentOS systems don't have this problem when using the same module.
Here is my service.pp class:
class ssh::service {
if $operatingsystem == Ubuntu {
$daemonname = ssh
} else {
$daemonname = sshd
}
service { $daemonname:
ensure = running,
enable = true,
require = Class[ssh::config],
}
}
Thanks,
Matt
--
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] puppet CA expired
[master] ca_ttl = 20y Neat trick. By the time it expires you'll be gone! :P -- 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: Custom type sample?
On Jun 15, 10:42 pm, Nigel Kersten ni...@puppetlabs.com wrote: Did you find this document? http://projects.puppetlabs.com/projects/1/wiki/Development_Practical_... Thanks! I hadn't found that link earlier, however there are still quite a few bits missing to actually getting things to work in a real environment. To that end, I took that example and another using a backend Provider and created the following sample/stub module repository: https://github.com/chetan/puppet-custom_type_examples I hope that'll be of use to anyone else trying to create a custom type. chetan -- 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] dashboard ENC and parameterized classes
On Wed, Jun 15, 2011 at 07:48:50PM -0700, Ashley Gould wrote:
On Wed, Jun 15, 2011 at 06:13:52PM +0100, Ken Barber wrote:
Certainly works for me in a simplified example ... can you simplify
your example so it just does a notify?
class firewall_extras (
$services = undef,
) {
notify { msg: message = $services }
}
class myfirewall {
class { firewall_extras: services = $::firewall_services }
}
Ok, I did finally get a basic parameterized class to work from
dashboard ENC:
class firewall_extras($tcp_ports) {
notify { msg: message = $tcp_ports, }
}
class firewall_wrapper {
class { firewall_extras: tcp_ports = $::fw_tcp_ports, }
}
---
agould@pmlab02-vhost:/data/puppet/production
/usr/share/puppet-dashboard/bin/external_node unxslet01.ucop.edu
---
name: unxslet01.ucop.edu
parameters:
fw_tcp_ports: 22 9080 3000
classes:
- firewall_wrapper
- common::suse
unxslet01:~ # puppet agent -t
info: Retrieving plugin
info: Loading facts in adinfo
info: Loading facts in adinfo
info: Caching catalog for unxslet01.ucop.edu
info: Applying configuration version '1308273566'
notice: 22 9080 3000
notice: /Stage[main]/Firewall_extras/Notify[msg]/message: defined 'message' as
'22 9080 3000'
notice: Finished catalog run in 7.64 seconds
But what I really want is to use a param class to override variables in
a base class. Below is a stripped version. the value for the param
I set in dashboard shows up in the override class but never makes it
to the base class.
# Base class
#
class firewall {
define firewall_conf (
$fw_services_ext_tcp = 22
) {
file { /etc/sysconfig/SuSEfirewall2:
content = template(firewall/SuSEfirewall2.erb),
}
notify { msg1: message = $fw_services_ext_tcp, }
}
# Implement default firewall setup
firewall_conf {default: }
}
# Override class
#
class firewall_override ( $tcp_ports ) inherits firewall {
# modify default firewall setup
Firewall::Firewall_conf[default] {
fw_services_ext_tcp = $tcp_ports,
}
notify { msg0: message = $tcp_ports, }
}
# Wrapper class for Dashboard
#
class firewall_wrapper {
class { firewall_override: tcp_ports = $::fw_tcp_ports, }
}
agould@pmlab02-vhost:/data/puppet/production
/usr/share/puppet-dashboard/bin/external_node unxslet01.ucop.edu
---
name: unxslet01.ucop.edu
parameters:
fw_tcp_ports: 22 9080 3000
classes:
- firewall_wrapper
- common::suse
- firewall
unxslet01:~ # puppet agent -t
info: Retrieving plugin
info: Loading facts in adinfo
info: Loading facts in adinfo
info: Caching catalog for unxslet01.ucop.edu
info: Applying configuration version '1308273896'
notice: 22 9080 3000
notice: /Stage[main]/Firewall_extras/Notify[msg]/message: defined 'message' as
'22 9080 3000'
notice: 22
notice:
/Stage[main]/Firewall/Firewall::Firewall_conf[default]/Notify[msg1]/message:
defined 'message' as '22'
notice: Finished catalog run in 6.76 seconds
--
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: Custom type sample?
Chetan wrote: On Jun 15, 10:42 pm, Nigel Kerstenni...@puppetlabs.com wrote: Did you find this document? http://projects.puppetlabs.com/projects/1/wiki/Development_Practical_... Thanks! I hadn't found that link earlier, however there are still quite a few bits missing to actually getting things to work in a real environment. To that end, I took that example and another using a backend Provider and created the following sample/stub module repository: https://github.com/chetan/puppet-custom_type_examples I hope that'll be of use to anyone else trying to create a custom type. This might also help: http://www.kartar.net/2010/02/puppet-types-and-providers-are-easy/ James -- James Turnbull Puppet Labs 1-503-734-8571 -- 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 dashboard
On Jun 14, 2011, at 11:56 AM, Craig White wrote: I am using Ubuntu 10.04 and ruby-enterprise (not ubuntu ruby) and installed puppet via gem. How can I install puppet-dashboard if I don't see a gem available and if I use the ubuntu package, i get the whole slop of ruby packages sucked in (which i am trying to avoid)? Frankly, I just let it install the packages because they won't do any harm. (I'm assuming you only use ruby for puppet) Here's how I got dashboard working: (Partly pesudo-code and I might be forgetting a step or two) get ruby-enterprise-1.8.7-2011.03.tar.gz untar and install ruby-enterprise-1.8.7-2011.03 install puppet-dashboard from the repository put this file in /etc/apache2/mods-avaliable/passengeree.load: LoadModule passenger_module /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/passenger-2.2.15/ext/apache2/mod_passenger.so PassengerRoot /opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/passenger-2.2.15 PassengerRuby /opt/ruby-enterprise-1.8.7-2010.02/bin/ruby a2dismod ruby a2dismod passenger a2enmod passengeree /etc/apache2/sites-enabled/puppet-dashboard: # Based on http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger Listen 3000 VirtualHost *:3000 # Passenger options that can be set in a virtual host # configuration block. PassengerHighPerformance on PassengerStatThrottleRate 120 PassengerMaxPoolSize 3 PassengerPoolIdleTime 300 PassengerUseGlobalQueue on RailsAutoDetect On RailsEnv production DocumentRoot /usr/share/puppet-dashboard/public/ Directory /usr/share/puppet-dashboard/public/ Options None AllowOverride AuthConfig Order allow,deny allow from all /Directory ErrorLog /var/log/apache2/puppet-dashboard_error.log LogLevel warn CustomLog /var/log/apache2/puppet-dashboard_access.log combined /etc/mysql/conf.d/innodb_file_per_table.cnf: #Without this isn't almost impossible to reclaim space from dashboard when reports are removed [mysqld] innodb_file_per_table=true service mysql restart cd /usr/share/puppet-dashboard/ Run the proper rake task to create and populate the DBs service apache2 restart -- 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.
