What commands are there to collect system information and convert it into puppet resources? We have a lot of systems that were not initially configured with puppet and we would like to gather information about those systems as puppet resources. I have been generating resource information using ''pupppet resource ...'' and that has been working reasonably well. For example, ''puppet resource user'' generates resources for all users on the system. If I want just one user, I can specify that user''s name, e.g. ''puppet resource user foo''. Same goes for types group, mount, package, and a few other types. But that pattern doesn''t work for all resource types or options. For example, ''puppet resource ssh_authorized_key'' doesn''t output anything. The ''cron'' type asks for a Title. ''interface'' errors that it could not find a type ''interface''. And although ''package'' lists all packages using the default package manager, it''s not immediately apparent how to generate resources for all gems, e.g. ''puppet resource package provider=gem'' does not list gems. Is ''puppet resource ...'' the "best practice" way to generate resource information or are there other tools more suited? Or are there options or environment variables that are not immediately apparent? Still reading through the docs, but any pointers in the right direction gladly accepted. Regards, - Robert -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Tuesday, February 19, 2013 10:00:39 AM UTC-6, Robert Citek wrote:> > What commands are there to collect system information and convert it > into puppet resources? > > We have a lot of systems that were not initially configured with > puppet and we would like to gather information about those systems as > puppet resources. I have been generating resource information using > ''pupppet resource ...'' and that has been working reasonably well. For > example, ''puppet resource user'' generates resources for all users on > the system. If I want just one user, I can specify that user''s name, > e.g. ''puppet resource user foo''. Same goes for types group, mount, > package, and a few other types. > > But that pattern doesn''t work for all resource types or options. For > example, ''puppet resource ssh_authorized_key'' doesn''t output anything. > The ''cron'' type asks for a Title. ''interface'' errors that it could > not find a type ''interface''. And although ''package'' lists all > packages using the default package manager, it''s not immediately > apparent how to generate resources for all gems, e.g. ''puppet resource > package provider=gem'' does not list gems. > > Is ''puppet resource ...'' the "best practice" way to generate resource > information or are there other tools more suited? Or are there > options or environment variables that are not immediately apparent? > > Still reading through the docs, but any pointers in the right > direction gladly accepted. > >I''ve not used it personally, but there is a project (I think) called Blueprint might be worth looking into. I seem to recall that it can scan a system and generate modules for it.> Regards, > - Robert >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Robert Citek
2013-Feb-20 00:37 UTC
Re: [Puppet Users] Re: Querying system to generate resources
Thanks. I''ll try that out: https://github.com/devstructure/blueprint Regards, - Robert On Tue, Feb 19, 2013 at 11:20 AM, llowder <llowderiv@gmail.com> wrote:> > > On Tuesday, February 19, 2013 10:00:39 AM UTC-6, Robert Citek wrote: >> >> What commands are there to collect system information and convert it >> into puppet resources? >> >> We have a lot of systems that were not initially configured with >> puppet and we would like to gather information about those systems as >> puppet resources. I have been generating resource information using >> ''pupppet resource ...'' and that has been working reasonably well. For >> example, ''puppet resource user'' generates resources for all users on >> the system. If I want just one user, I can specify that user''s name, >> e.g. ''puppet resource user foo''. Same goes for types group, mount, >> package, and a few other types. >> >> But that pattern doesn''t work for all resource types or options. For >> example, ''puppet resource ssh_authorized_key'' doesn''t output anything. >> The ''cron'' type asks for a Title. ''interface'' errors that it could >> not find a type ''interface''. And although ''package'' lists all >> packages using the default package manager, it''s not immediately >> apparent how to generate resources for all gems, e.g. ''puppet resource >> package provider=gem'' does not list gems. >> >> Is ''puppet resource ...'' the "best practice" way to generate resource >> information or are there other tools more suited? Or are there >> options or environment variables that are not immediately apparent? >> >> Still reading through the docs, but any pointers in the right >> direction gladly accepted. >> > > I''ve not used it personally, but there is a project (I think) called > Blueprint might be worth looking into. I seem to recall that it can scan a > system and generate modules for it. > > >> >> Regards, >> - Robert > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.