An appropriate solution to the NTP issue (and other services that require internet access) would be:
1 - add checkbox for enable NTP in NTP tab
2 - check for default gateway and dns resolution.
3 - if true, enable NTP checkbox, if false, disable NTP and add a warning to the user that NTP won't be available for your cluster and may lead to problems with many services. Warning won't be a popup, but will just be text on NTP Tab. Also, the 3 NTP server fields get marked read-only
4 - Modify check function for NTP -> unchecked ntp box always passes and ignores any values and writes no NTP conf to astute.yaml
checked NTP box enforces exactly the same as it does in Fuel 4.0. If it's checked and server can't be reached, it's marked as unsaveable.
An appropriate solution to the NTP issue (and other services that require internet access) would be:
1 - add checkbox for enable NTP in NTP tab
2 - check for default gateway and dns resolution.
3 - if true, enable NTP checkbox, if false, disable NTP and add a warning to the user that NTP won't be available for your cluster and may lead to problems with many services. Warning won't be a popup, but will just be text on NTP Tab. Also, the 3 NTP server fields get marked read-only
4 - Modify check function for NTP -> unchecked ntp box always passes and ignores any values and writes no NTP conf to astute.yaml
checked NTP box enforces exactly the same as it does in Fuel 4.0. If it's checked and server can't be reached, it's marked as unsaveable.