OCF_HEARTBEAT_SYSINF(7)

πŸ’– ocf_heartbeat_SysInfo β€” it's giving "records various node attributes in the CIB" πŸ’–

okay bestie, sit down, hydrate, because we're talking about ocf_heartbeat_SysInfo, the manual page for the SysInfo resource agent. Yes it's in section 7 of the manual. Yes it's a whole vibe. Let's go πŸ¦‹


✨ SYNOPSIS ✨

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

that's it. that's the whole summoning ritual. five little words and the node starts spilling its whole life story πŸ’…


🌸 DESCRIPTION 🌸

so this is a SysInfo Resource Agent. its entire job β€” its whole personality, its main character energy β€” is to record various attributes of a node, and it records them in the CIB. no cap.

here's a sample Linux output so you can see what the receipts look like:

arch: i686 os: Linux-2.4.26-gentoo-r14 free_swap: 1999 cpu_info: Intel(R) Celeron(R) CPU 2.40GHz cpu_speed: 4771.02 cpu_cores: 1 cpu_load: 0.00 ram_total: 513 ram_free: 117 root_free: 2.4

and here's a sample Darwin output, because macOS wanted a turn πŸ“:

arch: i386 os: Darwin-8.6.2 cpu_info: Intel Core Duo cpu_speed: 2.16 cpu_cores: 2 cpu_load: 0.18 ram_total: 2016 ram_free: 787 root_free: 13

and now the units, because numbers without units are just ✨chaos✨:

  • free_swap: Mb
  • ram_*: Mb
  • root_free: Gb
  • cpu_speed (Linux): bogomips
  • cpu_speed (Darwin): Ghz

lowkey obsessed with how bogomips is a real unit that real grown-ups shipped in real software. iconic. 😭


πŸŽ€ SUPPORTED PARAMETERS πŸŽ€

  • pidfile β€” the PID file, bestie. it's optional, it's a string, and the default is "/run/resource-agents/SysInfo-RESOURCE_ID". yes, that RESOURCE_ID is literally in there. don't @ me, it's the default fr fr.
  • delay β€” interval to allow values to stabilize 🧚 so like, let the numbers breathe before you judge them. optional, string, default "0s".

πŸ‘‘ SUPPORTED ACTIONS πŸ‘‘

this resource agent supports the following actions (operations), and honestly? each one ate:

  • start β€” starts the resource. suggested minimum timeout: 20s.
  • stop β€” stops the resource. suggested minimum timeout: 20s.
  • monitor β€” performs a detailed status check πŸ”. suggested minimum timeout: 20s. suggested interval: 60s.
  • 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: 20s.
πŸ’€ reminder bestie: meta-data is internal use only. it's not for you. it's for the machinery. stay out of the kitchen unless you're cooking.

πŸ’œ EXAMPLE CRM SHELL πŸ’œ

here's an example configuration for a SysInfo resource using the crm(8) shell β€” copy it exactly, character for character, no improvising:

primitive p_SysInfo ocf:heartbeat:SysInfo \
  op monitor timeout="20s" interval="60s"

🌈 EXAMPLE PCS 🌈

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

pcs resource create p_SysInfo ocf:heartbeat:SysInfo \
  op monitor timeout="20s" interval="60s"

🫢 SEE ALSO 🫢

go touch grass over there, it's a whole website ⭐


πŸ’… AUTHOR πŸ’…

ClusterLabs contributors β€” and if you want to know about individual authors, the resource agent source has the info. iykyk 🌸


πŸ’– okay that's the whole page. resource-agents UNKNOWN, dated 04/08/2026, from the OCF_HEARTBEAT_SYSINF(7) manual. slay, periodt, go record some node attributes βœ¨πŸ¦‹
πŸ“¦ where this page comes from