Okay, I am sure virtual resources are a good idea. The problem is other than may be for users I need to include in multiple places, I have not idea of teh right way to use them. I am looking for I guess the best practice in using virtual resource, and maybe some practical examples on right ways to use them. evan --~--~---------~--~----~------------~-------~--~----~ 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 May 13, 2009, at 9:12 AM, Evan Hisey wrote:> > Okay, I am sure virtual resources are a good idea. The problem is > other than may be for users I need to include in multiple places, I > have not idea of teh right way to use them. I am looking for I guess > the best practice in using virtual resource, and maybe some practical > examples on right ways to use them.Generally, virtual resources are useful primarily when you want to separate specification of a resource from the decision to deploy a resource to a host. This separation usually arises because there are multiple criteria that can result in a resource being deployed. In the case of users, the user might be in multiple groups, and any of those groups could result in the resource being deployed. A similar decision process could happen for hosts (you have a list of cluster hosts and based on cluster membership want to deploy specific host resources), ssh keys (deploy keys based on the user''s group membership and that group''s presence on the host), and much more. -- The trouble with the rat race is that even if you win, you''re still a rat. -- Lily Tomlin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> On May 13, 2009, at 9:12 AM, Evan Hisey wrote: > >> Okay, I am sure virtual resources are a good idea. The problem is >> other than may be for users I need to include in multiple places, I >> have not idea of teh right way to use them. I am looking for I guess >> the best practice in using virtual resource, and maybe some practical >> examples on right ways to use them. > > > Generally, virtual resources are useful primarily when you want to > separate specification of a resource from the decision to deploy a > resource to a host.Can''t a define achieve the same end? Specify the resource collection in the define at one place, and choose to deploy it in multiple other places. -- +-Geoff Crompton +--Debian System Administrator +---Trinity College --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---