VMware Tanzu Scheduler is a scheduler service exposed as a service broker in the VMware Marketplace. App developers use Scheduler to create, schedule, and interact with jobs that execute on VMware Tanzu Application Service. It allows scheduling the execution of Diego tasks (jobs), such as database migrations, emails, or batch jobs, and the execution of outbound HTTP requests (calls).
You can:
- Create jobs to execute tasks (Diego tasks).
- Execute jobs on an ad hoc basis.
- Schedule jobs to execute on a recurring basis.
- View job status and history.
You can interact with the service by using the Cloud Foundry Command Line Interface (cf CLI), Apps Manager, and the Scheduler HTTP API.
Product snapshot
The following table provides version and version-support information about Scheduler.
| Element | Details |
|---|---|
| Version | v2.0.9 |
| Release date | Jul 5, 2024 |
| Compatible VMware Tanzu Operations Manager versions | v2.10 or later |
| Compatible Tanzu Application Service versions | v2.11 or later |
| IaaS support | AWS, Azure, GCP, OpenStack, and vSphere |
Requirements
Scheduler requires a MySQL database.
You can use either of the following:
- VMware Tanzu SQL with MySQL for VMs v3.0 or later. In addition, you must choose the MySQL 8.0 option. See VMware Tanzu SQL with MySQL for VMs
- An external MySQL v8.0 or later database
Limitations
-
If your app uses a buildpack that does not generate a
webprocess type, such as Ruby or Python, you should do the following:- Create a Procfile in the root directory of the app before pushing it.
- Declare a
webprocess type in the file.
If you do not declare this process type, your app is not accessible when using the cf CLI after you create Scheduler jobs for it.
-
The maximum number of tasks that you can schedule is determined by the memory, disk, and log rate quotas in the Scheduler org and space. For more information, see Running tasks.
