Feature #17514

Job invocations should happen asynchronously

Added by Adam Ruzicka 4 months ago. Updated 4 months ago.

Status:New
Priority:High
Assigned To:-
Category:-
Target version:Foreman - Team Ivan backlog
Difficulty: Pull request:
Bugzilla link:1386270
Story points-
Velocity based estimate-

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1386270

Description of problem:

Customer needs to run many long-running job invocations at the same time on multiple machines.

These machines are located in a network with low bandwidth, so keeping many connections alive isn't possible as some jobs could take a long time (e.g: reposync, yum update).

These connections waste resources on the client hosts which are not very powerful machines.

This could be implemented by having another provider different to SSH or possibly by making ssh run the job and return right away (the capsule could check the status of the job somehow)

Additional info:

Currently they are running their own custom remote execution scripts which use Ansible core libraries to make calls asynchronously and poll for the status of the execution. The solution provided by Satellite does not necessarily have to poll for the status but it would need to provide a way to check it's status.

History

#1 Updated by Adam Ruzicka 4 months ago

  • Target version set to Team Ivan backlog

Also available in: Atom PDF