Project

General

Profile

Actions
Copy link

Feature #27409

closed

Initial support for running dynflow work on separate workers using Sidekiq

Added by Ivan Necas almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ivan Necas
Category:
Dynflow
Target version:
dynflow-1.4.0
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/Dynflow/dynflow/pull/329
Fixed in Releases:
dynflow-1.4.0
Found in Releases:
Red Hat JIRA:

Description

This issue is meant for MVP work to be done and the goal is ability to run the actions code in separate workers processes.

It should preserve the original intenral-workers model while allowing to run in the new model.

The scope if this card is to deliver the absolute minimum to that the rest of the work can be build on top of it while the initial changes would be already merged into master

Related issues 1 (0 open — 1 closed)

Blocks foreman-tasks - Tracker #27408: Dynflow workers extraction to separate processesClosed

Actions
Actions
Copy link
 #1

Updated by Ivan Necas almost 5 years ago

  • Pull request https://github.com/Dynflow/dynflow/pull/329 added
Actions
Copy link
 #2

Updated by Ivan Necas almost 5 years ago

  • Blocks Tracker #27408: Dynflow workers extraction to separate processes added
Actions
Copy link
 #3

Updated by Adam Ruzicka over 4 years ago

  • Status changed from New to Closed
  • Assignee set to Ivan Necas
  • Fixed in Releases dynflow-1.4.0 added
Actions
Copy link
 #4

Updated by Adam Ruzicka over 4 years ago

  • Target version set to dynflow-1.4.0
Actions
Copy link

Also available in: Atom PDF