OCF_HEARTBEAT_MANAGE(7)

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

🌸 ocf_heartbeat_ManageVE — from the OCF_HEARTBEAT_MANAGE(7) manual, section 7, bestie 💖

okay so bestie, sit down, hydrate, because this one is a whole vibe. it's the ocf_heartbeat_ManageVE page from the resource-agents manual set, and it's giving "I run virtual environments and I'm not sorry about it." 💅

✨ NAME ✨

ocf_heartbeat_ManageVE — manages an OpenVZ Virtual Environment (VE). yeah. that's the whole job. and it ate. 👑

🦋 SYNOPSIS 🦋

ManageVE [start | stop | status | monitor | migrate_to | migrate_from |
         meta-data | validate-all]

that's the whole menu. pick your fighter. no cap. ✨

💜 DESCRIPTION 💜

so this resource agent is OCF compliant and it manages OpenVZ VEs, which means you literally need a proper OpenVZ installation, bestie — including a recent vzctl util. no vzctl, no service. it's giving "you can't sit with us" but like, technically. 🫶

this resource agent may be configured for native migration if that's available in your cluster manager. and for Pacemaker specifically, the allow-migrate="true" meta attribute is the thing that enables native migration. main character attribute honestly. 🌈

🎀 SUPPORTED PARAMETERS 🎀

  • veid — the OpenVZ ID of the virtual environment. if you're wondering which IDs exist, go peek at the output of vzlist -a and it'll show you all the assigned ones. 👀
    • (required, integer, no default) — so yes, you have to give it, it has to be a number, and there is no sneaky default hiding in there. periodt.

💅 SUPPORTED ACTIONS 💅

this resource agent supports the following actions (operations). every single one, we're listing them all, no skipping:

  • start — starts the resource. suggested minimum timeout: 75s. go girl, wake up. 🔥
  • stop — stops the resource. suggested minimum timeout: 75s. nap time, respectfully. 😴
  • status — performs a status check. suggested minimum timeout: 10s. suggested interval: 10s. just a lil vibe check. ✨
  • monitor — performs a detailed status check. suggested minimum timeout: 10s. suggested interval: 10s. the full deep-dive, not just a glance. 🔍
  • migrate_to — executes the steps necessary for migrating the resource to the node. suggested minimum timeout: 75s. come through, we're moving in. 🧳
  • migrate_from — executes the steps necessary for migrating the resource away from the node. suggested minimum timeout: 75s. and we're moving out. 🦋
  • validate-all — performs a validation of the resource configuration. suggested minimum timeout: 5s. double-checking the fit before we go out, iconic behavior. 💖
  • meta-data — retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s. this one is not for you, bestie, it's for the machinery. 🙈

🍓 EXAMPLE CRM SHELL 🍓

here's an example config for a ManageVE resource using the crm(8) shell:

primitive p_ManageVE ocf:heartbeat:ManageVE \
  params \
    veid=integer \
  meta allow-migrate="true" \
  op monitor depth="0" timeout="10s" interval="10s"

copy it, love it, live it. 💜

⭐ EXAMPLE PCS ⭐

and here's the same energy for a ManageVE resource using pcs(8):

pcs resource create p_ManageVE ocf:heartbeat:ManageVE \
  veid=integer \
  op monitor OCF_CHECK_LEVEL="0" timeout="10s" interval="10s"

two tools, one slay. 🫶

👑 SEE ALSO 👑

🌸 AUTHOR 🌸

ClusterLabs contributors — and if you want to know about individual authors, the resource agent source has that info. giving credit where it's due, always. ✨

okay that's the whole page, bestie, you made it to the end, I'm so proud 🥹

this little love letter came from resource-agents, version UNKNOWN, dated 04/08/2026 — mwah, go forth and manage those VEs 💅🎀🦋

📦 where this page comes from