Google Batch is a fully managed service for servicing, queuing, and executing batch processing workloads on Google Cloud resources. It eliminates the need to configure third-party job schedulers or manage resource provisioning across zones. By defining resource parameters for your workload, Batch acquires and queues resources for job execution. Native integration with Google Cloud services streamlines scheduling, execution, storage, and analysis of batch jobs, allowing you to prioritize job submission and result consumption.
Connecting to Google Batch with HCL Workload Automation will help empower your environment. The Google Batch plug-in is available on Automation Hub. After downloading it, log in to the Dynamic Workload Console and go to the Workload Designer. Create a new job and select “Google Batch” in the Cloud section.
Connecting to the server
To begin, connect to the Google Cloud server. To do this, you have two options under the Connection tab:
1. GCP Default Credentials: If the VM is already located within the GCP environment, you can select this option since no explicit credentials are required.
2. GCP Server Credentials: By choosing this option, you can manually enter the project ID and the GCS account. (a unique name associated with each project).
By choosing Test Connection, you can check your Google Cloud connection.
Use this section to define options for GCP cloud batch function.
You can choose to make a batch using a script or container, delete an existing job, or both. To create a job, you have two options. Create a job using script or create a job using container.
How to create a job
You can select the “Create Job” to create a job,
Job Name: Enter the Job name.
Machine type: Machine Type must be defined in Google Cloud Batch Machines which are defined in Google Cloud Batch documentation.
Script: You can see the text area where you can input the script once you choose the “Script” radio button, provided that all relevant fields are enabled. while keeping the Container task’s associated fields enabled.
Task Count: Enter the total number of tasks. Must be a whole number between 1 and 10,000.
Task Parallelism: Enter the number of tasks you want to run at the same time. This must be a whole number between 1 and 1,000.
Task VCPUs: Enter between 0.5 and 224 vCPUs
Task Memory: Enter between 0.5 and 896 GB
Note: Job name, Machine type, taskCount, taskParallelism, task CPUs, task and Memory fields are mandatory fields
You can select the “Container” radio button to enable all the required fields, while keeping the fields related to the Script task disabled.
Containerimage URL: Enter your image URL from a public registry or use a private image hosted on the Google Container Registry.
Entry Point: Specify the command that have to run instead of your container’s entrypoint command.
Containterimage command: Enter the command to be run in place of the CMD command for your container image.
Note: It is not recommended to specify “zero” in the TaskCount, TaskParallelism, Task CPUs, or TtaskMemory columns.
Save Function Output to File
Select the check box to save the function output.
Output File Path: Provide the location to save the function output files.
Submitting your job
Add the job to the job stream that automates your business process flow. Select the action menu in the top-left corner of the job definition panel and click Submit Job into Current Plan. A confirmation message is displayed, and you can switch to the Monitoring view to see what is going on.