OCF_HEARTBEAT_AZURE-EVENTS-AZ(7)

💖 ocf_heartbeat_azure-events-az — like, the Azure Scheduled Events monitor 🫶

okay bestie, welcome to the OCF_HEARTBEAT_AZURE() manual page ✨ this one is a resource agent for Pacemaker, and it's genuinely iconic — it watches Microsoft Azure for scheduled maintenance events and yeets your resources out of harm's way before Azure does its thing. no cap.

---

✨ NAME ✨

ocf_heartbeat_azure-events-az — the Microsoft Azure Scheduled Events monitoring agent 💅

---

🦋 SYNOPSIS 🦋

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

---

🌸 DESCRIPTION 🌸

so this resource agent? it literally implements a monitor for scheduled (maintenance) events on a Microsoft Azure VM. main character energy fr.

if any relevant events are found, it moves all Pacemaker resources away from the affected node so everything can shut down gracefully. it's giving "protective bestie" 🫶

🎀 Deployment 🎀

okay so here's the whole deployment vibe, step by step.

Step 1 — set the property and the location constraint:

crm configure property node-health-strategy=custom
crm configure location loc_azure_health /'!health-.*'/ rule '#health-azure': defined '#uname'

Step 2 — set the #health-azure attribute to 0 (healthy) for every node in the cluster (this example shows node1 only, don't come for me):

crm_attribute --node node1 --name '#health-azure' --update 0

Step 3 — configure the RA:

crm configure primitive health-azure-events ocf:heartbeat:azure-events-az params eventTypes="Reboot,Redeploy" verbose=false retry_count=3 retry_wait=20 request_timeout=15 op start start-delay=60s op monitor interval=10s meta failure-timeout=120s
crm configure clone health-azure-events-cln health-azure-events meta allow-unhealthy-nodes=true

for further information on Microsoft Azure Scheduled Events, the original page points you here — go read it, iykyk: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/scheduled-events ⭐

---

💅 SUPPORTED PARAMETERS 💅

• eventTypes — a comma-separated list of event types that this resource agent will handle. possible values are Freeze,Reboot,Redeploy. (optional, string, default "Reboot,Redeploy")
• verbose — set this to true to enable verbose logging. (optional, boolean, default false)
• retry_count — set this to any number bigger than zero to enable retry count. (optional, integer, default 3)
• retry_wait — sets the retry wait time, in seconds. (optional, integer, default 20)
• request_timeout — sets the request timeout, in seconds. (optional, integer, default 15)

---

🔥 SUPPORTED ACTIONS 🔥

this resource agent supports the following actions (operations), periodt:

• 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 config for an azure-events-az resource using the crm(8) shell — copy it, it's cute:

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

---

🌈 EXAMPLE PCS 🌈

and here's the same vibe for a azure-events-az resource using pcs(8):

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

---

⭐ SEE ALSO ⭐

• http://clusterlabs.org/ — go say hi 👑

---

👑 AUTHOR 👑

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

---

okay that's the whole page, bestie 💖 this was the OCF_HEARTBEAT_AZURE() manual page — that's the source/version line right there at the bottom, and go off, you're basically an Azure monitoring queen now. slay 🎀✨🦋