[Puppet Users] Terraform provisioner?
Is anyone working on a Terraform provisioner? Or have one internal that they'd like to open source (If so, am volunteering to make it all nice for the outside world and write you documentation, etc). Cheers James -- * The Art of Monitoring (https://artofmonitoring.com) * The Docker Book (https://dockerbook.com) * The LogStash Book (https://logstashbook.com) * Pro Puppet (http://tinyurl.com/ppuppet2 ) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- 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/57FC506D.3030001%40lovedthanlost.net. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] 2015 IT Monitoring Survey - closing shortly!
TL;DR - the 2015 IT Monitoring Survey is closing shortly: https://www.surveymonkey.com/s/monitoringsurvey2015. The survey takes about 5 minutes to fill out and the results will again be presented on my blog, in some conference talks and made available as Creative Commons licensed data. The survey is totally anonymous and the data won’t be used for any commercial purposes. Thanks in advance! James Turnbull -- * The Art of Monitoring (http://artofmonitoring.com) * The Docker Book (http://dockerbook.com) * The LogStash Book (http://logstashbook.com) * Pro Puppet (http://tinyurl.com/ppuppet2 ) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- 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/55A95B56.9010009%40lovedthanlost.net. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Please take the 2015 Monitoring Survey!
TL;DR - Please take the 2015 Monitoring Survey at https://www.surveymonkey.com/s/monitoringsurvey2015. Last year I ran a monitoring survey, whose data I also reviewed as a series of posts on this blog (http://kartar.net/2014/11/monitoring-survey---background/). I was interested in running the survey because I think we’re seeing the beginnings of a significant change in the maturity of the monitoring landscape and I'd like to track that change. I’ve decided to make the survey a yearly event and am coinciding the launch of this year’s survey with Monitorama in Portland. The survey takes about 5 minutes to fill out and the results will again be presented on this blog, in some conference talks and made available as Creative Commons licensed data. The survey is totally anonymous and the data won’t be used for any commercial purposes. You can find the survey here - https://www.surveymonkey.com/s/monitoringsurvey2015. Thanks in advance! James Turnbull -- * The Art of Monitoring (http://artofmonitoring.com) * The Docker Book (http://dockerbook.com) * The LogStash Book (http://logstashbook.com) * Pro Puppet (http://tinyurl.com/ppuppet2 ) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- 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/558053EB.3070806%40lovedthanlost.net. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] IT Monitoring Survey
Hi all I am gathering some statistical data for a conference talk on IT monitoring that I am giving next year. I am hoping you will all be interested in responding to a quick survey about your IT monitoring environment. It's a totally anonymous and very simple survey that takes about 3-4 minutes to answer. The link to the survey is here: https://www.surveymonkey.com/s/monitorings Many thanks! James Turnbull -- * The Docker Book (http://dockerbook.com) * The LogStash Book (http://logstashbook.com) * Pro Puppet (http://tinyurl.com/ppuppet2 ) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -- 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/544C8BEC.8030008%40lovedthanlost.net. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] AWS OpsWorks Puppet support
Hi all If you are interested in Puppet support for AWS OpsWorks it'd really help us if you let Amazon know here: https://forums.aws.amazon.com/forum.jspa?ref_=tsm_1_tw_s_aws_mihcccforumID=153 That you're interested in this support. Thanks James -- James Turnbull 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Puppet Manage Cisco ASA
jim wrote: I am aware of https://puppetlabs.com/blog/puppet-network-device-management/ but this doesn't manager ACL's or object-groups yet, and my programming skills aren't that great Or has anyone used cisco one platform kit (onepk) via puppet Cisco is working on integration and we hope to have some news on this soon. Regards James Turnbull -- James Turnbull 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: AWS OpsWorks announcement using Chef
Vaidas Jablonskis wrote: It makes sense for Amazon to go with something like Chef, because it is more cloud oriented and it's easier to hack something up just to get it up and running quicker. Chef is more like shell scripting on steroids I would say, at least, that's how many people use it. We're going to be talking to AWS about adding Puppet support to OpsWorks soon. It is our understanding from them that this is based on an acquisition they made of a Chef-based solution rather than an endorsement of Chef. More news when we have it! Thanks James -- James Turnbull 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Yum Repositories appear to be offline
Ken Barber wrote: I've alerted operations. Thanks guys. On Mon, Feb 11, 2013 at 1:38 PM, Gregory B. Ops tell me they are back up and running. Regards James -- James Turnbull 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] LogStash Book released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I've just released 'The LogStash Book' (http://www.logstashbook.com/). It's a new book designed for SysAdmins, Operations staff, Developers and DevOps who are interested in deploying a log management solution using the open source tool LogStash (http://www.logstash.net/). It's available for sale on the site a PDF or ePUB: http://www.logstashbook.com/ Or from Amazon.com as a Kindle ebook: http://www.amazon.com/gp/product/B00B9JQTCO/ref=as_li_ss_tl?ie=UTF8camp=1789creative=390957creativeASIN=B00B9JQTCOlinkCode=as2tag=puppet0e-20 Given the overlap between Puppet folks and LogStash users I thought it might interest people. Regards James - -- Author of: * The LogStash Book (http://logstashbook.com) * Pro Puppet (http://tinyurl.com/ppuppet) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJRD9oQAAoJECFa/lDkFHAye0sH/RTxDbsWHWIhENwZNnpYjdJo G+wazhFEZ4Bs+siImxbBCJwlLU9y9EbkEBnooA4aWRiMIK58uGi0ptTGRbzPdW5d Tvk6ufqkxlV5DcuRm1iDBJQf6LTkLwd1igwcHC5tXydloW7MpZgiZUU69jL7Ldye UzStaGIYiSN8HR8hhRB9aaKoIrlR16hpYRkKIBDKfHvFvPa/zK/coZrklQLwl+et nuwaY7TYAyvtPPKnJeHPNjQqhLXxq0rYZnu1aEhwwWlViL5GQKWLEzvxbrb2geWp aYBDX+n3l9hqpWHrbY3SN1csOA/RoPY1YEoKaE0OYNjUOsZ58u+W7ZBNjNXtLV4= =8fTs -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Broken rsync mirroring for PuppetLabs APT repo
Arnaud Gomes-do-Vale wrote: Hi, I have sent this mail to i...@puppetlabs.com and received no answer, so I'm posting here as well; I hope somebody at PuppetLabs will be able to help. Arnaud I saw your saw email to info@. It arrived over Christmas so I am afraid people were thin on the ground at the office. I'll ask our Delivery and Ops teams to take a look and see if we can work out what's wrong. Thanks for letting us know! Regards James -- James Turnbull 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 We are moving! New address: Puppet Labs, Inc., 926 NW 13th Ave., Suite 210, Portland, OR 97209. -- 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] Report processor and available variables
Jean Baptiste Favre wrote: Hello, I'm trying to build a custom report processor so that I can get puppet metrics into Zabbix. I found one here: https://github.com/thomasvandoren/puppet-zabbix which basically works. The problem I have is that report processor mostly use self.host as hostname. But it represent certname in puppet world. I tried @hostname, but still get certname instead of hostname. Is there any way to get the real hostname into report processor ? As you're located on the master and all that gets passed to the report processor is the the contents of the report this is a little tricky. Off the top of my head you could use the self.host value to lookup the fact values from the node, i.e. if you're using PuppetBD (http://docs.puppetlabs.com/puppetdb/1/index.html) or the Inventory Service (http://docs.puppetlabs.com/guides/inventory_service.html). Hope that helps! Regards James Turnbull -- James Turnbull 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 We are moving! New address: Puppet Labs, Inc., 926 NW 13th Ave., Suite 210, Portland, OR 97209. -- 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] Do you want a Puppet Conference in Berlin, Germany
Geoff Galitz wrote: Hi. I'd be in (with enough notice, of course). I'd be even more in if the conference was on the other side of Germany near Cologne or even in Belgium. I'm assuming you already have a space you can use in Berlin, though? Geoff We're also going to have a PuppetCamp in Ghent, Belgium - probably before or after FOSDEM in 2013. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Meetup Australia (Melbourne, Sydney, Brisbane)
Stephen Johnson wrote: The Melbourne location has been decided Beer DeLuxe on Federation Square, Thursday 8/11/2012 5.30pm I may swing by briefly too! Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet 3.0 and yum groupinstall
jcbollinger wrote: On Wednesday, October 17, 2012 6:17:49 AM UTC-5, jdehnert wrote: I can't seem to find any direct reference yo this in the puppet 3.0 docs so does anyone know if puppet 3.0 can handle yum groupinstalls without resorting to using an exec? No, I'm pretty sure not. Puppet's built-in resources include Package to model individual packages, but nothing modeling package groups. I think it would be possible to write a custom resource type to cover that, but using such resources would require some care to avoid conflicting declarations of groups and packages within those groups. I believe this ticket is the closest we've come to this: http://projects.puppetlabs.com/issues/5175 And the workaround suggested there was an exec. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] FreeBSD 3.0 Port
Worker Bee wrote: Hi Everyone; Has anyone created a puppet agent 3.0 BSD port? I would be very grateful to get my hands on it! One of my colleagues informs me the FreeBSD 3.0 port should be ready early next week. http://www.freebsd.org/cgi/ports.cgi?query=puppetstype=all Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: The free software tarballs are now difficult to find
On Oct 16, 6:12 am, jcbollinger john.bollin...@stjude.org wrote: For what it's worth, I always prefer to get source for third-party software, and my absolute *least* favorite way to do so is from a source-control repository. I particularly like source RPMs, but tarballs generally work just fine for me. More generally, I want *one file*, associated with a specific release of the software and so labeled, and accessible via a general purpose network protocol such as HTTP or FTP from a location sponsored by the project. It is available from GitHub, tagged for each release, for example: https://github.com/puppetlabs/puppet/zipball/3.0.0 It's also available via Source RPM from our repos. I don't see any dark conspiracy behind PL's website changes, but I am a bit surprised by some of the responses from PL personnel. The tone, if not the actual content, seems in some cases to say there's nothing wrong, why are you bothering us with this? Clearly something *is* wrong as far as Adam is concerned. PL is certainly not obligated to cater to any individual user's preferences -- or even to the whole community's preferences -- but it is not helpful to anyone to try, as some of the responses seemed to do, to deny their validity. I'm not denying their validity of the issue. I am questioning what exactly the issue being raised is and the extent that it's a key issue for the community. Given a complaint that the source tarballs are hard to find, I would have expected a response more along the lines of We're sorry the changes to our web site have inconvenienced you. We assure you that our intent is not to hide or block access to open-source Puppet. We will consider whether the site can be changed further to better serve both PE and our open-source Puppet users. I might even have expected a suggestion to file a ticket or a solicitation for further community comment. My analysis of the situation was that this was less about the location of tarballs or access to software (given the numerous other ways you can get the software) but rather about the definition of free. Here some members of the community and Puppet Labs clearly differ. I believe, no matter what changes we make to our website, that the only way they will be satisfied is we return to a GPL-esque license. A change we're not going to make for a number of legitimate, documented, transparent business reasons. That limits our ability to have a productive conversation about these issues. That being said we are discussing internally whether to continue with this approach. We've not yet made a decision but I will communicate that decision either way when it's made. Kind Regards James Turnbull -- 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] Access to the Puppet open source tarballs
Hi all There has been some discussion lately on the list about a change we made to the website. The change removed the link that allows you to bypass providing your email when downloading tarballs on this page: http://info.puppetlabs.com/download-puppet-open-source In light of that discussion we've decided to restore that link. We’re sorry that the change was made without adequately consulting the community. We’re committed to being as transparent and open as possible about our business and how it interacts with the open source community. In this case we screwed up and didn’t do a good job of that. We plan to learn from that mistake and ensure it doesn’t happen again. We also want to make clear that this page is just one of the many ways you can get access to Puppet. The others include: 1. Github (for example https://github.com/puppetlabs/puppet/zipball/3.0.0) 2. Packages (http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html) 3. RubyGems (gem install puppet) 4. From your favorite distribution or repository service such as EPEL. You can see other methods here: http://puppetlabs.com/puppet/puppet-open-source/. A number of other comments were made about Puppet Labs commitment to open source that we also want to address. Puppet Labs remains committed to open source. We could not have gotten where we are today without the support, enthusiasm and passion of the open source community. Many of us at Puppet Labs have a long history of involvement in open source and a strong commitment to the success of the open source movement. Puppet continues to be released under the Apache 2.0 license. Apache 2.0 is a free and open source license shared by a huge number of projects including everything released by the Apache Foundation, for example the Apache web server itself. The license provides you with free and open source software as well as allows us to ensure Puppet becomes more ubiquitous and widespread across the industry. Puppet Labs has also continued to release and maintain Puppet, Facter, mcollective, Hiera, and a number of other tools as open source tools. We also plan to release new open source tools (as we did twice this year with PuppetDB and Razor). We have no plans to stop doing this. Indeed we've committed significant engineering resources to all these projects (2447 commits to Puppet alone just this year!) and will continue to build on this. Puppet Labs is a business though. The reason we've been able to commit so much to developing Puppet and its ecosystem is because we've sold Puppet Enterprise to customers. Many in our open source community may never buy Puppet Enterprise: it may not suit your price point, your business or you may not have need of the features it offers. But every license of Puppet Enterprise we sell pays engineers and allows us to grow and develop the Puppet platform. As a result you’ll see a strong focus on Puppet Enterprise on our website and in our marketing. As we mentioned above we’re committed to being as transparent and open as possible about our business and how it interacts with the open source community. Please feel free to hold us to that commitment. We can’t always guarantee we’ll be able to make everyone in the community happy but we will be as clear and open as we can about the changes and decisions we make. Please feel free to reach out to me, Dawn Foster or anyone else at Puppet Labs if you have any questions or concerns. Kind Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: The free software tarballs are now difficult to find
On Monday, October 15, 2012 1:05:41 PM UTC-7, windowsrefund wrote: Look, don't start trying to paint me in a negative light here. I'm not the one who has taken specific actions designed to alienate the free software community. Let's get back to the topic at hand. Someone obviously made the decision to make the community jump through yet another hoop in order to obtain and therefore, use, the free software version over PE. Who made that decision and how was that justified? More importantly, who is making the call to not revert the page now that objections have been raised? Adam Firstly, we're not going to revisit the discussions around the change of Puppet and Facter's license. We stated our reasoning at that time (see this blog post - http://puppetlabs.com/blog/relicensing-puppet-to-apache-2-0/). We accept that some members of the community (a very small number from the feedback we've received) have an issue with the change but it has been largely well received. Secondly, describing Puppet Lab's open source software as a red-headed step child is not only hyperbolic but it's also incorrect. We produce far more open source software than we do commercial software. The flurry of releases this year reflect this continued focus on the community and our commitment to open source software. Thirdly, as stated earlier, very few of our customers acquire the open source version of Puppet via the website. They use distribution provided packages or our own repositories. We agree we've removed the previously available bypass but we've also provided numerous other channels (that we've certainly not hidden from the community in any way) where you can get Puppet. Lastly, we freely admit that we're trying to feature Puppet Enterprise because it pays for us to continue to develop Puppet. That's our business model and we've been very clear now and in the past about that model and how commercial and open source software interact at Puppet Labs. As a result of our need to fund Puppet development we're clearly not going to meet the expectations of every member of the community but we've chosen a path we think, and feedback from the community reflects this, delivers to the needs of both the open source community and allows us to maintain a viable business. Kind Regards James Turnbull -- 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/-/UU5x--dJQkIJ. 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] Introducing our new Community Manager - Dawn Foster
Hi all I am thrilled to announce our new Community Manager: Dawn Foster. Dawn joins us from Intel where she managed several open source communities (I'm going to let her introduce herself in more detail in a later email). Dawn will initially be lurking and getting to know you all. She's going to have a focus on helping us communicate better, making the relationship between the community and Puppet Labs work better, extending our developer community, helping getting traction on tickets and features the community wants, sharing lots of cool metrics and generally working to make Puppet and the community more awesome. Please make Dawn welcome! Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] PuppetConf is next week!
Hi all Just a final ping about PuppetConf. It's next week in San Francisco 27-28 of September. We've got 600! registered. Some of you, about 60 or so, might remember the first camp at SFSU! We've grown just a tinsy bit since then. :) We'll also have about 60 Puppet Labs staff there, 70 sessions, demos, certification, training and a bunch of social events. If you'd like to attend there are still spots left, albeit they are vanishing fast, you can register at: http://puppetconf.com/register. Cheers James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?
Sam Kottler wrote: Who's got the ban hammer? :P The address appears to be now banned. Apologies for the spam. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Attending PuppetConf?
Sam Kottler wrote: Sorry, this was supposed to go to the Foreman list. My apologies. That's totally okay Sam. :) We'd love a Foreman meetup at PuppetConf. Happy to help facilitate so let me know if I can help. James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] What is meaning of | | ~ signal
Tim Sharpe wrote: Hi, - and - create ordering relationships (like the require and before metaparameters) ~ and ~ create notify relationships (like the notify and subscribe metaparameters) And the | | symbols are resource collectors: http://docs.puppetlabs.com/puppet/2.7/reference/lang_collectors.html Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How can MCollective replace puppet kick?
Sandra Schlichting wrote: Dear readers, I was shocked to see that puppet kick will be deprecated in 3.0.0 https://projects.puppetlabs.com/issues/15735 How can MCollective replace puppet kick? http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/AgentPuppetd Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Chart of the most common Ruby I should know for puppet 3?
Sandra Schlichting wrote: Hi all, Being new to puppet 3 and to Ruby. Does there exist a chart of the Ruby I should know? The Puppet language reference: http://docs.puppetlabs.com/puppet/2.7/reference/ A Ruby primer: http://www.ruby-lang.org/en/documentation/quickstart/ Although learning Puppet's language is far more important than learning Ruby. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Community Manager @ Puppet Labs
Hi all For the last few months Mike Stahnke has been handling our community management but he has been sadly lured back to Engineering to pursue his true love which is building, testing and releasing software. This leaves us with the need to find an awesome Community Manager. We'd love to hear from people in the Puppet community itself with interest in the role or please pass on the details if you know someone who you think will be great! Feel free to email any questions to me and the link to apply is here: http://bit.ly/SdaCHL Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Installing CloudFoundry.org components using Puppet
Bryan wrote: Hi, Does anyone have any experience of installing CloudFoundry.org components using Puppet? I found James Turnbull's repository (*), but it doesn't seem to have been updated since May 2011 and i'd be interested to hear from anyone with more recent experience. The installer appears to use Chef - so not sure if its worth the effort to re-implement using Puppet. Hi Bryan Yes that repo is probably out of date. I've not had any time to play with CloudFoundry recently. I wrote the original because I wasn't happy with the installer and how flexible it was. They may have improved that but if they've used Chef then any configurability will probably only be available via editing the cookbooks. If you decide you'd like Puppet modules I'd welcome patches. Thanks James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Tone on the list (was Re: [Puppet Users] Re: Custom types in environments working .... yes/no/maybe ?)
Douglas Garstang wrote: What a horrible clusterf*ck mess. Douglas Can you please keep your tone polite on the list. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] a complete solution for puppet
On Friday, July 27, 2012 8:10:05 AM UTC-7, Trevor Vaughan wrote: Best.Post.Ever Seconded. Scaling is not a stand-alone problem. Indeed beyond the infrastructure components you also need to consider how you scale risk and availability across multiple combinations of architecture and stack, your Puppet configuration, your module style, ENC/Hiera design and how you handle commonalities and exceptions. The default setup and configuration for any application or stack generally has a sweet spot. And generally that sweet spot isn't at 1 machine or 100,000 machines but tries to strike a balance in the middle. You will almost always need to tune the application or stack to your sweet spot. Regards James -- 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/-/KS5NOvClymYJ. 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 Online Linter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I just launched the Puppet Online Linter (http://www.puppetlinter.com/). It automates Puppet linting online (using Tim Share's awesome puppet-lint - http://puppet-lint.com/ ) and has two modes of operation: * Upload one or more manifest files and submit them for linting. The error output will be returned on screen. * Send a manifest via the API (http://www.puppetlinter.com/api) Two disclaimers: * This is not a Puppet Labs run project (hence my non-work email). Please report all errors to me rather than Redmine. And importantly about privacy: your Puppet code is only stored on the linter whilst it is being processed. After processing all data is deleted. Hope it's useful to you and feature requests welcomed! Cheers James - -- Author of: * Pro Puppet (http://tinyurl.com/ppuppet) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP8cMaAAoJECFa/lDkFHAyvpAH/AjqzYbuW3hNk+/BiEPfpPfx bZmLixUi/7nYideAA8u+1L8V3QFiaJj2irvhHtiAhDPzCk4bGl78h8pD3lBJOQPw uYcDl8NB9QVb86U0/jDsxLeSlJnRfakAEq0C+1C++qfOHNWlSXUJJLX9Afs7+Km7 5T6K1ZUoWrb1z0z7sLImoCIwHA++gvmoLHmEjLEWekU1qzKYTEFe6bT4XqIgcvLw TCaDraZXg2gHYwrOeAoHPW88P9Gjxa8RgCm9H3YjZNNH8/OAC975gV6golmYDJ2k ZpvmV+5gml1qxA6zYOFJnla1Ts9YmsUAYJBqG87orSXXltK65WXsu9T5q2bqDJY= =rgEh -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-Rundeck Integration
Carlbob wrote: Hello- I'm running puppet enterprise 2.5.1 and just installed the puppet- rundeck gem. When I try and start puppet-rundeck, I receive the message below: You need to have Puppet 0.25.5 or later installed /usr/lib64/ruby/gems/1.8/gems/puppet-rundeck-0.0.7/lib/puppet- rundeck.rb:34:in `configure': uninitialized constant Class::Puppet (NameError) from ./puppet-rundeck:62 I did pass in the correct path to my puppet.conf file using the -- config parameter. Not sure what's wrong. Does this gem work with Puppet Enterprise? I wrote the gem (prior to PE being released) and I suspect it doesn't work with PE at all. If you could log an issue then I'll see about doing some testing (https://github.com/jamtur01/puppet-rundeck) Thanks! James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Announce: Puppet 2.7.16 Available
Repos should be back working now. Temporary glitch. Regards James On Jun 14, 2012 12:08 PM, Jo Rhett jrh...@netconsonance.com wrote: On Jun 13, 2012, at 2:52 PM, Matthaus Litteken wrote: RPMs are available at https://yum.puppetlabs.com/el or /fedora https doesn't seem to work. http is working fine. *Significantly improve compilation performance when using modules This appears to be a flat 9 seconds across a wide variety of nodes, fwiw. Some nodes have few classes, some nodes have many, and before/after compilation times are exactly 9 seconds faster after the master upgrade. This is a ~5% improvement at this site. (a few were 8 seconds, but the vast majority were exactly 9 seconds different) -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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] Projects.puppetlabs.com outage 5/22/2012
Hi all Due to some required maintenance our provider is doing the Redmine projects site will be down from 6.00PM PST to 6.30PM PST tonight (5/22/2012). We apologize for the inconvenience and the short notice. If you have any questions or concerns please contact me. Thanks James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Triage-a-thon - 1/21/2012
Hi all We're really excited about the Triage-a-thon tomorrow. It's going to kick off at 7am PST and go to 4pm PST. We're going to be in the Puppet Labs offices in Portland (Suite 500 411 NW Park), #puppethack channel on Freenode and available via email on the various Puppet Lists and announcing progress on Twitter via the @puppetlabs account. For instructions and information on the event see: http://projects.puppetlabs.com/projects/puppet/wiki/Triageathon If you have any questions or issues or need help please don't hesitate to get in touch! Thanks James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Something wrong with puppet-users group?
Jeff Sussna wrote: All my other Google Groups load pretty quickly. Puppet-users is very slow and often times out. Yes - I just noticed this and I am not sure what's happening. We've only got 30K messages. I am unsure if that's a lot and perhaps causing an issue? Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Triage-A-Thon
Christopher Lee wrote: Hello, You have selected a date for the Triage-a-thon in the middle of SCALE. Would love to help out but I am guessing many people will be at SCALE including people at Puppet Labs. We knew it was during SCALE. We knew some people (including a couple of ours) will be there. But the Puppet community is pretty big and now very global (hence the early start West Coast time to allow East Coasters and Europeans to get involved). We'll also have plenty of Puppet Labs people in the office in Portland and online to help out too. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Triage-A-Thon
Brian Gallew wrote: #4020 has been ready for 4 months now. It really makes my efforts feel appreciated. Brian Totally get that this is frustrating. It's really hard for us because when the use of Puppet exploded so did the number of people logging tickets (hence the Triage-a-thon!). In the case of #4020 it's totally my fault and I apologize. I missed your update that you had submitted a new patch with tests. I'll ensure the ticket is updated and passed to Engineering for review. In future feel free to berate me when it looks like I've dropped the ball. It's the only way I'll learn. :) Thanks for your patience and your contribution! Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] need link for simple docuemntation
Sergio Galvan wrote: Hi , You can take a look to Learning Puppet: Modules http://docs.puppetlabs.com/learning/modules1.html I guess the best option to understand how modules work is to make some by your own. I also like to take a look at Github http://github.com , reading how others wrote their modules definitely it would help you out. The Forge (http://forge.puppetlabs.com) has about 260+ modules that are also useful examples. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Triage-A-Thon
Love Puppet? Hate the backlog of tickets? Want to help us out? The Puppet community has grown really fast and a lot of you have logged tickets and issues. We’ve tried to give those tickets as much love as we could but some slip through the cracks and sometimes we get overwhelmed. We’ve recognized this and want to try to get a handle on the backlog of tickets. But we need your help to do this. What we’re going to do is hold a Triage-a-thon hosted locally in our offices, virtually on IRC (Freenode #puppethack) and the Web. http://puppetlabs.com/events/triagepuppet/ We’re going to review all the open tickets in the Puppet project with a view to: * Update and confirm that issues are still relevant * Ensure tickets are in the right status and all the right information is present to help us resolve it * Close any invalid or no longer relevant tickets We’ll assign blocks of tickets to every participant, have documentation explaining what you need to do and provide people on the ground to help you make decisions and answer questions. Triaging starts Saturday January 21st from 7am and last until 4pm (-8 GMT). We’ll also provide pizza, snacks (and beer!) and a venue locally in our Portland, OR offices. Virtually we’ll provide an IRC channel, IM and rewards (t-shirts, patches, stickers, badges, and books) for people who triage tickets and get involved. We’ll also offer Amazon Gift Cards to our top 3 participants! You can register for the event here: http://triagepuppet.eventbrite.com/?ref=ebtn. We hope you'll be interested in attending and helping us make Puppet better. Thanks James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: [Puppet-dev] Re: When the lint accumulates...
Walter Heck wrote: On 2011-19-12 21:00, James Turnbull wrote: So what can you do to help? Well firstly help us identify any syntax, language constructions, structures etc that have caused issues for you or that when used result in errors or issues. You can let us know about these in three ways 1) When I run puppet-lint manifests/*.pp, it would be nice to have the filenames output. Right now it just outputs all errors for all files in one big list, which doesn't tell me which errror belongs to which file. There's a patch for this already: https://github.com/rodjek/puppet-lint/pull/38. 2) I'd like to define the errorlevel (eg. --errorlevel=error) I've added a ticket for this also: https://github.com/rodjek/puppet-lint/issues/45 Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: [Puppet-dev] Re: When the lint accumulates...
Christopher Johnston wrote: Is there a minimum version of ruby or puppet for it to work? I am open to running this on my entire puppet tree (close to 53 modules and growing). puppet-lint /etc/puppet/manifests /usr/lib/ruby/gems/1.8/gems/puppet-lint-0.1.7/bin/../lib/puppet-lint/plugin.rb:43: warning: parenthesize argument(s) /usr/lib/ruby/gems/1.8/gems/puppet-lint-0.1.7/bin/../lib/puppet-lint.rb:28:in `read': Is a directory - /etc/puppet/mE from /usr/lib/ruby/gems/1.8/gems/puppet-lint-0.1.7/bin/../lib/puppet-lint.rb:28:in `file=' from /usr/lib/ruby/gems/1.8/gems/puppet-lint-0.1.7/bin/puppet-lint:51 from /usr/bin/puppet-lint:19:in `load' from /usr/bin/puppet-lint:19 Christopher You're trying to read a directory - it needs a file. $ puppet-lint /path/to/file.pp I usually grep all my files in /etc/puppet/manifests or modules and pipe all the .pp files through puppet-lint. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] When the lint accumulates...
So some of you may be aware that Tim Sharpe from GitHub wrote a Puppet linting tool: $ gem install puppet-lint $ puppet-lint mymanifest.pp Source: https://github.com/rodjek/puppet-lint The linting tool checks Puppet code for best practice based on the Puppet Labs Style Guide: http://docs.puppetlabs.com/guides/style_guide.html A lot of us have been using puppet-lint (and puppet parser validate) to ensure our code is synoptically correct and as best practice as possible. We're also aware that there are some strange and odd things in the Puppet language and whilst we can't fix all them right now we'd like to find a way to highlight items and syntax that is sub-optimal for you via linting. So what can you do to help? Well firstly help us identify any syntax, language constructions, structures etc that have caused issues for you or that when used result in errors or issues. You can let us know about these in three ways: * Submit patches and additions to the linting tool. Patches in the form of failing tests are especially welcome if you aren't comfortable adding new tests yourself. * Email me or the list with tickets containing issues like this. * Send me or the list snippets of Puppet code that cause issues and the output/issue they result in. We'll also look at tracking as many of these as possible and where relevant update the Style Guide with them too. Cheers James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Learn from MY Mistake: false != false
Dan White wrote: Thanks for pointing that out for two reasons: (1) In the flow of the mailing list, simple little tricks like this can flash right past you if you are not reading carefully. (2) That thread gave me a better approach for what I am doing in my class. Thanks again, everyone ! This is an excellent example of something that could be caught by linting until the bug is fixed: https://github.com/rodjek/puppet-lint/issues/43 Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet kick getting hostname not match with the server certificate
John Kennedy wrote: OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd version - 2.6.6 I searched Google and none of the answers were a match for my set up... I can do 'puppetd --test' from the client and things work as expected. When doing puppet kick hostname I get the following: Triggering hostname Host hostname failed: hostname not match with the server certificate hostname finished with exit code 2 Failed: hostname John Did you ever work out the issue here? Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: [Puppet-dev] need help w/ puppet error when running against my sandbox environment
Brian L. wrote: Guys, I apologize ahead of time if this article shouldn't be posted here... I have spent a couple of hrs debugging an issue w/ my sandbox setup so that I can test my code before committing and pushing out my code in production. I ran it against my own environment=blam and got the following errors that I can't make out what it is… err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://m0008001.ppops.net/plugins … … err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class services at /etc/puppet/manifests/site.pp: 10 on node m0009477.lab.ppops.net Any idea where I should be looking? (I will also check out the book Pro Puppet by James Turnbull also to see if I can get some hints.) Thanks! Is there a class called services? What's on line 10 of /etc/puppet/manifests/site.pp? I'd bet it can't find that class. I've cc'ed in the puppet-user list which is a better place to ask this question. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Announce: Puppet 2.6.13rc1 Available
Jo Rhett wrote: I would think that a bug fix for #11143 should be in the next release. The issue hasn't had more the most basic triage done and we don't even have root cause. Nigel and Engineering may have a view on it but I would suggest it won't make .13 which is already in RC. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: [Puppet-dev] Puppet IRC logs
Dan Carley wrote: Nice work. Always a great resource for finding information about obscure error strings. Small request: could you setup a ServerAlias for puppetlogs.com http://puppetlogs.com? Done. James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet IRC logs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I finally got around to fixing the IRC logs up a little and adding them to their own site: http://www.puppetlogs.com/ The site contains search-able IRC logs for #puppet and #puppet-dev going back to late 2007 or so. It's maintained by me (not Puppet Labs) so best to contact me for issues rather than bother anyone else. Regards James - -- Author of: * Pro Puppet (http://tinyurl.com/ppuppet) * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOy0LNAAoJECFa/lDkFHAyOs8H/3lfiK5W0bTurrJcIEeFaSGT QxcxNzx/P9F6dbCnzjuHLIo1MnjVNMiYCIv7SvK6tYhH50PDrLOw/IeZvH9sijDy dEs9s+HsySjHjM4afTNpax5gx+Mm3mEZNXJt5MpABD0Z7xxRHUzw6ZwtTeJ/rccn 6WaOD5akWGAoTV9OH6/K2OWhO7pwy931drt2C1oJQik9mPnyzmFlyeqXxYq8Oh0s wRZ+jG2FTNxp8Kk6ZuR24mdT6ks3mxTa7WP2Dv2ucpMuqmgN4tycKt50iBudEXEO Q1EuOR6G8+tbEb+8Ijkr4GIi5nCp/7CswG2Uq84yLUQ3OPEH4aZIFLaeBzmp5KY= =Hcfb -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.
[Puppet Users] FOSDEM 2012: Configuration Systems Management DevRoom
Call for Papers - FOSDEM 2012 **Call for talks for the Configuration Systems Management DevRoom at FOSDEM 2012** Configuration Management DevRoom - http://fosdem.puppetlabs.com FOSDEM 2012 - http://fosdem.org/2012/ 4th 5th of February (date TBD) 2012, 09:00 to 17:00, Brussels, Belgium Contact: fos...@puppetlabs.com We will be holding a Configuration Management DevRoom at FOSDEM 2012 and are requesting abstracts for structured presentations now. Important information, dates: ? Submission deadline for abstracts: 2011-12-31 ? Notification of accepted speakers: 2012-01-05 ? Final schedule: 2011-01-10 **About this DevRoom** Configuration and Systems Management is in a renaissance. There is huge interest in automation, monitoring, performance management, configuration management, DevOps and the cloud. We're seeking people who are working in the field, interested in the field, or just interested in learning more about how to manage infrastructure better, cheaper and faster. We invite you to submit talks on these topics: * Configuration and Systems Management theory principles * Configuration and Systems Management tools - with an emphasis on real world use cases * Tools, techniques and case studies * The Cloud * Audit, Compliance and Security * DevOps NOTE: Puppet Labs is helping organize this room but we're looking for talks on more than Puppet! We're looking for talks on the cutting edge of systems tools and configuration management. This is your opportunity to show off your implementation, your tool or what your environment shine! Regards Nigel Kersten James Turnbull -- 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: Is it possible to get a list of all nodes in your manifests and all classes assigned to those nodes programatically in Ruby?
Trevor Vaughan wrote: Sorry but...bump? On 11/18/2011 02:20 PM, Trevor Vaughan wrote: Sorry if this is a double post, my e-mail glitched on me. Anyway, I'm trying to write a Ruby script that can get all defined nodes and all classes assigned to those nodes. I would prefer to not have to compile a catalog for each node. I tried looking through the puppet/util/rdoc material but it really didn't handle the node entries as far as I could tell and also didn't seem to have a way to get the info without printing it all out. Sorry missed this one - I do something vaguely similar for the Puppet Rundeck integration - have a look at the code at: https://github.com/jamtur01/puppet-rundeck Others may be able to chime in with better ideas. James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet-dev] Re: [Puppet Users] Re: Is it possible to get a list of all nodes in your manifests and all classes assigned to those nodes programatically in Ruby?
Trevor Vaughan wrote: Thanks James. I knew how to do that, I was actually trying to figure out if I could do it the hard way by delving the manifests instead of having to wait for a system to check in. I'm pretty close to saying that the answer is 'no'. Oh I see. You mean before the catalog is compiled? I think the only way to do that IS compile the catalog. But again others may be smarter than me. :) James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] When will Puppet officially support Ruby 1.9.2+
On Nov 18, 2011 5:57 PM, tetsutetsu@gmail.com wrote: Hello everyone, Ruby 1.8.7 is EOS now. So, when will Puppet become Ruby 1.9.2+ compatible? I am considering to deploy Puppet on a large hosts of servers. If Ruby 1.9.2 cannot be supported, I have to turn to Chef. Puppet has supported Ruby 1.9.2 since 2.7.0. Regards James -- 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] ANNOUNCE: Puppet Labs stdlib module version 2.2.0 released
Jo Rhett wrote:
James, I love the idea of this module but the wiki page you listed below
is fairly broken. The syntax under anchor certainly wouldn't parse, and
I'm staring at it and I'm not even sure what some of it is intending to
say...
Jo
The syntax does parse from what I can see and the wiki documentation is
automatically generated from the code inside the module so it's not 100%
perfect yet and needs some more work. I'll add a ticket mentioning the
documentation parser needs to be cleaned up a little or you're welcome
to do the same!
The module contains additional documentation for the type that I've
reproduced below:
A simple resource type intended to be used as an anchor in a composite
class.
class ntp {
class { 'ntp::package': }
- class { 'ntp::config': }
- class { 'ntp::service': }
# These two resources anchor the composed classes
# such that the end user may use require and before
# relationships with Class['ntp']
anchor { 'ntp::begin': } - class { 'ntp::package': }
class { 'ntp::service': } - anchor { 'ntp::end': }
}
This resource allows all of the classes in the ntp module to be
contained within the ntp class from a dependency management point of view.
This allows the end user of the ntp module to establish require and
before relationships easily:
class { 'ntp': } - class { 'mcollective': }
class { 'mcollective': } - class { 'ntp': }
Hope that helps!
Regards
James Turnbull
--
James Turnbull
Puppet Labs
1-503-734-8571
To schedule a meeting with me: http://tungle.me/jamtur01
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: [Puppet-dev] Re: ERROR: Connection reset by peer
Dmitry wrote: Or, if this situation is too uncommon, is there any way to ask puppet agent to always act as if master is running on remote host, even if it runs on the same host and to always communicate via network? Thanks. On Nov 15, 7:13 pm, Dmitry trtrmi...@gmail.com wrote: Hello! I use puppet-2.7.6 to sync several config files in my network. I use neither Mongrel nor Passenger (which probably means I use Webrick as http backend). When I run puppet agent from another machine, everything is fine. When I run agent from the same machine server is running on, I get the following error: # puppet agent --server =hostname.com --no-daemonize --onetime --verbose --no-show_diff skip err: /Stage[main]/Bsd/File[/root/.ssh/authorized_keys]: Could not evaluate: Conn ection reset by peer Could not retrieve file metadata for puppet:///modules/bsd/ root/.ssh/authorized_keys: Connection reset by peer at /usr/local/etc/ puppet/mod ules/bsd/manifests/init.pp:117 If I run same command several times, I usually get the same error at different stages (during request to different files puppet manages). But error is always the same: Connection reset by peer. Sometimes it finishes w/o error, but almost always I get this error. Some kind of random. What does it mean and how can I avoid it? Thanks! Probably best to ask this question on the Puppet-user list rather than the Puppet-dev list. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ANNOUNCE: Puppet Labs stdlib module version 2.2.0 released
We're pleased to announce a new release of the Puppet Labs stdlib module. This module provides a standard library of resources for developing Puppet Modules. This modules will include the following additions to Puppet: * Default Stages * Facts * Functions * Defined resource types * Types * Providers This module is officially curated and provided by Puppet Labs. The modules Puppet Labs writes and distributes will make heavy use of this standard library. The CHANGELOG since the last release is: 2011-11-08 Puppet Labs supp...@puppetlabs.com - 2.2.0 * #10285 - Refactor json to use pson instead. * Maint - Add watchr autotest script * Maint - Make rspec tests work with Puppet 2.6.4 * #9859 - Add root_home fact and tests The module is available via the Puppet Labs Forge at http://forge.puppetlabs.com/puppetlabs/stdlib. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://tungle.me/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] What the?? (gem install puppet not working) sorta... read on...
Peter Berghold wrote: Hi folks, In the past when I've wanted to install puppet to a system Ive just done a gem install puppet facter' and it has workd. After runing the gem install I tried running puppetd and was told not found. OK, so I started to dig and discovered that puppetd was indeed installed on the system, but in the directory /var/lib/gems/1.8/bin directory along with facter and all the other puppet friends. A quick round of symlinks and I was back in business. This was on a debian (squeeze) system. SO for all those that might run into what I did, I've blazed the trail... This was a decision the Debian team made about how gems would be deployed on Squeeze and maybe Etch (I think it changed later but when I am not sure). Some notes about it in this thread: http://stackoverflow.com/questions/2846804/whats-the-deal-with-rubygems-on-debian-its-different-and-strange Regards James Turnbull -- 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.
[Puppet Users] The getting of wisdom - Puppet Labs and Hiera
Over the last couple years R.I. Pienaar has attacked the problems of storing and separating data and logic in Puppet and other tools. He started with the extlookup function (which was merged into Puppet in the 2.6.x release series) a simple file-based hierarchical data store. He then tackled the problem with Hiera: a simple pluggable Hierarchical Database. Hiera is a significant enhancement over extlookup, comes with a much closer integration to Puppet than extlookup and supports a wider variety of data sources. We're thrilled to announce that Arri has decided to pass the Hiera project into the custodianship of Puppet Labs. From a license perspective nothing changes - Hiera remains free, open source and licensed under Apache 2.0. Puppet Labs will be taking on the patching, management and development of Hiera going forward. We'd also like to merge Hiera into Puppet core as extlookup was but we don't want to reduce its utility as a standalone tool and so we're still considering the best approach to take. We'd welcome input from the community on this. If you have tickets or issues to raise about Hiera please log them at: http://projects.puppetlabs.com/projects/hiera The Hiera code is now located at: https://github.com/puppetlabs/hiera https://github.com/puppetlabs/hiera-puppet https://github.com/puppetlabs/hiera-json Please feel free to email the list or me directly if you have any questions about this. Thanks James Turnbull -- 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.
Spam (was Re: [Puppet Users] Business Intelligence 2011 (November 12th,Delhi))
Lincy 123 wrote: Hi, I got to know of an exciting event happening in Delhi on November 12th Apologies all - this is spam that slipped through. 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] Review of new type provider
Jesse Peterson wrote: Hello, I'm new to both Ruby and Puppet. Puppet is fantastic - loving it so far. I created a new type provider (of parsed file type) for modifying newsyslog.conf files and am hoping some folks would be willing to review it to make sure there are no glaring mistakes or perhaps some shortcuts or language features I've missed since I'm new to both. Any input would be welcome. Either email directly or just comment on the gist if it gets to be off topic: https://gist.github.com/1230749 Looks okay to me - I'd recommend writing some tests for it - ParsedFile providers are notorious for subtle bugs and small changes causing odd effects. How often do new types/providers make it into the base system? Should one pursue that avenue (or perhaps the puppet modules project?). We're trying to keep the core lean and mean. So I'd recommend creating and adding a module to the Forge (http://forge.puppetlabs.com) with your new type and provider. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] OpenBSD/i386 Puppet 2.7.3
Darren Spruell wrote: These don't seem like complementary options to me (complementary to minimum/maximum password age, anyway). OpenBSD's useradd(8) is derived from NetBSD's so the same situation is likely to occur there. http://www.openbsd.org/cgi-bin/man.cgi?query=useraddsektion=8 http://netbsd.gw.com/cgi-bin/man-cgi?useradd+8+NetBSD-current Is a slightly modified provider needed? Yes. It'd be great if you could log a ticket please. Thanks James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] OpenBSD/i386 Puppet 2.7.3
dspruell wrote: Could not find a default provider for user I'd say this is a variant of http://projects.puppetlabs.com/issues/4963. A similar fix to the code in that ticket should work. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Slightly OT: Puppet + OpenQRM
treydock wrote: I've recently been looking to move my KVM management (currently via Puppet and virt-manager) to something web-based and robust (ie Cloud), and came across OpenQRM. Looking at the features list it mentions puppet Class/Machine management. Has anyone that uses Puppet extensively given this a try? I'd like to get input on how this works. The only ENC or GUI interface I've used with Puppet is Foreman (which is awesome btw), but this peaked my interest. Thus far I've tried Cloudstack (a few months ago) and Convirt, both were great, but not what I needed. Any input on experiences with OpenQRM as it relates to Puppet would be great, thanks. Trey So I wrote a very basic article some time ago: http://searchenterpriselinux.techtarget.com/tip/How-to-install-and-get-started-with-OpenQRM Things have changed quite a bit with the product since then and the best bet is probably to talk to the primary guy - Matthias Rechenburg. Cheers James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] OS X Lion group membership not updated
David Thompson wrote: Switching to puppet (2.7.3) for managing my OS X Lion systems, I'm finding group membership not being updated. Any help much appreciated... David I think there are a bunch of OSX Lion bugs in the ticket DB that might be worth checking if this one is picked up. We've got code for some and need to do some refactoring for others. Cheers James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Package provider for gentoo?
Peter Berghold wrote: Now I get: err: Could not prefetch package provider 'portage': Command update_eix is missing I'm running puppet 2.7.3 on both the puppet master and the client. Any thoughts? Caveat: I am not a Gentoo person. Is the binary update_eix present on the host? James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Inherited 0.2.5 installation
genkuro wrote: Out of curiosity, why the big version numbering jump for Puppet? The releases go from 0.x straight to 2.x. The big jump was because our release numbering was wrong - major feature-heavy releases occurred within minor release numbering. So when we had a chance we changed the numbering up to properly reflect feature/maintenance releases. Puppet looks great so far. But documentation is sprawling. It looks like 0.2.5 has been abandoned. Any idea where I can find dedicated 0.2.5 docs? Preferably online? We have stopped issuing maintenance for 0.25.5 except for potential security issues because more recent releases provide better performance and features. The reference docs for 0.25.5 are available at: http://docs.puppetlabs.com/references/0.25.5/ Generally speaking (where possible) the rest of the Docs site calls out versions of specific features. I'm guessing the 0.2.5 - 2.x migration must be common. Can I expect this to be a slam dunk? There are no major issues but testing is obviously recommended. The Puppet model is to upgrade the master first and then the clients. We guarantee backwards compatibility with older clients talking to newer masters but not vice versa. Hope that helps! James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Release tarball spec file
Douglas Garstang wrote:
I know this is a crazy request, but I was kind of wondering why it was
so hard for Puppet Labs to maintain the RPM spec file that comes
contained in the release tarball, so that modifications weren't required
to actually get it to build. Crazy huh?
For example, the SPEC file contains this...
Version:2.7.2
Release:0.2.rc1%{?dist}
but the release is 2.7.3. Also 'rc1' is hard coded in several places,
and so forth.
Douglas
Patches are always welcome. If you update it or change it then send a
pull request and it'll be more likely to be up-to-date.
That being said I echo Mike's comments about it being a helper for
people rather than our primary role as the upstream developer. My
preference is we focus on features and fixes rather than packaging
specification that is actually better handled by people downstream of us.
Regards
James Turnbull
--
James Turnbull
Puppet Labs
1-503-734-8571
Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd
and 23rd in Portland, Oregon, USA.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ANNOUNCE: Puppet Module Tool version 0.3.4
Hi all We've just released version 0.3.4 of the puppet-module tool used to create and retrieve modules from the Puppet Labs Forge (http://forge.puppetlabs.com). You can update using Ruby gems: $ gem install puppet-module There are several important changes in this release: * Add ability to install modules with hyphens * Add check for symlink when installing * Install modules to their name not full name * Add semantic version support The major functional difference is in how modules are installed, for example a module named: jamtur01-apache Will now be installed into your module path as: apache You can find the code and full commit logs at: https://github.com/puppetlabs/puppet-module-tool Regards James Turnbull -- 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] Redmine and Forge outage
Hi all This morning one of our hosting boxes - the one hosting our Redmine issues box and the Forge site - went down. The issue was a DC one and has been resolved. We apologise for any inconvenience and please feel free to email me if you have any continued issues! Thanks James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Master failover and cert names.
Douglas Garstang wrote: Well, this is frustrating. Let's say I have two puppet masters, where one is active, and the other is a hot stand by. Obviously each is going to have a different FQDN. Everything will work fine when the client talks to the server that signed it's certificate. However, after a failover to the secondary master, it's all going to fail because the FQDN of the master will not match. I've been searching around, reading the mailing list, and am surprised to find very little information on this. The new Pro Puppet book skims over this detail. You'd think they'd have some proof it before selling it. Douglas Did you read the chapter carefully? The Front End Load Balancer Configuration section explains this pretty clearly. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] ANNOUNCE: Cloud Provisioner v0.6.0rc1 release
Scott Smith wrote: Gonna take a wild guess that there are plans to support other providers.. Correct! Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: ANNOUNCE: Cloud Provisioner v0.6.0rc1 release
Jared Curtis wrote: Any plans to support other cloud providers? Specifically VMWare? Jared There are such plans. Obviously it's also open source so we'll add some further support and hopefully the community will chime in with other updates and enhancements that they require. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Registration for PuppetConf is now open!
Registration for PuppetConf (http://www.puppetconf.com ) is now open and the first 50 registrants will receive a free copy of Pro Puppet! We've got an awesome lineup of speakers [http://www.puppetconf.com/speakers] speaking on DevOps/Operations, Cloud Computing, and Puppet. The conference takes place in Portland, OR on September 22nd and 23rd with seven training opportunities taking place in the three days prior to the conference. Our camp series has been incredibly successful over the past 2 years, growing form 60 to 200 participants and we've decided to grow the conference this year. We're broadening the appeal by adding tracks on cloud computing and on operations in addition to Puppet-focused tracks. With regard to Operations, you'll hear from Pedro Canahuati, Facebook's SRE Manager, vocal DevOps enthusiasts John Willis, Damon Edwards, John Vincent, and Dave Connors, VP of Operations at Constant Contact. You'll also get expert advice on getting started with Puppet from speakers like Martin Englund from VMware. Martin is fresh off a successful bake-off between Puppet and other CM tools and will be speaking about what it's like to bring Puppet into an enterprise environment. You'll hear from R.I. Pienaar, the author of MCollective. Additionally, our entire development and professional services teams will be attending the conference. Another cornerstone of the conference will be our track on cloud computing. A wide range of talks touching on many of the leading cloud solutions will be presented along with expert tips for deploying and managing large cloud infrastructures. Jamie Cox will be presenting on Zynga's EC2 fleet and executives from Nimbula, Eucalyptus, Cloud.com, and Rick Clark, a founder of Openstack will give an insightful look into the future of cloud computing during a panel session. Over the course of the track we'll undoubtedly move closer to answering the question What would the world look like if the size of your server fleet was entirely flexible? Portland is also a great town for a visit too with good beer, wine, food and some cool stuff planned for attendees. We really hope you'll all come along! Cheers James -- 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] Problems In New Pro Puppet Book
Jon Forrest wrote: I should first say that I'm a complete beginner to Puppet so some of what I saw below could be incorrect. Pro Puppet is a pretty good book so far but it really should have had another editing step to correct the problems I've mentioned below. Thanks for the feedback. Better to send it to the publisher than sending it here - they can actually act on Errata. http://www.apress.com/9781430230571 Thanks again James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] catalog run time? what about facter run time?
vagn scott wrote: The catalog run time that is reported: does that include the facter run time? If not, how should I get that? What kind of performance statistics does puppet/facter keep, if any, and how do I access them? Is there a FM I should R? It doesn't include the Facter runtime but you can output performance data from Facter by running it with the --timing switch on the command line. As to other statistics - there are a number in reports that you can access. See http://projects.puppetlabs.com/projects/puppet/wiki/Report_Format_2. Regards James Turnbull -- 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] Large scale puppet deployments
Tim Bell wrote: I am looking for - an estimate on the number of machines that Puppet can manage - a pointer to how these large scale configurations can be set up Largest install I am aware of is 100K machines but I suspect they probably have more now. I know of multiple 50K to 100K installations and numerous 10K to 50K installations. Those usually involve multiple Puppet masters deployed geographically and locally redundant usually front-ended with load balances of various kinds (HW/Apache) with masters running Apache-Passenger, Nginx, Unicorn and the like. What's your use case and I can probably expand on this. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] The 2.6.9, 2.7.0 and 2.7.1 releases
Hi all There is a little bit of confusion about the status of fixes in the 2.6.9 and 2.7.0 releases. When 2.6.9 was being worked on the 2.7.0 release was frozen in release candidate. This means tickets fixed in 2.6.9 were NOT merged into 2.7.0. Nor were they merged into 2.7.1 which only had one critical fix in it. The code from the 2.6.9 tickets will be merged into the 2.7.2 release and relevant fixes from 2.6.9 will then work. Hope that clarifies things. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Linux hardening
Douglas Garstang wrote: This raises an interesting question. I had been doing something similar recently, and I had implemented the hardening within the specific puppet modules that they were related to. However, you've written a totally separate module. Which is better? I was specifically trying to provide an example of a module to apply a particular standard. I don't it makes much difference which approach you take. Although if you break the hardening into classes though you can make exceptions to which nodes they are applied. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] Linux hardening
Nicolas Arias wrote: Hi guys!. I want to use puppet to automate initial linux hardening and to maintain a security configuration standard. Does any one knows if there are modules going around that take care of the usual hardening steps?. If not, i will work on them and share them. I started this modeled on the CIS Linux Security guidelines. https://github.com/jamtur01/puppet-hardening It's not complete but covers a selection of the controls. You're welcome to fork/hack on it. Patches welcome etc. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 Join us for PuppetConf http://www.bit.ly/puppetconfsig, September 22nd and 23rd in Portland, Oregon, USA. -- 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] The Puppet Wiki
Hi all As you'd be aware there's some old and probably not great content on the wiki. We're going to begin moving the good stuff into the Docs site and purging it from the wiki (we'll put in redirects where needed too). We'd love help doing this if anyone is interested too - fork the Docs project at: https://github.com/puppetlabs/puppet-docs And hack away. If you have a page that you'd especially like or think deserves saving in the Wiki now is the time to clean up and edit it and make it nice and shiny. And of course as always feedback on this approach and any other documentation issues, weaknesses or problems is always welcomed. Either via tickets (http://projects.puppetlabs.com/projects/puppet-docs/issues/new) or via email. Thanks 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] 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.
[Puppet Users] Velocity and free beer
For anyone at Velocity this week we're doing some speaking and buying some drinks: http://www.puppetlabs.com/blog/santa-clara-schedule-asynchronous-real-time-monitoring-with-mcollective-at-velocity-puppet-labs-happy-hour/ Jeff McCune is speaking about MCollective and monitoring on Wednesday at 1pm. Also on Wednesday night we're buying drinks at TechMart right next door to the Santa Clara Convention Center from 4pm or so until we run out of beer. :) Regards 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] Testing, testing . . .
Guy Matz wrote: Any of you folks have any good tests that you use to make sure a module has completed successfully? Any best practice suggestions? I looked around on the www but didn't see anything about this. Please point me in the right direction if I missed it. thanks, Have you had a look at Cucumber-Puppet? http://projects.puppetlabs.com/projects/cucumber-puppet Regards James Turnbull -- 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 Support for OSX
Mister IT Guru wrote: Hi guys – I was wondering how well puppet performs on OSX. Anyone here had any experience using puppet under OSX? Very well and it's well supported. Google uses it to manage their internal OSX desktops as do a number of other companies, universities, etc. Regards 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] Re: New Puppet report processors...
treydock wrote: My [master] has : report = true reports = http, store, xmpp pluginsync = true The [agent] includes: report = true listen = true pluginsync = true The second agent I tested with also has the same configuration as the above [agent] Correct, the xmpp.yaml has all that information. What I was asking about the remote client not having mail.yaml is I enabled pluginsync on the remove client to see if the results would differ and it failed stating the mail.yaml was missing (locally on the client). But if the repots = xmpp is only defined for [master] then should I not include pluginsync = true on the clients? So you don't have anything like the line: Sending status for name.of.host to XMMP user jabber.user in your Puppet master syslog. Regards 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] Re: New Puppet report processors...
Craig wrote: Hi, These sample reports have been very useful, thanks! Is there is a way to only send a report once every 24 hours (say)? For example, I want to know about failed runs, but not every time someone is hacking around, changing something, re-running etc. I can think of all sorts of workarounds, just wondering if there's something built in to help here. There isn't currently - all of the report processors that trigger on failed runs trigger on all failed runs. I would suggest as an aside/workaround that you turn off notification-style reporting in your test environment (where I presume people are doing this hacking around :) ). My assumption is production Puppet runs that fail are important but you might not care about dev/test so much. Regards 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] Re: New Puppet report processors...
treydock wrote: I don't have any lines like that no. Could the daemon line for puppetmaster be effecting this? Is the -- reports option necessary since my puppet.conf has that specified? PUPPETMASTER_EXTRA_OPTS=--reports puppet_dashboard --debug Other than that and my puppet.conf I haven't found any further configurations I've implemented effecting use of reports Specifying --reports on the command line in PUPPETMASTER_EXTRA_OPTS I am pretty sure will override the puppet.conf configuration rather than add to it. I'd take it out of there and put it into puppet.conf on the master. Regards James Turnbull -- 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] Re: New Puppet report processors...
Don wrote: (possible double-post) James, This is all wonderfully helpful and I just spent a little while writing up a Zenoss processor to send an event on failure using XMLRPC::Client, modeled directly after your puppet-zendesk module, replacing the HTTParty guts with XMLRPC guts. I've encountered a problem though (and we can refer to puppet-zendesk code): When I stuff a fail() into a manifest and run, it fails, sends a report to the PM, and the PM logs this: Report zenoss failed: undefined method `status' for #Puppet::Transaction::Report:0x2b626b5ad7c0 The line in question is from zendesk.rb:25 if self.status == 'failed' ... end So, it's breaking there, but when I replace self.status with var and var = 'failed', bypassing the if, the rest of the code works and the event appears in zenoss. I'm running 2.6.4 on the master client. pluginsync is true on both, and reports = zenoss only on the master for this test. Why is self.status not working in this case? Odd. Can I see the rest of your code? If private you can email me offlist. Regards 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] Re: New Puppet report processors...
Don wrote: I'm running 2.6.4 on the master client. pluginsync is true on both, and reports = zenoss only on the master for this test. Why is self.status not working in this case? The issue is that status is only available in the V2 report format in Puppet 2.6.5 and onwards. Before this you need to check for err tags to find failed runs. Regards James Turnbull -- 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] Re: New Puppet report processors...
treydock wrote: This is the output from master.log during the failed puppet run. Sorry I meant the output from the master daemon puppetmasterd or puppet master. Thanks 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] Re: New Puppet report processors...
treydock wrote: Excuse the dumb question, but what file is the default location or what configuration variable defines that location? I've noticed the bulk of puppetmaster logs go either in /var/log/ puppet/masterhttp.log (previous message) or /var/log/message (syslog I'm assuming). Or is there a different place I should be looking? On the Puppet master it defaults to syslog - so it'll end up in /var/log/messages. Regards 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] Re: New Puppet report processors...
treydock wrote: Ok I restarted puppetmaster daemon and then broke a module to create a failed puppet run on the same host as the master...and here's /var/log/ messages from that Can I confirm you have: [master] report = true reports = xmpp [agent] report = true In your puppet.conf on the master and the [agent] block on the client? You mentioned an issue with the xmpp.yaml file? That should have you Jabber jid, password, target etc and be located in /etc/puppet on the master - not sync'ed with the module. Regards James Turnbull -- 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] Re: New Puppet report processors...
treydock wrote: The report processor was synced to /var/lib/puppet/lib/reports/ . I enabled puppetmaster to run in debug mode but haven't seen anything mentioning reports when I run test runs. I purposly misspelled a module for the puppetmaster and run puppetd --test, but no reports except those in puppet-dashboard. I could be looking in the wrong place. Here's the debug output of the failed puppet run...(hostname replaced) Can I get the master log please. That's where the report is triggered. Regards James -- 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: New Puppet report processors...
treydock wrote: These will be most useful!! Thank you. How can I test that these are functioning? I have setup the XMPP as well as modified that to send emails. However when I purposely cause a puppet run to fail I do not receive either email or jabber message. Is the report processor xmpp.rb pluginsync'ed on your Puppet master? Is there any log out on the Puppet master when you run in --debug mode? Regards James Turnbull -- 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] Concat Module posted to Onyx Point Github.
Greg Sutcliffe wrote: Hi again, After an hour or three of hacking, I've managed to add the insync? checks to both the build and fragment types. It's the first time I've ever really messed with types and providers, so it's very ugly (and probably has bugs), however I'm happy to share my patches. Would that be best a) here b) in puppet-dev, or c) direct to Onyx Point? Awesome stuff! The puppet-dev list is the best place. Cheers 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.
[Puppet Users] New Puppet report processors...
Hi all On my TODO list for about a year now has been a tutorial on how easy it is to write Puppet report processors and how much more you can do with them than just email/log/store Puppet report data. Rather than write a whole tutorial I decided to create a whole series of examples of report processors that should: a) Provide some immediate solutions that you can deploy right now, and b) Provide good examples of things you can do with report processing that you can take, fork and modify. All of them are released under the Apache 2.0 license. In that spirit I've created ten new report processors: 1. Reports failed runs to an IRC channel - https://github.com/jamtur01/puppet-irc 2. Reports failed runs and logs to PagerDuty - https://github.com/jamtur01/puppet-pagerduty 3. Reports failed runs to Jabber/XMPP - https://github.com/jamtur01/puppet-xmpp 4. Reports failed runs to Twitter - https://github.com/jamtur01/puppet-twitter 5. Reports failed runs and logs to Campfire - https://github.com/jamtur01/puppet-campfire 6. Reports failed runs to Twilio - https://github.com/jamtur01/puppet-twilio 7. Reports failed runs to Boxcar - https://github.com/jamtur01/puppet-boxcar 8. Reports failed runs to HipChat - https://github.com/jamtur01/puppet-hipchat 9. Sends metrics to a Ganglia server via gmetric - https://github.com/jamtur01/puppet-ganglia 10. Reports failed runs to Growl - https://github.com/jamtur01/puppet-growl Comments, feedback, testing and ideas for other integrations all welcomed. Regards 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.
[Puppet Users] Re: [Puppet-dev] Re: Open Source Team planning meeting summary
Andrew Forgue wrote: #5517 - behavior change within 2.6 makes it impossible to override class parameters of included parametrized classes This bug is almost singlehandedly preventing us from using parameterized classes. We honestly can't move to 2.7 (and the changes in scope) without this being fixed. Reason being, we cannot include a global class on all nodes that has settings for all nodes and then override the class with updated parameters to the class for a specific set of nodes. Parameterized classes, in theory are such a good idea, but the implementation and attention after the fact seems to be severely lacking. It seems to get pushed back every minor revision for some reason, but it would be great if it got fixed. I think Dan, Jeff et al and I would +1 #5517. Regards 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] Re: How to setup database for Inventory Service
Alessandro Franceschi wrote: Thank you for the feedback. I've momentarily postponed the inventory setup but, for the chronicle, just inserting the query you posted didn't work out of the box. I'll get back on this when sorted out other things. Al Al You should also be able to do: [master] dbmigrate=true In your puppet.conf and Puppet will automatically add the tables. Regards James Turnbull -- 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] Could not request certificate: undefined method `closed?' for nil:NilClass
crosmuller wrote: Hi list, I am trying to get a puppet certificate on a new client but I get error: err: Could not request certificate: undefined method `closed?' for nil:NilClass I googled and found that it had something to do with reverse DNS lookup, the client is behind a NAT firewall so I assume a reverse lookup will fail. Can I bypass this somehow? Puppet version on master and client is 0.25.4 This is a Ruby networking issue with 0.25.4 that is fixed in 0.25.5 and later. I'd recommend upgrading. Regards James Turnbull -- 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] How do you implement revert changes'
Mohamed Lrhazi wrote: For each change to production systems, one has to submit a script detailing what changes will be made and how to revert them back.. I was wondering if any of you, who implemented something similar, would care to share how they did it. There is no such thing as rollback. :) I wrote roll in and roll out manifests and tested both. The roll in manifest made the required packages. The roll out manifest reversed those changes. Simply reverting puppet's own config to a previous repository version would not be enough in most cases, as it would not necessarily involve restoring overwritten files on the clients, if those files were not originally generated from puppet itself. Files can be backed up remote file buckets. I guess Puppet's buckets would be involved in the answer, but my understanding is that they are not documented yet, correct? is such a feature planned for upcoming releases? It is documented. http://docs.puppetlabs.com/references/2.6.7/type.html#filebucket The feature already exists. Regards 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] Certificate Issues.... again
Lance Reed wrote: Not sure if the book has been closed on this, but I had this problem recently on new installs. The problem was fixed by keeping the hosts in time sync. They were 5 hours out of sync. Not sure why this caused an issue unless there is some sort of SSL computation issue? Your mileage may vary SSL relies on the time on the different hosts being in sync otherwise it assumes certificates are invalid or bogus. It's a security feature of SSL. Regards James Turnbull -- 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.
