Re: [Puppet Users] facter fails to detect network interfaces with long names
All, I put in a request to have the gentoo bug reopened and see if we can apply the same patch that the other distributions used. Thanks, Matt On Tue, Sep 20, 2011 at 11:16 AM, Alex L. Demidov wrote: > On Tue, Sep 20, 2011 at 06:50:25PM +0100, Ken Barber wrote: >> I think this gives a little weight to this ticket for Facter then: >> >> http://projects.puppetlabs.com/issues/1346 >> >> Although - I don't see a 9 char limitation on Debian Wheezy. Not sure >> where that patch came from though. I wonder how many other distros >> suffer from this. > > It seems that they (and RHEL/Fedora) patched this long ago. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405521 > >> >> Of slightly related interest - I do see a 15 character limit when >> using 'brctl addbr somelongnamefoo' to create a named interface - and >> that seems to exist for both ifconfig and ip addr when reading the >> interfaces. So I'm guessing 15 chars is the kernel limit or perhaps >> brctl limit :-). > > Luckily all my interface names under 15 chars length. > >> >> ken. >> >> On Tue, Sep 20, 2011 at 6:31 PM, Alex L. Demidov >> wrote: >> > On Tue, Sep 20, 2011 at 06:24:40PM +0100, Ken Barber wrote: >> >> Hi Alex, >> >> >> >> What happens when you run 'ip addr list' instead? >> > >> > It shows interface names properly and not truncated. >> > >> >> >> >> ken. >> >> >> >> On Tue, Sep 20, 2011 at 6:20 PM, Alex L. Demidov >> >> wrote: >> >> > I have Gentoo host where `ifconfig -a` prints long interface names >> >> > truncated to 9 chars (there is closed bug report [1]). >> >> > >> >> > Unfortunately, `facter` uses `ifconfig -a` output to get list of >> >> > interface names and because of truncation it generates `interfaces` >> >> > fact with incorrect interface names. Also it fails to retrieve >> >> > individual interface information with following message for >> >> > each interface with name "myinterface": >> >> > >> >> > Device "myinterfa" does not exist. >> >> > myinterfa: error fetching interface information: Device not found >> >> > >> >> > [1]: https://bugs.gentoo.org/show_bug.cgi?id=179920 >> > >> > -- >> > Alex L. Demidov (ALD9-RIPE). >> > http://alexeydemidov.com/ >> > Freelance Consulting. >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Puppet Users" group. >> > To post to this group, send email to puppet-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > puppet-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. >> > >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. > > -- > Alex L. Demidov (ALD9-RIPE). > http://alexeydemidov.com/ > Freelance Consulting. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Package provider for gentoo?
> This comes down to the package provider depending on eix, which is > presumably some sort of interface to portage that isn't standard; > fixing the provider should fix the problem there. That pretty much > depends on someone who cares sending an appropriate patch. (hint ;) > That's probably most of it. Can you provide a link to the file(s) on github within the puppet source specific to the gentoo packaging provider? I'll see if I can find to review it and consider extending or updating it to understand more of the gentoo build specific procedures. I'm not sure if this might require adding new keywords or resources, or if we're just talking about setting and creating class variables that the provider would interpret and implement. > >> - The handling of dependencies and libraries is not clear cut, and one >> usually has to create a separate script to run after puppet to ensure >> linking is correct and that python/perl/etc modules are happy. > > You *should* be able to tie that together with an appropriate exec to > at least automate it. > Yes and no -- it's not a clear cut process. Most of the time there are just a few calls after a package is installed, but frequently you'll want to limit those calls until all other package operations are complete, and/or run the calls over and over to slowly resolve dependencies if there is a failure. Some of the calls can also be quite expensive so they are only run when certain packages are modified - so there might be a bit of intelligence that has to be stored in code to get a fully optimized robust solution. Differing versions of portage can also have an impact/etc. > Daniel > -- > ⎋ Puppet Labs Developer – http://puppetlabs.com > ♲ 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-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. > > -- Matthew Marlowe m...@professionalsysadmin.com Senior Internet Infrastructure Consultant DevOps/VMware/SysAdmin https://www.twitter.com/deploylinux Gentoo Linux Dev "Courage is not simply one of the virtues, but the form of every virtue at the testing point." -- C.S. Lewis -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Package provider for gentoo?
Peter, Puppet works great on gentoo with the following caveats: - Puppet conceptually uses a binary package paradigm, and one needs to work around that. It would be nice if we could extend puppet for gentoo to make it more "source based distribution aware" and especially allow it to manage portage configuration files and limit compile times/etc. - Do to the differences between binary and source, one frequently will setup puppet to run only once/day on server nodes during off peak hours so that any compiling/package dependencies will not occur during critical periods - and if possible, all compiling will occur on the build server prior to puppet agent calls on other nodes. - Gentoo supports more cron systems than puppet supports (last I checked, puppet did not support fcron) - Gentoo admins are slightly behind redhat/fedora admins in writing public modules, this is an area where there is a significant amount of activity and I hope we can eventually catch up on. - The handling of dependencies and libraries is not clear cut, and one usually has to create a separate script to run after puppet to ensure linking is correct and that python/perl/etc modules are happy. There are additional issues, but all of them to date can be reasonably overcome/managed. I've been in contact with many admins w/ larger sized clusters and improving the puppet experience on gentoo is a frequent topic of conversation. I wouldn't be discouraged by any initial issues you find. Matt On Tue, Sep 6, 2011 at 12:46 PM, Peter Berghold wrote: > Doing a google after I sent the email I found the following page: > > http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Gentoo > > after doing a "emerge eix" and re-running the puppet transaction things > *look* to be going normally can't tell for sure since it is still > running and it is not generating any spew for me to look at. > > I'll know in a while if it worked. > > > > On Tue, Sep 6, 2011 at 3:43 PM, James Turnbull wrote: >> >> Peter Berghold wrote: >> > Now I get: >> > err: Could not prefetch package provider 'portage': Command update_eix >> > is missing >> > >> > I'm running puppet 2.7.3 on both the puppet master and the client. Any >> > thoughts? >> >> Caveat: I am not a Gentoo person. >> >> Is the binary update_eix present on the host? >> >> James >> >> -- >> James Turnbull >> Puppet Labs >> 1-503-734-8571 >> >> Join us for PuppetConf <http://www.bit.ly/puppetconfsig>, September 22nd >> and 23rd in Portland, Oregon, USA. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > > > -- > Peter L. Berghold > Owner, Shark River Technical Solutions LLC > > -- > 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. > -- Matthew Marlowe m...@professionalsysadmin.com Senior Internet Infrastructure Consultant DevOps/VMware/SysAdmin https://www.twitter.com/deploylinux Gentoo Linux Dev "Courage is not simply one of the virtues, but the form of every virtue at the testing point." -- C.S. Lewis -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Pushing changes to nodes
Hi Pavel, We implemented something similar to what you are asking on our own servers using commonly available tools: * pssh - cluster ssh tools * cron/etc on puppetmaster + puppetrun - our sysadmins or the puppetmaster itself determines when puppet configuration runs should be performed. * modified agent configs to be active on clients, but not to execute unless they receive a request directly from puppetmaster (no interval based runs) * NFSv4 to clients from puppet master We implemented the above because puppet's default method of execution is OK for binary based distributions, but not really for source based linux distributions. Using a "run only when puppet master tells us to" allows us to update source repositories on the master, and then have the master execute the necessary code on the clients to update before forcing a puppet update. In general, this means puppet only runs about once/week for most nodes. We add some additional bash/ruby code to create groups of nodes to update. Matt On Sun, Jun 5, 2011 at 4:48 AM, Pavel Shevaev wrote: > Hi! > > I've finally managed to migrate our servers deployment process to the > puppet and so far it works just fine. Puppet is great, but its default > pull model doesn't fit our requirements. I'm thinking about usage of > clusterssh(or something similar) in order to trigger the following > command on the nodes: > > sudo puppet agent --no-daemonize --verbose --onetime > > In our setup puppet agent is not running as a service on the nodes. > > I think it would be really nice to have this feature available in the > future versions of puppet, e.g: > > #puppet push > > What do you think? > > -- > Best regards, Pavel > > -- > 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. > > -- Matthew Marlowe Tel: 805-857-9144 http://www.professionalsysadmin.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.
Re: [Puppet Users] Puppet Master System Requirements
Keep in mind that there are many ways to run puppet. We manage ~100 nodes with just a single puppet master running within a gentoo VM w/ only single cpu core and 2GB ram. Catalog compile times average under 0.6 seconds. This is also w/ web brick. The puppet master VM also serves as a master nfs server and gentoo build server. Thats a lot of stuff on a single small VM, but it works perfectly for us because: a) our default puppet run interval is 4hrs (if something goes wrong w/ one of our manifests or the server, we'll probably notice it and stop it before too many servers get updated - for our purposes, we don't see any benefit to using an interval less than 4hrs. 4hrs is certainly sufficient for most common security updates and we also do not want to have normal updates impacting production performance during peak business hours - so 25% of servers updating every hour is perfect for us. ). b) Many of our servers, mostly the gentoo ones, only execute puppet when puppetrun is invoked either manually by systems administrators for the specific nodes they are reconfiguring or automatically as part of a nightly update systems maintenance cron job). Basically, puppet is extremely flexible w/ hardware, and it is likely your own preferences and production requirements will dictate the hardware needed rather than puppet itself. On Tuesday, May 10, 2011 06:04:22 am Panaman wrote: > I've been messing around with Puppet on a VM on my personal desktop. > It looks descent. I was wondering what kind of load this thing would > have managing about 400 nodes. > Does this thing require a beefy server? Matt -- Matthew Marlowe/ 858-400-7430 /DeployLinux Consulting, Inc Professional Linux Hosting and Systems Administration Services www.deploylinux.net * m...@deploylinux.net 'MattM' @ irc.freenode.net -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet with VMWare ESX
> > Not at all, Puppet with vmware guest platforms is fantastic. > +1 More to the point, puppet seems best at allowing rapid scale out of applications via virtualization. Our policy is to deploy all linux virtual machines via puppet. It is the physical machines serving as hypervisors or as critical cluster management/infrastructure that we don't let puppet currently touch. > We have a procedure in place that uses kickstart with CentOS and > puppet for post-install configuration that can bring a system up and > on the net and with all packages installed in under 10 minutes. We > deploy hosts constantly using this method, and each new host comes up > already puppet-managed, with vmware tools installed, and ready for > final configuration. > We currently do cloning of a template VM for new rhel nodes. We've avoided kickstart because a) we already have to go into vcenter to create/configure new vms properly and b) there isn't much that kickstart would give us we don't already get from cloning and running scripts after clone. When/if we can get to a point that puppet dashboard can tell vcenter to spawn a new vm, provision appropriate virtual hardware and vm settings, start kickstart, and then start puppet, then we'll switch to that :) -Matt -- Matthew Marlowe - http://www.deploylinux.net/ CEO @ DeployLinux Consulting, Inc m...@deploylinux.net, 858-400-7430 http://www.twitter.com/deploylinux -- 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.
