Bug 1266157 - Test FCOE storages domains
Summary: Test FCOE storages domains
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.1
: 3.6.1
Assignee: Aharon Canan
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks: RHEV_FCOE 1334745 1334748
TreeView+ depends on / blocked
 
Reported: 2015-09-24 15:54 UTC by Yaniv Lavi
Modified: 2016-05-10 12:46 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: RHEV_FCOE
Environment:
Last Closed: 2016-04-20 01:11:49 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yaniv Lavi 2015-09-24 15:54:34 UTC
Test FCoE for gaps\issues.

Comment 1 Fabian Deutsch 2015-10-08 10:27:16 UTC
This also needs to be tested on RHEV-H

Comment 3 Elad 2015-12-03 16:31:24 UTC
Tested storage basic sanity using a single host connected to storage server by FCoE. Used a regular FC domain(s) based on the LUNs exposed by FCoE.
The following flows tested and passed:

- DC initialization (domain creation, attachment and activation) (2 domains)
• VM creation with OS rhel7.1, with 2 disks attached (thin, prea)
• VM deletion with pre and thin disks
• Snapshot creation (live)
• Snapshot preview
• Snapshot undo
• Snapshot commit
• Clone from snapshot
• Live snapshot merge
• Cold snapshot merge
• Hotplug disk
• lsm (thin and pre)
• cold move
• Template creation 
• Template deletion
• create vm from temp (thin and cloned)
• vm export 
• template export
• vm import (while source image exists and while not)
• template import
• master domain failover (maintenance and block)

Using:
RHEL7.2
vdsm-4.17.11-0.el7ev.noarch
libvirt-daemon-1.2.17-13.el7.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.4.x86_64
sanlock-3.2.4-1.el7.x86_64
fcoe-utils-1.0.30-3.git91c0c8c.el7.x86_64
kernel - 3.10.0-327.el7.x86_64
rhevm-3.6.1-0.2.el6.noarch

Comment 4 Fred Rolland 2015-12-06 12:15:19 UTC
Elad, can you please also check:

- Add a new LUN to existing Storage domain ( discovery of new device).
- Resize a LUN that is part of an existing storage domain.


Note You need to log in before you can comment on or make changes to this bug.