domino logo
Tech Ecosystem
Get Started
Get started with Python
Step 0: Orient yourself to DominoStep 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get started with R
Step 0: Orient yourself to Domino (R Tutorial)Step 1: Create a projectStep 2: Configure your projectStep 3: Start a workspaceStep 4: Get your files and dataStep 5: Develop your modelStep 6: Clean up WorkspacesStep 7: Deploy your model
Get Started with MATLAB
Step 1: Orient yourself to DominoStep 2: Create a ProjectStep 3: Configure Your ProjectStep 4: Start a MATLAB WorkspaceStep 5: Fetch and Save Your DataStep 6: Develop Your ModelStep 7: Clean Up Your Workspace
Step 8: Deploy Your Model
Scheduled JobsLaunchers
Step 9: Working with Datasets
Domino Reference Projects
Search in Deployments
Security and Credentials
Secure Credential Storage
Store Project CredentialsStore User CredentialsStore Model Credentials
Get API KeyUse a Token for AuthenticationCreate a Mirror of Compute Environments
Collaborate
Share and Collaborate on Projects
Set Project VisibilityInvite CollaboratorsCollaborator Permissions
Add Comments
Reuse Work
Set Up ExportsSet Up Imports
Organizations
Organization PermissionsTransfer Projects to an Organization
Projects
Domino File System Projects
Domino File SystemOrganize Domino File System Project AssetsImport Git RepositoriesWork from a Commit ID in GitCopy a ProjectFork ProjectsMerge Projects
Manage Project Files
Upload Files to DominoCompare File RevisionsExclude Project Files From SyncExport Files as Python or R Package
Archive a Project
Revert Projects and Files
Revert a FileRevert a Project
Git-based Projects
Git-based Project Directory StructureCreate a Git-based ProjectCreate a New RepositoryOrganize Git-based Project AssetsDevelop Models in a WorkspaceSave Artifacts to the Domino File System
Project FilesSet Project SettingsStore Project Credentials
Project Goals
Add GoalsEdit GoalsLink Work to Goals
Organize Projects with TagsSet Project Stages
Project Status
Set Project as BlockedSet Project as CompleteSet Project as Unblocked
View Execution DetailsView Project ActivityTrack Project StatusRename a Project
Share and Collaborate
Set Project VisibilityInvite CollaboratorsCollaborator Permissions
Export and Import Project Content
Set Up ExportsSet Up Imports
See the Assets for Your ProjectPromote Projects to ProductionTransfer Project OwnershipIntegrate Jira
Domino Datasets
Manage Large DataDatasets Best PracticesCreate a DatasetUse an Existing DatasetFile Location of Datasets in Projects
Datasets and Snapshots
Update a DatasetAdd Tags to SnapshotsCreate a Snapshot of a DatasetDelete Snapshots of DatasetsDelete a Dataset
Upgrade from Versions Prior to 4.5
External Data
Considerations for Connecting to Data Sources
External Data Volumes
Mount an External VolumeView Mounted VolumesUse a Mounted VolumeUmount a Volume
Tips: Transfer Data Over a Network
Workspaces
Create a Workspace
Open a VS Code WorkspaceSet Custom Preferences for RStudio Workspaces
Workspace Settings
Edit Workspace SettingsChange Your Workspace's Volume SizeConfigure Long-Running Workspaces
Save Work in a WorkspaceSync ChangesView WorkspacesStop a WorkspaceResume a WorkspaceDelete a WorkspaceView Workspace LogsView Workspace UsageView Workspace HistoryWork with Legacy Workspaces
Use Git in Your Workspace
Commit and Push Changes to Your Git RepositoryCommit All Changes to Your Git RepositoryPull the Latest Changes from Your Git Repository
Run Multiple Applications in a Workspace
Clusters
Spark on Domino
Hadoop and Spark Overview
Connect to a Cloudera CDH5 cluster from DominoConnect to a Hortonworks cluster from DominoConnect to a MapR cluster from DominoConnect to an Amazon EMR cluster from DominoRun Local Spark on a Domino ExecutorUse PySpark in Jupyter WorkspacesKerberos Authentication
On-Demand Spark Overview
Validated Spark VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
On-Demand Ray Overview
Validated Ray VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
On-Demand Dask Overview
Validated Dask VersionConfigure PrerequisitesWork with Your ClusterManage DependenciesWork with Data
Environments
Set a Default EnvironmentCreate an EnvironmentEdit Environment DefinitionView Your EnvironmentsView Environment RevisionsDuplicate an EnvironmentArchive an Environment
Environments
Example: Create a New Environment
Customize Environments
Install Custom Packages with Git Integration
Add Packages to Environments
Use Dockerfile InstructionsUse requirements.txt (Python only)Use the Execution to Add a Package
Add Workspace IDEsAdd a Scala KernelAccess Additional Domains and HostnamesUse TensorBoard in Jupyter Workspaces
Use Partner Environments
Use MATLAB as a WorkspaceUse Stata as a WorkspaceAdd an NVIDIA NGC to DominoUse SAS as a Workspace
Executions
Execution StatesDomino Environment Variables
Jobs
Start a JobScheduled Jobs
Launchers
Launchers OverviewCreate a LauncherRun a LauncherCopy Launcher Definitions
View Job DetailsCompare JobsTag JobsStop JobsView Execution Performance
Execution Notifications
Set Notification PreferencesSet Custom Execution Notifications
Execution Results
Download Execution ResultsCustomize the Results DashboardAutomate Complex Pipelines with Apache Airflow
Model APIs
Configure a Model for Deployment
Scale Models
Scale Python ModelsScale Model Versions
Configure Compute ResourcesRoute Your ModelProject Files in ModelsEnvironments for ModelsShare and Collaborate on Models
Publish
Model APIs
Publish a ModelSend Test Calls to the ModelPublish a New Version of a ModelSelect How to Authorize a Model
Domino Apps
Publish a Domino AppHost HTML Pages from DominoGrant Access to Domino AppsView a Domino AppView All Domino AppsIdentify Resources to WhitelistPublish a Python App with DashPublish an R App with ShinyPublish a Project as a Website with FlaskOptimize App Scalability and PerformanceGet the Domino Username of an App Viewer
Launchers
Create a LauncherRun a LauncherCopy Launcher Definitions
Model Monitoring
Model Monitoring APIsAccessing The Model MonitorGet Started with Model MonitoringModel Monitor DeploymentIngest Data into The Model MonitorModel RegistrationMonitoring Data DriftMonitoring Model QualitySetting Scheduled Checks for the ModelConfigure Notification Channels for the ModelUse Model Monitoring APIsProduct Settings
Domino Command Line Interface (CLI)
Install the Domino Command Line Interface (CLI)Domino CLI ReferenceDownload Files with the CLIForce-Restore a Local ProjectMove a Project Between DeploymentsUse the Domino CLI Behind a Proxy
Troubleshooting
Troubleshoot Domino ModelsWork with Many FilesTroubleshoot Imports
Get Help
Additional ResourcesGet Domino VersionContact Technical SupportSupport BundlesBrowser SupportUser Guide Updates
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
User Guide
>
Workspaces
>
Clusters
>
On-Demand Ray Overview
>
Work with your Cluster

Work with your Cluster

Create a cluster with workspaces

Create an on-demand Ray cluster attached to a Domino Workspace:
  1. Go to Workspaces > New Workspace.

  2. From Launch New Workspace, select the Compute Cluster step.

  3. Specify the cluster settings and launch your workspace. After the workspace is up, it will have access to the Ray cluster you configured.

    new workspace with ray

Create a cluster with jobs

Create an on-demand Ray cluster attached to a Domino job:
  1. Go to Jobs > Run.

  2. From Start a Job, select the Compute Cluster step.

  3. Specify the cluster settings and launch your job. The job will have access to the Ray cluster you configured.

    new job with ray

You can use any Python script that interacts with your Ray cluster.

Set your cluster settings

cluster settings ray

Set the following cluster settings:
Number of Workers

The number of Ray node workers in the Ray cluster when it starts. The combined capacity of the workers will be available for your workloads.

Workers

The maximum number of Ray node workers that the cluster can reach when Auto-scale workers is enabled. See cluster autoscaling.

Max

The maximum number of workers that you can make available to your cluster is limited by the number of per-user executions that your Domino administrator has configured for your deployment or by the maximum simultaneous executions of the underlying Hardware Tier used for workers.

In addition to the number of Ray node workers, you will need one slot for your cluster master and one slot for your workspace or job.

Worker Hardware Tier

The amount of compute resources (CPU, GPU, and memory) that will be made available to each Ray node worker.

Head Hardware Tier

Same mechanics as the Worker Hardware Tier, but applied to the resources that will be available for your Ray cluster head node.

The Ray head node coordinates the Ray workers, so it does not need a significant amount of CPU resources. It will host the Ray Global Control Store. The amount of required memory will depend on the complexity of your application.

Cluster Compute Environment

Designates your compute environment for the Ray cluster.

Dedicated local storage per executor

The amount of dedicated storage in Gigabytes (2^30 bytes) that will be available to each Ray worker.

The storage will be automatically mounted to /tmp.

The storage will be automatically provisioned when the cluster is created and de-provisioned when it is shut down.

Warning

Connect to your cluster

When provisioning your on-demand Ray cluster, Domino sets up environment variables that hold the information needed to connect to your cluster.

Use the following snippet to connect.

Note
import ray
import ray.util
import os

...

if ray.is_initialized() == False:
   service_host = os.environ["RAY_HEAD_SERVICE_HOST"]
   service_port = os.environ["RAY_HEAD_SERVICE_PORT"]
   ray.util.connect(f"{service_host}:{service_port}")

Access the Ray Web UI

Ray provides a built-in dashboard with access to metrics, charts, and other features that helps understand the Ray cluster, libraries, and workloads.

Use the dashboard to:

  • View cluster metrics.

  • View logs, error, and exceptions across many machines in a single pane.

  • View resource utilization, tasks, and logs per node and per actor.

  • Kill actors and profile Ray jobs.

  • See Tune jobs and trial information.

Domino makes the Ray Web UI available for active on-demand clusters attached to both workspaces and jobs.

Ray UI from Workspaces

The Ray UI is available from a dedicated tab in your workspace.

access ui tabs ray

Ray UI from Jobs

The Ray UI is also available for running jobs from Details tab.

access_ui_job_ray.png

Cluster lifecycle

On workspace or job startup, a Domino on-demand Ray cluster with its cluster settings is automatically provisioned and attached to the workspace or job as soon as the cluster becomes available.

When the workspace or job terminates, the on-demand Ray cluster and all associated resources are automatically terminated and deprovisioned. This includes any compute resources and storage allocated for the cluster.

Cluster network security

The on-demand Ray clusters created by Domino are not meant to be shared between users. Each cluster is associated with a given workspace or a job instance. Access to the cluster and the Ray Web UI is restricted only to users who can access the workspace or the job attached to it. This restriction is enforced at the networking level and the cluster can only be reached from the execution that provisioned it.

Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.