Bug 1757317

Summary:	[RFE] Dynflow workers extraction
Product:	Red Hat Satellite	Reporter:	Marek Hulan <mhulan>
Component:	Dynflow	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	aruzicka, bkearney, egolov, inecas, lhellebr, vsedmik, wpinheir
Target Milestone:	6.8.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-2.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:59:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1840218
Bug Blocks:

Description Marek Hulan 2019-10-01 08:30:10 UTC

Description of problem:

Dynflow Worker process is now part of the executor, meaning they can't be restarted independently. As a first step to improve scalability, following two stories will be implemented


1. As a satellite user doing an install or an upgrade, the installer should create both the orchestration and worker processes with sane defaults. Both processes will run on the same machine as the satellite. 

2. As a satellite admin, I should be able to restart a worker process without impacting the uptime of the satellite or losing data.

Verification steps will be added later when we know names of new services.

Comment 9 Lukáš Hellebrandt 2020-07-07 09:08:50 UTC

Verified with Sat 6.8 snap 7.0.

Sidekiq is now used. It's now possible to:
- change a number of workers, number of their threads, their queues
- view log using "journalctl -u 'dynflow-sidekiq@*'"
- restart a worker without getting to inconsistent state

Note that this intentionally does not apply to external capsules.

See this demo:
https://www.youtube.com/watch?v=8xomzg_FBIs&feature=youtu.be&t=485

Comment 12 errata-xmlrpc 2020-10-27 12:59:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366