On Thu, Nov 1, 2012 at 12:12 PM, fatmcgav <[email protected]> wrote: > in the hunt to find a mechanism to manage our new NetApp filer configuration > using puppet, I've stumbled across the 'Puppet Network Devices' > functionality introduced in 2. 7. The idea looks perfect in principle, > however it looks like no-ones implemented support for NetApp filers as > yet...
I'm not aware of any yet. Excited to hear someone wants to start tackling this for NetApp. > So before I embark on writing the a module to support the NetApp, I thought > I'd ask the people more versed in puppet than myself if there are any known > issues, challenges gotchas, tips or tricks etc to guide me on my way... You should be comfortable with writing Puppet types and providers, otherwise trying to write a network resource as a first project might be a bit challenging. The slides from PuppetConf has some notes (start from page 39). http://www.slideshare.net/nanliu1 It boils down to: * implement a transport to talk with netapp api. * the resource type should specify apply_to_device (disable it to test with non 'puppet device' command) * start with puppet resource first (either hardcode or pass connectivity info via facts). If you run into specific issues just ask this list. Thanks, Nan -- 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.
