Creating a Job


Create and run a job in Data Science.

Ensure that you have created the necessary policies, authentication, and authorization for your jobs.

Before you begin:

Create a job artifact file.

To store and manage job logs, learn about logging.

To use storage mounts, you must have an Object Storage bucket or OCI File Storage Service (FSS) mount target and export path.

To use FSS, you must first create the file system and the mount point. Use the custom networking option and ensure that the mount target and the notebook are configured with the same subnet. Configure security list rules for the subnet with the specific ports and protocols.

Ensure that service limits are allocated to file-system-count and mount-target-count.

To use storage mounts, you must have an Object Storage bucket.

To use storage mounts, you must have an Object Storage bucket or OCI File Storage Service (FSS) mount point.

When creating jobs, you can use the fast launch enabled Compute shapes when they're available in the region. This launches the job in the fastest way possible.

Console
CLI
API
Use the Console to sign in to a tenancy with the necessary policies.
Open the navigation menu and click Analytics & AI. Under Machine Learning, click Data Science.
Select the compartment that contains the project with the model deployments.

All projects in the compartment are listed.

Click the name of the project.

The project details page opens and lists the notebook sessions.

Under Resources, click Jobs.

A tabular list of jobs in the project is displayed.

Click Create job.
(Optional) Select a different compartment for the job.
(Optional) Enter a unique name and description for the job (limit of 255 characters). If you don't provide a name, a name is automatically generated.

For example, job20210808222435.

Use one of the following options:

Bring your own container: Select to use your container, and then specify the image as a container with the custom environment variable keys.

Upload job artifact: Drag the job artifact file into the box.

A container image or a job artifact is required for a job.

(Optional) Create a default job configuration that's used when the job is run using these options.

Enter or select any of the following values:

Custom environment variable key

The environment variables that control the job. When you're using a container image, you must specify CONTAINER_CUSTOM_IMAGE, and other options are optional.

 Note



If you uploaded zip file or compressed tar file, add the JOB_RUN_ENTRYPOINT as a custom environment variable to point to the file.

Value

The value for the custom environment variable key.

You can click Additional custom environment key to specify more variables.

Command line arguments

The command line arguments that you want to use for running the job.

Maximum runtime (in minutes)

The maximum number of minutes that the job can run. The service cancels the job run if its runtime exceeds the specified value. The maximum runtime is 30 days (43,200 minutes). We recommend that you configure a maximum runtime on all job runs to prevent runaway job runs.

Select a Compute shape, either Fast launch or Custom configuration.

A shape is automatically selected.

We recommend that you use the fast launch option that automatically selects a Compute shape from a predefined pool of shapes so that the job can start as fast as possible. There must be a shape available in the pool for this option to be selected.

(Optional) Change the Compute shape by clicking Change shape. Then, follow these steps in the Select compute panel.
Select an instance type.
Select an shape series.
Select one of the supported Compute shapes in the series.
Select the shape that best suits how you want to use the resource. For the AMD shape, you can use the default or set the number of OCPUs and memory.

For each OCPU, select up to 64 GB of memory and a maximum total of 512 GB. The minimum amount of memory allowed is either 1 GB or a value matching the number of OCPUs, whichever is greater.

Click Select shape.
(Optional) To use logging, click Select, and then ensure that Enable logging is selected.
Select a log group from the list. You can change to a different compartment to specify a log group in a different compartment from the job.
Select one of the following to store all stdout and stderr messages:
Enable automatic log creation

Data Science automatically creates a log when the job starts.

Select a log

Select a log to use.

Click Select to return to the job run creation page.
For Storage. enter the amount of block storage to use between 50 GB and 10, 240 GB (10 TB). You can change the value by 1 GB increments. The default value is 100 GB.
Select one of the following options to configure the network type:

Default networking—The workload is attached by using a secondary VNIC to a preconfigured, service-managed VCN, and subnet. This provided subnet allows egress to the public internet through a NAT gateway, and access to other Oracle Cloud services through a service gateway.

If you need access only to the public internet and OCI services, we recommend using this option. It doesn't require you to create networking resources or write policies for networking permissions.

Custom networking—Select the VCN and subnet that you want to use for the resource (notebook session or job).

For egress access to the public internet, use a private subnet with a route to a NAT gateway.

If you don't see the VCN or subnet that you want to use, click Change Compartment, and then select the compartment that contains the VCN or subnet.

 Important



Custom networking must be used to use a file storage mount.

 Note



The network configuration of a notebook session can't be changed when the notebook session is reactivated. If a notebook session was configured to use a default network, you can't deactivate the notebook session then select custom networking when you reactivate it.

(Optional) To use storage mounts, click +Add storage mount.
Select a storage mount type, OCI Object Storage or OCI File Storage.
Select a compartment that contains the storage resource that you want to mount.
Select one of the following:
Object Storage

The bucket you want to use.

You can add an object name prefix. The prefix must start with an alphanumeric character. The allowed characters are alphanumerics, slash ( / ), hyphen ( - ) and underscore ( _ ).

File Storage

The mount target and export path you want to use.

You must use a custom network to use file storage.

Enter the path under which the storage is to be mounted.

Storage is mounted under the specified mount path. The path must start with an alphanumeric character. The destination directory must be unique across the storage mounts provided. The allowed characters are alphanumerics, hyphen ( - ) and underscore ( _ ).

You can specify the full path, such as /opc/storage-directory. If only a directory is specified, such as /storage-directory, then it's mounted under the default /mnt directory. You can't specify OS specific directories, such as /bin or /etc.

Click Submit.

Repeat these steps to add up to two storage mounts for notebook sessions and five storage mounts for jobs.

(Optional) Click Show advanced options to add tags to the job.
(Optional) Enter the tag namespace (for a defined tag), key, and value to assign tags to the resource.

To add more than one tag, click Add tag.

Tagging describes the various tags that you can use organize and find resources including cost-tracking tags.

Click Create.

After the job is in an active state, you can use job runs to repeatedly run the job.