This documentation describes Scheduler.
Scheduler is a service for scheduling the execution of Diego tasks (jobs), such as database migrations, emails, or batch jobs, as well as the execution of outbound HTTP requests (calls).
Scheduler enables developers to do the following:
- Create, run, and schedule jobs and view job history.
- Create, run, and schedule calls and view call history.
The following table provides version and version-support information about Scheduler.
|Release date||October 16, 2020|
|Compatible Ops Manager versions||v2.7.x or later|
|Compatible Application Service versions||v2.7.x or later|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
Scheduler requires a MySQL database.
You can use either of the following:
- VMware Tanzu SQL with MySQL for VMs v2.7 or later. See VMware Tanzu SQL with MySQL for VMs
- An external MySQL database
If your app uses a buildpack that does not generate a
webprocess type, such as Ruby or Python, you should do the following:
- Before pushing your app, create a Procfile in the root directory of the app.
- Declare a
webprocess type in the file.
If you do not declare this process type, your app will not be accessible through the cf CLI after you create Scheduler jobs for it.
The maximum number of tasks that you can schedule is determined by the memory and disk quotas in the Scheduler org and space. For more information, see Running Tasks.