Get desktop application:
View/edit binary Protocol Buffers messages
A Job's resource allocation policy describes when, where, and how compute resources should be allocated for the Job.
Used in:
Location where compute resources should be allocated for the Job.
Describe instances that can be created by this AllocationPolicy. Only instances[0] is supported now.
Service account that VMs will run as.
Labels applied to all VM instances and other resources created by AllocationPolicy. Labels could be user provided or system generated. You can assign up to 64 labels. [Google Compute Engine label restrictions](https://cloud.google.com/compute/docs/labeling-resources#restrictions) apply. Label names that start with "goog-" or "google-" are reserved.
The network policy.
The placement policy.
Accelerator describes Compute Engine accelerators to be attached to the VM.
Used in:
The accelerator type. For example, "nvidia-tesla-t4". See `gcloud compute accelerator-types list`.
The number of accelerators of this type.
Deprecated: please use instances[0].install_gpu_drivers instead.
A new or an existing persistent disk (PD) or a local ssd attached to a VM instance.
Used in:
Name of an existing PD.
Device name that the guest operating system will see. It is used by Runnable.volumes field to mount disks. So please specify the device_name if you want Batch to help mount the disk, and it should match the device_name field in volumes.
A new persistent disk or a local ssd. A VM can only have one local SSD setting but multiple local SSD partitions. See https://cloud.google.com/compute/docs/disks#pdspecs and https://cloud.google.com/compute/docs/disks#localssds.
Used in:
, ,A data source from which a PD will be created.
Name of a public or custom image used as the data source. For example, the following are all valid URLs: * Specify the image by its family name: projects/{project}/global/images/family/{image_family} * Specify the image version: projects/{project}/global/images/{image_version} You can also use Batch customized image in short names. The following image values are supported for a boot disk: * "batch-debian": use Batch Debian images. * "batch-centos": use Batch CentOS images. * "batch-cos": use Batch Container-Optimized images. * "batch-hpc-centos": use Batch HPC CentOS images.
Name of a snapshot used as the data source. Snapshot is not supported as boot disk now.
Disk type as shown in `gcloud compute disk-types list`. For example, local SSD uses type "local-ssd". Persistent disks and boot disks use "pd-balanced", "pd-extreme", "pd-ssd" or "pd-standard".
Disk size in GB. For persistent disk, this field is ignored if `data_source` is `image` or `snapshot`. For local SSD, size_gb should be a multiple of 375GB, otherwise, the final size will be the next greater multiple of 375 GB. For boot disk, Batch will calculate the boot disk size based on source image and task requirements if you do not speicify the size. If both this field and the boot_disk_mib field in task spec's compute_resource are defined, Batch will only honor this field.
Local SSDs are available through both "SCSI" and "NVMe" interfaces. If not indicated, "NVMe" will be the default one for local ssds. We only support "SCSI" for persistent disks now.
InstancePolicy describes an instance type and resources attached to each VM created by this InstancePolicy.
Used in:
The Compute Engine machine type.
The minimum CPU platform. See https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform.
The provisioning model.
The accelerators attached to each VM instance.
Boot disk to be created and attached to each VM by this InstancePolicy. Boot disk will be deleted when the VM is deleted. Batch API now only supports booting from image.
Non-boot disks to be attached for each VM created by this InstancePolicy. New disks will be deleted when the VM is deleted.
Either an InstancePolicy or an instance template.
Used in:
InstancePolicy.
Name of an instance template used to create VMs. Named the field as 'instance_template' instead of 'template' to avoid c++ keyword conflict.
Set this field true if users want Batch to help fetch drivers from a third party location and install them for GPUs specified in policy.accelerators or instance_template on their behalf. Default is false.
Used in:
A list of allowed location names represented by internal URLs. Each location can be a region or a zone. Only one region or multiple zones in one region is supported now. For example, ["regions/us-central1"] allow VMs in any zones in region us-central1. ["zones/us-central1-a", "zones/us-central1-c"] only allow VMs in zones us-central1-a and us-central1-c. All locations end up in different regions would cause errors. For example, ["regions/us-central1", "zones/us-central1-a", "zones/us-central1-b", "zones/us-west1-a"] contains 2 regions "us-central1" and "us-west1". An error is expected in this case.
A network interface.
Used in:
The URL of an existing network resource. You can specify the network as a full or partial URL. For example, the following are all valid URLs: * https://www.googleapis.com/compute/v1/projects/{project}/global/networks/{network} * projects/{project}/global/networks/{network} * global/networks/{network}
The URL of an existing subnetwork resource in the network. You can specify the subnetwork as a full or partial URL. For example, the following are all valid URLs: * https://www.googleapis.com/compute/v1/projects/{project}/regions/{region}/subnetworks/{subnetwork} * projects/{project}/regions/{region}/subnetworks/{subnetwork} * regions/{region}/subnetworks/{subnetwork}
Default is false (with an external IP address). Required if no external public IP address is attached to the VM. If no external public IP address, additional configuration is required to allow the VM to access Google Services. See https://cloud.google.com/vpc/docs/configure-private-google-access and https://cloud.google.com/nat/docs/gce-example#create-nat for more information.
NetworkPolicy describes VM instance network configurations.
Used in:
Network configurations.
PlacementPolicy describes a group placement policy for the VMs controlled by this AllocationPolicy.
Used in:
UNSPECIFIED vs. COLLOCATED (default UNSPECIFIED). Use COLLOCATED when you want VMs to be located close to each other for low network latency between the VMs. No placement policy will be generated when collocation is UNSPECIFIED.
When specified, causes the job to fail if more than max_distance logical switches are required between VMs. Batch uses the most compact possible placement of VMs even when max_distance is not specified. An explicit max_distance makes that level of compactness a strict requirement. Not yet implemented
Compute Engine VM instance provisioning model.
Used in:
,Unspecified.
Standard VM.
SPOT VM.
Preemptible VM (PVM). Above SPOT VM is the preferable model for preemptible VM instances: the old preemptible VM model (indicated by this field) is the older model, and has been migrated to use the SPOT model as the underlying technology. This old model will still be supported.
Compute resource requirements
Used in:
The milliCPU count.
Memory in MiB.
Extra boot disk size in MiB for each task.
An Environment describes a collection of environment variables to set when executing Tasks.
Used in:
, ,A map of environment variable names to values.
A map of environment variable names to Secret Manager secret names. The VM will access the named secrets to set the value of each environment variable.
An encrypted JSON dictionary where the key/value pairs correspond to environment variable names and their values.
Used in:
The name of the KMS key that will be used to decrypt the cipher text.
The value of the cipherText response from the `encrypt` method.
Represents a Google Cloud Storage volume.
Used in:
Remote path, either a bucket name or a subdirectory of a bucket, e.g.: bucket_name, bucket_name/subdirectory/
The Cloud Batch Job description.
Used in:
Output only. Job name. For example: "projects/123456/locations/us-central1/jobs/job01".
Output only. A system generated unique ID (in UUID4 format) for the Job.
Priority of the Job. The valid value range is [0, 100). Default value is 0. Higher value indicates higher priority. A job with higher priority value is more likely to run earlier if all other requirements are satisfied.
Required. TaskGroups in the Job. Only one TaskGroup is supported now.
Compute resource allocation for all TaskGroups in the Job.
Labels for the Job. Labels could be user provided or system generated. For example, "labels": { "department": "finance", "environment": "test" } You can assign up to 64 labels. [Google Compute Engine label restrictions](https://cloud.google.com/compute/docs/labeling-resources#restrictions) apply. Label names that start with "goog-" or "google-" are reserved.
Output only. Job status. It is read only for users.
Output only. When the Job was created.
Output only. The last time the Job was updated.
Log preservation policy for the Job.
Notification configurations.
The CloudEvent raised when a Job is created.
The data associated with the event.
The CloudEvent raised when a Job is deleted.
The data associated with the event.
The data within all Job events.
Used in:
,Optional. The Job event payload. Unset for deletion events.
Notification configurations.
Used in:
The Pub/Sub topic where notifications like the job state changes will be published. This topic exist in the same project as the job and billings will be charged to this project. If not specified, no Pub/Sub messages will be sent. Topic format: `projects/{project}/topics/{topic}`.
The attribute requirements of messages to be sent to this Pub/Sub topic. Without this field, no message will be sent.
Message details. Describe the attribute that a message should have. Without specified message attributes, no message will be sent by default.
Used in:
The message type.
The new job state.
The new task state.
The message type.
Used in:
Unspecified.
Notify users that the job state has changed.
Notify users that the task state has changed.
Job status.
Used in:
Job state
Job status events
Aggregated task status for each TaskGroup in the Job. The map key is TaskGroup ID.
The duration of time that the Job spent in status RUNNING.
VM instance status.
Used in:
The Compute Engine machine type.
The VM instance provisioning model.
The max number of tasks can be assigned to this instance type.
The VM boot disk.
Valid Job states.
Used in:
,Job state unspecified.
Job is admitted (validated and persisted) and waiting for resources.
Job is scheduled to run as soon as resource allocation is ready. The resource allocation may happen at a later time but with a high chance to succeed.
Resource allocation has been successful. At least one Task in the Job is RUNNING.
All Tasks in the Job have finished successfully.
At least one Task in the Job has failed.
The Job will be deleted, but has not been deleted yet. Typically this is because resources used by the Job are still being cleaned up.
Aggregated task status for a TaskGroup.
Used in:
Count of task in each state in the TaskGroup. The map key is task state name.
Status of instances allocated for the TaskGroup.
LifecyclePolicy describes how to deal with task failures based on different conditions.
Used in:
Action to execute when ActionCondition is true. When RETRY_TASK is specified, we will retry failed tasks if we notice any exit code match and fail tasks if no match is found. Likewise, when FAIL_TASK is specified, we will fail tasks if we notice any exit code match and retry tasks if no match is found.
Conditions that decide why a task failure is dealt with a specific action.
Action on task failures based on different conditions.
Used in:
Action unspecified.
Action that tasks in the group will be scheduled to re-execute.
Action that tasks in the group will be stopped immediately.
Conditions for actions to deal with task failures.
Used in:
Exit codes of a task execution. If there are more than 1 exit codes, when task executes with any of the exit code in the list, the condition is met and the action will be executed.
LogsPolicy describes how outputs from a Job's Tasks (stdout/stderr) will be preserved.
Used in:
Where logs should be saved.
The path to which logs are saved when the destination = PATH. This can be a local file path on the VM, or under the mount point of a Persistent Disk or Filestore, or a Cloud Storage path.
The destination (if any) for logs.
Used in:
Logs are not preserved.
Logs are streamed to Cloud Logging.
Logs are saved to a file path.
Represents an NFS volume.
Used in:
The IP address of the NFS.
Remote source path exported from the NFS, e.g., "/share".
Runnable describes instructions for executing a specific script or container as part of a Task.
Used in:
The script or container to run.
Container runnable.
Script runnable.
Barrier runnable.
Normally, a non-zero exit status causes the Task to fail. This flag allows execution of other Runnables to continue instead.
This flag allows a Runnable to continue running in the background while the Task executes subsequent Runnables. This is useful to provide services to other Runnables (or to provide debugging support tools like SSH servers).
By default, after a Runnable fails, no further Runnable are executed. This flag indicates that this Runnable must be run even if the Task has already failed. This is useful for Runnables that copy output files off of the VM or for debugging. The always_run flag does not override the Task's overall max_run_duration. If the max_run_duration has expired then no further Runnables will execute, not even always_run Runnables.
Environment variables for this Runnable (overrides variables set for the whole Task or TaskGroup).
Timeout for this Runnable.
Labels for this Runnable.
Barrier runnable blocks until all tasks in a taskgroup reach it.
Used in:
Barriers are identified by their index in runnable list. Names are not required, but if present should be an identifier.
Container runnable.
Used in:
The URI to pull the container image from.
Overrides the `CMD` specified in the container. If there is an ENTRYPOINT (either in the container image or with the entrypoint field below) then commands are appended as arguments to the ENTRYPOINT.
Overrides the `ENTRYPOINT` specified in the container.
Volumes to mount (bind mount) from the host machine files or directories into the container, formatted to match docker run's --volume option, e.g. /foo:/bar, or /foo:/bar:ro
Arbitrary additional options to include in the "docker run" command when running this container, e.g. "--network host".
If set to true, external network access to and from container will be blocked, containers that are with block_external_network as true can still communicate with each other, network cannot be specified in the `container.options` field.
Optional username for logging in to a docker registry. If username matches `projects/*/secrets/*/versions/*` then Batch will read the username from the Secret Manager.
Optional password for logging in to a docker registry. If password matches `projects/*/secrets/*/versions/*` then Batch will read the password from the Secret Manager;
Script runnable.
Used in:
Script file path on the host VM. To specify an interpreter, please add a `#!<interpreter>`(also known as [shebang line](https://en.wikipedia.org/wiki/Shebang_(Unix))) as the first line of the file.(For example, to execute the script using bash, `#!/bin/bash` should be the first line of the file. To execute the script using`Python3`, `#!/usr/bin/env python3` should be the first line of the file.) Otherwise, the file will by default be excuted by `/bin/sh`.
Shell script text. To specify an interpreter, please add a `#!<interpreter>\n` at the beginning of the text.(For example, to execute the script using bash, `#!/bin/bash\n` should be added. To execute the script using`Python3`, `#!/usr/bin/env python3\n` should be added.) Otherwise, the script will by default be excuted by `/bin/sh`.
Carries information about a Google Cloud service account.
Used in:
Email address of the service account. If not specified, the default Compute Engine service account for the project will be used. If instance template is being used, the service account has to be specified in the instance template and it has to match the email field here.
List of scopes to be enabled for this service account on the VM, in addition to the cloud-platform API scope that will be added by default.
Status event
Used in:
Type of the event.
Description of the event.
The time this event occurred.
Task Execution
Task State
This Task Execution field includes detail information for task execution procedures, based on StatusEvent types.
Used in:
When task is completed as the status of FAILED or SUCCEEDED, exit code is for one task execution result, default is 0 as success.
A TaskGroup defines one or more Tasks that all share the same TaskSpec.
Used in:
Output only. TaskGroup name. The system generates this field based on parent Job name. For example: "projects/123456/locations/us-west1/jobs/job01/taskGroups/group01".
Required. Tasks in the group share the same task spec.
Number of Tasks in the TaskGroup. Default is 1.
Max number of tasks that can run in parallel. Default to min(task_count, 1000). Field parallelism must be 1 if the scheduling_policy is IN_ORDER.
Scheduling policy for Tasks in the TaskGroup. The default value is AS_SOON_AS_POSSIBLE.
An array of environment variable mappings, which are passed to Tasks with matching indices. If task_environments is used then task_count should not be specified in the request (and will be ignored). Task count will be the length of task_environments. Tasks get a BATCH_TASK_INDEX and BATCH_TASK_COUNT environment variable, in addition to any environment variables set in task_environments, specifying the number of Tasks in the Task's parent TaskGroup, and the specific Task's index in the TaskGroup (0 through BATCH_TASK_COUNT - 1).
Max number of tasks that can be run on a VM at the same time. If not specified, the system will decide a value based on available compute resources on a VM and task requirements.
When true, Batch will populate a file with a list of all VMs assigned to the TaskGroup and set the BATCH_HOSTS_FILE environment variable to the path of that file. Defaults to false.
When true, Batch will configure SSH to allow passwordless login between VMs running the Batch tasks in the same TaskGroup.
How Tasks in the TaskGroup should be scheduled relative to each other.
Used in:
Unspecified.
Run Tasks as soon as resources are available. Tasks might be executed in parallel depending on parallelism and task_count values.
Run Tasks sequentially with increased task index.
Spec of a task
Used in:
The sequence of scripts or containers to run for this Task. Each Task using this TaskSpec executes its list of runnables in order. The Task succeeds if all of its runnables either exit with a zero status or any that exit with a non-zero status have the ignore_exit_status flag. Background runnables are killed automatically (if they have not already exited) a short time after all foreground runnables have completed. Even though this is likely to result in a non-zero exit status for the background runnable, these automatic kills are not treated as Task failures.
ComputeResource requirements.
Maximum duration the task should run. The task will be killed and marked as FAILED if over this limit.
Maximum number of retries on failures. The default, 0, which means never retry. The valid value range is [0, 10].
Lifecycle management schema when any task in a task group is failed. Currently we only support one lifecycle policy. When the lifecycle policy condition is met, the action in the policy will execute. If task execution result does not meet with the defined lifecycle policy, we consider it as the default policy. Default policy means if the exit code is 0, exit task. If task ends with non-zero exit code, retry the task with max_retry_count.
Deprecated: please use environment(non-plural) instead.
Volumes to mount before running Tasks using this TaskSpec.
Environment variables to set before running the Task.
Status of a task
(message has no fields)
Task states.
Used in:
,Unknown state.
The Task is created and waiting for resources.
The Task is assigned to at least one VM.
The Task is running.
The Task has failed.
The Task has succeeded.
The Task has not been executed when the Job finishes.
Volume describes a volume and parameters for it to be mounted to a VM.
Used in:
The source for the volume.
A Network File System (NFS) volume. For example, a Filestore file share.
A Google Cloud Storage (GCS) volume.
Device name of an attached disk volume, which should align with a device_name specified by job.allocation_policy.instances[0].policy.disks[i].device_name or defined by the given instance template in job.allocation_policy.instances[0].instance_template.
The mount path for the volume, e.g. /mnt/disks/share.
For Google Cloud Storage (GCS), mount options are the options supported by the gcsfuse tool (https://github.com/GoogleCloudPlatform/gcsfuse). For existing persistent disks, mount options provided by the mount command (https://man7.org/linux/man-pages/man8/mount.8.html) except writing are supported. This is due to restrictions of multi-writer mode (https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms). For other attached disks and Network File System (NFS), mount options are these supported by the mount command (https://man7.org/linux/man-pages/man8/mount.8.html).