ZStack Cloud Platform
Single Server, Free Trial for One Year
-
Documentation&Tools
Comprehensive product documentation and tools
-
Support & Services
Upholding the value of Customer First and the mission of Serving Customer, ZStack is dedicated to providing secure and stable services for customers.
-
Training & Certification
To educate ZStack partners and interested individuals about cloud computing and to cultivate cloud computing talent.
-
Content
ZStack provides innovative cloud infrastructure for ten major industries
VMware-to-ZStack Case Collection
The report provides three major
solutions and customer case studies for transitioning from VMware to ZStack.
ZStack Cloud 4.8.10>ZStack Cloud Product Manuals>ZStack CLoud
CLI Command Manual>Settings>Chrony Servers
Chrony Servers
Overview
Time Management: Manages the Cloud system time and allows you to configure time servers for the Cloud. After you configure NTP time servers for the Cloud, the clock of the time servers is synced with all nodes of the Cloud.
Concepts
Time management involves the following concepts：
- Internal time server: Uses a management mode or host as an NTP time server of the Cloud system time so the other nodes of the Cloud may sync time with the time server.
- External time server: Uses a node that does not belong to the Cloud as an NTP time server, which directly syncs time with all nodes of the Cloud or syncs time with the Cloud nodes via the internal time server.
- Time sync: The process in which the time of a node on the Cloud is synced with a time server.
Fundamentals
The time sync of the nodes on the Cloud with a time server is achieved mainly via network time protocol (NTP) and related algorithms. The following lists the sync process:
- You configure an internal or external time server for time sync.
- The nodes on the Cloud connect to the time server to obtain its timestamp information.
- Based on the timestamp, the nodes on the Cloud calculate their time difference with the time server.
- Based on their respective time difference, the nodes on the Cloud alter their local time to achieve time sync.
- The nodes on the Cloud implement process 2 to 4 regularly for sustained time sync.
The Cloud supports the following three time protocol modes:
- Internal: Uses a management mode or host as an NTP time server of the Cloud system time so the other nodes of the Cloud may sync time with the time server. You can add up to 2 internal time servers for the Cloud.
- Internal and External: Uses a node that does not belong to the Cloud as an NTP time server and uses a management mode or host as an NTP time server of the Cloud system time. The external time server syncs time with the internal time server first and then the internal time server syncs time with the other nodes of the Cloud. You can add up to 2 internal time servers and 2 external time servers for the Cloud.
- External: Uses a node that does not belong to the Cloud as an NTP time server, which syncs time with all nodes of the Cloud. You can add up to 2 external time servers for the Cloud.
Benefits
Time management has the following benefits:
- Accurate: The time clock adjustment algorithm used ensures an accurate time sync.
- Automatic: The time sync mechanism is auto implemented regularly. Manual interference is not required.
- Reliable: You can configure multiple time servers to ensure the reliability and stability of the time sync mechanism.
- Intuitive: Time server configuration and its relationship with the Cloud time are displayed in a topology. In addition, the current Cloud time and the time zone are displayed.
Scenarios
Time management applies to the following scenarios:
- Network management: The logs collected from different network devices require accurate time records for efficient troubleshooting. The time sync mechanism provided can well satisfy this demand.
- Billing: Time management can ensure consistent and accurate time records for billing systems so that the billing info is correct.
- Collaboration: Time management can ensure unified time for multiple systems so that they can well collaborate with each other based on the preconfigured execution time sequence when handling a complex task.
Operations
CheckNetworkReachable
Check whether the network is reachable. For example,
CheckNetworkReachable targetHostnames=10.13.5.232Parameters
| Name | Description | Optional | Valid Value | Starting Version |
|---|---|---|---|---|
| sourceHostnames | Specified set of source ip addresses or domain names. | Yes | 4.7.21 | |
| targetHostnames | Specified set of target ip addresses or domain names. | 4.7.21 | ||
| userTags | The user tags. For more information, see CreateUserTag. | Yes | 4.7.21 | |
| systemTags | The system tags. For more information, see CreateSystemTag. | Yes | 4.7.21 |
Next Chapter: Management Node