OCF_HEARTBEAT_AOETAR(7)

💖 OCF_HEARTBEAT_AOETAR(7) 💖

okay bestie, sit down, grab a strawberry 🍓, because today we're talking about ocf_heartbeat_AoEtarget — that's the manual page name, and yes the title is doing a little bit of shouting but we love her for it. This is a ClusterLabs OCF resource agent, and she's here to make ATA-over-Ethernet happen for you. no cap. ✨

---

✨ NAME ✨

ocf_heartbeat_AoEtarget — she manages ATA-over-Ethernet (AoE) target exports. that's it, that's the whole vibe. 💅

---

🌸 SYNOPSIS 🌸

AoEtarget [start | stop | monitor | meta-data | validate-all]

---

🦋 DESCRIPTION 🦋

so here's the tea ☕ — this resource agent manages an ATA-over-Ethernet (AoE) target using vblade. it literally takes any block device, or a file, and exports it as an AoE target using the Ethernet device, shelf, and slot number you tell it about. iconic behavior honestly. 👑

---

🎀 SUPPORTED PARAMETERS 🎀

the way these params are just sitting here waiting for you to fill them in. let's go one by one, bestie:

• device — the local block device (or file!) you wanna export as an AoE target. that's your star of the show. 🌟 (required, string, no default — so like, you HAVE to bring this one yourself)
• nic — the local Ethernet interface to use for exporting this AoE target. (required, string, default "eth0")
• shelf — the AoE shelf number to use when exporting this target. (optional, integer, no default)
• slot — the AoE slot number to use when exporting this target. (required, integer, no default — not optional, don't try it 🙈)
• pid — the file to record the daemon pid to. (unique, optional, string, default "/run/resource-agents/AoEtarget-RESOURCE_ID.pid")
• binary — location of the vblade binary. (optional, string, default "/usr/sbin/vblade")

---

🔥 SUPPORTED ACTIONS 🔥

this resource agent supports the following actions (operations). each one has a suggested minimum timeout, and we respect her boundaries:

• start — starts the resource. suggested minimum timeout: 15s.
• stop — stops the resource. suggested minimum timeout: 15s.
• monitor — performs a detailed status check. suggested minimum timeout: 15s. suggested interval: 10s.
• reload — suggested minimum timeout: 15s.
• meta-data — retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s.
• validate-all — performs a validation of the resource configuration. suggested minimum timeout: 15s.

---

💜 EXAMPLE CRM SHELL 💜

here's an example config for an AoEtarget resource using the crm(8) shell. copy-paste her, she's ready:

primitive p_AoEtarget ocf:heartbeat:AoEtarget \
  params \
    device=string \
    nic="eth0" \
    slot=integer \
  op monitor timeout="15s" interval="10s" depth="0"

---

🌈 EXAMPLE PCS 🌈

and if pcs(8) is more your thing (valid, honestly), here's the same energy:

pcs resource create p_AoEtarget ocf:heartbeat:AoEtarget \
  device=string \
  nic="eth0" \
  slot=integer \
  op monitor timeout="15s" interval="10s" OCF_CHECK_LEVEL="0"

---

👀 SEE ALSO 👀

• http://clusterlabs.org/ — go say hi, fr fr 🫶

---

💀 AUTHOR 💀

ClusterLabs contributors (see the resource agent source for information about individual authors). shoutout to everyone who ever touched this file, y'all ate. 🍽️

---

ok and one last thing bestie — this page is from resource-agents UNKNOWN, dated 04/08/2026, and it lives in section 7 of the manual. that's the whole manual page, you're officially AoE-literate now, no cap 💅✨ mwah, go export something 🎀