On Monday, February 18, 2013 9:15:05 AM UTC-6, Gavin Williams wrote: > > > I was expecting the full state transition to take several Puppet runs, as > the initial data replication to get from start to an 'Initialized' state > could take anything from a couple of minutes to a couple of days... > So changing the required state of the resource in-between runs was an > expected step - ideally it would be automated, but could be manual I > guess... > > That was not my point. You can have multiple classes that manage the same state detail in different ways. You just can't include more than one of them in the same catalog. Since you were planning multiple runs anyway, that is probably not a major issue.
At this point, however, I'm not sure what the question is. You asked "is this something Puppet could manage?" and the answer is "probably", especially considering that you're open to doing it across several runs. If you're looking for specific advice on how to describe steps 8-11 to Puppet then you'll need to provide more information. How can any person or agent determine to what stage the process has progressed? What are the system properties to be managed, and by what tool and/or operation are they managed? John -- 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+unsubscr...@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.
