Compute V1 Client - Class InstanceGroupManagersClient (1.20.0)

Reference documentation and code samples for the Compute V1 Client class InstanceGroupManagersClient.

Service Description: The InstanceGroupManagers API.

This class provides the ability to make remote calls to the backing service through method calls that map to API methods.

Constructor.

Flags the specified instances to be removed from the managed instance group. Abandoning an instance does not delete the instance, but it does remove the instance from any target pools that are applied by the managed instance group. This method reduces the targetSize of the managed instance group by the number of instances that you abandon. This operation is marked as DONE when the action is scheduled even if the instances have not yet been removed from the group. You must separately verify the status of the abandoning action with the listmanagedinstances method. If the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted. You can specify a maximum of 1000 instances with this method per request.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::abandonInstancesAsync() .

Retrieves the list of managed instance groups and groups them by zone. To prevent failure, Google recommends that you set the returnPartialSuccess parameter to true.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::aggregatedListAsync() .

Applies changes to selected instances on the managed instance group. This method can be used to apply new overrides and/or new versions.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::applyUpdatesToInstancesAsync() .

Creates instances with per-instance configurations in this managed instance group. Instances are created using the current instance template. The create instances operation is marked DONE if the createInstances request is successful. The underlying actions take additional time. You must separately verify the status of the creating or actions with the listmanagedinstances method.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::createInstancesAsync() .

Deletes the specified managed instance group and all of the instances in that group. Note that the instance group must not belong to a backend service. Read Deleting an instance group for more information.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::deleteAsync() .

Flags the specified instances in the managed instance group for immediate deletion. The instances are also removed from any target pools of which they were a member. This method reduces the targetSize of the managed instance group by the number of instances that you delete. This operation is marked as DONE when the action is scheduled even if the instances are still being deleted. You must separately verify the status of the deleting action with the listmanagedinstances method. If the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted. You can specify a maximum of 1000 instances with this method per request.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::deleteInstancesAsync() .

Deletes selected per-instance configurations for the managed instance group.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::deletePerInstanceConfigsAsync() .

Returns all of the details about the specified managed instance group.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::getAsync() .

Creates a managed instance group using the information that you specify in the request. After the group is created, instances in the group are created using the specified instance template. This operation is marked as DONE when the group is created even if the instances in the group have not yet been created. You must separately verify the status of the individual instances with the listmanagedinstances method. A managed instance group can have up to 1000 VM instances per group. Please contact Cloud Support if you need an increase in this limit.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::insertAsync() .

Retrieves a list of managed instance groups that are contained within the specified project and zone.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::listAsync() .

Lists all errors thrown by actions on instances for a given managed instance group. The filter and orderBy query parameters are not supported.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::listErrorsAsync() .

Lists all of the instances in the managed instance group. Each instance in the list has a currentAction, which indicates the action that the managed instance group is performing on the instance. For example, if the group is still creating an instance, the currentAction is CREATING. If a previous action failed, the list displays the errors for that failed action. The orderBy query parameter is not supported. The pageToken query parameter is supported only if the group's listManagedInstancesResults field is set to PAGINATED.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::listManagedInstancesAsync() .

Lists all of the per-instance configurations defined for the managed instance group. The orderBy query parameter is not supported.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::listPerInstanceConfigsAsync() .

Updates a managed instance group using the information that you specify in the request. This operation is marked as DONE when the group is patched even if the instances in the group are still in the process of being patched. You must separately verify the status of the individual instances with the listManagedInstances method. This method supports PATCH semantics and uses the JSON merge patch format and processing rules. If you update your group to specify a new template or instance configuration, it's possible that your intended specification for each VM in the group is different from the current state of that VM. To learn how to apply an updated configuration to the VMs in a MIG, see Updating instances in a MIG.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::patchAsync() .

Inserts or patches per-instance configurations for the managed instance group. perInstanceConfig.name serves as a key used to distinguish whether to perform insert or patch.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::patchPerInstanceConfigsAsync() .

Flags the specified VM instances in the managed instance group to be immediately recreated. Each instance is recreated using the group's current configuration. This operation is marked as DONE when the flag is set even if the instances have not yet been recreated. You must separately verify the status of each instance by checking its currentAction field; for more information, see Checking the status of managed instances. If the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted. You can specify a maximum of 1000 instances with this method per request.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::recreateInstancesAsync() .

Resizes the managed instance group. If you increase the size, the group creates new instances using the current instance template. If you decrease the size, the group deletes instances. The resize operation is marked DONE when the resize actions are scheduled even if the group has not yet added or deleted any instances. You must separately verify the status of the creating or deleting actions with the listmanagedinstances method. When resizing down, the instance group arbitrarily chooses the order in which VMs are deleted. The group takes into account some VM attributes when making the selection including: + The status of the VM instance. + The health of the VM instance. + The instance template version the VM is based on. + For regional managed instance groups, the location of the VM instance. This list is subject to change. If the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::resizeAsync() .

Specifies the instance template to use when creating new instances in this group. The templates for existing instances in the group do not change unless you run recreateInstances, run applyUpdatesToInstances, or set the group's updatePolicy.type to PROACTIVE.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::setInstanceTemplateAsync() .

Modifies the target pools to which all instances in this managed instance group are assigned. The target pools automatically apply to all of the instances in the managed instance group. This operation is marked DONE when you make the request even if the instances have not yet been added to their target pools. The change might take some time to apply to all of the instances in the group depending on the size of the group.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::setTargetPoolsAsync() .

Inserts or updates per-instance configurations for the managed instance group. perInstanceConfig.name serves as a key used to distinguish whether to perform insert or patch.

The async variant is Google\Cloud\Compute\V1\Client\InstanceGroupManagersClient::updatePerInstanceConfigsAsync() .

Return an ZoneOperationsClient object with the same endpoint as $this.

Resume an existing long running operation that was previously started by a long running API method. If $methodName is not provided, or does not match a long running API method, then the operation can still be resumed, but the OperationResponse object will not deserialize the final response.