On Feb 23, 1:25 pm, Brice Figureau <[email protected]> wrote: > I unfortunately didn't had time to work on my network device framework > for more than a month. I expect to resume this work soon :)
I know what that's like. That aws code has been sitting since the beginning of January. > I'm not sure it will be generic enough to support what you want to do, > but that'd be a great opportunity to generalize it :) Sure. I recall a lot of overlap in the NetworkDevice class that you were basing on. The thing that really killed my provider was serialized actions at internet latencies. The paradigm of batch fetching the status, updating hashed instances, then flushing changes seemed to be a smarter way forward. Route 53 also happened to map on to your "network" components as well. I have sets of credentials with many domains (devices), with many hosts (interfaces). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
