Releases: Project-OMOTES/orchestrator
Releases · Project-OMOTES/orchestrator
1.2.2
1.2.1
What's Changed
- delete alembic script and update readme by @MarkTNO in #74
- 54: Rename computation-engine to omotes-system, fix integration with new setup approach for integration_tests and fix issue in job_submitter that an error result still led to a succeeding test. by @lfse-slafleur in #77
- Remove connecting and subscribing to the job result dead letter queue. by @cwang39403 in #76
- 79: Integrate new START special value in TaskProgressEvents from worker. by @lfse-slafleur in #80
Full Changelog: 1.2.0...1.2.1
1.2.0
What's Changed
- 70: Forward job_reference from JobSubmission if available to Celery t… by @lfse-slafleur in #71
Full Changelog: 1.1.0...1.2.0
1.1.0
What's Changed
- 80 clean up left over job status progress and result queues by @cwang39403 in #62
- 63 delivery limit cancel a job if it is started more than a configurable threshold by @lfse-slafleur in #68
- 65 update workflow configuration remove any test workers and update expected params dict for simulator by @lfse-slafleur in #69
Full Changelog: 1.0.0...1.1.0
1.0.0
What's Changed
- 85 bugfix job timeout none is wrongly interpreted as timeout 0 by @cwang39403 in #61
- 58 utilize a single job submission queue instead of having one queue per workflow type by @lfse-slafleur in #60
Full Changelog: 0.1.0...1.0.0
0.1.0
What's Changed
- add dev.Dockerfile to run in docker with local code/sdk/protocol by @MarkTNO in #49
- 51 move omotes sdk internal orchestrator orchestrator interface from omotes sdk python to orchestrator by @lfse-slafleur in #53
- 39 Job in Orchestrator can timeout a running workflow by @cwang39403 in #50
- 52 Refactor broker interface orchestrator <-> worker celery to its own class and implement the new controls provided through sdk for exclusive queues to implement multi SDK support for available workflows feature.
Full Changelog: 0.0.13...0.1.0