I've been using Puppet to manage network interfaces on our machines. To do this I've got a class very similar to http://forge.puppetlabs.com/razorsedge/network . I'm encountering some annoyances with this method of handling it:
1) Every interface I have has to have a unique alias number. This means that whenever I want to add a new IP alias I have to grep through my entire tree and find an unused number. This seems... less then optimal. 2) If I'm changing an interface (say from normal to bonded networking) I have to go and switch the interface definitions for everything on that machine. This also makes it difficult to have the same module used on multiple machines (as their networking config needs to match exactly). 2a) This gets more annoying as some of our newer machines have network interfaces emX instead of ethX. This means that all the definitions need to be updated once again when we change hardware. Has anyone encountered this and come up with a decent solution? I should note that I'm using CentOS, all the modules I can find on forge appear to be doing very similar things. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/IPtvRTAwRWgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
