Description of problem:
Currently, iSCSI must be configured via editing config files. This is an error
prone process and difficult for non-expert users. Making this confgiuration
available via the LVM GUI will ease this purden. Plus it mates well with the
other LVM configuration tasks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The iSCSI initiator in RHEL 4 will be different in RHEL 5. The user level tools
and configuration files may also differ requireing different backend work for
any UI tool. We should try and provide as much commonality as possible.
We also want to have CHAP and iSNS support in the configuration.
Devel ACK a simple interface for 4.5.
Fixed in 1.0.23-1.0
iSCSI configuration utility is activated by going to Tools->iSCSI Configuration
in s-c-lvm main window.
If iscsi-initiator-utils.rpm is not installed, an error message should pop-up.
Utility should rescan targets for new luns on startup, starting iscsid if not
already running (and only if initiator has been configured for some targets).
A window should appear, listing all luns (one per row), including its devpath,
target name, lun id, hostname, scsi id (scsi wwid), and whether lun is active or
not (read-only checkbox).
There is a Refresh button, which will rescan targets for newly exported LUNs.
There is also a “Add new target” button, which should prompt for hostname and
port number of target to add.
Submitting a hostname-port pair, which doesn't lead to iscsi-target server,
should result in an error.
After a valid iscsi target server is entered, new targets should show up in the
iSCSI utility window; iscsid might get started if not already running.
Main s-c-lvm window should reload after iSCSI utility has been dismissed. Newly
added LUNs should be displayed in “Uninitialized Entities”, although they could
end up in other categories if already under LVM control.
All partitions and PVs that sit on iSCSI targets should have “iSCSI Device:
True” entry in the properties pane (one on the right).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.