[sles-beta] YAST using "wrong" commands to configure ISCSI targets

[Darren Thompson]

Team

I will include exerts of a conversation had about some bugs in the LIO
(ISCSI Target) configuration.

Is it sufficient to note that YAST is using the wrong tools in the existing
Bug notes or should I raise a new SR?

History:

https://bugzilla.novell.com/show_bug.cgi?id=881553#c26

..."> lio-utils are deprecated, being replaced by targetcli. => Why are
depreciated

> tools in the SLES12 codebase, please replace with "working" and update
> documentation accordingly.

Perhaps you do not understand. Upstream development of these public-domain
tools no longer occurs.

The documentation that comes with the package, in
/usr/share/doc/packages/lio-utils/lio-utils.HOWTO, says (among other things):

Warning: Use targetcli instead.
lio-utils are deprecated and have been superseded by targetcli.

Seems up to date to me.
>
> These utilities are brittle at best, as you have discovered. If you get your
> configuration correct, it works just fine (sans bugs).=> The "stop" option
> f**ks with the working configuration and should not. That is bad design.
> Why are "brittle" tools in the SLES12 codebase, please replace with "working"
> and update documentation accordingly.

I did not add these tools to sles12, so I cannot answer that question.

The updated tools _are_ present and working in sles 12. At least they will be
working once IBS approves my update requests.
>
> ISCSI can be mission critical, it certainly is the core to one of my clusters.
> "Brittle" would be unacceptable in a production system and certainly not in an
> "enterprise"/Supported Linux Offering which we could be using to offering SLA
> based support contracts to our clients.

Then I would suggest you use targetcli. Or you can continue to use lio-utils,
which seem to work once configured correctly. We will continue to support them
for SLE 12, but enhancements are unlikely. This is simply a fact of the public
software universe: when upstream development ends, you have to move to newer
software."


....


https://bugzilla.novell.com/show_bug.cgi?id=881553#c27


"Then I would suggest you use targetcli. => I did not

choose which tool was used. I used the GUI in YAST to create the target
configuration. If YAST is using the wrong tools, then YAST needs to be changed
to use the correct tools."


"


-- 

Darren Thompson

Professional Services Engineer / Consultant

 *[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au <steve at akurit.com.au>
Web: www.akurit.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140701/98c5ffe5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140701/98c5ffe5/attachment.jpg>