Re: [Puppet Users] puppet and git
On 10 September 2010 11:16, Matt Wallace wrote: > > > 1) I'm not sure how to get Hudson to merge the "staging" branch into > "master" > when the tests complete > > I've not used that bit of the Hudson Git plugin, but you can tell it to merge if your build passes: "You're done. Commits should now be automatically merged with the integration branch (they will fail if they do not merge cleanly), and built. If the build succeeds, the result of the merge will be pushed back to the remote git repository." (http://wiki.hudson-ci.org/display/HUDSON/Git+Plugin) > 2) I'm struggling to find a way for puppet 0.25 to perform a "git pull" on > all > the master branches _before_ it runs to ensure that the latest configs are > being distributed. > > Not sure you can, unless you run each client standalone. How about Hudson invoking something on the puppetmaster when the build passes? J. -- Julian Simpson The Build Doctor Ltd. http://www.build-doctor.com jul...@build-doctor.com (+44) 207 183 0323 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet dashboard and 64-bit mysql
Hi, On 8 September 2010 21:24, Tim wrote: > I was looking forward to trying this out, given the puported Solaris > support. However, in attempting to install the prereqs for dashboard, > I hit a major snag. My main server uses the blastwave MySQL install, > which is a 64-bit version of MySQL 5. > > mysql Ver 14.12 Distrib 5.0.90, for pc-solaris2.10 (x86_64) > > Apparently the mysql bindings for ruby don't like the 64-bit version. > You can pass an ARCHFLAGS environment variable on the command line to tell gem to compile against the correct architecture. I don't have a 64-bit Solaris machine to test, but you could have a look at the second comment from the bottom here: http://peppyheppy.com/2009/6/15/fail-sudo-gem-install-mysql-fixed J. -- Julian Simpson The Build Doctor Ltd. http://www.build-doctor.com jul...@build-doctor.com (+44) 207 183 0323 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 capistrano and repository
> > Running Puppet without a puppetmaster would be one reason. > > You could have a repository of your manifests that your machines check > out and run against. Cap is a poor mans way of orchestrating that > setup in lieu of something more powerful like MCollective. > > I could have asked that question in a more coherent way. I run Puppet without a puppetmaster myself. My process starts with a Rake build that invokes Puppet standalone, with all of the relevant configuration options supplied on the command line, with their paths resolved so I can check out my repo and then run 'rake puppet:run'. The original question suggested that they wanted something more complex, with a Continuous Integration-like approach to checking for changes. Personally I wouldn't do that as you should be able to run Puppet with impunity, whenever you feel like it. To me, testing for changes suggests that someone really isn't happy about the idea :) Best Julian. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 capistrano and repository
On 12 July 2010 14:33, bmort wrote: > > - start puppet with Capistrano > - puppet checks the 'repository' and determines changes have been > made > - applies any changes > > Can I ask why you want to do that? You want to push the Puppet manifests out to the node with Capistrano? It would be a simple capistrano task to run Puppet standalone. You can override configuration settings on the command line. But I 'm wondering why you'd want do to that. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: Splitting classes into separate files
> > Why is splitting classes and definitions into discrete files a problem? > > Personally, I think any convention is for the better, and it seems to gel with most languages to do things this way. You'll always get people who don't like the convention, however (often for valid reasons). Just google 'Maven' or 'Ruby on Rails' :) J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] running puppet withput puppetmasterd
>
> Actually, only this last thing (and that was what I wanted to do
> first) is what really requires to set the confdir explicitly, like
>
> cd /path/to/puppet/dir/manifests
>
> puppet --confdir /path/to/puppet/dir site.pp
>
> or without cd'ing in the manifests dir:
>
> puppet --confdir /path/to/puppet/dir /path/to/puppet/dir/site.pp
>
> running
>
> puppet /etc/puppet/manifests/site.pp
>
> runs just like this, I must have made something wrong elsewhere.
>
>
this is what works for me:
namespace :puppet do
puppetmaster= 'redacted.juliansimpson.org'
args = " --modulepath #{root}/etc/puppet/modules "
args += " --templatedir #{root}/etc/templates "
args += " --environment development "
task :test do
sh "cd etc/puppet && puppet #{args} --parseonly manifests/site.pp"
sh "cd etc/puppet && puppet #{args} --noop manifests/site.pp --debug"
end
desc "run the puppet stuff"
task :run do
sh "cd etc/puppet && puppet #{args} manifests/site.pp"
end
where #{root} is
root=File.dirname(__FILE__)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] running puppet withput puppetmasterd
When I run "puppet /etc/manifests/site.pp" I get onloy import errors. When I run puppetd it only complains that it cannot access any server. Try adding a --modulepath to the puppet command line. You may need to tweak your manifests: make sure that file urls are of the form puppet:///some/path. J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 Forge Readme standard?
> > > +1, structured data ftw. > Ditto. Takes Gabriel's intent of accurately describing modules and makes it machine-parsable. J. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 Forge Readme standard?
+1 to any well-formed data about modules. FWIW, there was a discussion last year about storing metadata in JSON or YAML format. J. On 31 May 2010 03:10, Daniel Pittman wrote: > "Gabriel - IP Guys" writes: > > > Just a idea to float out here among puppet forge users, > > > > Can we have a readme standard? For example, we could have a format like > the > > following > > FWIW, a *great* model to follow is probably the standard Unix manual page > format, which has had thirty years of working reasonably well for > documenting > this sort of thing. > > If you forgive my linking into a Perl tool, this is probably the most > user-friendly documentation about the structure of a good manual page for > software tools I know of: > > http://search.cpan.org/~jhi/perl-5.8.1/pod/pod2man.PL#NOTES > > Specifically, the 'NOTES' section includes the details on how to structure > the > manual page and what to include in each section. > > > Using a model like that means the puppet community can work from the base > of a > good, solid existing practice rather than inventing their own standards — > and, > of course, having to rediscover the same problems everyone else ran into. > :) > > Regards, > Daniel > > -- > ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 > 707 > ♽ made with 100 percent post-consumer electrons > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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-module-apache
> > > http://github.com/camptocamp/puppet-apache > > http://github.com/wesabe/puppet-apache2 > > http://github.com/puppet-modules/puppet-apache > > http://github.com/simpsonjulian/puppet-apache-ubuntu > > http://github.com/ohlol/puppet-apache > > I'd be delighted to see my apache module be made redundant. Every module I tried either: - had assumptions that I didn't like (e.g. one depended on augeas and I'm not a fan of machine-edited files), - had baked-in things like file locations from RedHat-style distros (cough *extlookup*) - only worked on Puppet 0.25 for no discernible reason If we agree on some features that we'd all like, then we could describe those in a cucumber spec. And then test it on the matrix of operating systems and Puppet versions - which Hudson ought to do nicely. J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Ubuntu /var/lib/puppet/lib failed.
> > Apr 26 11:12:36 ext-web1.fr.xxx.com puppetd[17974]: Starting Puppet > client version 0.24.5 > Apr 26 11:12:37 ext-web1.fr.xxx.com puppetd[17974]: > (/File[/var/lib/puppet/lib]) Failed to retrieve current state of > resource: No specified source was found from puppet://puppet/plugins > Apr 26 11:12:40 ext-web1.fr.xxx.com puppetd[17974]: Starting catalog run > Apr 26 11:12:40 ext-web1.fr.xxx.com puppetd[17974]: Finished catalog > run in 0.02 seconds > > Anyone know what it means? > > Looks like there was nothing to do. Plugins message is (IIRC) a red herring. Does it have a node entry? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 Conditional exec.
> The first poster said he would include os::centos in his module. What > happens if the module might be running on either CentOS or Ubuntu? I > don't think 'include os::centos' will work so great on an Ubuntu > system. How do you make it dynamic? > By using the $operatingsystem variable in the include. You can make an empty os::ubuntu class in a couple of lines if you have no resources to declare. -- The First Poster Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 Conditional exec.
> I wasn't able to get this to run for only CentOS. I tried a few
> different things in the site.pp. I wish I could put a case statement
> inside the exec, but puppet doesn't like that. So, below is what I had
> originally... how can I get the exec["yum-clean-all"] to only run for
> CentOS and not Ubuntu?
>
>
I make different classes. So the yum command would be in a class called
foo::centos. I might have an exec{ "aptitude update"} in a class called
foo::ubuntu, and a line in the class foo that went something like: include
foo::$operatingsystem. Might even be able to scratch up an example.
J.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] London Puppet Meet - Wednesday 31 March
Guys, I can't make it to the pub. Have a great time! Julian. On 30 March 2010 10:17, Paul Nasrat wrote: > On 30 March 2010 08:04, Gary Law wrote: > > Sorry guys, made my suggestion before I say this! Go for the Green Man... > > Not a problem. > > I owe you an email re solaris. > > Paul > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: London meetup during Training days
On 29 March 2010 15:18, scramble wrote: > The class will end around 5pm on Wednesday, so a meet-up around 6 or > 6:30 would be great. Open to suggestions from Paul or others... > > I double-booked this with my other half, so if I can make this it will be for a /very/ swift drink. Is anyone around on Thursday evening as well? I imagine some might have travel plans ... J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Behavior of Environments -- Bug?
I'd expect it to fail in such a way that the puppet run could not happen. Anything else could have worse consequences. J. On 22 March 2010 20:26, Paul Lathrop wrote: > Scott, > > I know it defaults to production if a environment is not specified. > However, that's not the case here. The client *is* specifying an > environment, the server doesn't know about that environment. I think > this is different than what you are describing - if the client does > not specify an environment, it is totally sane/correct to pass out the > "production" manifests. However, if the client specifies an > environment the server doesn't know about, isn't it at least worth > warning about? > > --Paul > > On Mon, Mar 22, 2010 at 11:50 AM, Scott Smith wrote: > > On 3/22/10 10:27 AM, Paul Lathrop wrote: > >> > >> IMHO this is a bug, but I can see how it might be by design. Any > >> comments? Should I file it? > >> > >> --Paul > >> > > > > Don't know if it's a bug but... Yeah it defaults to "production" - you > have > > to create an empty manifest for "production" in order to prevent Very > Scary > > Things from occuring if you happen to also have a "production" Puppet > env. > > > > -scott > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-us...@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-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Ukuug 2010
Patrick Debois, Kris Buytaert, and myself will be there. We're expecting a rumble with the LCFG guys. J. On 18 March 2010 07:04, Matthew Macdonald-Wallace wrote: > So who else is going to this next week? > > Anyone want to meet up? > > Matt. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Using Puppet for application deployment
> > > They're two distinct areas of 'deployment'. Puppet is more like, systems > > deployment, cap is app or content deployment in my eyes. > > Yes, I want to change that observation. > > I use Puppet for deploying my blog. It's a WordPress distro with a bunch of plugins, etc. It was too slow. I ended up inelegantly using rsync from puppet to push out the distro instead, which was insanely fast. Even that didn't come for free as I'm not using a Puppetmaster at the moment, and paths got annoying. (I do accept that's probably my issue, however). Anyway, my point is that Puppet needs to give you a way to deploy a tree of files, fast. If the new type mentioned above starts to give you that, so much the better: it gets tedious to push files to your version control system, ensure that your puppetmaster is up to date, and then invoke puppet on the node that you're deploying to. What's appealing about some developer-style deploy tools is that you can push exactly what you're working on to one or more nodes and test it. My experiences with Puppet suggest that it's not so convenient. My 6 years as a build and release manager tell me that it's generally a poor idea to use two application deployment tools. Hmmm. Julian J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Using Puppet for application deployment
> > > Can you share some examples of where your dividing line is and some of > the tasks that are hard to handle in Puppet today? > Here's how it worked: http://www.build-doctor.com/2009/12/09/dependency-hell/ Mainly, it was there to complement the lack of Rubygem dependencies, but it meant that there was a way for developers to maintain crontabs. We used Passenger and Rails so there wasn't much need to do anything else. I could have checked that there were processes running but the hosting peeps already had Monit. > > Ideally I'd like to figure out how to incorporate more of that into > puppet-core.Bruce has been working on a version control type, that > could be used to check sources > out of version control and eliminate some packaging needs for hosted > apps, though I'm curious as to what other niches might not be covered. > I've considered this for about ten seconds, but how about supporting some deployment tools in Puppet? So you could write a recipe that deploys middleware, application and other infrastructure for example. J. > --Michael > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Using Puppet for application deployment
> > >> Given that there are so many ways to skin the same cat, I'm wondering >> how others are doing their application deployments using Puppet. Or, >> if you are using Puppet but do your app deployments via some other >> mechanism, how do you do it, and why aren't you using Puppet to do it? >> >> Pete >> >> >> > I use capistrano for application deployment. I've managed to use both Puppet and Capistrano for deployment: Cap for the business code, and Puppet to ensure that dependencies are met. Puppet was called from Capistrano. J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] London meetup during Training days
The Green Man was our local until I left $DAYJOB last Friday. Should be fine on a Wednesday unless we have a huge group. On 3 March 2010 17:21, Paul Nasrat wrote: > On 3 March 2010 17:11, Dan Bode wrote: > > > > > > On Wed, Mar 3, 2010 at 2:37 AM, Al @ Lab42 wrote: > >> > >> Hei all, > >> In London, UK from March 29 to April 2 there are 2 Puppet training > >> classes: > >> > >> > http://reductivelabs.com/training/london-puppet-training/?x_lf_kt=2&_x_lf_kvid=7b51e3db-8ab0-4594-bcd8-3f84596a3748 > >> > >> I'm personally seriously evaluating the possibility to attend the > >> developer one, the 1st and 2nd, but in any case considering the active > >> Puppet London scene and this specific occasion, it would be nice to > >> organize a meetup in those days. > >> The idea has been raised on IRC and can be better discussed here... > >> Who is interested? > > > > I'm in. > > You're only invited if you come bearing goodies ;) > > > Wednesday is good for me. > > Fine, Wednesday it is. Guess that's the end of the one course and pre > developer course. I'll have to go scouting. ISTR us doing The Green > Man, Riding House St which is a Cider pub before. Else can find some > decent real ale pubs in the area that have space. > > Paul > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Magazine article comparing CPU usage of Puppet vs. Cfengine
> > I'm not really surprised by this, puppet is written in Ruby (an interpreted > language) vs CFengine which is written in C. I've used both, and I'd > gladly trade a little CPU performance for the stability gains offered by > puppet. CFengine is notoriously buggy in implementation, something I can > definitely attest to (like when spaces make a difference in > unions/intersections when the documentation plainly says they should > not...). > > I've used CfEngine 2, and would gladly trade CPU utilisation for the more expressive DSL. Swapping the order of operations round in the actionsequence declaration got boring, too. (not sure about version 3). J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] satellite sites management
> > Julian Simpson is working on making the backends pluggable so we should > have > something soon. > > Foreman already has integration on its side for extlookup (it's in trunk or > something) as soon as Julian and I finish making the backend pluggable it > will be able to integrate easily into foreman. > It should be very simple to add foreman support now. There's an ExtLookup class that has a backend. There's already the CSV backend that R.I. originally wrote, and it's pretty straightforward to see how you could pass it another backend. > > > As I recall however, extlookup.rb is not included in mainline puppet > > because Luke disagrees with the implementation I think. Could be > > wrong here. Best to ask him. I deploy it as part of my deploy:cold cap > task > > for new masters. > > Luke has said if we make it pluggable and make tests he'd be open to > including it in base so we're working on that. > It has tests. In fact it has reasonable test coverage. I'm just trying to pull logic out of the function that it originally shipped with and into the main ExtLookup class. I should probably reach out to the puppet-dev list so I can get some feedback. http://code.google.com/p/extlookup/ J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Making the new users experience easier
Late to the party here. I thought Gepetto looked useful for new puppet users. Similar to the Chef Repository on GitHub that new Chef users are encouraged to clone: http://wiki.opscode.com/display/chef/Chef+Repository I have a hunch that the Chef users are more likely to be Ruby developers and hence be used to git. Gepetto will let the new user create a well-structured repository without needing to be a git/github user. J. On 6 February 2010 01:16, Michael DeHaan wrote: > On Fri, Feb 5, 2010 at 2:38 PM, Patrick wrote: >> > > Great info everyone, thanks for all the feedback. Look for a lot of > improvements, especially in the documentation/example space soon. > > --Michael > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Combining our experience into a larger, common module repo
>> Can we start by grafting together everyone's modules and trying to >> namespace them? Has there been any discussion of bundling some common modules in the puppet distribution? It might help people get up to speed faster. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Combining our experience into a larger, common module repo
> I'd love to see this get off the ground. There have been a couple > of attempts at it - and you can see some background at: +1. I'd love to see better platform support for the modules that we have. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Inheritance versus inclusion
> I use the approach "inclusion over inheritance". Only inherit stuff if you > need to overwrite things. Eric Gamma (the guy who wrote the book on design patterns) said as much: http://www.artima.com/lejava/articles/designprinciples4.html J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 for app deployment
> Resurrecting this a bit... I have to check those tools (ControlTier, > Capistrano), but a more higher level question: does this mean those tools > sit on top of Puppet or other System Configuration Tool, doing changes to > Puppet manifiests, or simply that one assumes a System Configuration Tool to > keep the "system" (defined as ... dunno, everything but the applications? > Packages, services, disks, etc) managed and then uses a separate > language/model to deal with the particularities of web applications? I tried making the app responsible for declaring its immediate dependencies. Obviously you're going to need to have middleware etc. on the systems before you start app deployment. But if the app knows some of the gory detail, I think that's good. http://www.build-doctor.com/2009/12/09/dependency-hell/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Script for creating module directory stucture
> $ mkdir -p module/{manifests,files,templates}; touch
> module/manifests/site.pp
touch module/README module/metadata.json
git add module
git commit -m 'my great module"
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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 for app deployment
2010/1/11 SyRenity : > Hi. > >> >> Check out Capistrano or Vlad (I prefer Vlad). >> >> http://www.capify.org/index.php/Capistrano >> >> http://rubyhitsquad.com/Vlad_the_Deployer.html > > > Thanks. These 2 seems to be mostly Ruby/ROR oriented - any of them > working with Java/C++ apps, or my best bet still the ControlTier? I haven't used Vlad but Capistrano can be used for Java app deployment. Out of the box Capistrano is configured for deploying Rails apps but you can configure it for other kinds of app. http://code.google.com/p/bungeni-dspace/wiki/InstallingDspaceUsingCapistrano http://github.com/leehambley/railsless-deploy/ > > Regards. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 I use a desktop client as puppet master?
2010/1/11 Mr Gabriel : > Fully Qualified Domain Name seems to be a requirement for puppet master > server. I was expecting to run into issues say around 2/3 of the way > through, not at step one! > > So I guess my question is, is it possible to use a desktop system, with no > FQDN as the puppet master server? How many nodes are you planning to use? You can run puppet standalone if you want a gentle way to start. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: continues puppet run in production
> I'm not mad, I take pride in my laziness, I'm more efficient that way. On Laziness: Wall along with Randal L. Schwartz and Tom Christiansen writing in the second edition of Programming Perl, outlined the Three Virtues of a Programmer: Laziness - The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer. Also hence, this book. See also impatience and hubris. Impatience - The anger you feel when the computer is being lazy. This makes you write programs that don't just react to your needs, but actually anticipate them. Or at least pretend to. Hence, the second great virtue of a programmer. See also laziness and hubris. Hubris - Excessive pride, the sort of thing Zeus zaps you for. Also the quality that makes you write (and maintain) programs that other people won't want to say bad things about. Hence, the third great virtue of a programmer. See also laziness and impatience. (http://en.wikipedia.org/wiki/Larry_Wall) I see no reason why this shouldn't apply to systems administrators. Happy new year, everyone. J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: continues puppet run in production
> Is this the case or am I missing out on the big picture? Since when > does “being productive” come before production integrity? I've seen "production integrity" used as an excuse for not delivering new services, costing the business $$$. There has to be a balance... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: Class not compiled - help!
d to load library 'ldap' for feature 'ldap' >> debug: Failed to load library 'shadow' for feature 'libshadow' >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/ >> puppet/puppet.conf]: Autorequiring File[/etc/puppet] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/ >> puppet/ssl]: Autorequiring File[/var/lib/puppet] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/ >> certs] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ >> lib/puppet/classes.txt]: Autorequiring File[/var/lib/puppet] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/ >> puppet/state]: Autorequiring File[/var/lib/puppet] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/certs/xldn1784dis.ldn.swissbank.com.pem]: Autorequiring File >> [/var/lib/puppet/ssl/certs] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/ >> puppet/lib]: Autorequiring File[/var/lib/puppet] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/private_keys/xldn1784dis.ldn.swissbank.com.pem]: >> Autorequiring File[/var/lib/puppet/ssl/private_keys] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/public_keys/xldn1784dis.ldn.swissbank.com.pem]: >> Autorequiring File[/var/lib/puppet/ssl/public_keys] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ >> lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/ >> state] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ >> puppet/ssl/csr_xldn1784dis.ldn.swissbank.com.pem]: Autorequiring File[/ >> var/lib/puppet/ssl] >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ >> lib/puppet/state/state.yaml]: Changing mode >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ >> lib/puppet/state/state.yaml]: 1 change(s) >> debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ >> lib/puppet/state/state.yaml]/mode: mode changed '640' to '660' >> debug: Finishing transaction 23456253627420 with 1 changes >> debug: Loaded state in 0.00 seconds >> debug: Retrieved facts in 0.40 seconds >> debug: Retrieving catalog >> debug: Calling puppetmaster.getconfig >> debug: Retrieved catalog in 0.18 seconds >> info: No classes to store >> debug: Creating default schedules >> debug: Finishing transaction 23503399832680 with 0 changes >> info: Caching catalog at /var/lib/puppet/localconfig.yaml >> notice: Starting catalog run >> debug: Loaded state in 0.00 seconds >> debug: //File[/etc/motd]: Changing group >> debug: //File[/etc/motd]: 1 change(s) >> notice: //File[/etc/motd]/group: group changed 'root' to 'puppet' >> debug: Finishing transaction 23503399553140 with 1 changes >> debug: Storing state >> debug: Stored state in 0.01 seconds >> notice: Finished catalog run in 0.46 seconds >> >> Any help greatly appreciated, thanks >> >> Ben > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Modules metadata standards
2009/12/18 Al @ Lab42 : [snip] > Now, as a user, I think that it is important to know how to start to > write metadata files: format and minimal required parameters. > A final (?) decision is not to be rushed, but an indication of the > format and on some basic parameters that won't be changed for sure is > definitively welcomed. > If from this thread comes out an "officially Puppet complant" example > of a metadata file I'm an happy guy. > +1. Happy to agree the above. I'd rather specify less and get some broad agreement on what makes the minimal and official/community compliant metadata, than try and pin down every detail. I'd assumed that the metadata would be in Ruby code, but equally happy with JSON or YAML. Julian. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Proposals for modules naming conventions
Was there discussion on metadata for modules? I know Luke was experimenting with that. I'd love to see what OS(es) a module has been tested on, and what versions of Puppet. J. PS: WRT to RI Peinaar's mail: any votes on extlookup backends? Once I have extracted the CSV code it should be simple to add more. I'm thinking yaml or json, or something like that. 2009/12/17 Scott Smith : > Al @ Lab42 wrote: >> 1- a class for an application, sharing the same name. (IE: apache >> (not httpd) for managing Apache) >> Still I wonder why I (and many) use ssh instead of openssh :-) >> > > Hmm, I think most of the conventions are sensible, thanks for taking the time > to summarize it all! > > On point #1 however, I kind of disagree: Technically Apache (Software > Foundation) is the > organization, and the web server is Apache HTTP Server. I do agree that > `httpd' is way too generic. > In this case I prefer to use `apache::httpd' and `apache::tomcat' etc. > > Just my opinion :) > > -scott > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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: no name for client-ip
;> File[/var/lib/puppet/ssl/ca/private] >> debug: /File[/var/lib/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/ >> var/lib/puppet/ssl/ca] >> debug: /File[/var/lib/puppet/ssl/ca/inventory.txt]: Autorequiring File >> [/var/lib/puppet/ssl/ca] >> debug: Finishing transaction -611407368 with 0 changes >> debug: Using cached certificate for ca >> debug: Using cached certificate for ca >> debug: Using cached certificate for tbagchi-desktop >> notice: Starting Puppet server version 0.25.0 >> info: mount[files]: allowing 192.168.1.20 access >> info: mount[files]: allowing 192.168.1.57 access >> debug: No modules mount given; autocreating with default permissions >> debug: Creating interpreter >> debug: Finishing transaction -612840578 with 0 changes >> debug: Finishing transaction -612842468 with 0 changes >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> info: access[^/catalog/([^/]+)$]: allowing 'method' find >> info: access[^/catalog/([^/]+)$]: allowing $1 access >> info: access[/certificate_revocation_list/ca]: allowing 'method' find >> info: access[/certificate_revocation_list/ca]: allowing * access >> info: access[/report]: allowing 'method' save >> info: access[/report]: allowing * access >> info: access[/file]: allowing * access >> info: access[/certificate/ca]: adding authentication no >> info: access[/certificate/ca]: allowing 'method' find >> info: access[/certificate/ca]: allowing * access >> info: access[/certificate/]: adding authentication no >> info: access[/certificate/]: allowing 'method' find >> info: access[/certificate/]: allowing * access >> info: access[/certificate_request]: adding authentication no >> info: access[/certificate_request]: allowing 'method' find >> info: access[/certificate_request]: allowing 'method' save >> info: access[/certificate_request]: allowing * access >> info: access[/]: adding authentication any >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> err: Could not resolve 192.168.1.57: no name for 192.168.1.57 >> >> My server(192.168.1.20) config file is : >> >> [files] >> path /etc/puppet/files >> allow 192.168.1.20 >> allow 192.168.1.57 >> >> [plugins] >> path /var/lib >> >> Client(192.168.1.57) config file is: >> >> [main] >> server = 192.168.1.20 >> logdir=/var/log/puppet >> vardir=/var/lib/puppet >> ssldir=/var/lib/puppet/ssl >> rundir=/var/run/puppet >> factpath=$vardir/lib/facter >> pluginsync=true >> >> [puppetmasterd] >> templatedir=/var/lib/puppet/templates > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Best practice for modules used for multiple environments
2009/12/10 M.F.Haris : > Yeah I have a similar issue as I have to configure SNMP on different clients > and the structure of SNMP (configurations files and service management) is > different and vary from client to client as some clients are running on > Fedora, some on SuSe and some on IBM AIX. I've been trying to get some modules written for CentOS/RedHat working on my Ubuntu systems, and wondering the best way to do this myself. A good example is the differences between Apache on the two kinds of system: Apache runs as 'www' on the RH systems, and 'www-data' on the Debian-ish systems. The default docroot is different as well - '/var/www/html' on RH and '/var/www' on Debian/Ubuntu. The best solution I can think of at the module level is custom facts - ideally derived from a source of truth like the apache packages themselves. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] In my system source of plugin folder has destroyed...where to find this plugin folder.
Do you have the error message? 2009/12/10 sanjibdhar...@gmail.com : > Please help. > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] I am new bee in puppet please help me to configure a node to install something from central puppet master.
Suggest you start writing a *local* puppet manifest first and start running it (on your local machine) with puppet '/path/to/file'. Try reading up on the 'package' type in puppet (assuming that your software is packaged). Once you have that running you can look at running the same thing remotely. I hope that will make the learning curve flatter for you. J. 2009/12/10 sanjibdhar...@gmail.com : > I want to install some software by puppet into remote system how to do > this. > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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. > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 to add Ubuntu PPA repository (with signing key)?
> I meant implementing a new type like aptrepo there. Actually the best > design decision would be: rename yumrepo as packagerepo, split some of > the code as a provider yumrepo, add new code for a provider aptrepo. But > that isn't easy as pie and it requires ruby knowledge, apt and puppet > internals. This is the elegant, but complex solution. Now I'm balabbering. You're not blabbering. A new type in Puppet seems like the right idea to me. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Module Execution Order
> Lets dumb it down. How can I ENSURE that EVERYTHING from module A is > implemented before ANYTHING from module B? That's roughly like asking: How can I ensure that no code from jar file A depends on jar file B? It's really up to the individual classes inside the jar files to behave the way you want. I'd like to make a proposal around module metadata, so that you could declare things like: - this module depends on others - this module works for this list of $operatingsystems - this module uses this sysadmin strategy J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] Templates and loops..
2009/11/23 Christopher Johnston : > Its definitely there.. I even put a <%= processorcount %> to make sure the > variable is set. > <% processorcount.to_i-1 %> > <% for cpu in (0..processorcount) %> > Facter version is 1.52 > # facter | grep proc > processor0 => Intel(R) Xeon(R) CPU X5570 @ 2.93GHz > processor1 => Intel(R) Xeon(R) CPU X5570 @ 2.93GHz > processor2 => Intel(R) Xeon(R) CPU X5570 @ 2.93GHz > processor3 => Intel(R) Xeon(R) CPU X5570 @ 2.93GHz > processorcount => 4 And the <%= processorcount %> snippet resolved to 4 in your template? I'm stumped then. I thought you could do iteration with any ERB template, not just in Rails. J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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=.
Re: [Puppet Users] Templates and loops..
2009/11/19 Christopher Johnston : > How come this doesnt work? I write this in a normal ruby script it > works just fine. > > <% for cpu in (0..processorcount) %> > > I want to loop through the number of processor so a specific action > can be taken to generate content for a file. I get an error on the > master of: > > bad value for range at /etc/puppet" Processorcount isn't resolved. What machine are you running it on? What version of facter do you have? >> processorcount=nil => nil >> for cpu in (0..processorcount) >> puts cpu >> end ArgumentError: bad value for range from (irb):2 >> Cheers J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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=.
Re: [Puppet Users] Puppet explained, in badly-drawn cartoons
> It was slightly inspired by Luke's talk at GLLUG a couple of years > ago, but I don't have his Keynote skills, so I just drew everything > with pen and paper and scanned it in :) John's slide's were damn well done. Mine are more corporate. I spoke after him: http://www.build-doctor.com/2009/11/14/agile-systems-admi/ Julian. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=.
Re: [Puppet Users] Re: Problem with storedconfigs on Ubuntu Jaunty (9.04)
> Well, I didn’t. There is no menton of any more reconfiguring sqlite3 > beyond those threee statements in the puppet.conf, which I wrote > about. I took those statements from Puppet Wiki: > > storeconfigs = true > dbadapter = sqlite3 > dblocation = /var/lib/puppet/storeconfigs.sqlite > > I will add that no database was ever created in /var/lib/puppet/. > Did you try creating the sqlite database by hand? J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=.
[Puppet Users] Re: Marco...
It works for me. J. 2009/11/17 Douglas Garstang : > > Polo? > > Am I the only one having problems with this mailing list? Repeated > attempts to post often result in messages going to the bit bucket. Who > knows if this message will make it. > > Doug. > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Behavior Driven Infrastructure
My understanding is that Test Driven Development hit the mainstream (did smalltalk have a unit test framework?) with JUnit.[1] Junit allowed developers to automate their unit tests. All the unit tests for your project should run in seconds, if your codebase and tests are loosely coupled. e.g. testThatTheFooObjectReturnsABarWhenPassedABaz Those TDD style tests can be pretty ugly. In theory you can use them as a spec to describe what code does, but in practice, no. So a guy called Dan North coined the term Behaviour Driven Development, and focussed on the language used to help Business Analysts or other guys in suits to specify. This is where the Given/When/Then syntax comes from. He worked on JBehave as an alternative to JUnit so you can specify behavior. But Rspec and Cucumber are where the notion has taken off. I'd write more but I have to make my kids' dinner :) J. [1] http://www.junit.org/ 2009/11/9 Christian Kauhaus : > > Isaac Christoffersen schrieb: >> to validate the server configuration. The combination of TDD and BDD >> with server rollouts is very attractive. > > I think the whole topic is really hot. :-) > > It would probably a good idea to expand what the difference between TDD > and BDD in systems management actually is about. > > Not everyone here on the list is fine with the subtle differences in > terminology (for example, me ;-) ) > > Regards > > Christian > > -- > Dipl.-Inf. Christian Kauhaus <>< · k...@gocept.com · systems administration > gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany > http://gocept.com · tel +49 345 1229889 11 · fax +49 345 1229889 1 > Zope and Plone consulting and development > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Behavior Driven Infrastructure
orrectly configured >>>> and behaves the way you want? >>>> >>> >>>> [1]<http://blogs.sun.com/martin/entry/behavior_driven_infrastructure> >>>> >>> [although i've commented on the excellent blog entry, i'm posting here] >>> >>> Hi Martin, >>> It looks like there's a bit of crossover here with a project i've been >>> working on the last few months called cucumber-nagios[0]. It takes the >>> result of a Cucumber run and outputs it in the Nagios plugin format. >>> Essentially you use it to express your intentions in plain language, >>> and verify your intentions periodically through your monitoring >>> system. Just like what you've posted about. :-) >>> >>> Anyhow, I spoke about cucumber-nagios at the excellent Devopsdays in >>> Belgium last weekend, and I got talking with people about expanding >>> the library of steps to cover things like logins over SSH, file >>> manipulation, and mail delivery. It would be cool if we could >>> centralise our efforts and focus on building an awesome library of >>> reusable steps to test our infrastructure. >>> >>> Your point about doing behaviour driven development when writing >>> software is right on the mark. From an infrastructure perspective, I >>> like to think of Cucumber as the testing tool, and Puppet as the >>> programming language. >>> >>> Anyhow, i'd be interested to hear what other people think about this idea! >>> >>> Cheers, >>> Lindsay >>> >>> [0]http://auxesis.github.com/cucumber-nagios >>> >>> --http://holmwood.id.au/~lindsay/(me) >>> >> > >> > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Require Class?
Darn iPhone. Requiring a class will make puppet consider an entire
class of resources a dependency. So in the example you quoted, the
squid class would be executed before the apache service.
It allows abstraction over requiring individual resources, that's all.
Sent from my iPhone
On 25 Oct 2009, at 06:59, Douglas Garstang
wrote:
>
> Can someone tell me what a require => Class actually does? The
> documentation on this really isn't clear.
>
> The language tutorial at
> http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial says:
>
> "Like resources, you can also create relationships with classes like
> so:
>
> class apache {
> service { "apache": require => Class["squid"] }
> }
> The above uses the require metaparameter to make the apache class
> dependent on the squid class."
>
> What does that mean? Does that mean that the squid class has to be
> just available, or FULLY implemented and completed before the apache
> class???
>
> Three days and I am still dicking around with dependancy hell.
>
> Doug.
>
> >
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Require Class?
Require => Class will me
Sent from my iPhone
On 25 Oct 2009, at 06:59, Douglas Garstang
wrote:
>
> Can someone tell me what a require => Class actually does? The
> documentation on this really isn't clear.
>
> The language tutorial at
> http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial says:
>
> "Like resources, you can also create relationships with classes like
> so:
>
> class apache {
> service { "apache": require => Class["squid"] }
> }
> The above uses the require metaparameter to make the apache class
> dependent on the squid class."
>
> What does that mean? Does that mean that the squid class has to be
> just available, or FULLY implemented and completed before the apache
> class???
>
> Three days and I am still dicking around with dependancy hell.
>
> Doug.
>
> >
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Explicit Repo, Package ordering
> node tst_basenode {
>
> include yum
>
> Package {
> require => [
> Yumrepo["CentOS-Base"],
> Yumrepo["EPEL-Core"],
> ...
> ]
> }
> }
>
> node tst_childnode inherits tst_basenode {
> include ldap_client
> }
>
[snip]
> Quite simply, how do I GUARANTEE that my repos are done FIRST followed
> by any mandatory packages like yum and yum-priorities?
>
Disclaimer: I don't really do RPM based distros, and all this is
untested, and I should be fixing dinner.
If I were you I'd be writing something like this:
class base {
package {
"yum": ensure => present;
"yum-priorities": ensure => present;
}
yumrepo {
"foo": require => Package["yum-whatever-it-depends-on"];
"bar: require => Package["you-get-the-idea"};
}
}
node default {
include base
}
Note that resources are declared in lower case and references to them
are declared with the leading character upcased (so you declare a
package but refer to a Package["foo}"]. So declare what you need and
then map the relationships.
HTH,
Julian.
--~--~-~--~~~---~--~~
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: Object Dependancies
Hi Douglas, You do need to be explicit with dependencies between resources; it's a declarative system. You tell puppet what each resource needs, and it does all the work. I've found that it's easy to kid yourself that you've gotten your manifest right, but things only work because dependencies are there from a previous run. I prefer this to the approach of cfengine, where you had to declare a fixed order for types in an action sequence (files, then exec). Best Julian. 2009/10/24 Douglas Garstang : > > All, > > I've been putting a lot of puppet pieces together over the last few > days, and I've realised, I think, that you _REALLY_ need to be > explicit with your object dependancies. It looks like puppet just > drags all modules, all nodes, and everything else into one giant > namespace and executes them in NO PARTICULAR ORDER on the target. > > I see examples on the puppet recipies page that probably won't work > most of the time since puppet executes things in an apparently random > order. For example, the LDAP example at > http://reductivelabs.com/trac/puppet/wiki/Recipes/LDAPClientNSSwitch > makes no mention of the fact that the ldap.conf file needs to be > updated BEFORE the service is started by putting a before=> on the > file, or a require=> on the package. > > Or... am I just missing something here? > > Doug > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Stuck with puppet
Hi,
What happens when you run 'puppetd --test' on the client?
Best
Julian.
2009/10/20 Renato Tuveri :
>
> Hello a newbie here.
>
> The situation is that:
>
> 2 machine one master one client
> Puppet 0.24.5
>
> This my configuration:
>
> Client:
>
> /etc/puppet/puppetd.conf
>
> [puppetd]
> server = Asus-Vista-Box
> logdir = /var/log/puppet
> vardir = /var/lib/puppet
> rundir = /var/run
>
>
> master
>
> /etc/puppet/manifests/classes/sudo.pp
>
> class sudo {
> file { "/etc/sudoers":
> owner => "root",
> group => "root",
> mode => 440,
> }
> }
>
>
>
> /etc/puppet/manifests/site.pp
>
> import "classes/*"
>
> node default {
> include sudo
> }
>
>
> I make
>
> puppetca --list
> debian.lokku.net
>
> and
>
> puppetca --sign debian.lokku.net
> Signed debian.lokku.net
>
> But even I restart both client and master 100 times if I do:
>
> ls -l /etc/sudoers
> -rwxrwxrwx 1 root root 5 2009-10-20 17:52 /etc/sudoers
>
> What I did wrong?
>
> >
>
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Passenger Woes
Is there a file called rewindable_input.rb on the system? Looks like a missing gem or ruby path issue. J. Sent from my iPhone On 19 Oct 2009, at 18:52, Stephen Nelson-Smith wrote: > > Hello, > > I really didn't expect this to be difficult, but I've been struggling > with this all day :( > > I'm running CentOS 5.3, with rubygems, rack and fastthread, from EPEL. > > I'm running puppet-0.25.0-1 built from the spec file in the latest > stable tarball. > > I'm using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen (kanarip), > which is effectively EPEL too. > > I'm using the config.ru file from > http://github.com/reductivelabs/puppet/blob/master/ext/rack/files/config.ru > , > chowned to puppet and chmoded 644. > > I've added: > > [puppetmasterd] >ssl_client_header = SSL_CLIENT_S_DN >ssl_client_verify_header = SSL_CLIENT_VERIFY > > to my puppet.conf as directed in the README. > > I've set up an apache vhost as follows: > > PassengerHighPerformance on > PassengerMaxPoolSize 12 > PassengerPoolIdleTime 1500 > # PassengerMaxRequests 1000 > PassengerStatThrottleRate 120 > RackAutoDetect Off > RailsAutoDetect Off > > Listen 8140 > > LoadModule ssl_module modules/mod_ssl.so > > AddType application/x-x509-ca-cert .crt > AddType application/x-pkcs7-crl.crl > SSLPassPhraseDialog builtin > SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000) > SSLSessionCacheTimeout 300 > SSLMutex default > SSLRandomSeed startup file:/dev/urandom 256 > SSLRandomSeed connect builtin > SSLCryptoDevice builtin > > >SSLEngine on >SSLProtocol -ALL +SSLv3 +TLSv1 >SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP > >SSLCertificateFile /var/lib/puppet/ssl/certs/puppet.pem >SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/ > puppet.pem >SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem >SSLCACertificateFile/var/lib/puppet/ssl/ca/ca_crt.pem > ># If Apache complains about invalid signatures on the CRL, you > can try disabling ># CRL checking by commenting the next line, but this is not > recommended. >SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem > >SSLVerifyClient optional >SSLVerifyDepth 1 >SSLOptions +StdEnvVars > >DocumentRoot /etc/puppet/rack/public/ >RackBaseURI / > >Options None >AllowOverride None >Order allow,deny >allow from all > > > > When I start apache, and browse to the puppet server on 8140 I get a > 500 and see the following in the logs: > > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require': no such file to load -- rack/rewindable_input > (LoadError) >from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: > 31:in > `require' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/rack/request_handler.rb:27 >from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: > 31:in > `gem_original_require' >from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: > 31:in > `require' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/rack/application_spawner.rb:34 >from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: > 31:in > `gem_original_require' >from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: > 31:in > `require' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/spawn_manager.rb:157:in > `spawn_application' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/spawn_manager.rb:287:in > `handle_spawn_application' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/abstract_server.rb:352:in > `__send__' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/abstract_server.rb:352:in > `main_loop' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/ > phusion_passenger/abstract_server.rb:196:in > `start_synchronously' >from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/bin/ > passenger-spawn-server:61 > [ pid=5357 file=ext/apache2/Hooks.cpp:725 time=2009-10-19 > 23:09:10.957 ]: > Unexpected error in mod_passenger: Cannot spawn application > '/etc/puppet/rack': The spawn server has exited unexpectedly. > Backtrace: > in 'virtual boost::shared_ptr > Passenger::ApplicationPoolServer::Client::get(const > Passenger::PoolOptions&)' (ApplicationPoolServer.h:471) > in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:521) > > I'm baffled - I can't see what's wrong. Please help! :) > > TIA, > > S. > -- > Stephen Nelson-Smith > Technical Director > Atalanta Systems Ltd > www.atalanta-systems.com > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppe
[Puppet Users] Re: Best Practices Rewrite - First Draft
No objections here. I seem to recall that there had a been a discussion at PuppetCamp about perhaps moving to a pattens collection instead of set of best practices - not sure if anyone has bandwidth to to work on this but it might help to keep it in mind. Dan North wrote an article on this.[1] http://www.infoq.com/articles/better-best-practices Ironically I have loads of best practices articles on my blog. D'oh. J. 2009/10/18 Stephen Nelson-Smith : > > Hi, > >> If anyone feels up to grabbing this document and running with it, >> please feel free. > > Not sure if I accidentally half replied to this already > > I'd be very happy to pick this up. I'm just starting a new project - > bring some best practices to a somewhat chaotic and messy large > government Drupal infrastructure (and associated services) and am also > doing some puppet training, so gathering together collected wisdom, > adding my own experiences from 3 years of running puppet, and > maintaining the document seems like an ideal fit. > > Is everyone ok with this? > > S. > -- > Stephen Nelson-Smith > Technical Director > Atalanta Systems Ltd > www.atalanta-systems.com > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppetmaster config
Hi, [puppetd] is for the puppet process that runs on every puppet node. [puppetmasterd] is for the puppet master process. What is the issue with getting the client and server talking? What happens? J. 2009/10/14 Douglas Garstang : > > I'm getting really really frustrated with puppet. > > Why is it that when I install the puppet-server RPM, my default config > file in /etc/puppet/puppet.conf has a [puppetd] section and not a > [puppetmasterd] section? Isn't that what the puppetmaster looks for? > The output from --genconfig generates a config file with a > [puppetmasterd] section. I've been trying to get the client and server > to talk to each other for over 24 hours now and inconsistency's like > this are making it REALLY hard to get a good starting baseline. > > Doug. > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Best Practices Rewrite - First Draft
I swear people who use Puppet are more fertile. Congratulations, Paul! Julian. 2009/10/12 Nicolas Szalay : > Le dimanche 11 octobre 2009 à 12:58 -0700, Paul Lathrop a écrit : >> Hey everyone, >> >> Well, I really was meaning to get this cleaned up and put on the wiki, >> but the world seems to conspire against it. First couple of times I >> sat down to do it, I got Nagios pages. The last time was the real >> winner, though. Tuesday night I sat down to get feedback integrated >> and post this to the wiki when my partner called to me from the back >> room. >> >> To make a long story short: on Wednesday morning my son, who was >> originally due Dec. 31st, decided to make an early appearance. He's in >> the NICU, and doing great, but my attention is probably going to be >> elsewhere for awhile. > > Congrats ! > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Service started with "onestart" instead of "start"
I think older versions of puppet detect two providers for Service
types; puppet and BSD. It always picks BSD first ('onestart' is a BSD
command). You can override the provider by adding 'provider => debian
' to the declaration of the service.
You can also override this globally, IIRC.
J.
2009/10/5 Lisa :
>
> Hello all,
>
> I'm using Puppet to ensure a service is running. After stopping the
> service and running "puppetd -v -o --test", I sometimes (not always)
> get an error output like this one:
>
> "Could not start Service[myService]: Execution of '/etc/init.d/
> myService onestart"
>
> I wonder why it calls "onestart" instead of "start".
>
> Then I run "puppetd -v -o --debug" and get the following outputs:
> - when it runs ok:
>
> Service[myService](provider=debian): Executing 'ps -ef'
> Puppet::Type::Service::ProviderDebian: Executing '/usr/sbin/update-
> rc.d -n -f myService remove
> Service[myService](provider=debian): Executing '/etc/init.d/myService
> start'
> Puppet::Type::Service::ProviderDebian: Executing '/usr/sbin/update-
> rc.d -n -f myService remove
>
> - when it runs with error:
>
> Service[myService](provider=freebsd): Executing 'ps -ef
> Service[myService](provider=freebsd): Executing '/etc/init.d/myService
> onestart'
>
> Do you think the change of provider can explain the error ? Why can
> the provider change ? (I run the command in the same server).
>
> Thank you.
> Best wishes.
>
>
> >
>
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Windows support roadmap
I think the smart money would be on Iron Ruby, as there's a wealth of C# code for systems admin. There's a ton of info on how to programatically configure IIS6,7,8 via C#/VB. The prevalent automation language seems to be VB in the Windows world. The other option is PowerShell. Not sure about bindings for that, but I'll ask a windows guy I know if you like. J. On 3 Oct 2009, at 13:55, Paul Nasrat wrote: > > It was good to see some interest in the windows support, I'm trying to > co-ordinate us getting to a coherent release of providers and ensuring > the core is platform independent. Something at a high level like: > > Feature - JBoss install > Given a standard Windows 2003 server install > When puppetd client runs against a master with a jboss manifest > Then a JBoss user should exist, > And JDK should be installed > And JBoss should be installed > And JBoss should be running as a service > > Interesting thought was running puppet on IronRuby, > > Paul > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet Camp Schedule Posted
Doesn't have to be high quality video - a Flip cam recording would do it. I'll even lend Paul Nasrat mine ... J. 2009/9/22 Peter Burkholder : > >> >> Peter Meier a écrit : >> >>> (I'm working angles to see if we can get presentations >> >>> streamed/recorded. >> >>> >> >> +1 for this idea :-) >> >> >> > >> > I'd like to second that. Would be nice! >> > >> > cheers pete >> > >> > >> o yes , would love that too. Will even pay a few $$ to view it >> if if >> this help to fund the cost of the recording. > > Ditto that. >> >> >> regards, >> Ghislain. >> > > -- > Peter Burkholder > AARP | Web Strategy & Operations | 601 E Street, NW | Washington, DC > 20049 > pburkhol...@aarp.org | aim: peterbtech | ph: 202-434-3530 | cell: > 202-344-7129 | > > > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Best Practices Rewrite - First Draft
I would have assumed that you'd always want to qualify the module
names as the best practise. Collisions in namespaces wreak havoc in
many other domains. I'm thinking of Java class names being bound to
domain names as an approach that works elsewhere.
Am I being naive?
Best
Julian
2009/9/17 Peter Meier :
>
> Hi
>
>> I think that would be terrible. Having two different paths for the
>> same namespace is confusing and will easily lead to problems.
>
> yeah I feel more this way as well.
>
>> However, the example you give is correct: you can't have the same
>> module name in two modulepaths and usually want to prefix the
>> classnames to avoid name collisions.
>
> so for the Best Practises:
>
> If we do multiple sources for a file (and I do that a lot, as it makes
> puppet so flexible) what would you prefer?
>
> in module foobar and the 0.25 way:
>
> file{'/tmp/a':
> source => [ "puppet:///files/foobar/${fqdn}/a",
> "puppet:///files/foobar/a",
> "puppet:///modules/foobar/${operatingsystem}/a",
> "puppet:///modules/foobar/a" ],
> }
>
> or
>
> file{'/tmp/a':
> source => [ "puppet:///modules/site-foobar/${fqdn}/a",
> "puppet:///modules/site-foobar/a",
> "puppet:///modules/foobar/${operatingsystem}/a",
> "puppet:///modules/foobar/a" ],
> }
>
> ???
>
> cheers pete
>
> >
>
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: duplicate package definitions
I think John's probably right. My manifests are all written for
Ubuntu - which has a different set of package names for mysql:
mysql-server, mysql-client, etc.
Best
J.
2009/9/4 jcbollinger :
>
>
> On Sep 4, 1:46 am, Julian Simpson wrote:
>> You need to tell Puppet to manage both a gem and an RPM. Adding
>> 'provider => gem' to the appropriate package declaration will do that.
>
>> 2009/9/4 Matt Delves :
>> > The problem is that I currently have the mysql package installed as an
>> > rpm via puppet, though I'm also wanting to use puppet to manage the
>> > mysql ruby gem. Unfortunately when I do this, puppet complains with the
>> > following error:
>> > ArgumentError: Duplicate definition: Package[mysql] is already defined
>>
>> > Is there a way to get around this?
>
> Do try Julian's suggestion first, but I suspect that it will not be
> sufficient. The root problem appears to be that you are using the
> same name for the RPM package resource and the gem package resource.
> I don't think Puppet will allow two resources of the same name and
> type, even if they have different providers. If you do need package
> name uniqueness then you *might* be able to arrange it like so:
>
> # Puppet should refer to this Package resource as "mysql-gem", whereas
> gem should consider the gem name to be "mysql". Maybe.
> package { "mysql-gem":
> name => "mysql"
> # Must specify the provider when it is not the system default:
> provider => "gem"
> [...]
> }
>
> If that doesn't work either then you might need custom code to get
> around the problem.
>
> Good luck.
>
>
> John
> >
>
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: duplicate package definitions
You need to tell Puppet to manage both a gem and an RPM. Adding 'provider => gem' to the appropriate package declaration will do that. Best J. 2009/9/4 Matt Delves : > > Hey Folks, > Let me first setup the scenario. I have a server (managed via puppet) > that runs a mysql database. > > The problem is that I currently have the mysql package installed as an > rpm via puppet, though I'm also wanting to use puppet to manage the > mysql ruby gem. Unfortunately when I do this, puppet complains with the > following error: > ArgumentError: Duplicate definition: Package[mysql] is already defined > > Is there a way to get around this? > > Thanks, > Matt Delves > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Example of a site module?
Hi there, I setup my Puppet manifests before modules really took off. Recently I read the best practice info (nice work!) and saw that a convention has emerged with the 'site' module. Great. I'm delighted to keep all my secrets in there and open up any other modules I might write. But before I do that, can anybody share an example site module? Does it end up just being a site.pp with any relevant facts and private info? Do people keep anything else in there of note? Any pointers welcome. Thanks, Julian. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: passenger for Hardy
I've happily used the Brightbox Hardy packages on two different systems. Quite happy with them, though it's my first time using Passenger, so I can't really judge. At least some of the sources are on GitHub, too: http://github.com/johnl/deb-passenger/tree/master Julian. 2009/7/22 Nigel Kersten : > > On Wed, Jul 22, 2009 at 1:31 PM, Mark Foster wrote: >> >> >> >> On Jul 22, 9:11 am, Nigel Kersten wrote: >>> On Wed, Jul 22, 2009 at 9:05 AM, Mark Foster wrote: >>> > Just wanted to put the word out, if you are interested in running Puppet >>> > on >>> > Passenger with Ubuntu Hardy, the updated packages can be found @ the >>> > BitPusher PPA on Launchpad. >>> >>> >https://launchpad.net/~bitpusher/+archive/ppa >>> >>> How do these compare to the Brightbox packages for Hardy Mark? >>> >>> http://wiki.brightbox.co.uk/docs:phusion-passenger >>> >> >> I wasn't aware of their existence and it looks like they've got >> passenger covered pretty good (multiple versions of passenger for both >> i386 and amd64). > > >> However there is no sign of puppet >= 0.24.6 at their repo which is >> explicitly called out in the UsingPassenger wiki doc, so there is no >> one-stop shopping there for Hardy. >> Makes me wonder if they're eating their own dog food :) How should I >> know? > > So I had success with their packages on Hardy with puppet 0.24.8, and > we've just been using upstream Debian puppet 0.24.8, but Hardy looks > like it will require a backport going forward. > > > >> >> > >> > > > > -- > Nigel Kersten > nig...@google.com > System Administrator > Google, Inc. > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Resource ordering
Perhaps if you didn't declare the dependencies accurately, some orderings would work and some orderings would fail. Seems no different to a declarative build tool in that respect. Julian. 2009/7/17 Burkholder, Peter : > > I just finished listening to the Configuration Management panel from > OSBridge (on blip.tv). > > Near the end of it, Adam Jacob states that Puppet's resource dependency > ordering is non-deterministic, > and that manifests that work fine 19 times will fail the 20th time. > > Is this true? I'm puzzled that what Luke considers one of Puppet's > strong suits is derided by > others as its Achille's heel. > > -Peter > > > -- > Peter Burkholder > AARP | Web Strategy & Operations | 601 E Street, NW | Washington, DC > 20049 > email: pburkhol...@aarp.org | aim: peterbtech | ph: 202-434-3530 | cell: > 202-344-7129 | > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: HTTP as a source for files
I like the idea of HTTP if it gets me closer to stubbing out the puppetmaster when I'm developing manifests. Thinking I could stand up a webrick server to resolve all the file sources. Of course, I'd use Apache or Nginx in production. J. 2009/7/1 Marc Fournier : > > > Hello, > >> I've been looking into having Puppet deploy some larger files and I'm >> noticing that it ties up puppetmasters quite a bit and can often >> result in a timeout if the file is too large. Before I submit a >> feature request for a http method for file sources, I would throw it >> out to the group and see if anyone had any thoughts on it. >> >> [...] > > I'm convinced we could benefit from having other file sources than > file:// and puppet://. There already is a (similar) ticket for this: > http://projects.reductivelabs.com/issues/184 > > You might also be interested by Luke Kanies's reply to more or less the > same question on puppet-dev a few weeks ago: > http://groups.google.com/group/puppet-dev/browse_thread/thread/275658354cd45bab/60b7672fbc35c371 > > I've started working on this (but unfortunately got preempted and now > stalled). It shouldn't be too difficult to implement, but as far as I'm > concerned, my knowledge of ruby is currently too low to do this > efficiently :-( > > Marc > > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Testing manifests before you check in?
Thanks for sharing, David. Maybe there's the rub. The big systems can't be reduced down to such a simple approach, and the little systems don't require such rigour? I don't run many nodes but I do have this obsessing with testing infrastructure. J. > One of my problems with this approach is my heavy usage of > export/collect. A significant portion of my problems only surface after > more than one node has exported resources AND another one has collected > them. For me that means that a serious setup will have to have a live > testing environment that has instances of all live services and > integrates all recent changes from the developers. Changes that have > survived a few days without killing the testing environment then can be > rolled out into production. > > > For my personal systems I just develop in the "development" environment > and manually test on the live servers with "puppetd --test > --environment=development --noop" until I'm satisfied. Which, I have to > admit is not very rigorous. But then, I'm a one-man, few-nodes outfit > and can cut corners, others can't cut. > > > > Regards, DavidS > > -- > dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at > Klosterneuburg UID: ATU64260999 > > FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Testing manifests before you check in?
I've seen some excellent discussion on how some people in the
community test their puppet manifests before they check in. I'm still
left wanting a little more. Perhaps I'm being a little pedantic?
What I start with is making sure all the files are legal, with this Rake task:
desc "Test"
task :test do
sh "puppet --parseonly --modulepath=#{puppet_dir}/modules
#{site_manifest}"
end
That catches the accidental syntax errors. Of course, that's no
guarantee that they will actually work in the slightest. So what I
had been doing after that was to execute the manifests as a
non-priveleged user (typically when I'm on the train with my MacBook,
totally unable apply changes to Debian-esque systems anyhow):
desc "Local Puppet Run"
task :local do
sh "puppet --debug --verbose --noop --environment=development
#{site_manifest} \
--templatedir=#{puppet_dir}/templates \
--modulepath=#{puppet_dir}/modules"
end
This kinda works. I'd get better mileage by developing in a VM on my
MacBook. But it's still not enough to tell that my manifests are
vaguely sane: they depend on the fileserver to resolve mounts and the
puppetmaster to compile templates. I started experimenting with
trying to make relative paths in the manifests and file:// urls, but
that got painful quickly. What's been most useful so far is running
'puppetd --test' from the Rakefile. That task depends on another task
which invokes rsync to make sure that the '/etc/puppet' dir is
up-to-date. Once we're in production I won't be doing that on the
main puppetmaster machine.
So ideally, I'd like to be able to stand up a minimal version of the
puppetmaster (with some strings cut?) for the duration of the test
run. That would allow things like file serving without the SSL,
resolution of mounts, compilation of templates, etc. Then at the end
of my invocation of 'rake puppet:my_great_test', the puppetmaster (
perhaps using --no-daemonize) would quit, and I could parse the puppet
output for errors.
The benefit for me is that you can test a lot and gain a good opinion
of things before you go to the next stage of deploying. I'd like to
add this to my Continuous Integration service so a given version of my
infrastructure won't get tagged unless it can pass this test.
Does this appeal to anybody else? I'm keen to make sure that I don't
reinvent the wheel, or scratch an itch that nobody else feels.
Best,
Julian.
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Syntax checking hook when using git?
A Continuous Integration server like Hudson will allow you to poll the GIT repo and make loud noises if the syntax check fails. J. 2009/4/23 Mark Plaksin : > > Hi: > > We want to switch our Puppet config repository from SVN to Git. Our SVN > repository has a pre-commit hook that does a syntax check. If the check > fails, the commit fails. With SVN that hook runs on the server so it's > easy to have (the correct version of) the puppet binary there for the > hook to use. > > With Git it looks like the pre-commit hook has to run wherever a person > happens to have checked out the Git repository. That could be a > desktop, laptop...just about anywhere. It's harder to make sure the > correct version of Puppet is in all of those places. > > Is there a pretty way to solve this problem? How do you do it? > > Is there, perhaps, a way to create a standalone syntax checker that > doesn't require the rest of Puppet? > > Thanks! > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: London (UK) Puppet Meetup 24th March (UKUUG social)
I won't be out til the small hours, but I will try and stay out past 9. J. 2009/3/16 Gary Law : > 2009/3/16 Julian Simpson >> >> I should be there. I'll be standing next to Paul. > > > And I'm so double booked that night. Rats. I might be able to get the > for nine... will you still be there? > Gary > > -- > Gary Law > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: London (UK) Puppet Meetup 24th March (UKUUG social)
I should be there. I'll be standing next to Paul. J. 2009/3/15 Paul Nasrat : > > Various people have said they are going to UKUUG and I wanted to > remind people if they are about and want to discuss puppet, facter, > etc they can come along. > > Entry is not restricted to UKUUG attendees, I'll try and make myself > obvious by having some puppet related paraphenalia. > > http://www.ukuug.org/events/spring2009/social/ > > Paul > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: UK Meetups / Training
With a bit of notice I can do London puppet meetups. But not tomorrow, which is a shame. I probably won't be doing the UKUUG conference. I work just around the corner so I'm very keen to gatecrash the pub to meet Puppet peeps. J. 2009/2/17 Gary Law : > 2009/2/17 Joel Merrick >> >> Hi all! >> >> Are there any Puppet UK meetups or training etc. ? >> > > In the past there's been both, but I missed the last one. If anyone's > interested I'm free tomorrow night for a beer... London area ;) > Gary > > > -- > Gary Law > Email: gary...@garylaw.net > Chat googletalk/messenger: gary@gmail.com > iChat/jabber/AIM: gary@mac.com > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Testing puppet manifests
I'm now running puppet --parseonly for every .pp in subversion. I'm
running it via CI so the configs aren't updated until they pass that
test. Also just discovered the TextMate bundle which allows you to
validate your manifests before you check in. Priceless.
J.
2009/2/4 Matt :
> Hi Nigel,
>
> I gather you run puppet --parseonly for each new file that svn is going to
> commit. Do you have your pre-hook to share?
>
> Thanks,
>
> Matt
>
> 2009/1/7 Nigel Kersten
>>
>> We use environments for a release process, so we can test releases before
>> pushing them to our stable environments.
>> You can also get puppet to check manifests for syntax validity with
>> --parseonly, which we and a lot of other people use as commit hooks in
>> version control so that at least the syntax is guaranteed to be valid. That
>> catches the fat finger errors, and the release process with environments
>> lets us test the actual functionality.
>>
>> On Wed, Jan 7, 2009 at 4:02 AM, Matt wrote:
>>>
>>> HI all,
>>>
>>> First thing - I've been keeping the puppet manifest, configs,
>>> functions etc. in svn, but due to a few dodgy checkouts to the
>>> puppetmaster (non production) i'd like to get a better process in
>>> place. Are people using anything to test the puppet deployments?
>>> preferably in a continuous environment. How are you
>>> deploying/releasing puppet manifests etc.. to the master?
>>>
>>> Also a quick puppet question:
>>>
>>> I use this function to get an application tar file which is specified
>>> in node manifest $dist = app-37434-3439493-.tar.gz:
>>>
>>> exec { "get-app":
>>>cwd => "/opt/dist",
>>>creates => "/opt/dist/$dist",
>>>path=> ["/usr/bin", "/usr/sbin"],
>>>command => "curl -s -f -o $dist
>>> http://$repoUrl/app/$dist";,
>>>before => Exec["untar-dist"],
>>>}
>>>
>>> The 'creates' value ensures that it doesn't get re-downloaded on every
>>> puppet poll. Any new value to $dist works fine, but if $dist becomes
>>> an old value then the file already exists, so the exec and subsequent
>>> calls are not run.
>>>
>>> I guess using the file type would cure this, but I don't want the
>>> master to serve the file, as I use a similar curl command to get the
>>> file from S3 if specified.
>>>
>>> Thanks,
>>>
>>> Matt
>>>
>>>
>>
>>
>>
>> --
>> Nigel Kersten
>> Systems Administrator
>> Tech Lead - MacOps
>>
>>
>
>
> >
>
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Puppet Proposal (what problems will puppet solve)
Steve Traugott (http://www.infrastructures.org/) compares the problem to building cars by hand, vs the production line. It's a nice metaphor to use when you're trying to demonstrate what a significant change it can be. We still do stuff by hand in IT even though you can demonstrate that the error rate of doing it is far too high. I think IT workers end up far too often like the poor bloke on the clock in Metropolis. :) J. 2009/2/3 Bjørn Dyre Dyresen : > > > 2009/2/2 Zach Buckholz >> >> This may sound like a confusing / trick question, so please bare with me. >> >> What problem(s) will puppet solve? Why would I use it? >> >> I am trying to pitch the use of puppet in our environment and need to >> follow a formal proposal model. Which means I need to start with a problem >> to solve or situation to improve. >> >> The concept of what puppet will do needs to be explained to non-technical >> business leaders. >> >> This is what I have come up with so far; (I wish the reductive labs site >> had a wiki page for this) >> >> What is the problem? >> Unknown configurations >> Environment is not dynamic >> Messy >> No central model >> Hard to change >> No consistency >> Administration overhead >> Reactive instead of proactive >> Unorganized >> Need scripts to work with linux and solaris >> Hard to scale >> >> Can anyone add (non-technical explanations) to the above list? >> >> Zach >> This message is private and confidential. If you have received it in >> error, please notify the sender and remove it from your system. >> > > > > If you are consistent in your use of puppet you can use puppet as a > documentation resource. > Need to know how a particular server is configured? Look at the puppetcode! > > With puppet you can move servers with ease! > you write generic classes or modules. Need to move a particular service? > Just include it somewhere else! > > For consistency it's really easy to apply the same configuration to a lot of > hosts. Need to add a host? Well, just add it to the host group, and puppet > takes care of it! > > As for administration overhead. Puppet will give you less work to do! How? > You just make a puppet manifest/module/class/whatever suites you that takes > care of a certain thing. You know it works! You don't have to remember how. > Next time, just apply it to a host! And Done! > > If you need scripts to work on multiple platforms, Puppet does this really > well. Just add eg a case statement selecting what to apply based on > operating system. > > Puppet scales well. Having server being puppetmaster set up with > nginx/mongrel/puppet we can restart puppet 100 nodes at the same time having > no troubles at all. The server being a dual quadcore with 16 gb of ram is > serving approx 200 nodes and is not sweating a bit. Could easly serve the > double. > > > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Facter - the future - your input needed
Hi, > 1. Namespaces - add a namespace or tiered namespace to Facter, i.e. > network -> interface -> ipaddress. Sounds interesting. > 2. Additional output formats - JSON, XML? (winces) - Facter already > outputs in YAML. YAML support is growing. .NET developers are starting to use YAML. I'd never choose XML output over other features. Maybe if an "enterprise" client wanted to pay Luke to implement it :) > 3. Additional collection mechanisms, for example the ability to > specify a fact file, /etc/facter.conf, containing fact name=value pairs. /etc/factor.d ? > 4. A more Ruby DSL for facts I'd like to see that. I can't justify it in terms of any additional benefit that it would give right now, but it seems useful. J. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
