ID of the document to mount.
Path where the input document will be mounted inside the job. Interpreted relative to /parcel/data/in.
Documents that were accessed by the job. Includes both the prespecified
JobSpec.input_documents as well as any dynamically accessed documents.
Documents that were generated by the job and uploaded by the Parcel Worker.
A specification/manifest for the job. This is a complete description of what and how the job should run.
The command-line arguments to the command that should be run to start the
job. This corresponds to CMD in Docker terminology; note that images
running on Parcel are required to have a non-empty ENTRYPOINT, so the
actual command that runs will be the
concatenation
of ENTRYPOINT and this field.
The (fractional) number of cpus requested to run the job. This is clamped by a per-worker maximum.
Environment variables to use when running the image. Setting PATH is
not allowed.
The name of the docker image to use, optionally prefixed with an image repository hostname. See docker pull documentation for a full description of allowable formats.
Documents to download and mount into the job's container before cmd runs.
If any of these documents do not exist or you do not have permission to access them, the job will fail.
The amount of memory requested to run the job. This is clamped by a per-worker
maximum. Memory limit (format:
A human-readable name for the job. Intended to help with monitoring and debugging. The name SHOULD be unique among jobs submitted by the same user.
IP addresses (or CIDR-style masks) to which a job can open a connection during execution, e.g. 192.168.1.1/24, or 2001:db9::/64.
Files to be uploaded from the job's container as documents after cmd runs.
Files that do not exist will be silently skipped; the job will not fail.
A human readable message indicating details about why the pod is in this condition.
Filters for specifying the subset of jobs to be listed/fetched.
Selects jobs that accessed documents owned by this identity.
Selects jobs that were submitted by this identity.
The set of rules that define how a job is allowed to communicate with various network entities.
Network entities defined by CIDR-style masks.
An output document produced in the context of running a job.
Specification for a compute job for outputting a document.
Path to the file that should be uploaded as an output document. Interpreted relative to /parcel/data/out.
Owner to assign to the output document.
Generated using TypeDoc
Input document for a compute job.