Feature #17514

Job invocations should happen asynchronously

Added by Adam Ruzicka 11 months ago. Updated about 1 month ago.

Status:Closed
Priority:High
Assigned To:Adam Ruzicka
Category:-
Target version:Foreman - Team Ivan Iteration 17
Difficulty: Pull request:https://github.com/theforeman/foreman_remote_execution/pull/249, https://github.com/theforeman/smart_proxy_dynflow/pull/33, https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/32
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.


Related issues

Related to Foreman Remote Execution - Bug #20377: Provide features required by async-ssh in smart_proxy_dyn... Closed 07/21/2017
Related to foreman-tasks - Bug #20376: Provide features required by async-ssh in foreman-tasks-core Closed 07/21/2017

Associated revisions

Revision c68b3671
Added by Adam Růžička about 1 month ago

Fixes #17514 - Provide asynchronous variant of ssh provider

Revision cc611cef
Added by Adam Růžička about 1 month ago

Fixes #17514 - Allow enabling async ssh

History

#1 Updated by Adam Ruzicka 11 months ago

  • Target version set to Team Ivan backlog

#2 Updated by The Foreman Bot 5 months ago

  • Status changed from New to Ready For Testing
  • Assigned To set to Adam Ruzicka
  • Pull request https://github.com/theforeman/smart_proxy_dynflow/pull/33 added

#3 Updated by The Foreman Bot 5 months ago

  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/249 added

#4 Updated by The Foreman Bot 5 months ago

  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/32 added

#5 Updated by Ivan Necas 4 months ago

  • Target version changed from Team Ivan backlog to Team Ivan Iteration 17

#6 Updated by The Foreman Bot 3 months ago

  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/33 added

#7 Updated by Adam Ruzicka 3 months ago

  • Pull request deleted (https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/33)

Removing wrong PR

#8 Updated by Adam Ruzicka 3 months ago

  • Related to Bug #20377: Provide features required by async-ssh in smart_proxy_dynflow_core added

#9 Updated by Adam Ruzicka 3 months ago

  • Related to Bug #20376: Provide features required by async-ssh in foreman-tasks-core added

#10 Updated by Anonymous about 1 month ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF