OCF_HEARTBEAT_AZURE-EVENTS(7)

💫 ocf_heartbeat_azure-events — the manual, but make it make sense

okay bestie, you found the OCF_HEARTBEAT_AZURE() page and honestly? it's giving "your Azure VM is about to get yeeted for maintenance and we're gonna handle it gracefully." let's get into it 🫶

---

✨ NAME ✨

ocf_heartbeat_azure-events — a Microsoft Azure Scheduled Events monitoring agent. yes, it's a whole vibe, and its job is to keep an eye on Azure's maintenance moods 💅

---

🌸 SYNOPSIS 🌸

azure-events [start | stop | monitor | meta-data | validate-all]

---

🦋 DESCRIPTION 🦋

so basically: this resource agent is a monitor for scheduled (maintenance) events on a Microsoft Azure VM. Azure is out here scheduling stuff, and this agent is the friend who checks the group chat and tells everyone what's going down 👀

If any relevant events are found, it moves all Pacemaker resources away from the affected node, so the machine can shut down gracefully. no chaos, no drama, just a clean exit. iconic.

Usage:

[OCF_RESKEY_eventTypes=VAL] [OCF_RESKEY_verbose=VAL] azure-events ACTION

• action (required): Supported values: monitor, help, meta-data
• eventTypes (optional): a comma-separated list of event types the resource agent should consider relevant. Supported values: Freeze,Reboot,Redeploy. Default = Reboot,Redeploy
• verbose (optional): if set to true, it displays debug info. Default = false

Deployment:

crm configure primitive rsc_azure-events ocf:heartbeat:azure-events params eventTypes=Reboot,Redeploy verbose=false op monitor interval=10s crm configure clone cln_azure-events rsc_azure-events

for further information on Microsoft Azure Scheduled Events, please refer to the following documentation:

https://docs.microsoft.com/en-us/azure/virtual-machines/linux/scheduled-events

---

💖 SUPPORTED PARAMETERS 💖

• eventTypes — a comma-separated list of event types that will be handled by this resource agent. (Possible values: Freeze,Reboot,Redeploy)

(optional, string, default "Reboot,Redeploy")

• verbose — set to true to enable verbose logging

(optional, boolean, default false)

---

👑 SUPPORTED ACTIONS 👑

this resource agent supports the following actions (operations):

• start — starts the resource. Suggested minimum timeout: 10s.
• stop — stops the resource. Suggested minimum timeout: 10s.
• validate-all — performs a validation of the resource configuration. Suggested minimum timeout: 20s.
• monitor — performs a detailed status check. Suggested minimum timeout: 240s. Suggested interval: 10s.
• meta-data — retrieves resource agent metadata (internal use only). Suggested minimum timeout: 10s.

---

🎀 EXAMPLE CRM SHELL 🎀

here's an example configuration for an azure-events resource using the crm(8) shell:

primitive p_azure-events ocf:heartbeat:azure-events \
  op monitor timeout="240s" interval="10s"

---

🌈 EXAMPLE PCS 🌈

and here's the same energy for an azure-events resource using pcs(8):

pcs resource create p_azure-events ocf:heartbeat:azure-events \
  op monitor timeout="240s" interval="10s"

---

💜 SEE ALSO 💜

http://clusterlabs.org/

---

🌟 AUTHOR 🌟

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

---

ngl bestie, if you made it this far, you're lowkey a cluster legend. no cap 💅

mwah 💋 that's the OCF_HEARTBEAT_AZURE() manual — stay slaying, and may your nodes always migrate before Azure does its thing ✨🦋