action #9782
closed
Added by RBrownSUSE over 8 years ago.
Updated almost 7 years ago.
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
- 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)
- Write tests for FCoE Server setup on SLES (Probably starting from an asset)
- 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
- Description updated (diff)
- Description updated (diff)
- Target version changed from 156 to 162
- Checklist item changed from to [ ] SLE
- Target version changed from 162 to Milestone 2
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! ;)
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).
is openvswitch an option here? we have openvswitch on openQA now, creating it's own VLANs...
- 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
- Target version deleted (
Milestone 2)
- 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?
- 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
- 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.
- Assignee changed from xgonzo to maritawerner
Reassign to myself. Will follow-up wiht Olaf.
- Status changed from Feedback to Resolved
Discussed with Olaf. QA does not need to test here anything. There will be no investment in HW.
Also available in: Atom
PDF