On 12/09/11 20:13, Greg Sutcliffe wrote: > On 12 September 2011 18:26, Nan Liu <[email protected]> wrote: >> Yes with some work around required. You need to export RUBYLIB with >> the appropriate path. See example and known limitation section: >> https://github.com/puppetlabs/puppetlabs-f5 >> >> In my limited experience, seems easier to dev/test with puppet >> resource/puppet apply commands, just add apply_to_device to the >> resource type when you are ready for full testing using puppet device >> command. > > Thanks Nan - seeing what others are doing to extend puppet device is > massively helpful. I'll be reading your code closely tomorrow :)
You'll see when reading Nan's code that the biggest difference in the cisco and F5 stuff is the transport. The F5 provider Nan created uses directly the F5 http API, because its better (and certainly easier) than emulating a human typing commands through ssh :) like I did for the cisco stuff. That unfortunately shows that there are lots of differences between network devices types/models. You'll certainly find that the assumptions I did for cisco switch might not map cleanly your switch models. Something I couldn't really do when implementing only cisco IOS was to find and extract the commonalities between various device classes (both in terms of types and providers). I'm definitely interested in helping you implement those new models. Feel free to ping me on irc (masterzen on #puppet and #puppet-dev) or here if you need my help :) (and of course I'll be available live during puppet conf to answer questions) -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
