On 12-10-10 04:14 PM, Nicholas A. Bellinger wrote: > > Using targetcli to create the initial configuration is really best way > to go with modern downstream distribution code. For an interactive experience, I'd agree. > lio_node is an iscsi-target fabric specific CLI tool (part of lio-utils) > that is the legacy CLI method of driving configfs group layout > of /sys/kernel/config/target/iscsi/. Which is my only need, currently. But as you say, given that lio_node is CLI, it makes it easy to automatically shell script up a configuration based on devices found on a node, etc. without requiring a user to drive the interface. I don't know if targetcli really has any way to drive it from a shell script like that. > As Andy mentioned, Fedora uses JSON for persistent configuration with > targetcli+rtslib, so you'll want to use the official user-space > targetcli package that RHAT ships for best results in your case. Except that RHAT's implementation does not include the iscsi spec so it can't configure iscsi without one manually dropping the spec in. Not a biggie, just a note to mention that RHAT doesn't really officially support configuring iscsi with it. But then again, they don't ship and support the target driver either -- at the EL6 level at least. Cheers, b.
Attachment:
signature.asc
Description: OpenPGP digital signature
