fuel-dev team mailing list archive

[Matthew Mosesohn <mmosesohn@xxxxxxxxxxxx>]

Hi Fuelers!

I was wondering if you guys had some input on this dilemma. If you deploy
Fuel master node and do the following steps, your astute.yaml config will
be wrong:
1 - Boot from ISO
2 - Modify network parameters inside isolinux prompt
3 - Install and enter Fuelmenu
4 - Exit without saving

The workflow I put in place to solve half this problem was to write
astute.yaml config via a "--save-only" option that runs if showmenu=no. But
if you enter Fuelmenu and then don't save, this doesn't get run. Should we
run --save-only every time? If we launch Fuelmenu and try to save
automatically as soon asit runs, it will try to run all checks and then
possibly error and give ugly warnings that ruin user experience.
The alternative is to convince the user to save changes and go back.

I vote for the latter option, personally, mostly because we removed all the
kernel parameter configuration information from our user guide over 6
months ago, so we shouldn't be trying to cover edge cases where you
modified an undocumented feature and then failed to save when you launched
the tool.

I really do need your feedback so we can decide if this is a priority to
fix, and also how to fix it.

Best Regards,
Matthew Mosesohn