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 OverviewProjects PortfolioReference ProjectsProject Goals in Domino 4+
Git Integration
Git Repositories in DominoGit-based ProjectsWorking from a Commit ID in Git
Jira Integration in DominoUpload Files to Domino using your BrowserFork and Merge ProjectsSearchSharing and CollaborationCommentsDomino File SystemCompare File Revisions
Revert Projects and Files
Revert a FileRevert a Project
Archive 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 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 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
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 Kernels
Partner Environments for Domino
Use MATLAB as a WorkspaceUse Stata as a WorkspaceUse SAS as a WorkspaceNVIDIA 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 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 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
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 ChecksUnregister a Model
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 to Amazon S3 from DominoConnect to BigQueryConnect to DataRobotConnect to Generic S3 from DominoConnect to IBM DB2Connect to IBM NetezzaConnect to ImpalaConnect to MSSQLConnect to MySQLConnect to OkeraConnect to Oracle DatabaseConnect to PostgreSQLConnect to RedshiftConnect to Snowflake from DominoConnect to Teradata
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
>
Domino Workspaces
>
Workspaces

Workspaces

A Domino workspace is an interactive session where you can conduct research, analyze data, train models, and more. Use workspaces to work in the development environment of your choice, like Jupyter notebooks, RStudio, VS Code, and many other customizable environments.

Launch a workspace

  1. In the navigation pane, click Workspaces.

    workspaces-1

  2. Click + Create New Workspace. A workspace launch dialog opens.

  3. Enter a name for your workspace.

  4. Select an environment for your workspace. You can click one of Domino’s pre-defined environments, or create a custom environment of your own. To learn more about managing environments, see Customize the Domino Software Environment.

  5. Select the integrated development environment, or IDE, that you’ll use in your workspace (such as Jupyter). The IDEs available in this step are determined by the environment you select. To learn more about managing IDEs, see Domino pluggable notebooks.

  6. Select a Hardware Tier. A hardware tier represents the compute hardware used for your run. It can be a virtual instance in a cloud services provider, or a physical machine running in your deployment’s on-premise data center.

    Select a hardware tier

  1. Optional: Configure datasets or external data volumes in the Data section of the modal.

    workspaces 4

  2. If necessary, attach a compute cluster to your workspace. To learn more about clusters, see the following:

    • Domino Spark documentation

    • Domino Ray documentation

    • Domino Dask documentation

    • Domino OpenMPI documentation

      workspaces 5a

  3. Click Launch. A loading page opens in a new tab. You’ll be directed to your workspace when it’s ready.

    workspaces 6

    workspaces 7

Important

Edit your settings

You can edit your workspace’s settings to use a different hardware tier or a different environment.

  1. Open the settings and click Edit Settings.

  2. Make the changes and click Save & Restart.

    edit-workspace-settings-in-session

Save your work

Use Save in your IDE to save work you complete in your workspace.

Saving your work in a workspace is not the same as syncing your work to Domino. When you save changes in your workspace, you’re simply saving your work within your workspace. If you’d like to push those changes to the Domino File System (DFS), you’ll have to sync your work to Domino instead.

workspaces 26

Sync your work to Domino

Important

Sync your work to the Domino File System (DFS) using the navigation menu in your Domino workspace. You can sync all changes at once, or sync only recent changes made to your files. Domino recommends that you sync your work at least daily.

Sync changes to files
  1. Click File Changes in the navigation pane of your workspace.

  2. Under Files, expand File Changes to view changes.

  3. Enter a commit message.

  4. Click Sync to Domino. Changes to files in the /mnt directory of your workspace will be synced to the Domino File System (DFS). Changes to files outside of the /mnt directory will not be synced.

    workspaces 12

  5. After syncing to Domino is complete, you can view your files in the Files section of Domino.

    workspaces 12 1

Sync all changes
  1. Click File Changes in the navigation bar of your workspace.

  2. Under All Changes, enter a commit message.

  3. Click Sync All Changes. Domino will save all your work to the Domino File System (DFS).

    workspaces 11

Warning

Stop a workspace

You can stop a workspace and resume it at a later time. Frequently stopping and resuming a workspace session is a good way to manage compute costs (for example, EC2). Storage costs (for example, EBS), however, will continue to incur.

Important
Stop a workspace:
  1. Click Stop. A dialog with information about pausing your workspace opens.

    workspaces 13

  2. Click Stop My Workspace.

    workspaces-14

    workspaces 15

Persisted and reloaded settings

If you stop your workspace, the following settings will persist and will be available to you when you resume your workspace session at a later time:

  • Files saved in the /mnt directory

The following settings, however, will not persist and instead will reload when you resume your stopped workspace:

  • Files outside of the /mnt directory, including installed packages

  • Objects in memory

  • Datasets

If you’re using a Git-based project with CodeSync and the credentials to the git repository backing your code are updated or deleted while your workspace session is stopped, then the credentials will be updated correspondingly when you resume your workspace.

Resume a workspace

  1. Click Workspaces in the navigation menu.

  2. Go to the stopped workspace in your workspace dashboard. Click Start. Your workspace will resume in a new tab.

    workspaces 16

View workspaces

  1. Click Workspaces in the navigation menu.

  2. Click My Workspaces.

    workspaces 8

View all workspaces in your project:
  1. Click Workspaces in the navigation menu.

  2. Click All Workspaces.

    Workspaces that you started, or that collaborators on your project started, are listed here.

    workspaces 9

View workspaces in all your projects:

To view all workspaces in all your projects, go to the project list page. Your running and stopped workspace counts will show up on each project card.

+ workspace counts project list view

View deleted workspaces:
  1. Click Workspaces in the navigation menu.

  2. Click Deleted in the toolbar above your workspaces.

    workspaces 10

Delete a workspace

Warning

Ensure that all your work is synced to Domino before deleting a workspace. Failure to do so will result in unrecoverable work.

You can delete a workspace if it’s no longer needed. Workspaces must be stopped before they can be deleted.

  1. Stop your workspace. You can stop a workspace by clicking Stop in the workspaces dashboard, or clicking Stop in the toolbar from within your workspace dashboard.

  2. Go to the workspaces dashboard. Click the red trash bin icon.

    workspaces-17

  3. Confirm that you’d like to delete the workspace, then click Delete. The workspace will be deleted. You can view deleted workspaces by clicking Deleted.

    workspaces-18

Workspace settings

Settings are available for individual workspaces. You can also configure the automatic shutdown time for long-running workspaces.

Reconfigure a workspace

You can view a workspace’s settings from the workspaces dashboard.

  1. Click Workspaces in the navigation menu.

  2. Click Settings in the workspace’s panel.

    workspaces-19

    You can view settings information about your code, environment, hardware tier, and datasets.

  3. Click Edit Settings to change the workspace settings.

    Here you can reconfigure any of the parameters you defined when you first created the workspace.

    Workspace settings window

Configure long-running workspaces

Domino shuts down long-running workspaces after a period defined by your administrator. Follow these steps to adjust this period; you can make it shorter but not longer. This setting applies to all workspaces owned by you.

  1. In the lower left, click your account name.

  2. Click Account Settings:

    Account settings menu item

  3. Click Workspace Settings.

    Long-running workspace shutdown interval

  4. Select Shutdown my long-running workspaces after <n> minutes/hours.

    If you leave this unselected, the time limit configured by your administrator applies.

  5. Optionally, you can also select a different time limit for long-running workspaces.

    Note

Workspace data

You can view your workspace’s usage, logs, and history from the workspaces dashboard.

Workspace usage

  1. Click Workspaces in the navigation menu.

  2. Click Usage. The panel expands to show CPU usage for your workspace.

    workspaces-20

    workspaces 20

Workspace logs

  1. Click Workspaces in the navigation menu.

  2. Click Logs in the workspace’s panel.

    You can view “User” logs and “Setup” logs about your workspace. User logs include information about actions you take within your workspace. Setup logs contain information about Domino and Kubernetes. If your workspace fails, the logs are a good place to begin investigating.

    workspaces 21

    workspaces-22

    workspaces-23

Workspace history

  1. Click Workspaces in the navigation menu.

  2. Click History in the workspace’s panel. A dialog opens where you can view historical information about your workspace. You can see when a workspace was launched, stopped, and more.

    workspaces 24

    workspaces-25

Workspace volume size

Volumes represent the storage space dedicated to your workspace or Job.

The default volume size for all workspaces and jobs in Domino is 10GiB, configurable by an administrator.

You can change the size of your volume if you find that your workspace (or Job) will require more storage space.

Change the size of your volume:
  1. Go to your project’s settings.

  2. Under "Workspace and Jobs Volume Size", enter your desired volume size. The default minimum volume size is 4GiB, while the default maximum volume size is 200GiB. Both of these values are configurable. If you’d like to change the default minimum and maximum volume size limits, contact your Domino administrator.

    workspaces 28

Important

Work with old workspaces

Workspaces started prior to an upgrade to Domino 4.5 do not have long-living persistent volumes backing them. You can find workspaces from before 4.5 on the My Workspaces or All Workspaces tab, and stopped workspaces under the Deleted tab.

The following is an example of what an old workspace looks like:

utility workspace

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