From Peter Youngmeister:

You can enable any of the crons that are currently on hume on terbium with a
flag in site.pp (or more accurately, by removing enabled => false as the crons
are all set up to run from the primary DC by default). Also make sure to disable >them on hume by removing enabled => true.

I'm changing the title of this bug from an "audit" task to actually doing the change.

Tor proxy code merged and pushed to cluster.
Config: https://gerrit.wikimedia.org/r/#/c/60424/
Puppet: https://gerrit.wikimedia.org/r/#/c/60427/

Config can be probably just be merged now.

Geodata path fixed.
Puppet: https://gerrit.wikimedia.org/r/#/c/60434/

For update_special_pages we need a new location for the norotate logs to go

update_flaggedrevs_stats - Confusing comment about wikimedia-periodic-update.sh, file is in puppet

refreshlinks !?

(In reply to comment #2)

For update_special_pages we need a new location for the norotate logs to go

update_flaggedrevs_stats - Confusing comment about
wikimedia-periodic-update.sh, file is in puppet

refreshlinks !?

(checking in to prioritize for next quarter)

Any movement on these last things?

Anything left that isn't on the list?

Anything left that can't be moved for technical/datacenter issues (eg: swift/tampa dependency)?

All of the misc::maintenance cron jobs were migrated a while ago. The only cron job left on hume is the ganglia metric installed by misc::monitoring::jobqueue. Moving that particular cron job would cause the metric to be renamed, so the long term data would be harder to access.

Now that bug 46428 is fixed, there's no actual problem with cron jobs running on hume.