Project

General

Profile

Feature #24714

Support for non-ssh agent provider

Added by Dustin Crowl about 4 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

As a user, I would like to use asynchronous execution methods. These would be similar to the osa-dispatcher/osad model.

History

#1 Updated by Ivan Necas about 4 years ago

I don't understand what the requirement is. Could go as deep as possible with explaining what the feature should be about and which problem it would solve?

#2 Updated by Dustin Crowl about 4 years ago

Essentially, I am trying to solve the problem of using remote execution within an environment where SSH is so heavily locked down as to be nearly unusable by any automation that relies on it. I am not able to make effective use of remote execution due to root logins being disallowed, and mandatory two factor authentication for all other accounts. The solution in the past has been to make use of osa-dispatcher, which can schedule remote commands for execution by an agent running on the client systems once they have checked in and picked up the new task. I have not been able to locate a similar provider for the remote execution plug-in.

#3 Updated by Ivan Necas about 4 years ago

  • Subject changed from Asynchronous Execution to Support for non-ssh agent provider

Oh, I understand. Btw. there is a support for async triggering via ssh (added by #17514), but it seems your situation is you can't use ssh at all. Therefore I'm changing the subject to better capture this requirement.

We know we want to add support for this, it's just no known when exactly this will be.

#4 Updated by Ivan Necas about 4 years ago

  • Bugzilla link set to 1316598

#5 Updated by Dustin Crowl about 4 years ago

No worries, I appreciate it!

Also available in: Atom PDF