OCF_HEARTBEAT_EVMSSC(7)

πŸ’– ocf_heartbeat_EvmsSCC(7) β€” the EVMS SCC tea πŸ’…

okay bestie, so this is OCF_HEARTBEAT_EVMSSC(7), a page from the OCF resource agents manual. pull up a chair, grab a strawberry πŸ“, and let's talk about a resource agent that is lowkey retired.


✨ NAME ✨

ocf_heartbeat_EvmsSCC β€” manages EVMS Shared Cluster Containers (SCCs). (deprecated) yeah. we'll get to that. 🫠


✨ SYNOPSIS ✨

EvmsSCC [start | stop | status | monitor | meta-data]

that's the whole vibe. pick an action, any action. πŸ’…


✨ DESCRIPTION ✨

Deprecation warning: EVMS is no longer actively maintained and should not be used. This agent is deprecated and may be removed from a future release.

not me having to deliver bad news in the first sentence 😭 but fr fr, EVMS is not it anymore, and this agent is on its way out. don't build your whole cluster personality around it.

so what is it? it's a resource script for EVMS shared cluster container. it runs evms_activate on one node in the cluster. that's the entire job. one node, one activation, that's the moment. ✨


🌸 SUPPORTED PARAMETERS 🌸

  • ignore_deprecation β€” if you set this to true, it suppresses the deprecation warning for this agent. it's optional, it's a boolean, and it defaults to false. (so by default, yes, you will be hearing about the deprecation. the agent is a yapper about it, no cap. πŸ™ˆ)

πŸ”₯ SUPPORTED ACTIONS πŸ”₯

this resource agent supports the following actions (operations), and yes every single one comes with suggested minimum timeouts because we respect the clock around here:

  • start β€” starts the resource. suggested minimum timeout: 60s.
  • stop β€” stops the resource. suggested minimum timeout: 60s.
  • notify β€” suggested minimum timeout: 60s.
  • status β€” performs a status check. suggested minimum timeout: 10s. suggested interval: 10s.
  • monitor β€” performs a detailed status check. suggested minimum timeout: 10s. suggested interval: 10s.
  • meta-data β€” retrieves resource agent metadata (internal use only, bestie, don't touch it). suggested minimum timeout: 5s.

πŸŽ€ EXAMPLE CRM SHELL πŸŽ€

here's an example config for an EvmsSCC resource using the crm(8) shell β€” copy it exactly, character for character, because we do not freestyle configs:

primitive p_EvmsSCC ocf:heartbeat:EvmsSCC \
  op monitor depth="0" timeout="10s" interval="10s"

πŸ¦‹ EXAMPLE PCS πŸ¦‹

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

pcs resource create p_EvmsSCC ocf:heartbeat:EvmsSCC \
  op monitor OCF_CHECK_LEVEL="0" timeout="10s" interval="10s"

not the depth="0" vs OCF_CHECK_LEVEL="0" difference btw β€” different tools, different syntax, same energy. iconic behavior. πŸ‘‘


🌈 SEE ALSO 🌈


πŸ’œ AUTHOR πŸ’œ

ClusterLabs contributors β€” see the resource agent source for information about individual authors. (group project, group credit, we love to see it. 🫢)


and that's the whole page, bestie! πŸ’– this was the resource-agents UNKNOWN version, dated 04/08/2026 β€” so like, if you're reading this from the future, hi, hope EVMS got a nice retirement party. πŸŽ‰ periodt. ✨

πŸ“¦ where this page comes from