3030public final class BackendServiceHAPolicy extends com .google .api .client .json .GenericJson {
3131
3232 /**
33- * Enabling fastIPMove is not supported.
33+ * Specifies whether fast IP move is enabled, and if so, the mechanism to achieve it. Supported
34+ * values are: - DISABLED: Fast IP Move is disabled. You can only use the haPolicy.leader API to
35+ * update the leader. - >GARP_RA: Provides a method to very quickly define a new network endpoint
36+ * as the leader. This method is faster than updating the leader using the haPolicy.leader API.
37+ * Fast IP move works as follows: The VM hosting the network endpoint that should become the new
38+ * leader sends either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router Advertisement(RA)
39+ * packet (IPv6). Google Cloud immediately but temporarily associates the forwarding rule IP
40+ * address with that VM, and both new and in-flight packets are quickly delivered to that VM. Note
41+ * the important properties of the Fast IP Move functionality: - The GARP/RA-initiated re-routing
42+ * stays active for approximately 20 minutes. After triggering fast failover, you must also
43+ * appropriately set the haPolicy.leader. - The new leader instance should continue to send
44+ * GARP/RA packets periodically every 10 seconds until at least 10 minutes after updating the
45+ * haPolicy.leader (but stop immediately if it is no longer the leader). - After triggering a fast
46+ * failover, we recommend that you wait at least 3 seconds before sending another GARP/RA packet
47+ * from a different VM instance to avoid race conditions. - Don't send GARP/RA packets from
48+ * different VM instances at the same time. If multiple instances continue to send GARP/RA
49+ * packets, traffic might be routed to different destinations in an alternating order. This
50+ * condition ceases when a single instance issues a GARP/RA packet. - The GARP/RA request always
51+ * takes priority over the leader API. Using the haPolicy.leader API to change the leader to a
52+ * different instance will have no effect until the GARP/RA request becomes inactive. - The
53+ * GARP/RA packets should follow the GARP/RA Packet Specifications.. - When multiple forwarding
54+ * rules refer to a regional backend service, you need only send a GARP or RA packet for a single
55+ * forwarding rule virtual IP. The virtual IPs for all forwarding rules targeting the same backend
56+ * service will also be moved to the sender of the GARP or RA packet. The following are the Fast
57+ * IP Move limitations (that is, when fastIPMove is not DISABLED): - Multiple forwarding rules
58+ * cannot use the same IP address if one of them refers to a regional backend service with
59+ * fastIPMove. - The regional backend service must set the network field, and all NEGs must belong
60+ * to that network. However, individual NEGs can belong to different subnetworks of that network.
61+ * - The maximum number of network endpoints across all backends of a backend service with
62+ * fastIPMove is 64. - The maximum number of backend services with fastIPMove that can have the
63+ * same network endpoint attached to one of its backends is 64. - The maximum number of backend
64+ * services with fastIPMove in a VPC in a region is 64. - The network endpoints that are attached
65+ * to a backend of a backend service with fastIPMove cannot resolve to C3 machines. - Traffic
66+ * directed to the leader by a static route next hop will not be redirected to a new leader by
67+ * fast failover. Such traffic will only be redirected once an haPolicy.leader update has taken
68+ * effect. Only traffic to the forwarding rule's virtual IP will be redirected to a new leader by
69+ * fast failover. haPolicy.fastIPMove can be set only at backend service creation time. Once set,
70+ * it cannot be updated. By default, fastIpMove is set to DISABLED.
3471 * The value may be {@code null}.
3572 */
3673 @ com .google .api .client .util .Key
3774 private java .lang .String fastIPMove ;
3875
3976 /**
40- * Setting a leader is not supported.
77+ * Selects one of the network endpoints attached to the backend NEGs of this service as the active
78+ * endpoint (the leader) that receives all traffic. When the leader changes, there is no
79+ * connection draining to persist existing connections on the old leader. You are responsible for
80+ * selecting a suitable endpoint as the leader. For example, preferring a healthy endpoint over
81+ * unhealthy ones. Note that this service does not track backend endpoint health, and selects the
82+ * configured leader unconditionally.
4183 * The value may be {@code null}.
4284 */
4385 @ com .google .api .client .util .Key
4486 private BackendServiceHAPolicyLeader leader ;
4587
4688 /**
47- * Enabling fastIPMove is not supported.
89+ * Specifies whether fast IP move is enabled, and if so, the mechanism to achieve it. Supported
90+ * values are: - DISABLED: Fast IP Move is disabled. You can only use the haPolicy.leader API to
91+ * update the leader. - >GARP_RA: Provides a method to very quickly define a new network endpoint
92+ * as the leader. This method is faster than updating the leader using the haPolicy.leader API.
93+ * Fast IP move works as follows: The VM hosting the network endpoint that should become the new
94+ * leader sends either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router Advertisement(RA)
95+ * packet (IPv6). Google Cloud immediately but temporarily associates the forwarding rule IP
96+ * address with that VM, and both new and in-flight packets are quickly delivered to that VM. Note
97+ * the important properties of the Fast IP Move functionality: - The GARP/RA-initiated re-routing
98+ * stays active for approximately 20 minutes. After triggering fast failover, you must also
99+ * appropriately set the haPolicy.leader. - The new leader instance should continue to send
100+ * GARP/RA packets periodically every 10 seconds until at least 10 minutes after updating the
101+ * haPolicy.leader (but stop immediately if it is no longer the leader). - After triggering a fast
102+ * failover, we recommend that you wait at least 3 seconds before sending another GARP/RA packet
103+ * from a different VM instance to avoid race conditions. - Don't send GARP/RA packets from
104+ * different VM instances at the same time. If multiple instances continue to send GARP/RA
105+ * packets, traffic might be routed to different destinations in an alternating order. This
106+ * condition ceases when a single instance issues a GARP/RA packet. - The GARP/RA request always
107+ * takes priority over the leader API. Using the haPolicy.leader API to change the leader to a
108+ * different instance will have no effect until the GARP/RA request becomes inactive. - The
109+ * GARP/RA packets should follow the GARP/RA Packet Specifications.. - When multiple forwarding
110+ * rules refer to a regional backend service, you need only send a GARP or RA packet for a single
111+ * forwarding rule virtual IP. The virtual IPs for all forwarding rules targeting the same backend
112+ * service will also be moved to the sender of the GARP or RA packet. The following are the Fast
113+ * IP Move limitations (that is, when fastIPMove is not DISABLED): - Multiple forwarding rules
114+ * cannot use the same IP address if one of them refers to a regional backend service with
115+ * fastIPMove. - The regional backend service must set the network field, and all NEGs must belong
116+ * to that network. However, individual NEGs can belong to different subnetworks of that network.
117+ * - The maximum number of network endpoints across all backends of a backend service with
118+ * fastIPMove is 64. - The maximum number of backend services with fastIPMove that can have the
119+ * same network endpoint attached to one of its backends is 64. - The maximum number of backend
120+ * services with fastIPMove in a VPC in a region is 64. - The network endpoints that are attached
121+ * to a backend of a backend service with fastIPMove cannot resolve to C3 machines. - Traffic
122+ * directed to the leader by a static route next hop will not be redirected to a new leader by
123+ * fast failover. Such traffic will only be redirected once an haPolicy.leader update has taken
124+ * effect. Only traffic to the forwarding rule's virtual IP will be redirected to a new leader by
125+ * fast failover. haPolicy.fastIPMove can be set only at backend service creation time. Once set,
126+ * it cannot be updated. By default, fastIpMove is set to DISABLED.
48127 * @return value or {@code null} for none
49128 */
50129 public java .lang .String getFastIPMove () {
51130 return fastIPMove ;
52131 }
53132
54133 /**
55- * Enabling fastIPMove is not supported.
134+ * Specifies whether fast IP move is enabled, and if so, the mechanism to achieve it. Supported
135+ * values are: - DISABLED: Fast IP Move is disabled. You can only use the haPolicy.leader API to
136+ * update the leader. - >GARP_RA: Provides a method to very quickly define a new network endpoint
137+ * as the leader. This method is faster than updating the leader using the haPolicy.leader API.
138+ * Fast IP move works as follows: The VM hosting the network endpoint that should become the new
139+ * leader sends either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router Advertisement(RA)
140+ * packet (IPv6). Google Cloud immediately but temporarily associates the forwarding rule IP
141+ * address with that VM, and both new and in-flight packets are quickly delivered to that VM. Note
142+ * the important properties of the Fast IP Move functionality: - The GARP/RA-initiated re-routing
143+ * stays active for approximately 20 minutes. After triggering fast failover, you must also
144+ * appropriately set the haPolicy.leader. - The new leader instance should continue to send
145+ * GARP/RA packets periodically every 10 seconds until at least 10 minutes after updating the
146+ * haPolicy.leader (but stop immediately if it is no longer the leader). - After triggering a fast
147+ * failover, we recommend that you wait at least 3 seconds before sending another GARP/RA packet
148+ * from a different VM instance to avoid race conditions. - Don't send GARP/RA packets from
149+ * different VM instances at the same time. If multiple instances continue to send GARP/RA
150+ * packets, traffic might be routed to different destinations in an alternating order. This
151+ * condition ceases when a single instance issues a GARP/RA packet. - The GARP/RA request always
152+ * takes priority over the leader API. Using the haPolicy.leader API to change the leader to a
153+ * different instance will have no effect until the GARP/RA request becomes inactive. - The
154+ * GARP/RA packets should follow the GARP/RA Packet Specifications.. - When multiple forwarding
155+ * rules refer to a regional backend service, you need only send a GARP or RA packet for a single
156+ * forwarding rule virtual IP. The virtual IPs for all forwarding rules targeting the same backend
157+ * service will also be moved to the sender of the GARP or RA packet. The following are the Fast
158+ * IP Move limitations (that is, when fastIPMove is not DISABLED): - Multiple forwarding rules
159+ * cannot use the same IP address if one of them refers to a regional backend service with
160+ * fastIPMove. - The regional backend service must set the network field, and all NEGs must belong
161+ * to that network. However, individual NEGs can belong to different subnetworks of that network.
162+ * - The maximum number of network endpoints across all backends of a backend service with
163+ * fastIPMove is 64. - The maximum number of backend services with fastIPMove that can have the
164+ * same network endpoint attached to one of its backends is 64. - The maximum number of backend
165+ * services with fastIPMove in a VPC in a region is 64. - The network endpoints that are attached
166+ * to a backend of a backend service with fastIPMove cannot resolve to C3 machines. - Traffic
167+ * directed to the leader by a static route next hop will not be redirected to a new leader by
168+ * fast failover. Such traffic will only be redirected once an haPolicy.leader update has taken
169+ * effect. Only traffic to the forwarding rule's virtual IP will be redirected to a new leader by
170+ * fast failover. haPolicy.fastIPMove can be set only at backend service creation time. Once set,
171+ * it cannot be updated. By default, fastIpMove is set to DISABLED.
56172 * @param fastIPMove fastIPMove or {@code null} for none
57173 */
58174 public BackendServiceHAPolicy setFastIPMove (java .lang .String fastIPMove ) {
@@ -61,15 +177,25 @@ public BackendServiceHAPolicy setFastIPMove(java.lang.String fastIPMove) {
61177 }
62178
63179 /**
64- * Setting a leader is not supported.
180+ * Selects one of the network endpoints attached to the backend NEGs of this service as the active
181+ * endpoint (the leader) that receives all traffic. When the leader changes, there is no
182+ * connection draining to persist existing connections on the old leader. You are responsible for
183+ * selecting a suitable endpoint as the leader. For example, preferring a healthy endpoint over
184+ * unhealthy ones. Note that this service does not track backend endpoint health, and selects the
185+ * configured leader unconditionally.
65186 * @return value or {@code null} for none
66187 */
67188 public BackendServiceHAPolicyLeader getLeader () {
68189 return leader ;
69190 }
70191
71192 /**
72- * Setting a leader is not supported.
193+ * Selects one of the network endpoints attached to the backend NEGs of this service as the active
194+ * endpoint (the leader) that receives all traffic. When the leader changes, there is no
195+ * connection draining to persist existing connections on the old leader. You are responsible for
196+ * selecting a suitable endpoint as the leader. For example, preferring a healthy endpoint over
197+ * unhealthy ones. Note that this service does not track backend endpoint health, and selects the
198+ * configured leader unconditionally.
73199 * @param leader leader or {@code null} for none
74200 */
75201 public BackendServiceHAPolicy setLeader (BackendServiceHAPolicyLeader leader ) {
0 commit comments