Introduction
nspOS resource base
The nspOS, which is the common resource base of an NSP system, is deployed in an NSP cluster of one or more VMs in the Kubernetes container environment. A disaster-recovery, or DR, deployment, consists of matching NSP clusters in geographically separate data centers. A DR deployment is also called a geo-redundant deployment.
Some NSP components are not deployed in the NSP cluster, as described in Part III: NSP component deployment.
Time synchronization
CAUTION Service Degradation |
Some components, for example, members of an etcd cluster, fail to trust data integrity in the presence of a time difference. Failing to closely synchronize the system clocks among components complicates troubleshooting and may cause a service outage.
Ensure that you use only the time service described in this section to synchronize the NSP components.
The system clocks of the NSP components must always be closely synchronized. The RHEL chronyd service is the mandatory time-synchronization mechanism that you must engage on each NSP component during deployment.
Note: Only one time-synchronization mechanism can be active in an NSP system. Before you enable chronyd on an NSP component, you must ensure that no other time-synchronization mechanism, for example, the VMware Tools synchronization utility, is enabled.