Execution will run in a job that runs shell script with the extracted parameter. The idea behind a job here is to allow executing the script from any proxy node in the cluster and to monitor the job status:
All possible agent scripts are installed in the job image
Creating agent-image with all available fence script
Creating the job by the controller which uses same image with different commands
Job objects will be posted in fencing::executeFence
Controller will follow jobs status before moving to next steps (in controller::handleExistingNodeFences)
the controller needs to update the nodefence object status to "running" when job is executed.
Execution will run in a job that runs shell script with the extracted parameter. The idea behind a job here is to allow executing the script from any proxy node in the cluster and to monitor the job status:
the controller needs to update the nodefence object status to "running" when job is executed.