On Thu, Oct 25, 2012 at 6:05 PM, Brian Rak <d...@devicenull.org> wrote:
> 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. > Is this with respect to having to have eth0:0/eth0:1 for each IP address you want to assign to a single interface? I have my own network_config type at http://forge.puppetlabs.com/adrien/network that might be able to ease some of those problems, depending on what your exact problem is. > 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). > Is this with respect to bonding eth0 and eth1 and having to reassign the IP addresses? > 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. > Yeah, this is an annoyance. The solution for this will probably mean adding udev rules to sort this out so that eth0 will always be associated with a certain device regardless of how the distro wants to name things. > 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. If you are having trouble managing what interfaces get what configs on a wide base, have you considered storing the data in hiera and then pulling that out when generating interfaces? I've done that with our linode boxes; I drop all of the configuration for private addresses into hiera and if a machine has an address available, it assigns itself that from the hiera lookup. > -- > 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. > -- Adrien Thebo | Puppet Labs Operations -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
