Bug 278554

Summary:	iscsi initiator support in storage
Product:	[openSUSE] openSUSE 10.3	Reporter:	Michal Zugec <mzugec>
Component:	YaST2	Assignee:	Thomas Fehr <fehr>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None
Version:	Alpha 5plus
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michal Zugec 2007-05-28 08:05:27 UTC

My suggestion is to put some button "iSCSI disk" to storage module.
iSCSI is separate module starts as "disk activation" when withiscsi parameter is passed into bootloader
But it would be nice to start it from here, because it logically belongs here

Comment 1 Thomas Fehr 2007-05-29 09:15:43 UTC

Ok, will add button named "iSCSI" if iscsi-client is installed.
Hoefully this will not confuse the 99% of users that do not know what iSCSI is.

Which is the name of the YCP client to start?

Comment 2 Michal Zugec 2007-05-29 10:54:48 UTC

It's "yast2 iscsi-client"

I red about some UI changes, so you can hide that button somewhere (expert)?
Btw - after finish that client call som "disk re-read" (I forget name of that option) - to show when new disk appears

Comment 3 Thomas Fehr 2007-05-29 11:03:19 UTC

If you are fine with it, I could hide the option under "Expert"-button on
lower right corner. 

There is a similar functionality for S390 disk activation hidden there also.
I can make YaST2 to re-read everyting after the return from iscsi-client. 
This is also done when returning from S390 disk activation.

Comment 4 Michal Zugec 2007-05-29 11:06:59 UTC

sounds good ;-)

Comment 5 Thomas Fehr 2007-06-18 10:53:26 UTC

Implemented the necessary changed in current SVN head.
Will be available with yast2-storage-2.15.16.

Michal, could you please test if the newly configured disks show up in
expert partitions. My test systems have no such controller so I cannot check
this myself.

Comment 6 Michal Zugec 2007-06-18 13:28:38 UTC

I have problem while compiling storage module:

make[4]: Entering directory `/home/mzugec/work/trunk/storage/storage/src/modules'
Y2DIR=../../../libstorage/src/.libs LD_LIBRARY_PATH=../../../libstorage/src/.libs /usr/bin/ycpc -c -M. -I. -q -I . -I include -M ../../../libstorage/bindings/ycp FileSystems.ycp
FileSystems.ycp:24  [Interpreter] No table associated to module 'LibStorage'
FileSystems.ycp:24  [Parser] Can't load module 'LibStorage'.
FileSystems.ycp:32  [Parser] Unknown namespace 'LibStorage'. Missing 'import'?
FileSystems.ycp:32  [Parser] syntax error, unexpected SCANNER_ERROR
FileSystems.ycp:32  [libycp] Unreachable code at the end of file
make[4]: *** [FileSystems.ybc] Error 1

or should I rather use package from factory?

Comment 7 Thomas Fehr 2007-06-18 13:42:23 UTC

I would assume factory does not yet contain yast2-storage-2.15.16.
I set up an mbuild job today that went though without a problem.
You could use /work/built/mbuild/Lagrange-fehr-33/ which contains RPMs of the
code I put to STABLE today. Or you could use /work/src/done/STABLE/yast2-storage/
and build an RPM yourself.