Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using job object to execute agents #10

Open
bronhaim opened this issue Dec 18, 2017 · 0 comments
Open

Using job object to execute agents #10

bronhaim opened this issue Dec 18, 2017 · 0 comments
Labels

Comments

@bronhaim
Copy link
Collaborator

bronhaim commented Dec 18, 2017

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:

  1. All possible agent scripts are installed in the job image
  2. Creating agent-image with all available fence script
  3. Creating the job by the controller which uses same image with different commands
  4. Job objects will be posted in fencing::executeFence
  5. 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.

@bronhaim bronhaim added the new label Dec 18, 2017
@bronhaim bronhaim added on progress and removed new labels Dec 31, 2017
@bronhaim bronhaim changed the title define executor api Using job object to execute agents Dec 31, 2017
@bronhaim bronhaim added Done and removed on progress labels Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant