1OCF_HEARTBEAT_GCP-V(7)        OCF resource agents       OCF_HEARTBEAT_GCP-V(7)
2
3
4

NAME

6       ocf_heartbeat_gcp-vpc-move-route - Move IP within a GCP VPC
7

SYNOPSIS

9       gcp-vpc-move-route [start | stop | monitor | meta-data | validate-all]
10

DESCRIPTION

12       Resource Agent that can move a floating IP addresse within a GCP VPC by
13       changing an entry in the routing table. This agent also configures the
14       floating IP locally on the instance OS. Requirements :
15
16       - IP forwarding must be enabled on all instances in order to be able to
17       terminate the route
18
19       - The floating IP address must be chosen so that it is outside all
20       existing subnets in the VPC network
21
22       - IAM permissions (see
23       https://cloud.google.com/compute/docs/access/iam-permissions) : 1)
24       compute.routes.delete, compute.routes.get and compute.routes.update on
25       the route 2) compute.networks.updatePolicy on the network (to add a new
26       route) 3) compute.networks.get on the network (to check the VPC network
27       existence) 4) compute.routes.list on the project (to check conflicting
28       routes)
29

SUPPORTED PARAMETERS

31       ip
32           Floating IP address. Note that this IP must be chosen outside of
33           all existing subnet ranges
34
35           (unique, required, string, no default)
36
37       vpc_network
38           Name of the VPC network
39
40           (optional, string, default "default")
41
42       project
43           Project ID of the instance. It can be useful to set this attribute
44           if the instance is in a shared service project. Otherwise, the
45           agent should be able to determine the project ID automatically.
46
47           (optional, string, default "default")
48
49       interface
50           Name of the network interface
51
52           (optional, string, default "eth0")
53
54       route_name
55           Route name
56
57           (unique, optional, string, default "ra-gcp-vpc-move-route")
58
59       stackdriver_logging
60           If enabled (set to true), IP failover logs will be posted to
61           stackdriver logging
62
63           (optional, boolean, default false)
64

SUPPORTED ACTIONS

66       This resource agent supports the following actions (operations):
67
68       start
69           Starts the resource. Suggested minimum timeout: 180s.
70
71       stop
72           Stops the resource. Suggested minimum timeout: 180s.
73
74       monitor
75           Performs a detailed status check. Suggested minimum timeout: 30s.
76           Suggested interval: 60s.
77
78       validate-all
79           Performs a validation of the resource configuration. Suggested
80           minimum timeout: 5s.
81
82       meta-data
83           Retrieves resource agent metadata (internal use only). Suggested
84           minimum timeout: 5s.
85

EXAMPLE CRM SHELL

87       The following is an example configuration for a gcp-vpc-move-route
88       resource using the crm(8) shell:
89
90           primitive p_gcp-vpc-move-route ocf:heartbeat:gcp-vpc-move-route \
91             params \
92               ip=string \
93             op monitor depth="0" timeout="30s" interval="60s"
94

EXAMPLE PCS

96       The following is an example configuration for a gcp-vpc-move-route
97       resource using pcs(8)
98
99           pcs resource create p_gcp-vpc-move-route ocf:heartbeat:gcp-vpc-move-route \
100             ip=string \
101             op monitor OCF_CHECK_LEVEL="0" timeout="30s" interval="60s"
102

SEE ALSO

104       http://clusterlabs.org/
105

AUTHOR

107       ClusterLabs contributors (see the resource agent source for information
108       about individual authors)
109
110
111
112resource-agents UNKNOWN           03/25/2021            OCF_HEARTBEAT_GCP-V(7)
Impressum