]> git.apps.os.sepia.ceph.com Git - teuthology.git/commit
Add beanstalk as a possible queue backend for Teuthology Jobs along with Paddles
authorAishwarya Mathuria <amathuri@redhat.com>
Mon, 4 Oct 2021 13:54:41 +0000 (19:24 +0530)
committerAishwarya Mathuria <amathuri@redhat.com>
Fri, 3 Jun 2022 14:35:24 +0000 (20:05 +0530)
commit0ad33c0ace2555b21a984909d7020fc879d610ca
tree66dabb031c74a4847fc6e0d44c84841d05d89671
parent7726230ae5d0bedb6a6022da5b46542b5089bee2
Add beanstalk as a possible queue backend for Teuthology Jobs along with Paddles

With the use of the --queue-backend argument the user can specify which backend(paddles/beanstalk) they would like to use for maintaining the teuthology Jobs queue.
In order to avoid overlapping Job IDs, when a job is being scheduled in beanstalk it is also written to paddles which returns a unique ID.
This is the ID teuthology will treat as the Job ID throughout the run of the job.

To differentiate between the 2 queue backends, the teuthology-queue command has been split into teuthology-paddles-queue command and teuthology-beanstalk-queue command.

Signed-off-by: Aishwarya Mathuria <amathuri@redhat.com>
15 files changed:
scripts/beanstalk_queue.py [new file with mode: 0644]
scripts/dispatcher.py
scripts/paddles_queue.py [new file with mode: 0644]
scripts/queue.py [deleted file]
teuthology/beanstalk.py [new file with mode: 0644]
teuthology/config.py
teuthology/dispatcher/__init__.py
teuthology/dispatcher/supervisor.py
teuthology/kill.py
teuthology/orchestra/run.py
teuthology/report.py
teuthology/schedule.py
teuthology/test/test_dispatcher.py
teuthology/test/test_worker.py
teuthology/worker.py