On Wed, 2012-10-10 at 15:29 -0400, Brian J. Murrell wrote: > On 12-10-10 03:12 PM, Andy Grover wrote: > > > > If it's a json file instead of a shell script, I assume you're using a > > -fb version of targetcli? > > Ahhh. yes, indeed. > > > Then you don't need lio-utils. You can restore > > the config in /etc/target/saveconfig.json with 'targetcli restoreconfig > > clear_existing=true', which is what the distro's init scripts should be > > doing for you, if the service is enabled. > > Right. I see that now. I didn't actually have the targetcli RPM > installed on my production systems which is why there was no > configuration being saved or restored. > > Ultimately, I'm not sure if targetcli is the right tool in our > environment or not. Still getting a feel for the lay of the land. It > might be that some lio_node commands to create an initial configuration > followed by the prescribed tcm_dump and running the resulting script on > each boot is the best way for us to go. > Using targetcli to create the initial configuration is really best way to go with modern downstream distribution code. targetcli is a bash-style shell for driving the configfs layout of target-core + fabric drivers that allows anyone to easily configure /sys/kernel/config/target/*. Along with rtslib, this allows our user-space to be "future-proofed" so that new target fabric drivers work out of the box without a hard requirement for a user-space code update in order to drive /sys/kernel/config/target/$NEW_TURBO_FABRIC/ 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/. It does not drive anything related to /sys/kernel/config/target/core/, or ../config/target/$OTHER_FABRICS.. 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. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html