Project

General

Profile

Actions

action #9782

closed

FCoE

Added by RBrownSUSE over 8 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
-
Start date:
2015-12-02
Due date:
% Done:

30%

Estimated time:
Difficulty:

Description

Priority for SLE12 SP2

Similar to iSCSI Issue #9482, FCoE should be capable of doing in openQA without additional hardware

Because FCoE offload adapters are all different, and we do not have a wide collection of cards, the advice from Hannes is to focus on testing software FCoE

This is similar to iSCSI on SLES, in that we should be able to test both FCoE Client AND FCoE Server

So this task would be similar to the iSCSI one

  1. Add any backend support needed to QEMU (http://www.espenbraastad.no/post/kvm-with-ipxe-in-rhel6/ implies this will be the same as required for iSCSI)
  2. Write tests for FCoE Server setup on SLES (Probably starting from an asset)
  3. write tests for installation over FCoE that use the FCoE Server

As FCoE is very similar to FC, there is no need to test FCoE against real hardware assuming FC will be


Checklist

  • SLE
Actions #1

Updated by RBrownSUSE over 8 years ago

  • Description updated (diff)

9482

Actions #2

Updated by RBrownSUSE over 8 years ago

  • Description updated (diff)
Actions #3

Updated by RBrownSUSE over 8 years ago

  • Target version changed from 156 to 162
Actions #4

Updated by RBrownSUSE over 8 years ago

  • Checklist item changed from to [ ] SLE
Actions #5

Updated by RBrownSUSE over 8 years ago

  • Assignee set to dzedro
Actions #6

Updated by RBrownSUSE about 8 years ago

  • Target version changed from 162 to Milestone 2
Actions #7

Updated by dzedro about 8 years ago

I have never seen FCoE before, no idea how it looks like when it works, but I'm sure it doesn't work on any hardware.

Maybe Espen Braastad could boot from a Fibre Channel SAN via FCoE, but virtio-net doesn't support FCoE even compiled from ipxe.org.
I compiled virtio-net.rom but in installation withfcoe=1 there is eth0 device not capable of FCoE or DCB and only retry detection button active
I could use compiled rom only by overwriting existing rom, qemu can't define custom network driver/rom, so I have no idea how would we use it in openQA.

Maybe I did something wrong, any ideas or help are welcome! ;)

Actions #8

Updated by RBrownSUSE about 8 years ago

For the FCoE target, I was assuming you'd use the same underlying tools you use with iSCSI - http://linux-iscsi.org/wiki/Fibre_Channel_over_Ethernet

for the initiator you'd need to use fcoe-utils, which I believe we have in SLE 12 ... docs are like here https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/fcoe-config.html

So really, it should be the same as the iSCSI tests you've already done, just more CLI, no YaST modules ;)

Actions #9

Updated by dzedro about 8 years ago

I'm pretty sure it's not so easy to just run FCoE over any ethernet card.

FCoE doesn't run over regular Ethernet though, it requires Data Centre Ethernet/Bridging - an evolution of Ethernet that is only current supported on a very limited number of, typically high-end, switches such as Cisco's Nexus range.
Source: http://serverfault.com/questions/424969/fcoe-on-any-ethernet-switch

FCoE most probably needs VLAN setup http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_fcoe_ops_appB.html

Need DCB feature most probably too, all network cards I tried didn't had DCB capability.

In qemu I can hook SAN/iSCSI device on boot, but that's all, no FCoE/DCB posibillity to do any setup, see http://paste.opensuse.org/07024e51

Actions #10

Updated by dzedro about 8 years ago

FCoE need more than just ethernet card, also some freaky switch with FCoE configuration.

yast2 fcoe-client -> Help -> Interfaces:
FCoE is possible if a VLAN interface is configured for FCoE on the switch.
The values for FCoE VLAN Interface in detail:
not available: Fibre Channel over Ethernet is not possible (must be enabled on the switch first).

Actions #11

Updated by RBrownSUSE about 8 years ago

is openvswitch an option here? we have openvswitch on openQA now, creating it's own VLANs...

Actions #12

Updated by dzedro about 8 years ago

Richard below is approx. 5 years old post, now I know why I didn't hear/see/use FCoE before :P
http://www.networkworld.com/article/2220631/cisco-subnet/why-fcoe-is-dead--but-not-buried-yet.html

Actions #14

Updated by RBrownSUSE about 8 years ago

  • Status changed from New to In Progress
  • Priority changed from High to Normal
  • % Done changed from 0 to 30

Marking as in progress, but blocked

Adjusting Prio accordingly

Actions #15

Updated by maritawerner over 7 years ago

  • Target version deleted (Milestone 2)
Actions #16

Updated by maritawerner over 7 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from dzedro to RBrownSUSE

Ricahrd, any recommandations here? Shoudl Jozef try again or should we skip that?

Actions #17

Updated by RBrownSUSE about 7 years ago

  • Assignee changed from RBrownSUSE to maritawerner

We should test either FCOE or FC, we need to have coverage of one, not necessarily both

I don't have a preference as to which - whichever is easier? Both need hardware it seems

Actions #18

Updated by maritawerner about 7 years ago

  • Assignee changed from maritawerner to xgonzo

Reassigning to Harald. I asked him already about HW plans for FY 2018. I do not have any update here.

Actions #19

Updated by maritawerner about 7 years ago

  • Assignee changed from xgonzo to maritawerner

Reassign to myself. Will follow-up wiht Olaf.

Actions #21

Updated by maritawerner almost 7 years ago

  • Status changed from Feedback to Resolved

Discussed with Olaf. QA does not need to test here anything. There will be no investment in HW.

Actions

Also available in: Atom PDF