]> 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)
committerZack Cerza <zack@redhat.com>
Tue, 31 May 2022 19:45:56 +0000 (13:45 -0600)
commita2d0abd562a8c99d5cfb005750f45cfb010d079d
tree9f8d71e837b5fe2a8d3192a5057844d311445caa
parente37b71ad1cf035ea02a85e4cfdff7c374b627152
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