NTP Settings XOA?
-
NTP is already configured and enabled by default in XOA.
But maybe it can't reach NTP servers, do a
sudo ntpq -pto get details. Could be also your own computer/browser time that is off. -
@olivierlambert @darkbeldin That's what I tried to say: NTP ist blocked here by firewall, what I'm missing is a GUI option to set (a) manual NTP server(s) - like it's possible via xsconsole for XCP-ng.
-
@cg It's not possible directly throught the GUI because NTP config for XO is already done and should not really be changed.
So you have to do it in the conf file. -
@darkbeldin said in NTP Settings XOA?:
@cg It's not possible directly throught the GUI because NTP config for XO is already done and should not really be changed.
So you have to do it in the conf file.The assumption is that XOA has internet access. But on most company networks that isn't possible, or is only possible through a proxy.
XO/XOA does have an option for proxy, so why not for NTP?
Ultimately I think most config options should have a web based front-end.
-
This is a "system" operation, we tend to keep this kind of this "split" from XO itself (easier for our Open Source XO users to install it anywhere they like, without too many deps to the operating system where XO is running).
However, if you want assistance to set that in XOA, we'll be happy to help via a support ticket
-
@olivierlambert said in NTP Settings XOA?:
This is a "system" operation, we tend to keep this kind of this "split" from XO itself (easier for our Open Source XO users to install it anywhere they like, without too many deps to the operating system where XO is running).
Alright. I can understand this, and it isn't hard to fix manually. Is this documented? I could not find
ntpmentioned in the docs at https://xen-orchestra.com/docs/ -
@s-pam Probably one of us has to write a quick "how to edit ntp.conf". Not super complex, just a bit of time.
And of course: I wished it would be in GUI and doesn't need extra console action.
Finally: I think all usual debian packages (e.g.) use the same ntp file, so one could easily read/write that file - no matter if it's XOA or a "custom XO". -
@darkbeldin the problem is "already done" for XOA: It's preset by you, which means I had no chance to configure it before.
Blocked traffic should be a more common thing in 'better' company networks. -
To be fair, since we started XOA, I don't remember about any requests about this. I assume that people with a network that's not open for outbound NTP requests are in general also able to modify this without asking us. That might explain why it's a pretty uncommon request
Also, if you don't know how to do this, you can ask us via our support system, that's exactly why we are here
edit: to be clear, I'm not "refusing" anything. It's just that adding this feature is not ultra-trivial in XO since we don't have any precedent (XO modifying the system). So it might take time/resources. Obviously, contributions are welcome, as always!
-
@olivierlambert if the solution is to SSH in and fix it by hand, it's not a big deal to me. I would just see the product more 'round' if GUI would handle things like setting system IP as well as NTP servers.
(As I can't see the XOA System -> IPs menu withoud paid license: What's hidden there? Do you configure XOA IP there? How you do it without editing /etc/network/interfaces?) -
This section has nothing to do with XOA IP address, but useful to restrict some VMs to some IP address. I agree it's unclear. But as I said, for now, there's 0 GUI to configure the system per se.
That's why I said it could be an addition sure, but there's nothing yet, so adding it will take some time or efforts, and it's not a priority as we speak (our backlog is already pretty big). But again, as an Open Source project, we are welcoming contributions!
