[keyserver] Introduce concept of auxiliary node for running certain cronjobs
ClosedPublic
Actions

Authored by ashoat on Aug 21 2024, 6:00 PM.

Details

Reviewers

will

Commits

rCOMMda87979b4a12: [keyserver] Introduce concept of auxiliary node for running certain cronjobs

Summary

We'll use the auxiliary node for running the the Comm team dev scripts (RUN_COMM_TEAM_DEV_SCRIPTS) and for database backup.

Depends on D13134

Test Plan

Ran this on my personal server and confirmed that it worked

Diff Detail

Repository

rCOMM Comm

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

ashoat created this revision.Aug 21 2024, 6:00 PM

Herald added a subscriber: tomek. · View Herald TranscriptAug 21 2024, 6:00 PM

Unfortunately Phabricator got a little confused on this diff, and is marking some changes in a confusing way. Basically I just pulled out three cronjobs here and put them at the end:

backupDB
createDailyUpdatesThread
postLeaderboard

The first is additionally gated by COMM_JSONCONFIG_facts_backups, and the other two are additionally gated on RUN_COMM_TEAM_DEV_SCRIPTS. When their gates are enabled, they can be run on either the primary or auxiliary nodes.

Harbormaster completed remote builds in B31208: Diff 43562.Aug 21 2024, 6:18 PM

ashoat requested review of this revision.Aug 21 2024, 6:18 PM

will accepted this revision.Aug 21 2024, 10:48 PM

This revision is now accepted and ready to land.Aug 21 2024, 10:48 PM

Closed by commit rCOMMda87979b4a12: [keyserver] Introduce concept of auxiliary node for running certain cronjobs (authored by ashoat). · Explain WhyAug 22 2024, 12:06 AM

This revision was automatically updated to reflect the committed changes.

ashoat added a commit: rCOMMda87979b4a12: [keyserver] Introduce concept of auxiliary node for running certain cronjobs.