Hello Vladimir, from me -1.
We can discuss if enable fuelmenu=yes or not in grub, but I wouldn't get
rid of it. I've never heard complaints against fuelmenu from users, and
it's widely used for basic settings afterinstall.
If the users had to manually edit another configuration file, should
they remember to run a validator tool over it every time after editing
the file? Or do we add a futher layer that invokes $EDITOR and after
:wq, some validator performs a check...? IMO that's poor UX, and why
reimplement it, in fuelmenu there are already nice fixed choices and
check commands that restricts potential human mistakes.
F.
On 07/23/2015 04:23 AM, Vladimir Kozhukalov wrote:
Dear colleagues,
What do you think of getting rid of fuelmenu and substituting it with
thoroughly commented text file + some validation + vim? The major pro
of this is that text file is easier to extend and edit. Many people
prefer vim UX instead of wandering through the semi-graphical
interface. And it is not so hard to implement syntax and logic
checking for the text file.
Please give your opinions about this.
Vladimir Kozhukalov
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
