OCF_HEARTBEAT_VDO-V(7)

📦
version 4.18.0 · 14 versions
, in fedora 43, fedora 44

💖 NAME 💖

ocf_heartbeat_vdo-vol — ok so this is the VDO resource agent, bestie. That's the whole name, that's the whole vibe. It lives in section 7 of the manual, and it's about to make your high-availability life so much easier 🦋

✨ SYNOPSIS ✨

vdo-vol [start | stop | status | monitor | meta-data | validate-all]

like, that's the whole mood. six little actions, one icon behavior 💅

🌸 DESCRIPTION 🌸

Okay so listen. This is an OCF Resource script for VDO (Virtual Data Optimizer) volume(s). It manages your VDO volume(s) as a HA resource — as in, high availability, as in, your cluster stays cute and your volumes stay online. Periodt.

🚨 Two things you literally cannot skip, bestie: - The configuration file needs to be synced to all nodes. All of them. Every single one. No leaving anyone out, that's not the energy we're bringing. - The systemd vdo service must be disabled when you're using this agent. Yes, disabled. They cannot both be running the show, that's a main character conflict and it ends badly 😭

🎀 SUPPORTED PARAMETERS 🎀

  • config — the Configuration file. It's optional, it's a string, and there is no default. So like, if you want it, you gotta say it. Speak up, queen 👑
  • volume — the VDO Volume. Also optional, also a string, also no default. And here's the little trick: leave it empty for all 🌈 if you just want everything, you leave it blank and let the agent do its thing.

👑 SUPPORTED ACTIONS 👑

This resource agent supports the following actions (operations) — aka the six moves it knows how to do, and it does them well:

  • start — Starts the resource. Suggested minimum timeout: 60s. Yeah, a whole minute. Starting a VDO volume is not a quick little thing, give it room to breathe 💖
  • stop — Stops the resource. Suggested minimum timeout: 20s. Twenty seconds and she's out, bye 👋
  • status — Performs a status check. Suggested minimum timeout: 20s. Just a vibe check on whether things are alive.
  • monitor — Performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 10s. So it's checking every ten seconds — this is the one that actually watches, iykyk 🔥
  • validate-all — Performs a validation of the resource configuration. Suggested minimum timeout: 20s. Basically the pre-flight check, making sure everything's giving what it's supposed to give.
  • meta-data — Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 20s. That's not for you, bestie, that's for the machinery 🙈

🌈 EXAMPLE CRM SHELL 🌈

Here's what it looks like when you're configuring a vdo-vol resource using the crm(8) shell:

primitive p_vdo-vol ocf:heartbeat:vdo-vol \
  op monitor depth="0" timeout="20s" interval="10s" start-delay="10s"

look at that. clean. gorgeous. slay 💅

⭐ EXAMPLE PCS ⭐

And here's the same energy but for pcs(8):

pcs resource create p_vdo-vol ocf:heartbeat:vdo-vol \
  op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="10s" start-delay="10s"

two different tools, one flawless resource. we love options 🫶

🦋 SEE ALSO 🦋

💀 AUTHOR 💀

ClusterLabs contributors (see the resource agent source for information about individual authors). Not one person, a whole collective. Group chat energy from day one, honestly iconic 🧚

okay that's the whole page bestie, you're officially VDO-pilled 💖✨🎀 This was resource-agents UNKNOWN, dated 04/08/2026 — and it's the OCF_HEARTBEAT_VDO-V(7) manual, section seven, for ocf_heartbeat_vdo-vol, if you're keeping receipts. no cap. bye bestie 💅🌸

📦 where this page comes from