Hi all, I'm discussing the following bug and code review for a wider audience: https://bugs.launchpad.net/fuel/+bug/1263934 https://review.openstack.org/#/c/68670/
I value appreciate your feedback and suggestions for how to improve the user experience. In the first iteration of Fuel Menu, there was no NTP, but just DNS settings. A user can set an upstream DNS server that fails to connect in Fuel Menu, but if there are problems, it will show a warning to the user when trying to save (but still saves). If you make the DNS server empty, it will also warn with a slightly more friendly warning. With NTP, in this patch I've added an "Enable NTP" option. Before, you had to remove all 3 server entries in order to suppress the error that blocks saving. Displaying multiple sequential warnings in Fuel Menu isn't very appealing to users, so I opted for one automatic decision to be made: disable NTP automatically if there is no gateway. It's easy to detect, and it's very unlikely to be able to reach an NTP server without a gateway. Therefore, it should just be disabled by default. That having been said, this means we're defaulting Fuel install to not use a 3rd party NTP source and not pushing our users to set up an Internet connection for the Fuel node. What are your thoughts? How else should this be architected? Best Regards, Matthew Mosesohn -- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
