Hi,
On 07/03/2009 11:30 PM, Bill Nottingham wrote:
Hans de Goede (hdegoede@xxxxxxxxxx) said:
Write out NM_CONTROLLED=no for NICs used for FCoE, note that unlike with
iSCSI we do not blindly write out NM_CONTROLLED=no for all NICs, but just
for the NIC which is used for FCoE.
The iSCSI behaviour is undesirable, but the whole writing of NM_CONTROLLED=no
for iSCSI will go away as soon as NetworkManager is fixed to not down
devices when it takes over control, which should be fixed soon.
If that's fixed soon, shouldn't we not need the hack for FCoE either?
No, because as I've explained before (and I really wish people would start
understanding this) FcOE is not a network based storage protocol.
FcOE does raw, direct encapsulation of FC frames (which is a storage protocol
like sata) in ethernet frames (The MTU even changes to 2300 to make things fit),
so in essence the NIC becomes a storage controller. So NetworkManager should not
try to touch the NIC in any way and this is not a hack.
FCoE basically is: use the NIC as an FC storage controller as its cheaper then
a real one.
Regards,
Hans
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
