You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 3, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 3, 2021. It is now read-only.
Job and cluster implementations should be aligned to ease transition between the two modes for users. This will also decrease code complexity/duplication and facilitate support.
Currently a cluster is a: Batch pool and job.
A job is a: Batch job schedule with a job specification that has an autopool and predefined Tasks for each application.
Going forward, we should convert clusters to job specifications with autopool. So a cluster will be a job with an empty set of Batch tasks and keep_alive set to True on the autopool specification.
API Changes:
job configuration has a cluster configuration and a list of applications
Refactors:
cluster is implemented as job with keep_alive set to false and no applications defined
Activity
[-]Change Implementation of Jobs[/-][+]Align cluster and job implementations[/+]