13f3f31bf1
1. What is the problem? Currently we use cast method to trigger XJob daemon which we have risk to lose jobs. 2. What is the solution to the problem? As proposed in the specification[1], we create a database record for each new job before invoking cast method, so the job will not be lost even if there is something wrong with the message broker. 3. What the features need to be implemented to the Tricircle to realize the solution? XJob reliability is enhanced. [1] https://review.openstack.org/#/c/412762/ Change-Id: I86f37093aa1843f1daaf61b99541d3f921ef28ef |
||
|---|---|---|
| .. | ||
| api | ||
| cmd | ||
| common | ||
| db | ||
| network | ||
| tempestplugin | ||
| tests | ||
| xjob | ||
| __init__.py | ||