Hi, While analyzing a bug report, I just stumbled over a weirdness in how the network barclamp (pebbles) enumerates network interfaces of different speeds internally. Assuming you have a node with two 1GBit and one 10Gbit interface. No custom ordering is defined in the interface map and the NICs are detected as: eth0 -> first 1GBit, eth1 -> 10Gbit and eth2-> second 1GBit.
Internally (in Barclamp::Inventory.build_node_map in barclamp_lib.rb) crowbar will map these interfaces to the following internal names: eth0: 1g1, 100m1, 10m2 eth1: 10g1, 1g2, 100m2, 10m2 eth2: 1g3, 100m3, 10m3 That means: 1. every NIC will get several (internal) names, one for each speed it supports 2. the counter in the interface name is per supported speed. I.e. internally in crowbar eth1 is regarded as the first 10Gig NIC and the 2nd 1Gig NIC. This might sound logically in the first place but can have interesting effects for conduit_maps. E.g. if I want do use the second 1 GBit NIC for the the intf1 conduit I would have to specify "1g3" in the conduit map is that really the desired behavior? Or is this a bug? Is this documented somewhere? -- Ralf _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
