Hi Markus, On Fri, 2013-07-12 at 03:52 -0700, Markus Burger wrote: > We just released an internally developed puppet-networkdevice module > in the hope that some other folks might be interested in it :).
This is very interesting! > It's currently still in an early stage but should be pretty usable for > the basic usecases. > > -> https://github.com/uniak/puppet-networkdevice > > ## Overview > > The Cisco Networkdevice Module provides a common way to manage various > configuration properties with Puppet and was initially based on the > network_device utility provided by Puppet. Your development is much more complete than my very limited implementation, congrats! > Currently most providers, types, etc are suffixed with _ios as to > avoid collusion with the network_device code already provided by > puppet. That make sense, but you also apparently integrated some of the bits that were in the core (I was thinking about the transport classes). I won't speak for the core maintainers here, but that'd be great if you could have used what was in the core. What was preventing you to use the mechanisms/features that were already there? Is that you wanted to modify/add things on top of that? So now that we have this module, is it time to remove all the cisco stuff from the core, and leave only the base network device mechanism (possibly enriched by some of the functionalities this module provides)? -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
