(Difference between revisions)
| Line 7: | Line 7: | ||
=== Feture Description === | === Feture Description === | ||
The intent is to use the organization's NTP server to sync time on all the hosts in ovirt setup. | The intent is to use the organization's NTP server to sync time on all the hosts in ovirt setup. | ||
| + | The Info should be extracted from the user during the installation, and pupulated/configured on all the hosts in an ovirt system through bootstrap & registration. | ||
| Line 12: | Line 13: | ||
* Organizations will prefer using their own NTP server rather than install a new one for ovirt. | * Organizations will prefer using their own NTP server rather than install a new one for ovirt. | ||
* The NTP server should be configured only once (during ovirt installation), and populated to all hosts through bootstrap and registration. | * The NTP server should be configured only once (during ovirt installation), and populated to all hosts through bootstrap and registration. | ||
| − | * Changing the NTP server after installation in not supported - and will require | + | * Changing the NTP server after installation in not supported - and will require manual steps to sync it to all the hosts in the setup. |
| + | * The NTP server is accesible from all the hosts | ||
| Line 27: | Line 29: | ||
===== Engine ===== | ===== Engine ===== | ||
| − | * Need to utilize this new NTP config (if given) | + | * Need to utilize this new NTP config option (if given) during bootstrap |
| − | * Need to utilize this new NTP config (if given) | + | * Need to utilize this new NTP config option (if given) during registration/approval |
* Need to add support for the optional NTP server in vds_installer.py | * Need to add support for the optional NTP server in vds_installer.py | ||
===== vdsm:bootstrapping ===== | ===== vdsm:bootstrapping ===== | ||
| + | * vdsm-bootstrap - shoudl support configuring NTP on any host bootstrapped | ||
| + | * bootstrapping code now has to support ovirt-node as well | ||
| + | Q - should we skipp the NTP config if the NTP server is not accessible on bootstrap | ||
===== vdsm:registration ===== | ===== vdsm:registration ===== | ||
| + | * The registration code should support the optional NTP configuration | ||
| + | * since ovirt-node has already code for that - the registration should utilize it | ||
| Line 41: | Line 48: | ||
* engine - handle the vdsm NTP configuration reported by VDSM (save in DB + throw event log if misconfigured) | * engine - handle the vdsm NTP configuration reported by VDSM (save in DB + throw event log if misconfigured) | ||
* UI - display the reported NTP configureation | * UI - display the reported NTP configureation | ||
| + | * setup - develop a new ovirt-setup-plugin for NTP server - in case the user wants to install a new NTP server (on the ovirt-server host) | ||
=== Questions === | === Questions === | ||
* Should we support more than 1 NTP server ? | * Should we support more than 1 NTP server ? | ||
| − | * Should we expose this config through the ovirt-config utility ? | + | * Should we expose this config as a general config option through the ovirt-config utility ? |
| + | |||
| + | |||
| + | === Additional notes === | ||
| + | * When using remote DB - need to configure it's NTP as well. | ||
Revision as of 15:43, 30 June 2012
Contents |
Adding NTP Support
Feature necessity
KVM is very sensitive to time issues especially when migrating a VM between 2 hosts with a big time gap. In a large deployment we need to make sure that the time is synched on all the hosts in the setup.
Feture Description
The intent is to use the organization's NTP server to sync time on all the hosts in ovirt setup. The Info should be extracted from the user during the installation, and pupulated/configured on all the hosts in an ovirt system through bootstrap & registration.
Assumptions
- Organizations will prefer using their own NTP server rather than install a new one for ovirt.
- The NTP server should be configured only once (during ovirt installation), and populated to all hosts through bootstrap and registration.
- Changing the NTP server after installation in not supported - and will require manual steps to sync it to all the hosts in the setup.
- The NTP server is accesible from all the hosts
The feature building blocks
ovirt-setup
- Need to extract NTP server details from user during the installation
- The NTP config should be optional
- Need to update the ntp server in vdc_option table
- Need to configure the ovirt-server ntp to sync with the NTP server
DataBase
- Need to add the NTP server configuration to the vdc_options table
Engine
- Need to utilize this new NTP config option (if given) during bootstrap
- Need to utilize this new NTP config option (if given) during registration/approval
- Need to add support for the optional NTP server in vds_installer.py
vdsm:bootstrapping
- vdsm-bootstrap - shoudl support configuring NTP on any host bootstrapped
- bootstrapping code now has to support ovirt-node as well
Q - should we skipp the NTP config if the NTP server is not accessible on bootstrap
vdsm:registration
- The registration code should support the optional NTP configuration
- since ovirt-node has already code for that - the registration should utilize it
Optional additions to the feature
- vdsm - to report it's NTP configuration
- engine - handle the vdsm NTP configuration reported by VDSM (save in DB + throw event log if misconfigured)
- UI - display the reported NTP configureation
- setup - develop a new ovirt-setup-plugin for NTP server - in case the user wants to install a new NTP server (on the ovirt-server host)
Questions
- Should we support more than 1 NTP server ?
- Should we expose this config as a general config option through the ovirt-config utility ?
Additional notes
- When using remote DB - need to configure it's NTP as well.
