Last modified: 2014-09-06 05:37:31 UTC
It would be nice to have an idea of which "version" is on each node of the cluster. One relatively easy way to do this would be to have the scap family of applications create/update a file in a known location inside /a/common on tin early in the application invocation. This file could record the time the sync was started, the deploying user and any message given describing the reason for the sync. This information is all public already via SAL. The sync should then ensure that this file is always copied to the cluster hosts even if the command is sync-file or sync-dir and not a full scap. The internal design of scap should accommodate this relatively simply. Having this information available on each cluster host would allow creation of inquiry and monitoring tools that look for hosts that are out of sync with the state of the primary repo on tin.
