> I agree that Facter could do a better job merging the secondary "interface"
> into the primary one here. It shares the networking fact code with a few
> other platforms (mainly OSX and the BSDs) and it currently doesn't do any
> specific logic for Linux to merge bonded interfaces together.
>
I don't thinks that specific to bonded interfaces, a plain eth0 would work the
same way.
> We could potentially address this in a backwards-compatible way by adding a
> "secondary" field to a interface entry that is an array of the remaining
> secondary addresses. Thus, the "bond0:1" interface would be effectively
> moved to "networking.interfaces.bond0.secondary.0". Would that make sense to
> do?
That's sound good. And perhaps add a primary: "..." to secondaries too.
So the structured fact will look like :
networking => {
....
interfaces => {
eth0 => {
secondaries => [ "eth0:1" ]
},
eth0:1 => {
primary => "eth0"
},
},
}
So it would be easy to filter interfaces in template or other places
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/DE6C8BA7-3685-42A0-BFAA-E4E82E35B557%40orange.fr.
For more options, visit https://groups.google.com/d/optout.
