As a user of WDQS, I only want non-lagged servers to be pooled.
As an operator of WDQS I don't want to be alerted transient issues that are part of normal operations during data reload.
WDQS data-transfer cookbook needs to wait for updater to catchup on lag before removing icinga downtime and repooling servers.
We already have code to wait for updater to catch up on lag in the data-reload cookbook. This code should be moved to Spicerack (so that it is in a central location) and should be used for both the data-reload and data-transfer cookbooks.
AC:
- no alert are raised during normal operations of the data-transfer cookbook
- wdqs servers are not pooled until they are fully catched up on lag