disk-detect/s390-dasd/s390-zfcp: Restructure installer and put DASD and FCP configuration into disk detection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hw-detect (Debian) |
Fix Released
|
Unknown
|
|||
hw-detect (Ubuntu) |
Fix Released
|
Undecided
|
Dimitri John Ledkov | ||
s390-dasd (Debian) |
Fix Released
|
Unknown
|
|||
s390-dasd (Ubuntu) |
Fix Released
|
Undecided
|
Dimitri John Ledkov | ||
s390-zfcp (Debian) |
Fix Released
|
Unknown
|
|||
s390-zfcp (Ubuntu) |
Fix Released
|
Undecided
|
Dimitri John Ledkov |
Bug Description
== Comment: #1 - Hendrik Brueckner <email address hidden> - 2016-03-18 09:23:45 ==
On Linux on z Systems, there are two major disk storage environments,
the direct-attached storage disk (DASD) and SCSI over Fibre-Channel.
There are the s390-dasd and s390-zfcp d-i modules to configure and
enable DASDs and FCP devices. Note that on s390x, disks are not
available by default to Linux and must be enabled in advance.
The s390-dasd and s390-zfcp both provide the harddrive-detection
dependency and, thus, each could fulfill the dependency to silenty
ignore the other. That behavior does not allow to mix DASDs and
SCSI disk on single installation (except you call both manually,
for example, in the expert mode).
To improve and provide a "guided" flow, I have split the harddrive
detection dependency for s390-dasd and s390-zfcp as follows:
- s390-dasd provides harddrive-
- s390-zfcp provides harddrive-
disk-detect depends on
-> harddrive-
-> harddrive-
and continues to provide the harddrive-
With this split, the guided installation will install disk-detect to
solve the harddrive-detection dependency. In turn, disk-detect will
then rely on the s390-dasd and s390-zfcp d-i modules to provide DASD
and FC-attached SCSI disks. If both modules fail, the user perceives
the default disk-detect behavior, for example, users might configure
iSCSI.
The other nice benefit of this dependency split is the seamlessly
enablement of multipath with disk-detect (through preseeding).
For s390, multipathing should be always considered when SCSI is used.
I probably will extend the s390-zfcp module to set disk-detect's
multipath debconf variable for usability.
There are already Debian bug reports with patches to provide this solution:
disk-detect: https:/
s390-dasd: https:/
s390-zfcp: https:/
Related branches
tags: | added: architecture-s39064 bugnameltc-139323 severity-high targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
Changed in ubuntu: | |
assignee: | Skipper Bug Screeners (skipper-screen-team) → Dimitri John Ledkov (xnox) |
affects: | ubuntu → hw-detect (Ubuntu) |
Changed in s390-dasd (Ubuntu): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in s390-zfcp (Ubuntu): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in hw-detect (Debian): | |
status: | Unknown → New |
Changed in s390-dasd (Debian): | |
status: | Unknown → New |
Changed in s390-zfcp (Debian): | |
status: | Unknown → New |
tags: | added: block-proposed |
Changed in hw-detect (Ubuntu): | |
status: | New → Invalid |
Changed in s390-dasd (Ubuntu): | |
status: | New → Invalid |
Changed in s390-zfcp (Ubuntu): | |
status: | New → Fix Committed |
tags: | removed: block-proposed |
Changed in hw-detect (Debian): | |
status: | New → Fix Released |
Changed in s390-dasd (Debian): | |
status: | New → Fix Released |
Changed in s390-zfcp (Debian): | |
status: | New → Fix Released |
Changed in hw-detect (Ubuntu): | |
status: | Invalid → Confirmed |
Changed in s390-dasd (Ubuntu): | |
status: | Invalid → Confirmed |
Changed in s390-zfcp (Ubuntu): | |
status: | Fix Released → Confirmed |
tags: | removed: block-proposed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1559193/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]