Scheduler for PCF
This documentation describes Scheduler for Pivotal Cloud Foundry (PCF).
Scheduler for PCF is a service for scheduling the execution of Diego tasks, such as database migrations, emails, or batch jobs, as well as the execution of outbound HTTP calls.
Scheduler for PCF 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 for PCF.
|Release date||July 5, 2018|
|Compatible Ops Manager version(s)||v2.2.x, v2.1.x, v2.0.x, v1.12x, and v1.11.x|
|Compatible Elastic Runtime version(s) *||v1.12.x and v1.11.x|
|Compatible Pivotal Application Service version(s) *||v2.2.x, v2.1.x, and v2.0.x|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
* As of PCF v2.0, Elastic Runtime is renamed to Pivotal Application Service (PAS).
Scheduler for PCF requires a MySQL database.
You can use any of the following:
- The MySQL for PCF v1.10 tile. See MySQL for PCF v1.10.
- The MySQL for PCF v2.x tile. See MySQL for PCF. Pivotal recommends having the MySQL for PCF v2.x tile installed if you are installing Scheduler for PCF v1.2.
- 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 for PCF org and space. For more information, see Running Tasks.