Thanks for your input folks. I have successfully run the manifests we
have with out trouble. I'm looking forward to simplifying my job with
this great tool, along with a few other side projects. Puppet is the
first CMS I've laid hands on and so far, I'm stoked. :)

On Thu, Aug 11, 2011 at 3:23 PM, Eric Shamow <e...@puppetlabs.com> wrote:
> John,
>
> I suspect you're right. User requirements FTW.
>
> -Eric
>
> --
> Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
> 23rd in Portland, OR.
>
> Eric Shamow
> Professional Services
> http://puppetlabs.com/
> (c)631.871.6441
>
> On Thursday, August 11, 2011 at 2:45 PM, jcbollinger wrote:
>
>>
>>
>> On Aug 11, 11:52 am, Eric Shamow <e...@puppetlabs.com 
>> (http://puppetlabs.com)> wrote:
>> > This could also be a place for the use of exported resources. End result 
>> > is similar to puppet resource but can change dynamically, which is nice.
>>
>> If the OP already had Puppet manifests for the machine he wanted to
>> clone, then he would not need to go through this exercise in the first
>> place. He could more or less just assign all the same classes to the
>> new node that are assigned to the existing one. That would be a lot
>> easier than exporting all of one node's resources and collecting them
>> on the other, or using 'puppet resource' to analyze the original
>> machine.
>>
>> I interpreted the OP's use of "configuration" differently: I think he
>> means what we more typically might describe as "state" (indeed, he
>> later uses that term himself). He's looking for tools with which to
>> create Puppet manifests describing the existing machine, which he will
>> then apply to the new one. Exported resources are clearly no help
>> there, because there are no existing resource declaration to export.
>>
>>
>> John
>>
>> --
>> 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 
>> (mailto:puppet-users@googlegroups.com).
>> To unsubscribe from this group, send email to 
>> puppet-users+unsubscr...@googlegroups.com 
>> (mailto: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.
>
>

-- 
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.

Reply via email to