If a machine is a VM (e.g. KVM or VMware) we will want to use the PHC0
clock as a master source if it's available since we want to sync with
the hypervisor for accuracy. If the host is hardware, we want to ensure
that multiple time sources are available and therefore the PHC device
should not be configured as stratum 0.
This change introduces a test, where the PHC (/dev/ptp0) device is only
used if the host is a VM.
Remove the hook templates to avoid update-status churn.
This is causing update-status to reconfigure everything every time
because the template doesn't have :
hookenv.atexit(basic.clear_config_states)
so the "config.changed" flag is always set.
This commit removes any reference to hook.template - the correct hook
template is provided by the "basic" layer.
If the settings for pools, source and peers are all empty, we drop the
package default config file for chrony. This enables custom config if
PHC is available.
