network_config should support vlan interfaces about puppet-network HOT 3 OPEN

Here's some thoughts on a possible [simple] implementation of vlan support into network_config.

• add a new boolean parameter to the network_config type called vlan; an alternative possibility would be add some sort of parameter to declare the type of the interface. Eg. raw|bond|bridge|vlan
• the debian & redhat providers would both need to be modified to parse the namevar and or the device name into a raw interface name part and a vlan ID part, if the vlan parameter is true.
• in the redhat provider the "vlanness" of an interface could be be detected by either parsing the filename directly or the device variable in the per interface configuration. It seems that perhaps parsing the device variable would be slightly simpler, only requiring a small hook in parse_file instead of having to build two separate lists of files. If it was desired to validate the format of the files being parsed, it might be easier to do it the other way around and track the name of the file that was parsed to valid the device var in general. No modification of format_file/etc. should be necessary if we are requiring the vlan param on the type to be set.
• in the debian provider the Instance.initialize method looks like a good place to parse the name into raw & vlan tagged components. format_file would need to be modified to inject the vlan-raw-device line.

Thoughts/comments/criticisms?

from puppet-network.

Off issue discussed with @adrienthebo has resulted in the conclusion that it makes more sense to add a parameter to set the type of interface that's being configured. eg, vlan|bridge|bond as these states seem to be mutually exclusive, at least under the linux kernel.

from puppet-network.

Hello:

What's the status of this issue? I'm just pinging old issues. Is this possibly related to #98?

from puppet-network.