Thank you John, I think you hit the nail on the head. I just started this gig and the sysadmin before me started the process of setting up our machines to be managed by puppet. We have a project to add a redundant server and he started this project with puppet in mind, but the manifests are not all done. He left in a bit of a hurry and I'm left to clean up and fill in the gaps where I can. As server1 is sound in it's current state, I was hoping I could use puppet to inspect that machines state and generate manifests that would make it simple to clone the machines state to another machine.
It's ok, I believe I have the manifests good enough for a dry run. Anything missed now will be caught later when we start running full regression tests on the fail-over server. I'm starting to gather up the ammo needed to convince the boss to let me start moving most of our services into the cloud. From here on out, any new machines will be managed with puppet. It's quite a nice tool now that I'm starting to get the hang of it. Cheers! Mike On Thu, Aug 11, 2011 at 2:45 PM, jcbollinger <john.bollin...@stjude.org> wrote: > > > On Aug 11, 11:52 am, Eric Shamow <e...@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. > 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.
