OCF_HEARTBEAT_GCP-P(7)

💾 ocf_heartbeat_gcp-pd-move — like, the whole manual, bestie 💾

okay so real talk: this is page OCF_HEARTBEAT_GCP-P(7) from the OCF resource agents manual, and it's about ocf_heartbeat_gcp-pd-move — the resource agent that attaches/detaches a persistent disk on your current GCP instance. let's get into it 💅

---

✨ NAME ✨

ocf_heartbeat_gcp-pd-move — Attach/Detach a persistent disk on current GCP instance 🎀

---

✨ SYNOPSIS ✨

gcp-pd-move [start | stop | monitor | meta-data]

---

✨ DESCRIPTION ✨

so basically this Resource Agent can attach or detach a regional/zonal disk on your current GCP instance. no cap, that's the whole vibe. 🔥

Requirements — there is literally one (1) requirement and it's this:

• The Disk has to be properly created as regional/zonal in order to be used correctly. that's it. that's the requirement. it's giving "please read this before you file a bug" energy 😭

---

✨ SUPPORTED PARAMETERS ✨

• disk_name — The name of the GCP disk. this one's the main character 👑 (unique, required, string, no default)
• disk_scope — Disk scope 🦋 (optional, string, default "detect")
• disk_csek_file — Path to a Customer-Supplied Encryption Key (CSEK) key file. fancy encryption stuff, iykyk 🔐 (optional, string, no default)
• mode — Attachment mode (READ_WRITE, READ_ONLY) — pick your fighter ⭐ (optional, string, default "READ_WRITE")
• device_name — An optional name that indicates the disk name the guest operating system will see. like a lil nickname for your disk 🫶 (optional, boolean, default false)
• stackdriver_logging — Use stackdriver_logging output to global resource (yes, true, enabled). yes, those are the three values, no i didn't make that up 💀 (optional, string, default "no")

---

✨ SUPPORTED ACTIONS ✨

This resource agent supports the following actions (operations), and honestly it's a whole menu:

• start — Starts the resource. Suggested minimum timeout: 300s. (yes, 300s, that's not a typo, it's a big one 😤)
• stop — Stops the resource. Suggested minimum timeout: 15s.
• monitor — Performs a detailed status check. Suggested minimum timeout: 15s. Suggested interval: 10s. the lil vibes check that keeps everything alive 🩺
• meta-data — Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s. 🙈 don't touch, it's internal

---

✨ EXAMPLE CRM SHELL ✨

here's an example config for a gcp-pd-move resource using the crm(8) shell — copy it exactly, bestie, every backslash matters 😭

primitive p_gcp-pd-move ocf:heartbeat:gcp-pd-move \
  params \
    disk_name=string \
  op monitor timeout="15s" interval="10s" depth="0"

---

✨ EXAMPLE PCS ✨

and here's the pcs(8) version for a gcp-pd-move resource — same energy, different tool 🧚

pcs resource create p_gcp-pd-move ocf:heartbeat:gcp-pd-move \
  disk_name=string \
  op monitor timeout="15s" interval="10s" OCF_CHECK_LEVEL="0"

hey — notice these two are not identical? the crm one has depth="0" and the pcs one has OCF_CHECK_LEVEL="0". that's how the original rolls it, so that's how i'm rolling it. no "fixing" allowed ✨

---

✨ SEE ALSO ✨

• http://clusterlabs.org/ — go say hi 🌈

---

✨ AUTHOR ✨

ClusterLabs contributors (see the resource agent source for information about individual authors) 💜

---

aaand that's the page! 🎀 this lovely lil doc came from <rainbow>resource-agents UNKNOWN</rainbow>, dated <pink>10/01/2026</pink> — so go forth, attach your disks, detach your disks, and remember: properly created regional/zonal or it's not gonna slay 💅✨🦋