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
Notifications
On-Demand Open MPI
Configure MPI PrerequisitesFile Sync MPI ClustersValidate MPI VersionWork with your ClusterManage Dependencies
Projects
Projects OverviewProjects PortfolioReference ProjectsProject Goals in Domino 4+
Git Integration
Git Repositories in DominoGit-based Projects with CodeSyncWorking from a Commit ID in Git
Jira Integration in DominoUpload Files to Domino using your BrowserFork and Merge ProjectsSearchSharing and CollaborationCommentsDomino Service FilesystemComparing File RevisionsRevert Projects and Files
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 WorkspaceRecreate A Workspace From A Previous CommitUse 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 OverviewConnecting to a Cloudera CDH5 cluster from DominoConnecting to a Hortonworks cluster from DominoConnect to a MapR cluster from DominoConnect to an Amazon EMR cluster from DominoRunning Local Spark on a Domino ExecutorUsing PySpark in Jupyter WorkspacesKerberos Authentication
On-Demand Ray
On-Demand Ray OverviewValidated Ray VersionConfigure PrerequisitesWork with your ClusterManage DependenciesWork with Data
On-Demand Dask
On-Demand Dask OverviewValidated Dask VersionConfigure PrerequisitesWork with Your ClusterManage DependenciesWork with Data
Customize the Domino Software Environment
Environment ManagementDomino Standard EnvironmentsInstall Packages and DependenciesAdd Workspace IDEsAdding Jupyter KernelsAutomatic Adaptation of Custom Images
Partner Environments for Domino
Use MATLAB as a WorkspaceUse Stata as a WorkspaceUse SAS as a Workspace
Advanced Options for Domino Software Environment
Publish in Domino with Custom ImagesInstall Custom Packages in Domino with Git IntegrationAdd Custom DNS Servers to Your Domino EnvironmentConfigure a Compute Environment to User Private Cran/Conda/PyPi MirrorsUse 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 ImageExport to NVIDIA Fleet Command
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
Model Monitoring and Remediation
Monitor WorkflowsData Drift and Quality Monitoring
Set up Monitoring for Model APIs
Set up Prediction CaptureSet up Drift DetectionSet up Model Quality MonitoringSet up NotificationsSet Scheduled ChecksSet up Cohort Analysis
Set up Model Monitor
Connect a Data SourceRegister a ModelSet up Drift DetectionSet up Model Quality MonitoringSet up Cohort AnalysisSet up NotificationsSet Scheduled Checks
Use Monitoring
Access the Monitor DashboardAnalyze Data DriftAnalyze Model QualityExclude Features from Scheduled Checks
Remediation
Cohort Analysis
Review the Cohort Analysis
Remediate a Model API
Monitor Settings
API TokenHealth DashboardNotification ChannelsTest Defaults
Monitoring Config JSON
Supported Binning Methods
Model Monitoring APIsTroubleshoot the Model Monitor
Connect to your Data
Data in Domino
Datasets OverviewProject FilesDatasets Best Practices
Connect to Data Sources
External Data VolumesDomino Data Sources
Connect to External Data
Connect Domino to DataRobotConnect to Azure Data Lake StorageConnect to BigQuery from DominoConnect to Google Cloud StorageConnect to IBM DB2 from DominoConnect to IBM Netezza from DominoConnect to Impala from DominoConnect to MSSQL from DominoConnect to MySQL from DominoConnect to Okera from DominoConnect to Oracle Database from DominoConnect to PostgreSQL from DominoConnect to Redshift from DominoConnect to S3 from DominoConnect to SnowflakeConnect to Teradata from Domino
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
>
Configure Prerequisites

Configure Prerequisites

Before you can start using on-demand Ray clusters on Domino you must ensure that this functionality is enabled and properly configured on your deployment.

Note

Enable Ray on your deployment

Domino Administrators must Enable on-demand Ray functionality by setting the ShortLived.RayClustersEnabled feature flag to true.

The flag is on by default unless a Domino Administrator disables it for a deployment.

Create a base Ray cluster environment

By default, Domino does not include a Ray compatible Compute Environment that can be used for the components of the cluster. Without at least one such environment available, you cannot create a cluster.

When using on-demand Ray in Domino you will have two separate environments, one for the Ray cluster (base or worker environment) and one for the workspace/job execution (compute environment).

To create a new base Ray cluster environment, follow the general Environment Management with the following environment_attributes.

new ray base environment modal

  • Base image

    Select the Custom Image option and enter an image URI that points to a deployable Ray image.

    Domino recommends that you use the latest release tag for your version of Ray from the options published by the Ray project at https://hub.docker.com/u/rayproject.

    The images available include a core image as well as an image with all required prerequisites for ML workload. Additionally, the images are available for different python versions, as well as for CPU and GPU variants.

    For example, for Ray 1.3.0 and Python 3.8 the options are:

    • rayproject/ray:1.3.0-py38

    • rayproject/ray:1.3.0-py38-gpu

    • rayproject/ray-ml:1.3.0-py38

    • rayproject/ray-ml:1.3.0-py38-gpu

  • Supported clusters

    Select Domino managed Ray (Required). This ensures that the environment will be available for use when creating Ray clusters from workspaces and jobs.

  • Visibility

    You can set this attribute the same way you would for any other Compute Environment based on your desired visibility.

  • Dockerfile Instructions

    Leave blank to use the images as provided by Ray project.

    You can modify this section to include additional packages that might be necessary for your workloads and must be available on the Ray cluster nodes.

    To learn more, see Managing Dependencies

  • Pluggable Notebooks / Workspace Sessions

    Leave this section blank because the Ray base environments are not intended to include notebook configuration.

Prepare your Ray execution compute environment

In addition to the base Ray cluster environment, you must configure the Ray compute environments for workspaces and/or jobs that will connect to your cluster.

Domino recommends that you use the following base image to create a compatible workspace: quay.io/domino/ray-environment. See Domino Ray Environment for more information about this base image.

Customize this workspace compute environment:
  1. Use the image mentioned previously and add Docker Instructions.

  2. Use your own image and customizations. Then, use the following Docker Instructions to add the Ray packages.

    USER root
    
    ### Change Ray version as needed.
    ENV RAY_VERSION=<ENTER_RAY_VERSION>
    
    ### If you want install Ray RLlib or "all", which includes it, you must
    ### install "cmake" first.
    RUN sudo apt-get install -y cmake
    
    ### Change this depending on which Ray extras you want to install:
    ### All options are ray, ray[tune], ray[rllib], ray[serve]
    ### If you want everything you can just use ray[all].
    ### See note above the "cmake" is required for ray[rllib] or ray[all].
    RUN pip install ray[all]==$RAY_VERSION
    
    ### Add any additional packages that you may need which are not included
    ### in the base image you are using for the compute environment. You would
    ### want the versions of these to match the versions of these packages on
    ### the base Ray cluster image.
    ### For example, for Torch you may include
    ### RUN pip install torch==1.8.0 torchvision==0.9.0
    
    USER ubuntu
Note
Domino Data LabKnowledge BaseData Science BlogTraining
Copyright © 2022 Domino Data Lab. All rights reserved.