Comment # 5 on bug 975604 from Anton Samsonov

(In reply to Lee Duncan from comment #3)
> The lio-utils are not yet deprecated, although the targetcli interface
> is much easier to use for customers. Personally, I would like to see us
> to using targetcli instead of lio-utils in YaST, but we are currently
> evaluating replacing targetcli with targetcli-fb, which is the current
> "best" API, so no use changing YaST for now.

If you are looking forward to rewrite that module substantially, please,
consider adding an option for choosing where to get the configuration from:

1. live state of kernel module ("running config"), - the current behavior;
2. configuration files on disk ("startup config").

The first option is great and intuitive, but it leads to disastrous results in
case something went wrong and the configuration (or its part) was not
successfully loaded: the user is presented with the current state only, which
may be totally empty or missing some parts, and any attempt to apply the
changes leads to those once failed parts to be lost forever. That is where the
second options comes in, allowing the user to fix the problem and try again.

However, the second option might be as dangerous as the first one if used
blindly, because it will discard any temporary changes introduced manually or
by scripts. Therefore it may be practical to display the difference between
running config and startup config, if any, so the user could make the choice
concisely. Moreover, if that is feasible, it would be nice to have an option to
leave those differences intact, i. e. only apply the changes made to startup
config without removing any extra settings.