|
Size: 1393
Comment:
|
Size: 1386
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| == Servers == | == Nodus == |
| Line 9: | Line 9: |
| * fb1 runs the central ntp server used by martian. This is run through ntp daemon with configuration file present in {{{/etc/ntp.conf}}} | == FB1 and FE subnetwork == This was successfully implemented by Jamie. See elog [[https://nodus.ligo.caltech.edu:8081/40m/16302 | 40m/16302]] for complete details. |
| Line 11: | Line 12: |
| * fb1 uses nodus and caltech ntp server (131.215.239.14 or ntp-02.caltech.edu) | === Server === |
| Line 13: | Line 14: |
| * All FE computers use fb1 and nodus as the ntpservers and run ntp client using ntp daemon service. | * fb1 runs the ntp server used by FE computers. This is run through ntp with configuration file present in {{{/etc/ntp.conf}}} |
| Line 15: | Line 16: |
| * The configuration files for FE ntp service is present in on fb1 {{{/diskless/root.jessie/etc/ntp.conf}}} | * fb1 uses 4 servers from debian.pool.ntp.org as ntp servers. |
| Line 17: | Line 18: |
| * To change anything in FE computers, one needs to chroot into the root.jessie chroot jail which is exported to the FEs as their os. | === Clients === * All FE computers use fb1 at the ntpservers. * The configuration files for FE ntp service is present in on fb1 {{{/diskless/root/etc/systemd/timesyncd.conf}}} * To change anything in FE computers, one needs to chroot into the root chroot jail which is exported to the FEs as their os. |
| Line 20: | Line 26: |
| chroot /diskless/root.jessie /bin/bash | sudo chroot /diskless/root.jessie /bin/bash |
| Line 23: | Line 29: |
| * This will take you to terminal in debian os which is exported to FEs. You can use apt-get to install anything here. | * This will take you to the terminal in debian os which is exported to FEs. You can use apt-get to install anything here. |
| Line 25: | Line 31: |
| * Logging into FEs themselves, one can not edit or add any file as the whole filesystem is read-only and imported from fb1. But one can check the status of ntp service by: | * Logging into FEs themselves, one can not edit or add any file as the whole filesystem is read-only and imported from fb1. But one can check the status of timesyncd service and ntp synchronization status by: |
| Line 27: | Line 33: |
| sudo systemctl status ntp }}} and {{{ ntpd -p |
sudo systemctl status systemd-timesyncd |
| Line 34: | Line 36: |
| ntpstat | timedatectl |
| Line 36: | Line 38: |
| * Relevant elog post threads: [[https://nodus.ligo.caltech.edu:8081/40m/16292 |40m/16292]] and [[https://nodus.ligo.caltech.edu:8081/40m/16286 | 40m/16286]]. |
NTP Synchronization
Nodus
* Nodus runs an NTP server using chronyd. The configuration files are present at: /etc/chronyd.conf
* Nodus uses 4 servers from rhel.pool.ntp.org as ntp servers.
FB1 and FE subnetwork
This was successfully implemented by Jamie. See elog 40m/16302 for complete details.
Server
* fb1 runs the ntp server used by FE computers. This is run through ntp with configuration file present in /etc/ntp.conf
* fb1 uses 4 servers from debian.pool.ntp.org as ntp servers.
Clients
* All FE computers use fb1 at the ntpservers. * The configuration files for FE ntp service is present in on fb1 /diskless/root/etc/systemd/timesyncd.conf
* To change anything in FE computers, one needs to chroot into the root chroot jail which is exported to the FEs as their os.
sudo chroot /diskless/root.jessie /bin/bash
* This will take you to the terminal in debian os which is exported to FEs. You can use apt-get to install anything here.
* Logging into FEs themselves, one can not edit or add any file as the whole filesystem is read-only and imported from fb1. But one can check the status of timesyncd service and ntp synchronization status by:
sudo systemctl status systemd-timesyncd
timedatectl