#!/bin/bash# Install chrony as neededif!command-vchronyc&>/dev/null;then# Detect the package manager and install chronyifcommand-vapt&>/dev/null;then# Debian, Ubuntu, and derivativesecho"Detected apt. Installing chrony..."apt-getupdateapt-getinstall-ychronyelifcommand-vdnf&>/dev/null;then# Fedora, RHEL 8+, CentOS 8+echo"Detected dnf. Installing chrony..."dnfinstall-ychronyelifcommand-vyum&>/dev/null;then# RHEL 7, CentOS 7echo"Detected yum. Installing chrony..."yuminstall-ychronyelifcommand-vzypper&>/dev/null;then# openSUSE, SLESecho"Detected zypper. Installing chrony..."zypperinstall-ychronyelseecho"Please install chrony manually."exit1fifi# Different distros place chrony config in# different locations, detect this.if[-f"/etc/chrony/chrony.conf"];thenCHRONY_CONF="/etc/chrony/chrony.conf"elseCHRONY_CONF="/etc/chrony.conf"fi# Load PTP-KVM clock for high-accuracy clock synchronization# PTP-KVM allows the VM to read a cross time-stamp of a platform# provided clock and the VM CPU Clock (CycleCounter), providing# resiliency from network and virtualization variability when# synchronizing the realtime/wall clock/sbin/modprobeptp_kvmecho"ptp_kvm">/etc/modules-load.d/ptp_kvm.conf# NTP servers might indicate the wrong time due to chrony# greatly reducing the polling frequency, resulting in# overall negative impact to the clock synchronization# achieved, especially after live migration events.## We disable NTP servers to prevent these issues.## Customers interested in monitoring the clock accuracy compared to NTP sources# should run a second instance of chrony in a no-change mode to do so.# Disable NTP servers:sed-i'/^server /d'$CHRONY_CONFsed-i'/^pool /d'$CHRONY_CONFsed-i'/^include /d'$CHRONY_CONF#Disable DHCP based NTP config:sed-i's/^NETCONFIG_NTP_POLICY="auto"/NETCONFIG_NTP_POLICY=""/'/etc/sysconfig/network/configtruncate-s0/var/run/netconfig/chrony.serversechoPEERNTP=no|sudotee-a/etc/sysconfig/networkserviceNetworkManagerrestartsystemctldisablesystemd-timesyncd.servicetimedatectlset-ntpfalse# Configure PTP-KVM based HW refclock, with leap second smearing# Google's clocks are doing leap second smearing, and therefor chrony shouldn't attempt to adjust# the time received from PTP-KVM to adjust for leap seconds.sed"s/^leapsectz/#leapsectz/"-i$CHRONY_CONFecho"refclock PHC /dev/ptp_kvm poll -1">>$CHRONY_CONF# For extra debugging logging, uncomment the following line#echo "log measurements statistics tracking" >> $CHRONY_CONF# Enable chrony's clock accuracy tracking log,# for monitoring and auditing.echo"log tracking">>$CHRONY_CONF# Restart chrony (Ubuntu named it differently)systemctlrestartchronydsystemctlrestartchrony

#!/bin/bash# From https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/installation#install-latest-versioncurl-sSOhttps://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.shbashadd-google-cloud-ops-agent-repo.sh--also-installOPS_AGENT_CONF="logging:    receivers:        chrony_tracking_receiver:            type: files            include_paths:                - /var/log/chrony/tracking.log    processors:        chrony_tracking_processor:            type: parse_regex            regex: \"^.*PHC0.*  (?<max_error>[-\d\.eE]+)$\"    service:        pipelines:            chrony_tracking_pipeline:                receivers: [chrony_tracking_receiver]                processors: [chrony_tracking_processor]"OPS_AGENT_CONF_PATH="/etc/google-cloud-ops-agent/config.yaml"echo"$OPS_AGENT_CONF">"$OPS_AGENT_CONF_PATH"systemctlrestartgoogle-cloud-ops-agent

#!/bin/bashif[-z"$1"];thenecho"Usage: time-sync-logging-dashboard.sh <project_id>">&2exit1fiPROJECT_ID="$1"PROJECT_NUMBER=$(gcloudprojectsdescribe"$PROJECT_ID"--format="value(projectNumber)")SERVICE_ACCOUNT_EMAIL=${PROJECT_NUMBER}-compute@developer.gserviceaccount.comgcloudprojectsadd-iam-policy-binding"${PROJECT_ID}"\--member="serviceAccount:${SERVICE_ACCOUNT_EMAIL}"\--role="roles/compute.instanceAdmin"gcloudprojectsadd-iam-policy-binding"${PROJECT_ID}"\--member="serviceAccount:${SERVICE_ACCOUNT_EMAIL}"\--role="roles/monitoring.metricWriter"gcloudprojectsadd-iam-policy-binding"${PROJECT_ID}"\--member="serviceAccount:${SERVICE_ACCOUNT_EMAIL}"\--role="roles/logging.logWriter"cpclock-error-metric.json/tmp/clock-error-metric.jsonsed-i"s/PROJECT_ID/${PROJECT_ID}/"/tmp/clock-error-metric.jsongcloudloggingmetricscreate--project"${PROJECT_ID}"phc-clock-max-error-gce--config-from-file=/tmp/clock-error-metric.jsongcloudmonitoringdashboardscreate--project"${PROJECT_ID}"--config-from-file=metric-dashboard.json