Is there a migration/upgrade strategy to move the targetcli/lio-utils/.py "configuration" to the targetcl-fb/rtslib-fb/json format?
(apart from reading the *.py configuration and manually creating the json files)
From what I grasp, at least part could be read into configfs with the old configuration and could be extracted and saved to json from the new python code.
This possibly would work when having lio-utils installed to read/start the old configuration and having targetclif-fb/rtslib-fb installed (or available) without interfering with the running setup.
Yes, while LIO is running, all configuration is available via configfs. Loading configuration with lio-utils then saving configuration with targetcli (or targetctl) to .json should work.
I am basically forwarding this request from today (2014-03-11) from Arch Linux:
https://aur.archlinux.org/packages/targetcli-fb/
Is there a migration/upgrade strategy to move the targetcli/lio-utils/.py "configuration" to the targetcl-fb/rtslib-fb/json format?
(apart from reading the *.py configuration and manually creating the json files)
From what I grasp, at least part could be read into configfs with the old configuration and could be extracted and saved to json from the new python code.
This possibly would work when having lio-utils installed to read/start the old configuration and having targetclif-fb/rtslib-fb installed (or available) without interfering with the running setup.