Just a quick howto: this is how the ClusterControl jobs can be scheduled from the s9s command line program. The example also shows how the tags can be used to identify one specific job.
This is just a copy from one of my tests. It is creating a scheduled job, that goes back, identifies the job by the tag and checks what its state is. The job is scheduled just a few seconds in the future, so that the test doesn't have to wait much.
And it is creating the "success" job that does nothing and ends with a "SUCCESS" state. One might think it is a useless job, but in fact it is excellent... for testing.
This test screates a job that is sceduled, checks it, then waits a while for the job to be triggered and executed. Then the test checks if the job is indeed executed.
pipas@core2:tests$ s9s job \ --success \ --schedule="2019-11-05T10:41:50.000Z" \ --job-tags="testScheduledJob" Job with ID 2 registered. o The exit code is 0, ok. pipas@core2:tests$ s9s job --list --job-tags=testScheduledJob ID CID STATE OWNER GROUP CREATED RDY TITLE 2 0 SCHEDULED pipas testgroup 11:41:40 0% Simulated Success Total: 2 o The job is in scheduled state, ok. pipas@core2:tests$ sleep 20 pipas@core2:tests$ s9s job --list --job-tags=testScheduledJob ID CID STATE OWNER GROUP CREATED RDY TITLE 2 0 FINISHED pipas testgroup 11:41:40 100% Simulated Success Total: 8 o The job is in finished state, ok.