OCF_HEARTBEAT_GCP-V(7)

📦
version 4.18.0+git105.9ea1183 · 13 versions
, in opensuse-leap 16.0

💅 OCF_HEARTBEAT_GCP-V(7) — like, the whole manual page, bestie

okay so welcome to ocf_heartbeat_gcp-vpc-move-vip, from the OCF_HEARTBEAT_GCP-V(7) manual, no cap. this is the resource agent that moves a floating IP around on Google Cloud Platform, and honestly? it ate. let's get into it 🫶

✨ NAME ✨

ocf_heartbeat_gcp-vpc-move-vip — Floating IP Address or Range on Google Cloud Platform. that's the whole vibe 💖

✨ SYNOPSIS ✨

gcp-vpc-move-vip [start | stop | monitor | meta-data | validate-all]

like, those are your five actions, periodt.

🦋 DESCRIPTION 🦋

Floating IP Address or Range on Google Cloud Platform — and the way it does it is so clever: it uses Alias IP address functionality to attach a secondary IP range to a running instance. literally attaching extra IPs to something that's already up. iconic behavior ngl ✨

🌸 SUPPORTED PARAMETERS 🌸

aka the knobs you can turn, bestie, pay attention 📝

  • alias_ip — the IP range you wanna add, including the CIDR netmask (e.g., 192.168.0.1/32).
heads up: this one is unique, required, string, and has no default. so yeah, you HAVE to set it. no skipping 🙈
  • alias_range_name — the Subnet name for the Alias IP.

(optional, string, no default)

  • hostlist — List of hosts in the cluster, separated by spaces.

(optional, string, no default)

  • project — Project ID of the instance. It can be useful to set this attribute if the instance is in a shared service project. Otherwise, the agent should be able to determine the project ID automatically.

(optional, string, default "default")

  • serviceaccount — Path to Service account JSON file.

(optional, string, no default)

  • stackdriver_logging — If enabled (set to true), IP failover logs will be posted to stackdriver logging.

(optional, boolean, default false)

🎀 SUPPORTED ACTIONS 🎀

This resource agent supports the following actions (operations) — and yes, the timeouts are real, don't come for me:

  • start — Starts the resource. Suggested minimum timeout: 300s. (yeah she's a slow starter, give her three hundred seconds, she's worth it 💅)
  • stop — Stops the resource. Suggested minimum timeout: 15s.
  • monitor — Performs a detailed status check. Suggested minimum timeout: 15s. Suggested interval: 60s.
  • meta-data — Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 15s.
  • validate-all — Performs a validation of the resource configuration. Suggested minimum timeout: 15s.

🧚 EXAMPLE CRM SHELL 🧚

The following is an example configuration for a gcp-vpc-move-vip resource using the crm(8) shell:

primitive p_gcp-vpc-move-vip ocf:heartbeat:gcp-vpc-move-vip \
  params \
    alias_ip=string \
  op monitor timeout="15s" interval="60s" depth="0"

copy it, paste it, slay it 💖

🔥 EXAMPLE PCS 🔥

The following is an example configuration for a gcp-vpc-move-vip resource using pcs(8):

pcs resource create p_gcp-vpc-move-vip ocf:heartbeat:gcp-vpc-move-vip \
  alias_ip=string \
  op monitor timeout="15s" interval="60s" OCF_CHECK_LEVEL="0"

note the OCF_CHECK_LEVEL="0" instead of depth="0" — different tool, different syntax, iykyk 👑

🌈 SEE ALSO 🌈

💜 AUTHOR 💜

ClusterLabs contributors (see the resource agent source for information about individual authors). love that for them, truly a group project that got an A 🫶

and that's the whole page, bestie. no details left behind, we keep it thorough around here 💅

sign-off time: this gem comes from resource-agents (version UNKNOWN, yeah they never told us 😭) and the page is dated 10/01/2026. mwah 💋 🎀

📦 where this page comes from