Re: [Puppet Users] Re: hiera-eyaml-gpg gives strange error
Am 30.01.2014 08:05, schrieb Dirk Heinrichs: Am 29.01.2014 17:27, schrieb Simon Hildrew: Can you raise an issue on the github project at https://github.com/sihil/hiera-eyaml-gpg with details on how you produced the error? Sure. https://github.com/sihil/hiera-eyaml-gpg/issues/11 Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com mailto:d...@recommind.com *Skype*: dirk.heinrichs.recommind www.recommind.com http://www.recommind.com http://www.recommind.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52EA06A5.5030308%40recommind.com. For more options, visit https://groups.google.com/groups/opt_out. inline: Logo.gif
Re: [Puppet Users] howto determine a users homedir in a class file
You can change the path to authorized_keys as it is done in my ssh puppet module (http://forge.puppetlabs.com/thbe/ssh). The next version of this module will give you the possibility to deploy usernames with keys as parameters but I'm not sure when I'll find time to implement this. Till now you have to put the username key files manually in /etc/ssh.d/ Regards Thomas 2014-01-30 Andrew andrewgray1...@gmail.com: So ... I am tasked with managing ssh keys for which I want to use puppet to do the deployment. I dont know ahead of time which users will using/assigned keys so, my question is. how to determine the homedir of any user? is there a variable present with this info without resorting to an exec? Not all users have /home/$USER homedirs, (eg apache=/var/www, puppet=/var/lib/puppet), I need to create a .ssh dir in the users homedir and copy some private keys in there. The authorized_keys type includes a user property, so the public key is easy. kinda stumped ... Any ideas? Thanks in advance. Regards, Andrew -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1944e04e-e98c-4cb6-8e3f-e470c88ce6ad%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- Linux ... enjoy the ride! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAELoU1MBZ6dO9Sz_oAwK%2B%3Dd1JfyYf3ysovGfbSgTW%2B9uLOv5ZA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Reg : War deployment with Puppet
Must admit i would be interested in seeing what other peoples approaches has been for this, we have been thinking about going down the route of getting the war files and any relevant library files put into a rpm/deb package and getting puppet to install the rpm though the OS package manager. Paul C. On Thursday, 30 January 2014 06:54:26 UTC, krishna bhaskara rao wrote: Hi, Can any one share me sample snippets to deploy war in tomcat. if deployment fails, how to rollback. With Regards, Krishna. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/241ed902-f5c6-4f83-a2de-85a13b1948ed%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: ody/pkginventory problem / How do _you_ get a listing of all packages installed on a system?
Greetings,
Thanks for the response.
The pkginventory is already doing this inside of util/pkg.rb:
rpm -qa --qf %{NAME}\t%{VERSION}-%{RELEASE}
I am fully aware of how multiple kernels work. As stated, the kernel was
just an example. I need/want every package installed returned to me and the
version of the pkginventory code currently listed in the forge is
nondeterministic on what package version is returned when multiple versions
exist. This is the problem for me.
We have been running our mods in production for a few days now and things
are running well.
Thanks!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/91bc1223-9c0a-40ce-886f-cc42685f7cda%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What is the best replacement for Puppet Dashboard ?
I use puppetboard too - it's really great, and much lighter on the database. A big improvement on puppet-dashboard. Only one issue remains, that means I must keep my puppet-dashboard.. There's a bug in the puppetdb-terminus - so nodes which manifest fails compilation fails - does NOT get a report send to puppetboard, so you can't catch failing compilation failures :( Odlly enough, puppet does send the http reports when there's a failed compilation - so puppet-dashboard knows about them. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/008d0d13-10f1-496c-8589-a451df72a0b1%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] howto determine a users homedir in a class file
Here we go:
Part 1: Custom Fact (modules/users/lib/facter/user_home.rb)
require 'etc'
Etc.passwd { |user|
Facter.add(home_#{user.name}) do
setcode do
user.dir
end
end
}
When you are creating a user, you have access to the homedir. I use a define
that has default parameters of
$userhome = /home/${title},
$username= $title,
You can override the userhome value. The combination of resources I found to
work is as follows:
exec { mkdir-${username}:
command = /bin/mkdir -p ${homedirdir},
unless = test -d ${homedirdir},
}
file { $userhome:
ensure = directory,
require = [
User[$username],
Exec[mkdir-${username}],
]
}
file { ${userhome}/.ssh:
ensure = directory,
require = User[$username],
}
file { ${userhome}/.ssh/authorized_keys:
ensure = present,
require = File[${userhome}/.ssh],
}
ssh_authorized_key { ${username}_rsa_key:
ensure = $ensure,
user = $username,
key= .,
type = 'ssh-rsa',
}
Now, for putting keys in other user homedirs - like a role account for
restricted ssh - using only the role account login and the user account login,
$home_fact = home_${role_account_login}
$homedir = inline_template(%= scope.lookupvar('::${home_fact}') %)
User[$role_account_login]-
File [ ${homedir}/.ssh/authorized_keys] -
ssh_authorized_key {
${user_account_login}_rsa_key_for_${role_account_login}:
ensure = $ensure,
key = ,
type = 'ssh-rsa',
user = $role_account_login,
}
The chaining was discovered thru some long and painful trial and error.
Also, there is the matter of the options parameter for ssh_authorized_key,
but I did not want to complicate this too much.
This should get you moving forward.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin
Hobbes)
On Jan 29, 2014, at 11:04 PM, Andrew andrewgray1...@gmail.com wrote:
So ...
I am tasked with managing ssh keys for which I want to use puppet to do the
deployment.
I dont know ahead of time which users will using/assigned keys so, my question
is.
how to determine the homedir of any user? is there a variable present with this
info without resorting to an exec?
Not all users have /home/$USER homedirs, (eg apache=/var/www, puppet=/var/lib/puppet),
I need to create a .ssh dir in the users homedir and copy some private keys in there.
The authorized_keys type includes a user property, so the public key is easy.
kinda stumped ...
Any ideas?
Thanks in advance.
Regards,
Andrew
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/1944e04e-e98c-4cb6-8e3f-e470c88ce6ad%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/26ebf32b-3cb0-4aca-877e-b5e16a3e5f99%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] SSL issues - certificate verify failed
Hi, I am having similar issue, cant figure out why. Can any one help me with this ?? thanks, Teja. On Friday, August 10, 2012 5:29:27 AM UTC-7, Axel Bock wrote: hm, nevermind, I somehow solved it. although I'm not (yet) sure how. It involved a lot of restarting and deleting :) thanks anyways! Axel. 2012/8/10 Axel Bock axel...@arbeitsagentur.de javascript: Hello readers, I have this little issue that my puppet client refuses to do anything because of SSL validation errors. Maybe I'll just post dump of what happens, that makes it clear I hope. Does anyone have a suggestion why that might happen? what I already checked: On the master: - Puppet and puppetmaster is running - Something is listening on Port 8140 (although I cannot telnet-connect to it, it closes immediately for whatever reason) - in /var/lib/puppet/ssl: find . -type f -delete On the client: - in /var/lib/puppet/ssl: find . -type f -delete I would appreciate any help that's available ... thanks greetings! Axel. ... and now the little dump: (CLIENT) *root@l1311022:/var/lib/puppet/ssl$* *puppet agent --test* info: Creating a new SSL key for l1311022.our.domain.de warning: peer certificate won't be verified in this SSL session (2x) info: Creating a new SSL certificate request for l1311022.our.domain.de info: Certificate Request fingerprint (md5): 19:60:00:FE:95:D8:1B:D1:7A:0A:08:C1:1F:E1:94:4E warning: peer certificate won't be verified in this SSL session (3x) Exiting; no certificate found and waitforcert is disabled (SERVER) *l1215022:/var/lib/puppet/ssl # pca -l* notice: Signed certificate request for ca notice: Rebuilding inventory file l1311022.our.domain.de(19:60:00:FE:95:D8:1B:D1:7A:0A:08:C1:1F:E1:94:4E) *l1215022:/var/lib/puppet/ssl # pca -s --all* notice: Signed certificate request for l1311022.our.domain.de notice: Removing file Puppet::SSL::CertificateRequest l1311022.our.domain.de at '/var/lib/puppet/ssl/ca/requests/l1311022.our.domain.de.pem' l1215022:/var/lib/puppet/ssl # (CLIENT) *root@l1311022:/var/lib/puppet/ssl$ puppet agent --test* warning: peer certificate won't be verified in this SSL session info: Caching certificate for ca warning: peer certificate won't be verified in this SSL session info: Caching certificate for l1311022.our.domain.de info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed err: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed Could not retrieve file metadata for puppet:// l1215022.our.domain.de/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run err: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed The config files look like this: (CLIENT) [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = /var/lib/puppet/ssl modulepath = /etc/puppet/modules:/opt/puppet/share/puppet/modules [agent] certname = l1311022.our.domain.de server = l1215022.our.domain.de report = true graph = true pluginsync = true classfile = $vardir/classes.txt localconfig = $vardir/localconfig (SERVER) [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = /var/lib/puppet/ssl certname = l1215022.our.domain.de [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ToaPaY7mtgwJ. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ff1a8174-be84-4f8a-afe0-fa0f7cd16d1c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Choo choo here comes the FOSDEM train
Hi everyone, I've booked at Sogno d’Italia for approx. 30 people. They are expecting us somewhere between 19h00 and 19h20 (that's 7PM for the Americans). I've changed the Eventbrite event to allow tickets up to 35 which means there's about 15 places left if you want to join in. So, if you want food, please register :). See you soon! -- Daniele Sluijters On Thursday, 23 January 2014 11:27:36 UTC+1, Johan De Wit wrote: On 01/23/2014 11:18 AM, Daniele Sluijters wrote: Hi everyone, This is starting to shape up nicely. We've got a group of about twenty people registered now, I'm guessing a few more will join us so I'm thinking we'll end up with about 30 people, which is good. As you all know, the FOSDEM beer party is taking place the night before in Delirium. If you haven't been to Delirium, even if you don't like beer, just go and have a look around. The sheer amount of beer available is mind-blowing. If you're wondering about the local cuisine, the Huffington Post is here to help you: http://www.huffingtonpost.com/2014/01/21/belgian-cuisine-food_n_4617498.html Johan: Do we have an idea yet where we can crash with 20-30 people? Not really, maybe we should send out some scouts, and do a reservation in the neighbourhood ? Previous year, seems the puppeteers took over an italian restaurant :) Sogno D'italia. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3cda1ead-993b-4b9d-9f50-75198552c88e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Johan De Wit Open Source Consultant Red Hat Certified Engineer (805008667232363) Puppet Certified Professional 2013 (PCP006) _ Open-Future Phone +32 (0)2/255 70 70 Zavelstraat 72 Fax +32 (0)2/255 70 71 3071 KORTENBERG Mobile+32 (0)474/42 40 73 BELGIUM http://www.open-future.be _ Next Events: Puppet Fundamentals Training | http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february Puppet Intruction Course | http://www.open-future.be/puppet-introduction-course-7th-february Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-february Zabbix for Large Environments Training | http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february Subscribe to our newsletter | http://eepurl.com/BUG8H -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8708e021-0490-4632-80f5-76c5db969d49%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Puppet Dashboard Groups
Hi, Thanks for the reply Richard, I will try this and share the details! -Kaustubh On Wednesday, January 29, 2014 2:13:13 PM UTC-5, Richard Berwald wrote: I recently faced the same challenge. I did not want to group by osfamily but by another fact. I came up with this solution: 1) retrieve a list from PuppetDB in format 'nodename:factvalue' for all nodes using puppetdbquery on a puppetmaster (sudo puppet query facts --facts=factname some query that resolved to true) 2) retrieve the group list from the console with 'rake nodegroup:list' 3) Compare the existing groups with the groups based upon the values from the fact and create missing groups with 'nodegroup:add[groupname] 4) For each (already) existing group, get all members of the group with 'nodegroup:group_list[groupname]' 5) Compare the nodenames that are already in the group with the list of nodenames from PuppetDB, and add missing nodes of a group with node:group[nodename,standardgroup:groupname] I came to this solution because rake calls felt relatively slow (about 7 seconds per call) on our platform and I wanted it to be able to potentially scale to thousands of nodes. This runs once a night from an old fashioned cron. Richard On Monday, January 27, 2014 3:16:09 PM UTC+1, kaustubh chaudhari wrote: Hi, I was looking for a way to group the servers dynamically. Eg: create a Windows Group and all the existing nodes and new nodes should be part of Windows group. I edit a group and then add each server, but practically its not possible with 2k servers in all!! Is there a way to do that? -Kaustubh -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e584314b-c88c-4dea-a55a-9c2f9eedbde0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Reg : War deployment with Puppet
we used to package into rpms as well On 30 January 2014 11:50, PaulC paul.can...@gmail.com wrote: Must admit i would be interested in seeing what other peoples approaches has been for this, we have been thinking about going down the route of getting the war files and any relevant library files put into a rpm/deb package and getting puppet to install the rpm though the OS package manager. Paul C. On Thursday, 30 January 2014 06:54:26 UTC, krishna bhaskara rao wrote: Hi, Can any one share me sample snippets to deploy war in tomcat. if deployment fails, how to rollback. With Regards, Krishna. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/241ed902-f5c6-4f83-a2de-85a13b1948ed%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACzr%3DFcrk1udFVCQTYKF%2BkPPou-1%2Bh9JVpgUY8RyavOjjJb9xQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Error Message: Could not set present on ensure: Function not implemented
On Wednesday, January 29, 2014 2:00:28 PM UTC-6, Jon Jaroker wrote: Hello, Would anyone know what the error message Could not set present on ensure: Function not implemented means. It is appearing in Puppet 2.7.13 on a File resource type. The --debug flag does not give any hints. [...] Any suggestions on how to troubleshoot this? That's certainly an unhelpful message. I suspect it really means an unanticipated error occurred while trying to sync the target file's 'ensure' property. Since you are ensuring present, Puppet would only be trying to do something with the ensure property if [it thought that] the file does not yet exist. Some things to look at: 1. Unless you want to accommodate the possibility that the target file is a symlink, I would ensure 'file' rather than 'present'. That is unlikely to resolve the problem, however. 2. Check whether the File's target directory exists. 3. Check whether the File's target directory is readable and writable to the Puppet agent. Check that every directory in the path to it is readable. Even with the agent running as a privileged user such as root, there are still ways that it might be denied access (e.g. SELinux, root squashing [for network filesystems]). John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/882a1699-d99c-43b8-af80-e3c0da5616b5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Node Corruption
On Wednesday, January 29, 2014 7:16:45 PM UTC-6, Doug_F wrote: All, I have a problem where I was mucking about in a Module which failed. One of my Debian nodes I was testing it on started acting funky. Now my single Debian node is getting some weird module activity. Classes defined by $::kernel fact are defined properly. Templates based off $::osfamily fact seem to fail to RedHat. I could be that that is the first in most of my case statements but I don't know. I have commented out the offending module. I have at least 2 other debian nodes are still getting correct catalogues. I have tried rolling back the node to its first install and reinstalling puppet. I have cleaned out the Certs on both client and master. I have restarted the Master and puppetdb. curl localhost:8080/v3/nodes/deb-vm.part.net/facts/osfamily ... name : osfamily, value : Debian ... Anyone know of some temp / state file on the master that may need to be removed / fixed? If you know of other troubleshooting steps that would be great as well. The problem is more likely to be outside Puppet than inside. Something has been changed on the node so that Facter no longer computes the 'osfamily' fact correctly. That probably means it also does not compute the 'operatingsystem' fact correctly. It might be illuminating to insert one or more Notify resources into your manifests to tell you what values the problem node is actually reporting for those facts. Looking at the Facter source, however, it seems pretty likely that the problem revolves around the file /etc/debian_version having been removed from the node. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5a71d50c-7661-4aca-b5b9-ed237432f181%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Node Corruption
On Thursday, January 30, 2014 8:22:35 AM UTC-6, jcbollinger wrote: Looking at the Facter source, however, it seems pretty likely that the problem revolves around the file /etc/debian_version having been removed from the node. Hmm. Having re-read the problem description, I am less confident in my first response. It's still worthwhile to check /etc/debian_version, though, and to verify more directly (i.e. via a Notify) what fact values the master is receiving for key facts. I stand by my assertion that the proximal issue is more likely outside Puppet than inside. If /etc/debian_version is not related to the problem, then it might be helpful to see one of the templates that is behaving unexpectedly. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c22078c6-ecba-42d8-9aff-55943b35e49c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Choo choo here comes the FOSDEM train
Hi, Awesome, thanks Daniele! I have just registered for the dinner, though I'm still not 100% sure I'll be there (there's an air controller strike, argh!). But I'll be lurking around, like (almost) every year :-) For a photo : https://github.com/thias I'll be mostly interested in discussing anything related to modules and the Forge, but if any official Puppet Labs representatives are there, I'd also be interested in getting in touch about consulting in Spain and training. Cheers, Matthias On Thu, 30 Jan 2014 05:33:29 -0800 (PST) Daniele Sluijters daniele.sluijt...@gmail.com wrote: Hi everyone, I've booked at Sogno d’Italia for approx. 30 people. They are expecting us somewhere between 19h00 and 19h20 (that's 7PM for the Americans). I've changed the Eventbrite event to allow tickets up to 35 which means there's about 15 places left if you want to join in. So, if you want food, please register :). See you soon! -- Matthias Saou ██ ██ ██ ██ Web: http://matthias.saou.eu/ ██ Mail/XMPP: matth...@saou.eu ██ ██ GPG: 4096R/E755CC63██ ██ ██ 8D91 7E2E F048 9C9C 46AF ██ ██ ██ ██ 21A9 7A51 7B82 E755 CC63 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140130154806.664bec64%40r2d2.marmotte.net. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] run or execute only by call with manually running agent
Hi all,
I have an install routine that should never be executed by puppet
automatically.
But I would like to execute it sometimes by running something like this:
puppet agent -t --ignoreschedules --tags never
One idea is to create a schedule
class never{
schedule { 'never':
repeat = 0,
}
exec
}
or
class never{
schedule { 'never':
periode = never,
}
exec
}
What is a good solution?
Regards,
Andreas
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/1feb194c-3ebf-41f8-9aff-f743783a2114%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: checking is package is installed ?
Hi, I think the explaination of Gareth is wrong. absend will uninstall a package I am using absend to uninstall package and here is a web site about that. http://www.puppetcookbook.com/posts/remove-package.html Best regards Andreas -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b93a1321-01ea-4c20-b15e-ac07a35e5bd3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: checking is package is installed ?
On 30 January 2014 15:41, Andreas Dvorak andreas.dvo...@gmail.com wrote: Hi, I think the explaination of Gareth is wrong. No, he's exactly right. And please be careful with your spelling...it's 'absent', not 'absend'. Your puppet manifests are not scripts/sets of instructions. They define what end-state you want the node that applies the resource to be in when the agent has finished running. i.e. by specifying 'absent' in your package resource you're not explicitly telling puppet to uninstall the package. The package may already not be present, in which case puppet won't do anything at all (it has nothing to do). If the package is present though, puppet will indeed uninstall it. Kind Regards, Matt. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKUTv3KpqcVvX%2B35ynQmJqHFovLRWswyUpWdRmqcYnVuEb9dxQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Copy files after Apache install...but only once.
Hi,
I am trying to install Apache with a default set of config files. I have
the following class:
class base_apache {
case $operatingsystem {
windows: {
file { 'apache_installer_package':
path= 'D:/Downloads/Puppet/',
ensure = directory,
source = 'puppet:///files/Apache-Installers/',
recurse = true,
purge = false,
source_permissions = ignore,
replace = no,
before = Package['Apache HTTP Server 2.2.25']
}
package { 'Apache HTTP Server 2.2.25':
ensure = installed,
source =
'D:\\Downloads\\Puppet\\httpd-2.2.25-win32-x86-openssl-0.9.8y.msi',
install_options = {'INSTALLDIR' =
'D:\Apache2.2','SERVICENAME' = 'Apache.2.2','ALLUSERS' = 1},
before = File['default_apache_config']
}
file { 'default_apache_config':
path= D:/Apache2.2/conf,
ensure = directory,
source = 'puppet:///files/Apache2.2/conf',
recurse = true,
purge = true,
source_permissions = ignore,
replace = yes,
}
}
}
}
As you can see, I am installing Apache using MSI package and then copying
over the default set of configs. This works, however If I make a
modification to the config files, Puppet will notice that it has changed
and overwrite it on the next run.
What I want it to do if copy the files ONLY IF the package directive had
to install Apache. If it already existed on the server and it didn't do
anything, don't do the File['default_apache_config'] bit... I could set
replace = no but then it wouldn't work on the first one run either as the
installer creates its own default set of configs.
Is this possible or do I have to be a bit cleverer than that?
Thanks
Alex
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/63463e7d-b280-43e2-9ebc-6e87eb43635a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: [Puppet Users] circular dependency between user/home and parent directory owned by that user
Hi,
Simple :
User[‘david’]-File[‘/haha’]
Ref: http://docs.puppetlabs.com/learning/ordering.html
Dominique Arpin
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
De : puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] De la
part de David Portabella
Envoyé : 30 janvier, 2014 11:28
À : puppet-users@googlegroups.com
Objet : [Puppet Users] circular dependency between user/home and parent
directory owned by that user
For illustrating purposes,
I need a david user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by david.
this code does not work,
because user requires the /haha directory, and the /haha directory requires the
david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
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.commailto:puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mise en garde concernant la confidentialité : Le présent message, comprenant
tout fichier qui y est joint, est envoyé à l'intention exclusive de son
destinataire; il est de nature confidentielle et peut constituer une
information protégée par le secret professionnel. Si vous n'êtes pas le
destinataire, nous vous avisons que toute impression, copie, distribution ou
autre utilisation de ce message est strictement interdite. Si vous avez reçu ce
courriel par erreur, veuillez en aviser immédiatement l'expéditeur par retour
de courriel et supprimer le courriel. Merci!
Confidentiality Warning: This message, including any attachment, is sent only
for the use of the intended recipient; it is confidential and may constitute
privileged information. If you are not the intended recipient, you are hereby
notified that any printing, copying, distribution or other use of this message
is strictly prohibited. If you have received this email in error, please notify
the sender immediately by return email, and delete it. Thank you!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/C2F62CDF5915D0458F0528664315BAE732344C13%40MTL1EXC01.scqmtl.loto-quebec.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] circular dependency between user/home and parent directory owned by that user
For illustrating purposes,
I need a *david* user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by *david*.
this code does not work,
because user requires the /haha directory, and the /haha directory requires
the david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: checking is package is installed ?
Hi, If you want to check if a server is compliant with a defined end state, you can set noop=true in the resources, or just run puppet in noop mode. Regards El 30/01/2014 16:51, Matthew Burgess matthew.2.burg...@gmail.com escribió: On 30 January 2014 15:41, Andreas Dvorak andreas.dvo...@gmail.com wrote: Hi, I think the explaination of Gareth is wrong. No, he's exactly right. And please be careful with your spelling...it's 'absent', not 'absend'. Your puppet manifests are not scripts/sets of instructions. They define what end-state you want the node that applies the resource to be in when the agent has finished running. i.e. by specifying 'absent' in your package resource you're not explicitly telling puppet to uninstall the package. The package may already not be present, in which case puppet won't do anything at all (it has nothing to do). If the package is present though, puppet will indeed uninstall it. Kind Regards, Matt. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKUTv3KpqcVvX%2B35ynQmJqHFovLRWswyUpWdRmqcYnVuEb9dxQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF_B3ddHY20pPZA8q3eQrT29ijKKHop3H9Vx3RTXM%3Drqc0dn-A%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] circular dependency between user/home and parent directory owned by that user
again,
it is a circular dependency.
what you are saying is to first create user and then file.
but to create the user, we need the file first also.
On Thursday, January 30, 2014 5:31:10 PM UTC+1, Arpin Dominique (Nter)
wrote:
Hi,
Simple :
User[‘david’]-File[‘/haha’]
Ref: http://docs.puppetlabs.com/learning/ordering.html
*Dominique Arpin*
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
*De :* puppet...@googlegroups.com javascript: [mailto:
puppet...@googlegroups.com javascript:] *De la part de* David Portabella
*Envoyé :* 30 janvier, 2014 11:28
*À :* puppet...@googlegroups.com javascript:
*Objet :* [Puppet Users] circular dependency between user/home and parent
directory owned by that user
For illustrating purposes,
I need a *david* user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by
*david*.
this code does not work,
because user requires the /haha directory, and the /haha directory
requires the david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
Mise en garde concernant la confidentialité : Le présent message,
comprenant tout fichier qui y est joint, est envoyé à l'intention exclusive
de son destinataire; il est de nature confidentielle et peut constituer une
information protégée par le secret professionnel. Si vous n'êtes pas le
destinataire, nous vous avisons que toute impression, copie, distribution
ou autre utilisation de ce message est strictement interdite. Si vous avez
reçu ce courriel par erreur, veuillez en aviser immédiatement l'expéditeur
par retour de courriel et supprimer le courriel. Merci!
Confidentiality Warning: This message, including any attachment, is sent
only for the use of the intended recipient; it is confidential and may
constitute privileged information. If you are not the intended recipient,
you are hereby notified that any printing, copying, distribution or other
use of this message is strictly prohibited. If you have received this email
in error, please notify the sender immediately by return email, and delete
it. Thank you!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/021d8313-7665-44d3-82fd-fe9be08490c9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] circular dependency between user/home and parent directory owned by that user
hi, im still new to puppet, but from linux logic cant you just first ensure
file is there with (deployment)-group permissions - create user (with same
group) - change permissions
On Fri, Jan 31, 2014 at 12:51 AM, David Portabella
david.portabe...@gmail.com wrote:
again,
it is a circular dependency.
what you are saying is to first create user and then file.
but to create the user, we need the file first also.
On Thursday, January 30, 2014 5:31:10 PM UTC+1, Arpin Dominique (Nter)
wrote:
Hi,
Simple :
User['david']-File['/haha']
Ref: http://docs.puppetlabs.com/learning/ordering.html
*Dominique Arpin*
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
*De :* puppet...@googlegroups.com [mailto:puppet...@googlegroups.com] *De
la part de* David Portabella
*Envoyé :* 30 janvier, 2014 11:28
*À :* puppet...@googlegroups.com
*Objet :* [Puppet Users] circular dependency between user/home and
parent directory owned by that user
For illustrating purposes,
I need a *david* user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by
*david*.
this code does not work,
because user requires the /haha directory, and the /haha directory
requires the david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mise en garde concernant la confidentialité : Le présent message,
comprenant tout fichier qui y est joint, est envoyé à l'intention exclusive
de son destinataire; il est de nature confidentielle et peut constituer une
information protégée par le secret professionnel. Si vous n'êtes pas le
destinataire, nous vous avisons que toute impression, copie, distribution
ou autre utilisation de ce message est strictement interdite. Si vous avez
reçu ce courriel par erreur, veuillez en aviser immédiatement l'expéditeur
par retour de courriel et supprimer le courriel. Merci!
Confidentiality Warning: This message, including any attachment, is sent
only for the use of the intended recipient; it is confidential and may
constitute privileged information. If you are not the intended recipient,
you are hereby notified that any printing, copying, distribution or other
use of this message is strictly prohibited. If you have received this email
in error, please notify the sender immediately by return email, and delete
it. Thank you!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/021d8313-7665-44d3-82fd-fe9be08490c9%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAKiz-NfFhE-cq0QtUWCzD1puRxRg7v4qgOZGVRhGNubmKDF0gA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] circular dependency between user/home and parent directory owned by that user
Actually, simpler than that.
Using the stdlib puppet-forge module, I can say
$homedirdir = dirname ( $userhome )
and then
exec { mkdir-${username}:
command = /bin/mkdir -p ${homedirdir},
unless = test -d ${homedirdir},
}
When the user resource is created, this combination creates the directory with
the proper permissions.
user { $username:
ensure = present,
home = $userhome,
require = Exec[mkdir-${username}],
}
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin
Hobbes)
On Jan 30, 2014, at 11:31 AM, Arpin Dominique (Nter)
dominique.ar...@casino.qc.ca wrote:
Hi,
Simple :
User[‘david’]-File[‘/haha’]
Ref: http://docs.puppetlabs.com/learning/ordering.html
Dominique Arpin
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
De : puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] De la
part de David Portabella
Envoyé : 30 janvier, 2014 11:28
À : puppet-users@googlegroups.com
Objet : [Puppet Users] circular dependency between user/home and parent
directory owned by that user
For illustrating purposes,
I need a david user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by david.
this code does not work,
because user requires the /haha directory, and the /haha directory requires the
david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mise en garde concernant la confidentialité : Le présent message, comprenant
tout fichier qui y est joint, est envoyé à l'intention exclusive de son
destinataire; il est de nature confidentielle et peut constituer une
information protégée par le secret professionnel. Si vous n'êtes pas le
destinataire, nous vous avisons que toute impression, copie, distribution ou
autre utilisation de ce message est strictement interdite. Si vous avez reçu ce
courriel par erreur, veuillez en aviser immédiatement l'expéditeur par retour
de courriel et supprimer le courriel. Merci!
Confidentiality Warning: This message, including any attachment, is sent only
for the use of the intended recipient; it is confidential and may constitute
privileged information. If you are not the intended recipient, you are hereby
notified that any printing, copying, distribution or other use of this message
is strictly prohibited. If you have received this email in error, please notify
the sender immediately by return email, and delete it. Thank you!
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/C2F62CDF5915D0458F0528664315BAE732344C13%40MTL1EXC01.scqmtl.loto-quebec.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/2efda94b-5a70-4df1-953f-6230e639ca2b%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] circular dependency between user/home and parent directory owned by that user
Something like managehome = false ?
On 30 Jan 2014 16:51, David Portabella david.portabe...@gmail.com wrote:
again,
it is a circular dependency.
what you are saying is to first create user and then file.
but to create the user, we need the file first also.
On Thursday, January 30, 2014 5:31:10 PM UTC+1, Arpin Dominique (Nter)
wrote:
Hi,
Simple :
User['david']-File['/haha']
Ref: http://docs.puppetlabs.com/learning/ordering.html
*Dominique Arpin*
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
*De :* puppet...@googlegroups.com [mailto:puppet...@googlegroups.com] *De
la part de* David Portabella
*Envoyé :* 30 janvier, 2014 11:28
*À :* puppet...@googlegroups.com
*Objet :* [Puppet Users] circular dependency between user/home and
parent directory owned by that user
For illustrating purposes,
I need a *david* user with home directory /haha/david,
and at the same time, the directory /haha also needs to be owned by
*david*.
this code does not work,
because user requires the /haha directory, and the /haha directory
requires the david user,
so we have a circular dependency,
and it seems that puppet does not know how to handle this.
user {'david':
ensure = present,
home= '/haha/david',
managehome = true
}
file {'/haha':
ensure = directory,
owner = 'david'
}
how to solve this?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/puppet-users/da03b929-db57-4964-acf9-060beec69d2c%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mise en garde concernant la confidentialité : Le présent message,
comprenant tout fichier qui y est joint, est envoyé à l'intention exclusive
de son destinataire; il est de nature confidentielle et peut constituer une
information protégée par le secret professionnel. Si vous n'êtes pas le
destinataire, nous vous avisons que toute impression, copie, distribution
ou autre utilisation de ce message est strictement interdite. Si vous avez
reçu ce courriel par erreur, veuillez en aviser immédiatement l'expéditeur
par retour de courriel et supprimer le courriel. Merci!
Confidentiality Warning: This message, including any attachment, is sent
only for the use of the intended recipient; it is confidential and may
constitute privileged information. If you are not the intended recipient,
you are hereby notified that any printing, copying, distribution or other
use of this message is strictly prohibited. If you have received this email
in error, please notify the sender immediately by return email, and delete
it. Thank you!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/021d8313-7665-44d3-82fd-fe9be08490c9%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CACzr%3DFfnwNGcBhxYwq7%2Bd7e1kf180mOVv5EinhvOshyr97qnmg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Choo choo here comes the FOSDEM train
The puppet stand is located in the K building, on the second level. Please feel free to 'pop by' ... see you @ fosdem On 01/30/2014 03:48 PM, Matthias Saou wrote: Hi, Awesome, thanks Daniele! I have just registered for the dinner, though I'm still not 100% sure I'll be there (there's an air controller strike, argh!). But I'll be lurking around, like (almost) every year :-) For a photo : https://github.com/thias I'll be mostly interested in discussing anything related to modules and the Forge, but if any official Puppet Labs representatives are there, I'd also be interested in getting in touch about consulting in Spain and training. Cheers, Matthias On Thu, 30 Jan 2014 05:33:29 -0800 (PST) Daniele Sluijters daniele.sluijt...@gmail.com wrote: Hi everyone, I've booked at Sogno d’Italia for approx. 30 people. They are expecting us somewhere between 19h00 and 19h20 (that's 7PM for the Americans). I've changed the Eventbrite event to allow tickets up to 35 which means there's about 15 places left if you want to join in. So, if you want food, please register :). See you soon! -- Johan De Wit Open Source Consultant Red Hat Certified Engineer (805008667232363) Puppet Certified Professional 2013 (PCP006) _ Open-Future Phone +32 (0)2/255 70 70 Zavelstraat 72 Fax +32 (0)2/255 70 71 3071 KORTENBERG Mobile+32 (0)474/42 40 73 BELGIUM http://www.open-future.be _ Next Events: Puppet Fundamentals Training | http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february Puppet Intruction Course | http://www.open-future.be/puppet-introduction-course-7th-february Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-february Zabbix for Large Environments Training | http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february Subscribe to our newsletter | http://eepurl.com/BUG8H -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52EA9C9D.8030906%40open-future.be. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] PuppetDB 1.6.0 final now available
PuppetDB 1.6.0 final * RC1: January 7th, 2014. * RC2: January 14th, 2014. * RC3: January 22nd, 2014. * Final: January 30th, 2014. PuppetDB 1.6.0 Downloads Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories Binary tarball: http://downloads.puppetlabs.com/puppetdb/ Source: http://github.com/puppetlabs/puppetdb Please report feedback via the Puppet Labs tickets site, using an affected PuppetDB version of 1.6.0: https://tickets.puppetlabs.com/browse/PDB Documentation: http://docs.puppetlabs.com/puppetdb/1.6 Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb PuppetDB 1.6.0 Release Notes PuppetDB 1.6.0 is a performance and bugfix release. Things to take note of before upgrading: * There is a known issue in Puppet 3.4.0, 3.4.1 and 3.4.2 with duplicate failed events being tracked here: https://tickets.puppetlabs.com/browse/PUP-1524. This is being fixed in an upcoming release of Puppet. In 1.6.0 this error will become more obvious as we are now raising full stack traces, so you may notice it more readily after the upgrade. * There are a number of database migrations performed upon first startup. This will require extra free disk space on your PostgreSQL server while we rebuild some tables, so make sure you have enough free space _before_ you start the upgrade. Since a full table migration takes a copy of the old table, a good rule of thumb would be to check your current database usage (using du -sh on the database directory for example) and ensure you have as much free space on that partition. While all migrations are protected by an atomic database transaction, it never hurts to backup your database beforehand just in case. * Also due to the migrations that will take place, it might take several minutes (depending on the size of your database) before PuppetDB can respond to requests again. Give the migration ample time to complete and you should be fine. * Make sure all your PuppetDB instances are shutdown and only upgrade one at a time. * As usual, don’t forget to upgrade your puppetdb-terminus package also (on the host where your Puppet Master lives), and restart your master service. * This is primarily a performance release, so we’re interested in any feedback (good or bad) as to how helpful these changes have been especially around catalog hash-miss performance and general updates on the database. Most of the performance improvements are around facts and catalogs, so we don’t expect any improvements for report storage this time around. Changes specific to rc3: * (PDB-313) Fix catalog resource metadata not updating with parameters change * (PDB-307) Remedy unit test failures with latest mocha gem * Fixed an issue with acceptance testing missing ruby-devel on EL5 (VirtualBox) Changes specific to rc2: * (PDB-303) Utilise final version of prismatic/schema 0.2.0 * (PDB-279) Sanitize report imports * (PDB-247) Fixes the namespace override warnings from schema * (PDB-107) Support chained CA certificates Notable improvements and fixes: * (PDB-81) Deprecate JDK6. It's been EOL for quite some time. * (#21083) Differential fact storage Previously when facts for a node were replaced, all previous facts for that node were deleted and all new facts were inserted. Now existing facts are updated, old facts (no longer present) are deleted and new facts are inserted. This results in much less I/O, both because we have to write much less data and also because we reduce churn in the database tables, allowing them to stay compact and fast. * (PDB-68) Differential edge storage Previously when a catalog wasn't detected as a duplicate, we'd have to reinsert all edges into the database using the new catalog's hash. This meant that even if 99% of the edges were the same, we'd still insert 100% of them anew and wait for our periodic GC to clean up the old rows. We now only modify the edges that have actually changed, and leave unchanged edges alone. This results in much less I/O as we touch substantially fewer rows. * (PDB-69) Differential resource storage Previously when a catalog wasn't detected as a duplicate, we'd have to reinsert all resource metadata into the catalog_resources table using the catalog's new hash. Even if only 1 resource changed out of a possible 1000, we'd still insert 1000 new rows. We now only modify resources that have actually changed. This results in much less I/O in the common case. * Streaming resource and fact queries. Previously, we'd load all rows from a resource or fact query into RAM, then do a bunch of sorting and aggregation to transform them into a format that clients expect. That has obvious problems involving RAM usage for
Re: [Puppet Users] Re: Reg : War deployment with Puppet
Puppi? On 30 Jan 2014 13:52, Andrey Kozichev akozic...@gmail.com wrote: we used to package into rpms as well On 30 January 2014 11:50, PaulC paul.can...@gmail.com wrote: Must admit i would be interested in seeing what other peoples approaches has been for this, we have been thinking about going down the route of getting the war files and any relevant library files put into a rpm/deb package and getting puppet to install the rpm though the OS package manager. Paul C. On Thursday, 30 January 2014 06:54:26 UTC, krishna bhaskara rao wrote: Hi, Can any one share me sample snippets to deploy war in tomcat. if deployment fails, how to rollback. With Regards, Krishna. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/241ed902-f5c6-4f83-a2de-85a13b1948ed%40googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACzr%3DFcrk1udFVCQTYKF%2BkPPou-1%2Bh9JVpgUY8RyavOjjJb9xQ%40mail.gmail.com . For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAAohVBfKhmaWx7ZDGzPgPV%3DA0ZcMZtR5ZqzvW%2B8S%3DbP4WbpM_w%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Reg : War deployment with Puppet
We package the war into a RPM and then use an exec statement to extract the war. Matt On Jan 30, 2014, at 3:50 AM, PaulC paul.can...@gmail.com wrote: Must admit i would be interested in seeing what other peoples approaches has been for this, we have been thinking about going down the route of getting the war files and any relevant library files put into a rpm/deb package and getting puppet to install the rpm though the OS package manager. Paul C. On Thursday, 30 January 2014 06:54:26 UTC, krishna bhaskara rao wrote: Hi, Can any one share me sample snippets to deploy war in tomcat. if deployment fails, how to rollback. With Regards, Krishna. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/241ed902-f5c6-4f83-a2de-85a13b1948ed%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/BFC7346E-5E79-480C-B4C1-7B996B34ADDC%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Help changing a power shell to Puppet types and providers
Due to the run time issue with puppet/ruby calling powershell windows
update and i could nt be able to open the zip file
http://forge.puppetlabs.com/liamjbennett/windows_autoupdate
So I am using instead registry setting to disable the auto update, any
suggestions for the below
confine :operatingsystem = windows
setcode do
reg_exe = #{ENV['SystemRoot']}\\System32\\reg.exe
#Disabling Autoupdate
begin
Facter::Util::Resolution::exec(#{reg_exe} ADD HKEY_LOCAL_MACHINE\\
SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate\\AU /v AutoUpdate /t
Reg_DWORD /d 1)
rescue Exception = e
puts e
end
end
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/02673469-7d7f-4ef0-a8cd-61b409612052%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet stand @ fosdem
Hi All, The puppet and puppet user groups stand is located in the K building, on the second floor, somewhere in the middle. Feel free to pop by to say hello See you @ fosdem -- Johan De Wit Open Source Consultant Red Hat Certified Engineer (805008667232363) Puppet Certified Professional 2013 (PCP006) _ Open-Future Phone +32 (0)2/255 70 70 Zavelstraat 72 Fax +32 (0)2/255 70 71 3071 KORTENBERG Mobile+32 (0)474/42 40 73 BELGIUM http://www.open-future.be _ Next Events: Puppet Fundamentals Training | http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february Puppet Intruction Course | http://www.open-future.be/puppet-introduction-course-7th-february Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-february Zabbix for Large Environments Training | http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february Subscribe to our newsletter | http://eepurl.com/BUG8H -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52EABA52.6080106%40open-future.be. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet ERROR 400
solved thank you
On Wednesday, January 15, 2014 2:15:00 PM UTC-7, Vassiliy Vins wrote:
Hi!
I've created 2 files:
file *test.pp* with code :
class copy {
file {testfile:
path = /home/vassiliy/myfile,
source = puppet:///mpoint/client1/testfile,
mode = '644'
}
}
and file site.pp wuth code:
import test.pp
node client1 {
include copy
}
in fileserver.conf was created section like:
[mpoint]
path /etc/puppet/files
allow *
file *testfile* is in folder /etc/puppet/files/client1/
I got on client1/var/log/messages next:
ERROR 400 on SERVER: Not authorized to call find on
/file_metadata/client1/testfile with {:links = manage}
Any ideas, why? where to look at? thnx
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/b43b1b68-b81d-4cc2-8bb7-3390426e5cf4%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Enterprise 3.1.2 Available
Dear Puppet Enterprise Users, Puppet Enterprise 3.1.2 is now available. This is a bug fix and security release of Puppet Enterprise. All users of Puppet Enterprise 3.x are encouraged to upgrade when possible to Puppet Enterprise 3.1.2 Puppet Enterprise 3.1.2 includes fixes to address a regression in Puppet Enterprise 3.1.1 where the unspecified default file mode in Puppet was set to 0600 instead of 0644. Also included is an updated OpenSSL library to address CVE-2013-6449. For more information on this vulnerability, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-6449 As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. Thanks, Rob Braden Release Engineer Puppet Labs *Join us at PuppetConf 2014, September 23-24 in San Francisco - * http://bit.ly/pupconf14 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANrW%3D%3D15Tk_yBYNSK6yviZv6Y9d5HXv97SC8e5Zozmui6P%3DLuw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Enterprise 2.8.5 is Available
Dear Puppet Enterprise Users, Puppet Enterprise 2.8.5 is now available. This is a bug fix release of Puppet Enterprise. All users of Puppet Enterprise 2.8.x are encouraged to upgrade when possible to Puppet Enterprise 2.8.5. Puppet Enterprise 2.8.5 includes fixes to address a regression in Puppet Enterprise 2.8.4 where the unspecified default file mode in Puppet was set to 0600 instead of 0644. Also included is a fix for upgrades on recent Amazon AMI images. As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. Thanks, Rob Braden Release Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANrW%3D%3D2YcnFDh97YaXyX2pY3vMzo4dHLmQKA213j_uiNPdXqGQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Reg : War deployment with Puppet
Usually package into an RPM, but not always, which installs into
something like /usr/{lib|share}/package/something.war and then create
a link to it from the tomcat webapps directory. Tomcat's autodeploy
will take care of unpacking it.
--
Later,
Darin
On Thu, Jan 30, 2014 at 3:13 PM, Matthew Schmitt killas...@gmail.com wrote:
We package the war into a RPM and then use an exec statement to extract the
war.
Matt
On Jan 30, 2014, at 3:50 AM, PaulC paul.can...@gmail.com wrote:
Must admit i would be interested in seeing what other peoples approaches has
been for this, we have been thinking about going down the route of getting
the war files and any relevant library files put into a rpm/deb package and
getting puppet to install the rpm though the OS package manager.
Paul C.
On Thursday, 30 January 2014 06:54:26 UTC, krishna bhaskara rao wrote:
Hi,
Can any one share me sample snippets to deploy war in tomcat. if
deployment fails, how to rollback.
With Regards,
Krishna.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/241ed902-f5c6-4f83-a2de-85a13b1948ed%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/BFC7346E-5E79-480C-B4C1-7B996B34ADDC%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CADaviKuy%2BSutrtegW0d1LAirTo_8FnT1VpJ377eZGK%2BM0PGZJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Node Corruption
/etc/debian_version is in place and facter on the box returns correctly. If I run the puppetmaster in debug I can see it checking hiera for RedHat not Debian values as it does when another debian client contacts it. On Thursday, January 30, 2014 7:32:41 AM UTC-7, jcbollinger wrote: On Thursday, January 30, 2014 8:22:35 AM UTC-6, jcbollinger wrote: Looking at the Facter source, however, it seems pretty likely that the problem revolves around the file /etc/debian_version having been removed from the node. Hmm. Having re-read the problem description, I am less confident in my first response. It's still worthwhile to check /etc/debian_version, though, and to verify more directly (i.e. via a Notify) what fact values the master is receiving for key facts. I stand by my assertion that the proximal issue is more likely outside Puppet than inside. If /etc/debian_version is not related to the problem, then it might be helpful to see one of the templates that is behaving unexpectedly. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5607a894-ca8e-46cc-9ffe-2542f43423f2%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Trouble with notify/require/before/subscribe
Greetings,
I am trying to puppetize a process that goes like this:
1) remove package a.i386
2) create repo file
3) install package a.x86_64 from repo
4) update config_file_1
5) update config_file_2
6) update config_file_3
7) start service
Shouldn't be too hard right? Except I have played with every combination I
can think of using with notify, subscribe, before, and require and I can't
seem to get this to all happen in the same run. It always does a part of it
the first run then requires a second run to finish up (a couple of
variations required three and even four runs!). I am struggling to find out
where I am going wrong. The code I have right now is the best in that it
always requires _just_ two runs to complete. I edited out a lot of the
parameters that are trivial just to focus on the dependency problem. I can
share full code if I really need to but it is a bit messy as I pass all
kinds of stuff to the template and I don't want to confuse the issue.
Here is the basis of my code:
package { ['a.i386']:
ensure = absent,
before = Package['a.x86_64'],
}
yumrepo { RepoA:
# stripped out other paramters
notify = Package['a.x86_64'],
}
package { ['a.x86_64']:
ensure = absent,
subscribe = Yumrepo['RepoA'],
}
file { /etc/config_file_1:
# stripped out other paramters
subscribe = Package['a.x86_64'],
}
file { /etc/config_file_2:
# stripped out other paramters
subscribe = Package['a.x86_64'],
}
file { /etc/config_file_3:
# stripped out other paramters
subscribe = Package['a.x86_64'],
}
service { 'a':
# stripped out other paramters
subscribe =
File[/etc/config_file_1,/etc/config_file_2,/etc/config_file_3],
}
As stated, I get a consistent run out of this. I just have to do it twice.
First run:
a.i386 is removed
Yumrepo is created
scheduling refresh of service
All three files fail to install
service fails
Second run
a.x86_64 is created
scheduling refresh of service
All three files install
service works
Why?
According to this page [1] subscribe Causes a resource to be applied after
the target resource. The subscribing resource will refresh if the target
resource changes. Thus the scheduling of a refresh shouldn't happen until
/after/ the files and NONE of the files are supposed to run until /after/
the package is installed! But clearly, this is not the case! At least the
service schedule happens after the files fail so that is somewhat in order.
And the repo is created properly, so that is a plus. I have a feeling that
it is because the yum repo isn't refreshed before trying to install the
package, but I am not 100% sure on that. As far as I can tell through
debug, puppet never even attempts to install a.x86_64 until the second run.
[1]
http://docs.puppetlabs.com/puppet/latest/reference/lang_relationships.html
The only thing left that I can think of that I haven't tried would be to
shove each process into a subclass then chain them together something like
this
{class::remove}-{class::addyum}-{class::install}-{class::configfiles}-{class::service}
but that seems /really/ silly.
Can someone please point out where things are going screwy for me? I would
greatly appreciate it.
Thanks!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4562f58e-d88d-4d84-bab3-9337c6a081f9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Correction: Re: Announce: Puppet Enterprise 3.1.2 Available
One correction: It was brought to our attention that the announcement referenced OpenSSL CVE-2013-6449. That was incorrect. The correct advisory is CVE-2013-6550, for more information, see http://puppetlabs.com/security/cve/cve-2013-6450. On Thu, Jan 30, 2014 at 1:08 PM, Rob Braden brad...@puppetlabs.com wrote: Dear Puppet Enterprise Users, Puppet Enterprise 3.1.2 is now available. This is a bug fix and security release of Puppet Enterprise. All users of Puppet Enterprise 3.x are encouraged to upgrade when possible to Puppet Enterprise 3.1.2 Puppet Enterprise 3.1.2 includes fixes to address a regression in Puppet Enterprise 3.1.1 where the unspecified default file mode in Puppet was set to 0600 instead of 0644. Also included is an updated OpenSSL library to address CVE-2013-6449. For more information on this vulnerability, please visit http://puppetlabs.com/security, or visit http://puppetlabs.com/security/cve/cve-2013-6449 As a current Puppet Enterprise user, you can upgrade to this new version as part of your annual subscription. If upgrading, it is recommended to upgrade your master and console servers first. As always, we want to hear about your experiences with Puppet Enterprise. If you have any questions about upgrading, be sure to get in touch with Puppet Labs Support. Thanks, Rob Braden Release Engineer Puppet Labs *Join us at PuppetConf 2014, September 23-24 in San Francisco - * http://bit.ly/pupconf14 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANrW%3D%3D3UfbC_5aCEg3z4Y0SRo6ge4omuyJGzZN%2BgiZdLJYyCxg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What is the best replacement for Puppet Dashboard ?
That issue should be fixed soon, I'm told. The reports do get sent to puppetboard, but the report processor throws an unhandled exception because it references one of the 'metrics' hash fields, which is empty in failed reports (this should be fixed in master to log an error message instead). However, the bigger issue is that (a) puppet reports only include per-resource statuses, not an overall status, so there's nothing in the current report format that indicates that it was a failed run, let alone why, and (b) there's no place to store that information in the PuppetDB schema (yet) once it makes it into the reports. If you're interested in this issue, you should watch the following issues: [PDB-16] Store status for reports - Puppet Labs Tickets - https://tickets.puppetlabs.com/browse/PDB-16 [PDB-36] Add agent run failure information to reports - Puppet Labs Tickets - https://tickets.puppetlabs.com/browse/PDB-36 [PUP-283] Improve agent error reporting - Puppet Labs Tickets - https://tickets.puppetlabs.com/browse/PUP-283 [PUP-916] Document report format changes for improved agent reporting - Puppet Labs Tickets - https://tickets.puppetlabs.com/browse/PUP-916 -Jason On 01/30/2014 07:59 AM, Klavs Klavsen wrote: I use puppetboard too - it's really great, and much lighter on the database. A big improvement on puppet-dashboard. Only one issue remains, that means I must keep my puppet-dashboard.. There's a bug in the puppetdb-terminus - so nodes which manifest fails compilation fails - does NOT get a report send to puppetboard, so you can't catch failing compilation failures :( Odlly enough, puppet does send the http reports when there's a failed compilation - so puppet-dashboard knows about them. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/008d0d13-10f1-496c-8589-a451df72a0b1%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52EAFEA3.20401%40jasonantman.com. For more options, visit https://groups.google.com/groups/opt_out.
