Hi all, my name is Arnau Bria and I''m a sys admin in a center where we must deal with hundred hosts. We''re currently working with quattor, but it''s too complex for our purposes, so I''m looking for new admin tool. I''ve been playing with CFengine for few days (2 or 3) and I''ve seen some limitations that makes me thing that CFE is not our solution. So now, I''ve met puppet and I''d like to test it, but before playing with it, I''d like to ask for the main problems I saw in CFE and try to save some time. 1.-) RPM. In CFE I wanted to use "yum install", "yum group install" and "rpm -Uvh" in same host group (or class), but for different packages/metapackages. I was no able, and I think, for replies I got from list, I will not... So, is puppet able to use many rpm install commands in same host? *Did not find the answer here: http://reductivelabs.com/trac/puppet/wiki/TypeReference#package 2.-) CFE logs are crazy... I need syslog or nagios and parse them myself... I''ve seen: http://www.devco.net/pubwiki/Puppet/PuppetView and looks very nice, but has puppet a sumary of what has done in the client with a simple "OK" or "KO"? (Obviously I won''t say ok or ko, but maybe it could say if all steps when fine or not..) So, could someone answer these questions? I''m really interested in using this software! TIA, Arnau --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi all, my name is Arnau Bria and I''m a sys admin in a center where we must deal with hundred hosts. We''re currently working with quattor, but it''s too complex for our purposes, so I''m looking for new admin tool. I''ve been playing with CFengine for few days (2 or 3) and I''ve seen some limitations that makes me thing that CFE is not our solution. So now, I''ve met puppet and I''d like to test it, but before playing with it, I''d like to ask for the main problems I saw in CFE and try to save some time. 1.-) RPM. In CFE I wanted to use "yum install", "yum group install" and "rpm -Uvh" in same host group (or class), but for different packages/metapackages. I was no able, and I think, for replies I got from list, I will not... So, is puppet able to use many rpm install commands in same host? *Did not find the answer here: http://reductivelabs.com/trac/puppet/wiki/TypeReference#package 2.-) CFE logs are crazy... I need syslog or nagios and parse them myself... I''ve seen: http://www.devco.net/pubwiki/Puppet/PuppetView and looks very nice, but has puppet a sumary of what has done in the client with a simple "OK" or "KO"? (Obviously I won''t say ok or ko, but maybe it could say if all steps when fine or not..) So, could someone answer these questions? I''m really interested in using this software! TIA, Arnau --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2008/10/29 Arnau <arnau.bria@gmail.com>:> Hi all, > [..snip..] > 1.-) RPM. In CFE I wanted to use "yum install", "yum group install" > and > "rpm -Uvh" in same host group (or class), but for different > packages/metapackages. I was no able, and I think, for replies I got > from list, I will not... > So, is puppet able to use many rpm install commands in same host? > > *Did not find the answer here: > http://reductivelabs.com/trac/puppet/wiki/TypeReference#packageSure, you should be able to do that. For the yum groupinstall you might have to run that as an exec (someone else here might know more), but in general you''d have something like the below completely contrived example: node foo { include example } class example { package { "some_rpm": provider => ''rpm'', ensure => ''installed'', source => ''http://my_rpm_repo/some_rpm.rpm"; "some_yum": ensure => ''installed'', provider => ''yum''; } exec { "yum installgroup foobar": unless => "yum grouplist | grep foobar", } }> 2.-) CFE logs are crazy... I need syslog or nagios and parse them > myself... > I''ve seen: > http://www.devco.net/pubwiki/Puppet/PuppetView and looks very nice, > but > has puppet a sumary of what has done in the client with a simple "OK" > or "KO"?There are a couple of ways to get this information, you could take a look at reports: http://reductivelabs.com/trac/puppet/wiki/ReportReference and the "Reports and Reporting" link from there. The puppet client can log to a file or a syslog server, and produces logs of what has been done to a system. If you really really need to know the exact state that puppet believes the system is in, you can poke at /var/lib/puppet/state/state.yaml, but you probably should use one of the other methods...> So, could someone answer these questions? I''m really interested in > using this software! > > TIA, > ArnauHope that gives you some answer, cheers .r'' --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, Oct 29, 2008 at 8:48 PM, RijilV <rijilv@gmail.com> wrote:> > 2008/10/29 Arnau <arnau.bria@gmail.com>:[...]> Sure, you should be able to do that. For the yum groupinstall you > might have to run that as an exec (someone else here might know more), > but in general you''d have something like the below completely > contrived example: > > node foo { > include example > } > > class example { > package { > "some_rpm": > provider => ''rpm'', > ensure => ''installed'', > source => ''http://my_rpm_repo/some_rpm.rpm"; > "some_yum": > ensure => ''installed'', > provider => ''yum''; > }Here I''m mixing rpm and yum depending on the rpm, is it? Always with package type? *I really like and need this one...> > exec { "yum installgroup foobar": > unless => "yum grouplist | grep foobar", > } > } >So, I''m not using "package" here, I''m doing it with exec, telling that if the package is foobar, execute "yum groupinstall"... but then, it will be logged out of package type section... is it?> > > 2.-) CFE logs are crazy... I need syslog or nagios and parse them > > myself... > > I''ve seen: > > http://www.devco.net/pubwiki/Puppet/PuppetView and looks very nice, > > but > > has puppet a sumary of what has done in the client with a simple "OK" > > or "KO"? > > There are a couple of ways to get this information, you could take a > look at reports: > http://reductivelabs.com/trac/puppet/wiki/ReportReference and the > "Reports and Reporting" link from there. The puppet client can log to > a file or a syslog server, and produces logs of what has been done to > a system. If you really really need to know the exact state that > puppet believes the system is in, you can poke at > /var/lib/puppet/state/state.yaml, but you probably should use one of > the other methods... >Really interesting, I must look it.> > So, could someone answer these questions? I''m really interested in > > using this software! > > > > TIA, > > Arnau > > > Hope that gives you some answer,Sure, many thanks for your reply!> > cheers > .r'' >Cheers, Arnau --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
2008/10/29 Arnau Bria <arnau.bria@gmail.com>:> > > On Wed, Oct 29, 2008 at 8:48 PM, RijilV <rijilv@gmail.com> wrote: >> >> 2008/10/29 Arnau <arnau.bria@gmail.com>: > > [...] > >> >> Sure, you should be able to do that. For the yum groupinstall you >> might have to run that as an exec (someone else here might know more), >> but in general you''d have something like the below completely >> contrived example: >> >> node foo { >> include example >> } >> >> class example { >> package { >> "some_rpm": >> provider => ''rpm'', >> ensure => ''installed'', >> source => ''http://my_rpm_repo/some_rpm.rpm"; >> "some_yum": >> ensure => ''installed'', >> provider => ''yum''; >> } > > Here I''m mixing rpm and yum depending on the rpm, is it? Always with package > type? > *I really like and need this one...Yeah, the package type is platform independent, and pretty configurable. You can read more about the built-in types over at: http://reductivelabs.com/trac/puppet/wiki/TypeReference>> exec { "yum installgroup foobar": >> unless => "yum grouplist | grep foobar", >> } >> } > > So, I''m not using "package" here, I''m doing it with exec, telling that if > the package is foobar, execute "yum groupinstall"... but then, it will be > logged out of package type section... is it?Honestly I wouldn''t use package groups like this. I would just create a RPM that requires all the stuff that I want installed and use yum/apt to install that particular rpm. Also, for what its worth, I would probably not ever use RPM directly. Setting up a local yum or apt repository is easy and it will save you quite a bit of work in the long run. Also I''m not sure there isn''t a way to get puppet''s default package provider to handle yum grouplists like the above, I''ve just never done it. .r'' --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Arnau, The groupinstall is specific behavior to yum, it isn''t an abstraction supported by Package resource. If you really really really want to manage package groups, I recommend creating a packagegroup type instead of an exec based on a grep. The exec might be sufficient as a quick and dirty solution to get started provisioning, but it is only one direction and if you are going to manage lot''s of package groups over time you will wish you had a type. I would also recommend you manage your own repos. There is some investment up front, but it will pay off in the long run and simplifies your change management process significantly. Cheers, Andrew On Thu, Oct 30, 2008 at 10:39 AM, RijilV <rijilv@gmail.com> wrote:> > 2008/10/29 Arnau Bria <arnau.bria@gmail.com>: > > > > > > On Wed, Oct 29, 2008 at 8:48 PM, RijilV <rijilv@gmail.com> wrote: > >> > >> 2008/10/29 Arnau <arnau.bria@gmail.com>: > > > > [...] > > > >> > >> Sure, you should be able to do that. For the yum groupinstall you > >> might have to run that as an exec (someone else here might know more), > >> but in general you''d have something like the below completely > >> contrived example: > >> > >> node foo { > >> include example > >> } > >> > >> class example { > >> package { > >> "some_rpm": > >> provider => ''rpm'', > >> ensure => ''installed'', > >> source => ''http://my_rpm_repo/some_rpm.rpm"; > >> "some_yum": > >> ensure => ''installed'', > >> provider => ''yum''; > >> } > > > > Here I''m mixing rpm and yum depending on the rpm, is it? Always with > package > > type? > > *I really like and need this one... > > Yeah, the package type is platform independent, and pretty > configurable. You can read more about the built-in types over at: > http://reductivelabs.com/trac/puppet/wiki/TypeReference > > >> exec { "yum installgroup foobar": > >> unless => "yum grouplist | grep foobar", > >> } > >> } > > > > So, I''m not using "package" here, I''m doing it with exec, telling that if > > the package is foobar, execute "yum groupinstall"... but then, it will be > > logged out of package type section... is it? > > Honestly I wouldn''t use package groups like this. I would just create > a RPM that requires all the stuff that I want installed and use > yum/apt to install that particular rpm. Also, for what its worth, I > would probably not ever use RPM directly. Setting up a local yum or > apt repository is easy and it will save you quite a bit of work in the > long run. > > Also I''m not sure there isn''t a way to get puppet''s default package > provider to handle yum grouplists like the above, I''ve just never done > it. > > > .r'' > > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, Oct 30, 2008 at 5:39 PM, RijilV <rijilv@gmail.com> wrote:> > So, I''m not using "package" here, I''m doing it with exec, telling that if > > the package is foobar, execute "yum groupinstall"... but then, it will be > > logged out of package type section... is it? > > Honestly I wouldn''t use package groups like this. I would just create > a RPM that requires all the stuff that I want installed and use > yum/apt to install that particular rpm. Also, for what its worth, I > would probably not ever use RPM directly. Setting up a local yum or > apt repository is easy and it will save you quite a bit of work in the > long run.Yep, I will manage my own repos, but I''m looking for some felxiblity in package management... Also, rpm is for emergency... sometimes they make me install some strange rpm version out of metapackege, and it''s easy to do a rpm -e --nodeps / rpm -i --nodeps than rebuilding the metapackage. yum is enough for day to day administration, but before moving to a system, I want to know how flexible is each system.> > Also I''m not sure there isn''t a way to get puppet''s default package > provider to handle yum grouplists like the above, I''ve just never done > it. >I was thinking in modifying some code, maybe create a new personal "provider" could be enough. Need to study it...> .r'' >Thanks for your replies. Arnau --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Thu, Oct 30, 2008 at 6:12 PM, Andrew Shafer <andrew@reductivelabs.com>wrote:> Arnau,Hi Andrew,> > The groupinstall is specific behavior to yum, it isn''t an abstraction > supported by Package resource.Yep, *yum*: Support via yum. Required binaries: python, rpm, yum. Default for operatingsystem == fedoracentosredhat. Supported features: installable, uninstallable, upgradeable, versionable. SO, I imagine I should create a group_installable feature... is it?> If you really really really want to manage package groups, I recommend > creating a packagegroup type instead of an exec based on a grep. The exec > might be sufficient as a quick and dirty solution to get started > provisioning, but it is only one direction and if you are going to manage > lot''s of package groups over time you will wish you had a type.One question on that, if create packagegroup type, logs will go out of package section... is it? I have many workarounds for solving many problems. But I''m looking for solving all my problems using native types...> > I would also recommend you manage your own repos. There is some investment > up front, but it will pay off in the long run and simplifies your change > management process significantly.Sure. I keep that in mind and is basic for our new conf.> > Cheers, > Andrew >Thanks for your replies! Arnau --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---