I currently like how the existing system works as it leads users into separating each of their docker install’s config and data. But yes this is a little over the top for many and a little ping pong on the user interface.
I suggest that we leave the existing rock-ons-root config as it is as that is only a one off anyway. Only obvious addition is an auto option / button, ie:-
Currently we have the explanation header and the selection of the “Root Share”.
In the circumstance where there is only one pool (ie most less advanced installs) offer to create the minimum 5GB Share (it can always be expanded). Named for example “auto_rock_ons_root”.
If more than one user created pool exists then flag the auto option as "only available on single pool configurations, please select an existing Share or create one on your desired pool"
So to summarize the “Configure Rock-on Service” screen would have an “Auto create and configure” button that would create a “auto_rock_ons_root” share and set it in the existing “Root Share” selector once pressed. The button would be greyed out / disabled on multi pool installs and have the above explanation as to why. We can’t know which pool to make a rock-ons-root on so the user will have to do it. But if there was only one user created pool then we can auto make a minimum share for them on the spot. There might also be an opportunity here to sense an existing auto named pool and offer to use it if found. ie the Wizard notices an existing auto_rock_ons_root named share and states its existence and if the user would like to use it, we have to check for it anyway before creating it to making sure we don’t share name clash so we might as well offer up setting a new config to inherit a previous installs auto_rock_ons_root if found (not sure how difficult / feasible this would be though).
As for the individual Rock-on setup wizards we could offer a similar “Auto create and configure” button (big button with that title). Like wise it would in all instances just create a set of minimal shares appropriate for the particular Rock-on. I know this is a little tricky but a basic config size is pretty easy (eg 1GB) and a data size can just start at say 20G (or say 10% of total storage); again all can be resized on the fly anyway and we have nice config areas for all of that.
With this scenario we train the user on the “Auto create and configure” button in the initial Rock-ons configure screen and so when they come across it again they know what to expect; ie it will make and fill out all those storage / config / data share question things that have to be done some how. Given the button suggestion will essentially auto create shares and auto populate the existing config / data questions with those shares it is also clearer to the user what is happening, so they will know where all of these auto_whatever named shares come from when they visit the shares page.
I think this qualifies as fewer inputs as the button is a one click fix for creating and selecting the config & data shares that might be needed. There will however be more actual inputs shown though. Work around if this is not desired is an advanced tick box that shows the existing config / data selectors which might otherwise be hidden.
Of course in all of the above we are assuming a user created pool, if one is not found then just prompt with “no user created pool found / available, please make one here” with a link to jump them to the pools page. Problem is when people want to use the rockstor_rockstor pool (not idea). So we just add “skip to advanced mode” link which activates our tick box and lets users through even if they haven’t created a pool yet.