User story #9290
closedAdd an API endpoint to call rudder-remote-run
Description
We want to be able to call rudder-remote-run from API, with a class parameter.
The first version will be limited to nodes directlyreachable from the root server (i.e: nodes behind a relay can't get the command, and we must return an error for them).
There is actually two endpoints to do:
- one synchrone, which is directed to ONE node with a class parameter, start rudder-remote-run, wait for the execution, and send the command output in the API call answer. So API call is blocking, and can block for long time. The output may not be streamed - it would be better, but it is not mandatory
- one asynchrone, that only take the class parameter as argument, and start the command on all node directly under the server, but just send back a "ACK, I started rudder-remote-run on these nodes".
The second method would be better if it can akso take a group id as parameter, and return which nodes didn't get the command (because for ex. behind a relay).
The second method is not prioritary and can be made in an other ticket.
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1274
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Updated by François ARMAND over 8 years ago
- Related to User story #2876: We should be able to force a node to execute cf-agent with the Webapp interface added