On 12 September 2011 21:53, Brice Figureau <[email protected]> wrote: > 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.
No doubt - although for Allied Telesis, I am also using telnet transport :) > 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). They map surpisingly well, as you'll probably see when I get around to putting it on github > 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) That's great, I'll definitely get in touch with you there (username gwmngilfen). This week has descended into firefighting, but next week is looking good for some more coding. Nan, with regards to running "RUBYLIB=foo puppet master", how does that map onto passenger? I assume I can put a SetEnv RUBYLIB /path/to/module in my apache configuration? I'll certainly be trying that, but since I'm writing this email anyway, I thought I'd ask. Thanks again for the support thus far :) Greg -- 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.
