Skip to content

Conversation

@ajfloeder
Copy link

Summary

Adds fence_recorder, a new Pacemaker fence agent that uses a request/response file pattern to coordinate fencing with external systems.

Use Case

This agent is designed for environments where fencing decisions need to be coordinated with external systems (e.g., storage controllers, cloud providers, or custom orchestration) that perform cleanup operations before fencing completes.

Instead of directly fencing nodes, fence_recorder:

  1. Writes a fence request to a configurable directory
  2. Waits for an external responder to process the request and write a response
  3. Returns success/failure to Pacemaker based on the response

@knet-jenkins
Copy link

knet-jenkins bot commented Dec 9, 2025

Can one of the project admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-646/1/input

@ajfloeder ajfloeder force-pushed the fence_recorder-new-fence-agent branch from 036e40e to 0260fdf Compare December 9, 2025 21:20
@knet-jenkins
Copy link

knet-jenkins bot commented Dec 9, 2025

Can one of the project admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-646/2/input

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant