domino logo
Tech Ecosystem
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 Domino ProjectStep 3: Configure Your Domino 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 Domino Datasets
Domino Reference
Projects
Projects Overview
Revert Projects and Files
Revert a ProjectRevert a File
Projects PortfolioProject Goals in Domino 4+Jira Integration in DominoUpload Files to Domino using your BrowserCopy ProjectsFork and Merge ProjectsSearchSharing and CollaborationCommentsDomino Service FilesystemCompare File RevisionsArchive a Project
Advanced Project Settings
Project DependenciesProject TagsRename a ProjectSet up your Project to Ignore FilesUpload files larger than 550MBExporting Files as a Python or R PackageTransfer Project Ownership
Domino Runs
JobsDiagnostic Statistics with dominostats.jsonNotificationsResultsRun Comparison
Advanced Options for Domino Runs
Run StatesDomino Environment VariablesEnvironment Variables for Secure Credential StorageUse Apache Airflow with Domino
Scheduled Jobs
Domino Workspaces
WorkspacesUse Git in Your WorkspaceUse Visual Studio Code in Domino WorkspacesPersist RStudio PreferencesAccess Multiple Hosted Applications in one Workspace Session
Spark on Domino
On-Demand Spark
On-Demand Spark OverviewValidated Spark VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
External Hadoop and Spark
Hadoop and Spark OverviewConnect 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 Ray
On-Demand Ray OverviewValidated Ray VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
Customize the Domino Software Environment
Environment ManagementDomino Standard EnvironmentsInstall Packages and DependenciesAdd Workspace IDEs
Partner Environments for Domino
Use MATLAB as a WorkspaceCreate a SAS Data Science Workspace EnvironmentNVIDIA NGC Containers
Advanced Options for Domino Software Environment
Install Custom Packages in Domino with Git IntegrationAdd Custom DNS Servers to Your Domino EnvironmentConfigure a Compute Environment to User Private Cran/Conda/PyPi MirrorsScala notebooksUse TensorBoard in Jupyter Workspaces
Publish your Work
Publish a Model API
Model Publishing OverviewModel Invocation SettingsModel Access and CollaborationModel Deployment ConfigurationPromote Projects to ProductionExport Model Image
Publish a Web Application
App Publishing OverviewGet Started with DashGet Started with ShinyGet Started with FlaskContent Security Policies for Web Apps
Advanced Web Application Settings in Domino
App Scaling and PerformanceHost HTML Pages from DominoHow to Get the Domino Username of an App Viewer
Launchers
Launchers OverviewAdvanced Launcher Editor
Assets Portfolio Overview
Connect to your Data
Data in Domino
Datasets OverviewDatasets Best Practices
Data Sources Overview
Connect to Data Sources
External Data Volumes
Git and Domino
Git Repositories in DominoWork From a Commit ID in Git
Work with Data Best Practices
Work with Big Data in DominoWork with Lots of FilesMove Data Over a Network
Advanced User Configuration Settings
User API KeysDomino TokenOrganizations Overview
Use the Domino Command Line Interface (CLI)
Install the Domino Command Line (CLI)Domino CLI ReferenceDownload Files with the CLIForce-Restore a Local ProjectMove a Project Between Domino DeploymentsUse the Domino CLI Behind a Proxy
Browser Support
Get Help with Domino
Additional ResourcesGet Domino VersionContact Domino Technical SupportSupport Bundles
domino logo
About Domino
Domino Data LabKnowledge BaseData Science BlogTraining
User Guide
>
Domino Reference
>
On-Demand Ray
>
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.

Quota 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 Gigibytes (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.