OCF_HEARTBEAT_VMWARE(7)

✨ ocf_heartbeat_vmware ✨

okay bestie, so this is the manual page OCF_HEARTBEAT_VMWARE(7) from the OCF resource agents set, and it's literally all about wrangling VMWare Server 2.0 virtual machines. no cap. let's get into it πŸ’–


🌸 NAME 🌸

ocf_heartbeat_vmware β€” manages VMWare Server 2.0 virtual machines

like... it babysits your VMs. that's the whole job. iconic behavior honestly πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

vmware [start | stop | monitor | meta-data]

that's it. four little moves. pick your fighter πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

it's an OCF compliant script, which is giving very much "team player" energy, and its whole thing is controlling vmware server 2.0 virtual machines. so like, when the cluster says jump, this script asks how high. periodt ✨


πŸ’œ SUPPORTED PARAMETERS πŸ’œ

these are the knobs you get to turn, bestie. respect them πŸ™

  • vmxpath β€” the path to your VMX configuration file. this one is required, it's a string, and there is no default. so you literally have to tell it, it's not gonna guess πŸ₯Ί
  • vimshbin β€” the path to the vmware-vim-cmd executable. this one is optional, it's a string, and the default is "/usr/bin/vmware-vim-cmd". so if your vim-cmd lives somewhere normal, you can just... not mention it. main character energy fr fr πŸ’…

πŸ”₯ SUPPORTED ACTIONS πŸ”₯

this resource agent supports the following actions (operations). and yes, each one has a suggested minimum timeout, because patience is a virtue or whatever 🌈

  • start β€” starts the resource. suggested minimum timeout: 600s.
  • stop β€” stops the resource. suggested minimum timeout: 600s.
  • monitor β€” performs a detailed status check. suggested minimum timeout: 30s. suggested interval: 300s.
  • meta-data β€” retrieves resource agent metadata (internal use only, so don't touch, that's not for you bestie πŸ™ˆ). suggested minimum timeout: 5s.

🌟 EXAMPLE CRM SHELL 🌟

here's an example configuration for a vmware resource using the crm(8) shell. look at it. it's so cute:

primitive p_vmware ocf:heartbeat:vmware \
  params \
    vmxpath=string \
  op monitor timeout="30s" interval="300s" depth="0"

πŸ’– EXAMPLE PCS πŸ’–

and here's the same vibe but for pcs(8), because we contain multitudes:

pcs resource create p_vmware ocf:heartbeat:vmware \
  vmxpath=string \
  op monitor timeout="30s" interval="300s" OCF_CHECK_LEVEL="0"

🧚 SEE ALSO 🧚

go look at this if you want more:


πŸ‘‘ AUTHOR πŸ‘‘

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

they did that. no notes. 🫢


and that's the whole page, bestie!! this was resource-agents UNKNOWN, dated 04/08/2026, and it's page OCF_HEARTBEAT_VMWARE(7). slay, bye πŸ’…πŸŒΈβœ¨

πŸ“¦ where this page comes from