Issue #3153 has been updated by James Turnbull.
So my first thoughts are the old code is probably good as a "don't do this the same way again" guide. I recommend a start from scratch with a new type. I think the first issue is to data model something that works for a variety of platforms, something like: interface name (namevar) interface type (loopback, normal, alias ...?) description ensure (onboot) boot protocol (DHCP/etc) interface number IP address netmask broadcast And then flesh out for Solaris and others. Providers are sufficiently unique that it could be quite a complex exercise. ---------------------------------------- Feature #3153: Network interface type http://projects.reductivelabs.com/issues/3153 Author: Michael DeHaan Status: Accepted Priority: Normal Assigned to: Category: network Target version: Affected version: 0.25.4 Keywords: networking types Branch: Talking with user, would be nice to be able to model network interface config in Puppet to faciliate easy changes -- OS installers particularly Anaconda do not allow all options. Taking a look at interface modelling in Cobbler will show some of the things we'd like to represent -- including bonding and arbitrarily named interfaces, as well as some examples of kludgy templates for configuring those on RHEL/Fedora. Will take additional work to make something Debian/Ubuntu other friendly. This seems to also require the need to express arbitrary datastructures in external nodes. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
