Release notes

3.6.13 (October 1, 2019)

Changes

• Fixed an issue where attempting to reopen a recently closed tab in Edge v17+ that contained a Domino workspace session would result in a 404. The reopened tab will now connect to the workspace session successfully.

 

3.6.12 (September 26, 2019)

Changes

• Improved performance of loading model instance logs in the UI.
• Removed checkboxes on the rows in some tables that did not support any bulk actions.
• Fixed an issue where changes to timeout settings for Model APIs were sometimes not taking effect.
• Fixed an issue where changes to the visibility setting of a Model API would sometimes not persist.

 

4.0.0 (September 24, 2019)

Welcome to Domino 4!

In addition to helpful new features for data scientists and project leaders, Domino 4 introduces a new architecture with all components running on Kubernetes. This change makes Domino easier to install, configure, monitor, and administer, and allows Domino to run in more environments than ever before. Visit admin.dominodatalab.com to learn about the technical design of Domino 4 and read guides for configuration and administration.

Breaking changes

• Domino 4.0 sunsets support for V1 environments. Convert any existing V1 environments to V2 environments to continue to use them.

• Domino 4.0 sunsets support for legacy API endpoints. Only Model APIs are supported.

• Many previous interfaces and options for managing Domino executors have been replaced with the introduction of the new Kubernetes compute grid. There are new dashboards for viewing Kubernetes infrastructure and active execution pods, and new options for configuring Hardware Tiers.

  

  Click to read more about Managing the compute grid in Domino 4.

• Domino 4.0 removes support for SSH access to a Run container.

• Domino 4.0 removes support for arbitrary Docker arguments for things like custom volume mounts.

• Domino 4.0 removes support for connecting to VPNs from Run containers.

• In Domino 4.0, user logins must use the new Keycloak authentication service. Any existing legacy LDAP integrations will need to have their configurations migrated to Keycloak.

• Domino 4.0 ships with a new collection of Domino 4.0 standard environments. Users who want to use NVIDIA GPUs in Domino 4.0 should base the environments they want to use for those workflows on the new standards, as they are built with NVIDIA Docker. Note that these new standard environments do not support working with GPUs from Python 2.

New features

• Domino 4.0 adds a new Assets Portfolio that allows users to quickly discover and see key information about the data products they have access to in Domino, including Model APIs, Apps, Launchers, and Scheduled Jobs.

  

• A new ProjectManager admin role is available. This role grants a user contributor access to projects owned by other users who are members of the same organization as the ProjectManager. This allows the ProjectManager to view those projects in the Projects Portfolio, discover their published assets in the Assets Portfolio, and view the projects’ contents as a contributor.

• Domino 4.0 introduces Project Goals. Goals represent outcomes or subtasks within projects. Project contributors can link files, Workspace sessions, Jobs, Apps, and Model APIs to goals, which show up on the goal card in the project overview. This provides a way to track all work related to a specific goal in the project, and can make navigating large and busy projects easier.

  

• New options are available in the Notifications and Workspace Settings sections of user Account Settings that allow for opt-in to email notifications or auto-termination for long-running Workspace sessions with a configurable duration.

  

  

  Admins also now have additional options for defining which Workspace sessions to treat as long-running, enforcing notification requirements for users, and sending additional global notifications about long-running sessions to admins.

Additional changes

• Visual styling and design for tables, buttons, links, accordion headers, breadcrumbs, and tab navigation have all been improved and made consistent across the Domino application.

 

 

3.6.11 (September 11, 2019)

Changes

• Removed the checkboxes on table rows when there are no bulk actions available on objects in the table.
  
  
• Clicking the button to duplicate an environment now redirects the user to the duplicate environment description page. Previously, taking this action would reload the original environment's description page.

 

3.6.10 (September 4, 2019)

Changes

• Fixed an issue where stopping a Workspace from the Workspaces dashboard would erroneously indicate to the user that they were discarding changes even when there were no uncommitted changes in the session.

 

3.6.9 (August 30, 2019)

Changes

• Improved performance of loading model instance logs in the UI.
  
  
• Improved garbage collection for temporary folders and volumes on executors.
• Fixed an issue where stopping and committing from the Workspace UI would not execute the post-run scripts from the user's environment.
• Added a modelManager.modelContainer.restartCountLimit option which defines how many times a Model API can fail to launch before being descheduled and not restarting further.

 

3.6.8 (August 26, 2019)

Changes

• Restyled the support button so that it no longer obscures other interactive UI components.

 

3.6.7 (August 20, 2019)

Changes

• Fixed an issue with event telemetry reporting that could cause some actions in the UI to hang indefinitely.
• Fixed an issue where logs would sometimes erroneously indicate a lack of executor capacity.

 

3.6.6 (August 13, 2019)

Changes

• Added a modelmanager.requestBufferSize to override the size of the uWSGI request buffer for published models. This will allow creating models that take larger requests without causing invalid HTTP request size errors.
• Fixed an issue that could cause opening a Workspace to 404 for users with uppercase characters in their LDAP federated usernames.

 

3.6.5 (August 6, 2019)

Changes

• Fixed an issue with CLI login.

 

3.6.4 (August 2, 2019)

Changes

• Fixed an issue where the support widget could cover up interactions in the application.

 

3.6.3 (July 30, 2019)

Changes

• Added a button to the dispatcher admin UI to download the files from the working directory of an active Run.

 

3.6.2 (July 22, 2019)

Changes

• Fixed an issue where if a user had made changes in a workspace, then reopened that workspace in a new tab or window, attempting to stop and commit changes would not correctly commit the changes.

 

3.6.1 (July 19, 2019)

Changes

• Fixed some issues with rendering custom support buttons.
• Admin users who stop their own workspaces will no longer receive a notification that an admin stopped their workspace.
• Fixed a rendering issue with the help link in the workspace logs panel.

 

3.6.0 (July 17, 2019)

Breaking changes

• The legacy Runs dashboard is no longer available in Domino 3.6. After upgrading to 3.6, the new Jobs dashboard interface will be enabled.

Changes

• Domino 3.6 introduces Datasets scratch spaces. These are mutable filesystem directories for temporary data storage and exploration. They are a compliment to the core Datasets functionality. Read more about scratch spaces here.
  
  
• New API endpoints for working with Datasets are available.
• The following types of events have been added to project activity feeds:
  
  • Publishing a Model API
  • Publishing an App
  • Publishing or modifying a scheduled Job
  • Creating, editing, or deleting files from the Domino UI
  • Creating, editing, or deleting files as the result of a Workspace sync
• A new timeline component has been added to the Jobs dashboard. This component shows a time series of dominostats.json values being tracked across experiments. Read more here.
  
  
• If you are a collaborator on a project, and an administrator or project owner stops one of your Workspace sessions, you will now get an email notification with details.
• For new deployments, Domino 3.6 introduces a new authentication service that supports additional protocols and SSO providers.
• Tables throughout the UI have been switched over to a new component type for unified and improved styling.
• Previously, when an executor in Maintenance Mode was stopped, starting the executor from the Dispatcher UI would take the executor out of Maintenance Mode automatically. Now, the executor will start but remain in Maintenance Mode. Executors will only exit Maintenance Mode when an administrator manually toggles Maintenance Mode.
• Fixed some issues with model tester connectivity to published models.
• Fixed formatting issues with UI text on the environment definition page.
• Fixed an issue with port assignment for Spark that could impact connectivity.

 

3.5.4 (July 2, 2019)

Changes

• Previously, when an executor in Maintenance Mode was stopped, starting the executor from the Dispatcher UI would take the executor out of Maintenance Mode automatically. Now, the executor will start but remain in Maintenance Mode. Executors will only exit Maintenance Mode when an administrator manually toggles Maintenance Mode.

 

3.5.3 (June 26, 2019)

Changes

• Added support site URL to the Projects Portfolio help link.
• Fixed an issue where members of an organization were not inheriting the correct permissions on published Apps in projects owned by the organization.

 

3.4.11 (June 25, 2019)

Changes

• Fixed an issue where members of an organization were not inheriting the correct permissions on published Apps in projects owned by the organization.

 

3.5.2 (June 20, 2019)

Changes

• Fixed an issue that could lead to long load times for the Workspaces dashboard.

• Changed implementation of filtering out default quick-start projects from the Projects Portfolio to allow for filtering on custom default projects.
• Fixed an issue where older activity could incorrectly be listed as recent in user activity reports.

 

3.4.10 (June 20, 2019)

Changes

• Fixed an issue that could lead to long load times for the Workspaces dashboard.

• Fixed an issue where cloning a hardware tier could lead to intermittent Error getting hardware tier messages in project settings.

 

3.5.1 (June 13, 2019)

Changes

• Renamed the Projects filter in the Activity Feed to Project Events.

• Fixed an issue where some older Runs were incorrectly showing up as recent workloads in user activity reports.

• Fixed an issue with Domino 3.5.0 where the button to SSH into a Run container would not display in the Jobs dashboard details panel.
• The default quick-start project created for all users no longer appears in the Projects Portfolio.

• Fixed a logging issue with the Domino frontend application that could cause host instability.

• Fixed an issue where tagging a project did not reliably reindex the project for search with the new tag.

 

3.4.9 (June 11, 2019)

Changes

• Fixed a logging issue with the Domino frontend application that could cause host instability.

• Fixed an issue where tagging a project did not reliably reindex the project for search with the new tag.

 

3.5.0 (June 7, 2019)

New features

• Domino 3.5 introduces project stages. Stages are a customizable set of labels that can be used to track the progress of your project through your team’s data science life cycle. The set of available stages can be configured by Domino administrators in a new interface accessible through the admin portal.
  
  
  
  The stage at the top of the Project Stage Configuration will be the default stage for new projects. Projects can be moved to any other available stage by the project’s owner or contributors.
  
  
  

  Project stage is managed from a new menu that users can open by clicking the project title in the project menu. Stage changes are recorded in the project activity feed.
  
  

• Projects owners and contributors can also use the project stage menu to flag a project as blocked with a description of the blocker, or mark a project as complete with a description of the project conclusion.
  
  
  
  Blocker and completion events also appear in the project activity feed with an attached discussion thread for comments. The same project status menu used to raise blockers and mark projects complete can be used to resolve blockers and reopen completed projects. Note that projects marked as blocked or complete are still fully functional Domino projects. These statuses are labels used by team leaders to track project status.
  
  
• Domino admins have access to a new Projects Portfolio interface, designed as a dashboard for data science leaders to organize and understand projects worked on by their teams. The portfolio can filter projects by stage and status, and includes customizable columns of project information.
  
  
  
  The Projects Portfolio is accessible from the Control Center main menu.
  
  
• A new option is available for creating Dataset snapshots via browser upload.
  
  
  
  Browser uploads to Datasets can support up to 50GB or 50,000 files per snapshot. Uploads can be paused and resumed to allow for network interruptions to laptops or workstations. Note that paused or interrupted uploads that are not resumed within 24 hours are discarded and will need to be started again.
  
  
• The upload-dataset command in the Domino CLI has new functionality similar to the new browser upload feature. It now supports up to 50GB and 50,000 files per upload, and can be resumed if interrupted. Install Domino CLI 3.5+ and run domino help upload-dataset for usage instructions.
  
  

• For licensing purposes, Domino now distinguishes between users who have signed up only to browse and consume results, and users who run practitioner workflows. The former type of user will not be treated as taking up a Domino practitioner license until they launch a Run, Workspace, or publish a data product like an App or Model. Starting Runs via Launchers published by other users does not count as a practitioner workflow.

  The Users page of the Domino admin portal includes new information to track license usage and practitioner status. Admins can easily identify users who are taking up a practitioner license, see when those users were last active in Domino, and deactivate accounts as desired.
  
  
  
  All of the information in the Users page can also be downloaded as CSV via User Activity Reports.

• Columns in the Jobs dashboard will now automatically resize to accommodate the sizes of the displayed values.
  
  
• When generating a new Dataset snapshot by running a Job, the script file selector will now autocomplete with the names of files in the current project.
  
  
• Added a publicProjectsEnabled option which, when disabled, removes Public as an option for project visibility.

 

Issues resolved

• Project collaborators with Launcher User permissions can no longer access the Workspaces dashboard.
• Project collaborators with Launcher User permissions will no longer see Unauthorized errors when trying to open the Jobs dashboard to view the results of Jobs they started with Launchers.
• Fixed an issue where console logs were sometimes not displaying in the Logs tab on the Jobs and Workspaces dashboards.
• Fixed an issue where Jobs started from the Domino CLI could not appear in the Jobs dashboard.
• Public projects that allow anonymous execution will no longer require a sign-in to access the Workspaces dashboard.
• Previously, a limit of 1000 Domino environments could be listed on the Environments overview. This limit has been removed.
• Fixed an issue where cloning a hardware tier could lead to intermittent Error getting hardware tier messages in project settings.
• The hardware tier dropdown menu in the project settings will now load correctly even when admins are actively creating many additional hardware tiers.
• Fixed an issue where attempting to stop a model version in the middle of startup would stop the underlying model host instance, but not show the model as stopped in the UI, leaving it stuck in an Instance not started state.

 

3.4.8 (May 28, 2019)

Changes

• Fixed an issue where Domino with elastic executor scaling could sometimes create new executor hosts when there was still available capacity on stopped hosts. Domino will now more reliably restart existing available hosts instead of launching new ones.

• Fixed an issue where transferring a project to an Organization would cause the Create an app.sh file button on the app publishing page to point to a non-existent URI, producing 404 errors.
• Previously, a limit of 1000 Domino environments could be listed on the Environments overview. This limit has been removed.
• Fixed issue with bulk downloading files from the project files page. Using checkboxes next to files should now reliably allow users to bulk download the selected files.

 

3.4.7 (May 21, 2019)

Changes

• Project collaborators with Launcher User permissions can no longer access the Workspaces dashboard.

• Fixed several issues related to excessive Dispatcher logging.

 

3.4.6 (May 13, 2019)

Changes

• Fixed an issue where Spark connectivity ports listed in Spark configuration files and ports open in Run containers could be different, resulting in no connectivity to Spark.

• Fixed an issue where Run results would fail to render when certain special characters appeared in filenames. 

 

3.4.5 (May 6, 2019)

New features

• It is now possible for Domino administrators to set up custom default projects that all new Domino users will own a copy of. Setting up custom default projects replaces the Domino-standard quick-start project.

  Learn more in Change the default project for new users.

 

3.4.4 (April 29, 2019)

Changes

• Changed the Start time field in the Jobs dashboard to show the time the Job entered the Queued state. Previously, this field showed when the Job entered the Running state, which could be a noticeable time after the user initiated the Job depending on startup times.
• Fixed an issue where Control Center data would fail to load into the UI due to a malformed API call.
• Fixed an issue where changing the time constraints on Model instance logs did not correctly filter the logs to only those in the indicated times.

 

3.4.3 (April 23, 2019)

Welcome to Domino 3.4!

New features

• Domino 3.4 introduces a new activity feed that pulls together records of important events across your project. The activity feed shows Jobs started, Workspace sessions launched, and comments left on both Runs and files.

  It also has an option to quickly open a Run comparison.
  
  
  

• There are new API endpoints available for adding, removing, and configuring external Git repositories.

  Click to learn more about project-level endpoints and repository-level endpoints.

• Domino now records and displays in the UI which branch of an external repository was checked out for the start and end commit of a Run.
  
  
• Domino now supports OpenSSH formatted SSH keys as credentials for accessing external Git repositories.
• Domino now supports adding Bitbucket App Passwords as credentials for accessing external Git repositories.
• Domino now supports adding Git repositories stored in Azure Repos.
• Error messages related to errors in the domino.yaml configuration file for Datasets advanced mode have been improved. Learn more in About domino.yaml.
• The Workspace session UI now has more consistent options for controlling which repositories are committed to when performing a manual sync or stopping the session.
• Apps can now be made aware of the Domino username of the user viewing them, by accessing a new HTTP header. Learn more by reading How to get the Domino username of an App viewer.
• New configurable health checks have been added that can mark Domino executors as unhealthy when they are low on disk space. Learn more about configurable health checks.

• Substantial changes have been made to the way Domino handles unhealthy and unresponsive executors.

  Domino no longer automatically puts machines in Maintenance Mode. Instead, Maintenance Mode is reserved as a state Domino admins can place a machine in for actual maintenance. Unhealthy or unresponsive executors will be automatically moved by Domino into a new Unusable state.
  
  Read more about these changes in Executor maintenance in Domino 3.4+.

• Kubernetes deployment logs are now available for Domino models, from the same interface that hosts instance and build logs. If you experience persistent issues with model deployment in Domino, you may need to retrieve and send these logs to the Domino support team. Only Domino admins can download these logs.
  
  
• A new Project column has been added to the Datasets administration UI to help disambiguate cases of identical Dataset names.
  
  
• It is now possible to specify a hardware tier when starting a run from the python-domino library.
• Apps can now run on a Kubernetes cluster, bringing greater reliability to your apps via autorestart. This feature is in limited availability for this release. Please contact support@dominodatalab.com to learn more.

 

Issues resolved

• Copying a project now also copies the configurations for attached external Git repositories.
• Fixed issue where the Jobs dashboard would spawn an error modal window that could not be closed by the user.
• Improved long load times for some pages in the Model API publishing UI.
• Fixed issue with logs not displaying correctly on the Apps dashboard.
• Fixed issue where in some cases the status of an App on the Overview tab would not update during publishing.
• Fixed issue where publishing an App could change its permissions from Anyone with a Domino account to Invited users only (others may request).
• Fixed some issues with filtering on the Files page for a project.

 

2.11.18 (April 3, 2019)

Changes

• Turned off Apache HTTP logging in Domino CLI.
• Fixed issue with kubeadm access to S3 for backups in AWS deployments.

 

3.3.8 (April 3, 2019)

Changes

• Turned off Apache HTTP logging in Domino CLI.

 

3.3.7 (March 27, 2019)

Issues resolved

• Fix issue where Jobs submitted through the Domino CLI would sometimes not appear in the Jobs dashboard.

 

3.3.6 (March 20, 2019)

Issues resolved

• Fix issue where public projects that enabled Runs by anonymous users would get 500 errors when loading the Jobs dashboard or Workspaces dashboard if anonymously started Runs were present.

 

3.3.5 (March 18, 2019)

This release of Domino 3.3.5 includes cumulative changes of several development releases since the release of Domino 3.3.1.

New features

• A Relaunch button has been added to the Workspaces dashboard. You can use this button to launch a new Workspace session based on the hardware tier, environment, and optionally the project revision of a past Workspace session.
  
  
• Clicking Delete all marked Snapshots from the Dataset administration interface now shows a confirmation dialog that itemizes the Snapshots to be deleted.
  
  

Issues resolved

• Fix issue with heap usage and garbage collection that could cause frontend outages.
• Stop frontend from trying to reconnect to stopped executors, which was causing spurious timeout errors.
• Improve unclear error messages when users attempt to open a Workspace session they do not have permission to view.
• Fix issue where in some cases the Domino project menu would fail to render or disappear in response to user action.
• Fix issue where changing the project default hardware tier in the project menu would not affect Runs started from the Quick Action menu until the page was refreshed. Changing the default hardware tier from the project menu now takes effect immediately.
• Clicking the Stop button for a Workspace session on the Workspaces dashboard will no longer simultaneously open the confirmation dialog and the session details pane. Only the confirmation dialog will open.
• Project collaborators with access to the Workspaces dashboard, including Owners, will no longer be able to open Workspace sessions started by other users. Only the user that launched a Workspace session can open it.
• Fixed an issue where starting an App in Domino would sometimes switch the App permissions to Invited users only.
• Copying a project now correctly copies over the project’s added Git repositories and their configurations.
• Resolved inconsistencies in the UI text for Datasets versus data sets and data set collections.
• Fix issue where re-running a Job that produced a Dataset Snapshot did not enforce Snapshot limits, allowing the target Dataset to exceed the limit.
• Fix issue where the SSH command shown for connecting to an App-hosting executor would sometimes be too long to display in the text field that showed it. Those text fields have been made scrollable for these cases.
• When users change the project default environment or the environment from the Workspaces dashboard, the available Workspace cards will now populate correctly with the Workspaces available in the chosen environment.
• Fix issue where hanging symlinks in the Dataset output directory could cause Snapshot creation to fail.

 

 

3.3.1 (February 20, 2019)

Welcome to Domino 3.3!

We’ve introduced some powerful new features for working with big data and managing your experiments.

New features

• Domino 3.3 introduces Domino Datasets, a new feature for high-performance storage of big data in Domino.
  
  Datasets get attached to your Runs in Domino as network directories, which greatly improves startup and sync times. Unlike project files, there is no limit to the individual file size, number of files, or total file volume you can store in Datasets.
  
  
  
  

  Note

  Datasets are available for use immediately for Domino deployments running in the cloud on version 3.3.1+. If you want to use Datasets with your on-premises deployment of Domino, contact your Customer Success Manager.

  To learn more about Datasets, read:

  • Datasets overview

  • Datasets best practices

  • Datasets advanced mode tutorial

  • Converting legacy Data Sets to Domino Datasets

  • Datasets administration

 

• Domino 3.3 also introduces new tools for managing experiments in Domino.
  
  The previous Runs dashboard has been replaced by a new Jobs dashboard.
  
  
  
  

  This new dashboard offers several enhancements, including:

  • Customizable columns of sortable data about your Jobs, including keys from dominostats.json

  • More powerful tagging features for quick and effective organization

  • Bulk actions to tag, archive, or stop Jobs

  Additionally, the Jobs dashboard only shows information about Jobs. Similar separate dashboards have been added where you can find the same information about Workspace sessions and Hosted Apps.

  Note

  While the new Jobs dashboard is enabled by default on new deployments of Domino 3.3.1+, if you have upgraded to 3.3.1 from a previous version of Domino, you may need to manually enable it.

  To enable the new dashboard, a system administrator must set the ShortLived.JobsDashboardEnabled feature flag to true.

  Contact support@dominodatalab.com if you need assistance.

• Domino CLI now auto-detects proxy configurations and should work out-of-the-box in more cases.
  
  Manual configuration of CLI proxy settings is still available if necessary.

 

Issues resolved

• Fixed an issue where Apps would sometimes render incorrectly due to the Domino toolbar not loading.
• Resolved an issue where the full name of the default hardware tier was not displaying on the Start Run dialog.
• Improved the performance of opening the Start Run dialog.
• Fixed a bug where transferring ownership of an environment to another user would fail.
• The /v4/organizations API POST endpoint will now use the real name parameter it receives for the organization name. Previously, this endpoint was always using an incorrect hardcoded value.
• Previously, users could POST to /v4/projects/projectToCopyId/copy multiple times with the same projectToCopyId, resulting in multiple identically named copies. Now, attempting to make a copy that would produce an identically named project fails.
• Fixed an issue where executors in on-premises deployments of Domino were sometimes shut down when they shouldn’t be.
• Fixed a bug where the edit option for environment name wasn’t showing up on the environment overview page.

 

3.2.9 (January 31, 2019)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Notes

• The Create Model form will now only list projects on which the user is an Owner or Contributor.
• Improved loading times of the Create Model form.
• Improved loading times of the Model Versions page.

 

3.2.7 (January 11, 2019)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Breaking changes

• There is no longer a feature flag to disable the Domino 3.0 UI. Versions of Domino 3.2.6+ no longer support using the old Domino 2.X UI.
• Previously, all models published in Domino would log model inputs and outputs by capturing the request and response body in the model instance logs. Request and response logging is now configurable with a checkbox when publishing a model version, and it defaults to OFF.

New features

• A new Quick Action button is available. Click Quick Action at the top of the project menu, or press 'A' with a project open to access quick actions.
  
  You can use quick actions to select and launch a workspace:
  
  
  
  Or start a run:
  
  
• The default landing page after signing in to Domino (https://<your-domino-url>/overview) has been changed to a new activity overview. On this page you can see your recent Runs, which includes Runs that are in-progress or finished in the last hour:
  
  
  
  And your scheduled runs:
  
  
  
  Click the name of a run to open it in the Runs dashboard.
  
  Previously, the default landing page was the Projects page. You can access this page by clicking Projects from the main menu. If you want to return to the activity overview, click Domino at the top of the main menu.
• You can now click the hardware tier and compute environment tab from the project menu to quickly change those settings in a fly-out menu:
  
  
• When scheduling a Run in a project that belongs to an organization, admins can now set the Run as field to any member of the organization.
• A new configuration point is available to change which LDAP field the Domino user fullName attribute is derived from. Set com.cerebro.domino.ldap.fullNameAttribute to the name of the LDAP field you want to use for fullName. This defaults to cn.
• New deployments of Domino 3.2.7+ will use MongoDB 3.4 for the central database.

Issues resolved

• To improve security, authentication tokens have been removed from Kubernetes pods where they were not required.
• Previously, after archiving a project, the project would continue to be listed in the Projects tab for the default environment used by the project. Clicking the project name in that table would result in a 404 error. Archived projects no longer appear in the Projects tab for their default environment.
• Fixed an issue where it was possible for two different users to create compute environments with identical names, then make both of them global. They would then not be distinguishable in the environment select dropdown. Attempting to make an environment global now checks for name uniqueness, and reports an error if the check fails:
  
  
• Previously, it was possible to archive an environment that was in use as the default environment by one or more projects. Those projects retained access to that environment until they were switched to a new default. Now, in order to archive an environment, it must not be in use by any projects. Attempting to archive an environment in use will result in an error.
• An issue that could cause an error when loading the Workspaces page was caused by incompatible versions of Apollo and some other Graphql dependencies. These have been updated to working versions.
• Fixed an issue that could lead to a race condition in the Domino object database.
• Fixed an issue where setting an EBS Volume Size Override on a hardware tier would sometimes not successfully change the volume size on executors.
• Previously, using Domino with kubeadm and autoscaling relied on some external dependencies that were not available entirely in Domino mirrors. These dependencies have been set up in mirrors.domino.tech and Domino is configured to use them.

Known issues

• A performance issue where the versions tab of a model can take a long time to render when there are many model versions.
• A performance issue where the models overview can take a long time to render when there are many models.
• An issue where Domino Frontend hosts can use excessive disk space for /tmp.
• The boilerplate comment in a new project’s .dominoresult file is inaccurate. Instead of:
  
  List the filenames here that you want to show up in the results view
  
  It should say:
  
  List the filenames here that you want to exclude from the results view
• A bug where trying to edit the description of a Run from the Runs dashboard may fail.
• Trying to select a V1 environment from the new compute environment fly-out menu is not supported. Attempting to do so will produce an Environment not set error toast.

 

3.1.10 (January 9, 2019)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Notes

• Domino services have been updated to run on Java 1.8.0_181.
• Fixed an issue where setting custom certificates with both domino.trusted_ca_cert_file and domino.ldap.trusted_cert_file could cause a race condition and fail to update the Java keystore.
• Fixed an issue where the /v4/project/<id>/copy endpoint could produce projects with identical names. This endpoint now enforces unique project names.
• Fixed a bug with the API endpoint to retrieve projects by owner that caused it to return an empty set even when provided with a valid user ID.
• Fixed an issue with the datasets V2 beta feature where attempting to write to a dataset from a workspace would cause the workspace to not shut down correctly, and the dataset write to fail.

 

2.11.14 (January 9, 2019)

Notes

• Fixed an issue where setting custom certificates with both domino.trusted_ca_cert_file and domino.ldap.trusted_cert_file could cause a race condition and fail to update the Java keystore.
• Fixed a bug with the API endpoint to retrieve projects by owner that caused it to return an empty set even when provided with a valid user ID.

 

2.11.13 (January 2, 2019)

Notes

• Amazon Elastic Container Registry images are supported as a base image for compute environments.
• Fixed an issue where the /v4/project/<id>/copy endpoint could produce projects with identical names. This endpoint now enforces unique project names.

 

2.11.12 (December 13, 2018)

Notes

• Fixed an issue where the Domino UI running in Internet Explorer would sometimes make duplicate API calls.

 

2.11.11 (December 7, 2018)

Notes

• To improve security, authentication tokens have been removed from Kubernetes pods where they were not required.

 

2.11.10 (December 6, 2018)

Notes

• Fixed an issue where on some upgrade paths a version incompatibility between several dependencies could cause the Workspaces page to fail to load.

 

3.1.6 (December 5, 2018)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Notes

• Fixed an issue where on some upgrade paths a version incompatibility between several dependencies could cause the Workspaces page to fail to load.

 

3.1.5 (November 15, 2018)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Notes

• This release focused on code refactors and small implementation changes to improve executor stability and central database performance.

 

3.1.4 (November 8, 2018)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Notes

• Fixed an issue that could cause users with Launcher user permissions on a project to hit a 404 error when trying to access the project's runs.

 

2.11.9 (November 8, 2018)

Notes

• The default read and connect timeouts for Domino executor replication have been increased to 120 seconds. These timeouts are now configurable with the following keys:

  httpService.connectTimeoutSec
httpService.readTimeoutSec

 

3.1.2 (October 29, 2018)

If you’re new to Domino 3, check out the welcome guide for information about the new UI design, and features like Launchpad and Control Center.

Notes

• Fixed an issue where enabling global two-factor authentication could cause some executors to fail to start.
• Previously, users opening Domino workspaces could sometimes run into a CORS issue when running notebooks with a subdomain, resulting in a 404 error. This issue has been fixed.
• A non-thread-safe implementation of some libraries in Domino was previously responsible for some cases of unusually high CPU usage. This has been fixed by changing to a thread-safe implementation.

 

2.11.8 (October 24, 2018)

This release of 2.11.8 follows the release of Domino 2.11.6.

Notes

• Domino now supports specifying a custom field from your LDAP server for specifying users’ full names. The previous standard value of 'cn' continues to be the default. Contact your Domino Account Manager to discuss making this change to your existing deployment.
• Previously, users opening Domino workspaces could sometimes run into a CORS issue when running notebooks with a subdomain, resulting in a 404 error. This issue has been fixed.
• A non-thread-safe implementation of some libraries in Domino was previously responsible for some cases of unusually high CPU usage. This has been fixed by changing to a thread-safe implementation.

 

2.11.6 (October 16, 2018)

This release of 2.11.6 follows the release of Domino 2.11.3.

Notes

• A new configuration option is available to set how many lines of logs to return when viewing run logs. The option logs.run.fetchSize controls this, and defaults to 10,000.
• Fixed an issue where enabling global two-factor authentication could cause some executors to fail to start.
• A new configuration option is available to disable user access to the Domino API and CLI. Set com.cerebro.domino.api.isEnabled to false to disable all programmatic access. Users will only be able to interact with Domino through the web application if this is set.
• The stdout panel in the Runs dashboard now polls for fresh stdout data from the active executor once every 3 seconds. This is a reduction in frequency from the previous value of 2 seconds, and will reduce backend load.

 

 

2.11.3 (September 11, 2018)

This release of 2.11.3 follows the release of Domino 2.11.1.

Issues resolved

• A metadata encoding issue that was causing some scheduled runs to fail when a deployment upgraded to Domino 2.11 has been fixed.
• Resolved an issue that caused model builds to fail when launched from a project with an attached external Git repository.
• Fixed an issue where under some conditions runs could get stuck in the Preparing state due to a failure to pull an external Git repository.
• Domino Executors will no longer be able to resolve symlinks in project files or external Git repositories. If you have workflows that depend on symlinks, you will need to refactor them before upgrading to Domino 2.11.3.

 

2.11.1 (September 11, 2018)

Issues resolved

• Fixed an issue present in 2.11.0 that caused runs and model builds to fail if an external Git repository had been added to the project. These builds will now succeed.

Security

• This patch changes the way Domino issues cookies to users of the Domino web application. Cookies are now always sent over SSL.
• Options have been added to disable some client-side monitoring features.

 

 

2.6.7 / 2.8.3 (September 1, 2018)

The following security patches are available in Domino 2.6.7 and Domino 2.8.3.

Security

• This patch changes the way Domino issues cookies to users of the Domino web application. Cookies are now always sent over SSL.
• To improve security, Domino Executors will no longer be able to resolve symlinks in project files or external Git repositories. If you have workflows that depend on symlinks, you will need to refactor them before upgrading to Domino 2.8.3.

 

2.11.0 (August 31, 2018)

This release of Domino 2.11.0 directly follows Domino 2.9.0.

Features

• Added new monitoring to track run status and executor health.
• Improved the layout and scaling of the Dispatcher Admin UI.

Issues resolved

• Fixed various issues with v1 API endpoints that were present in Domino 2.9.0. Deployments using v1 API endpoints can now safely upgrade from 2.8.0 to 2.11.0.
• Resolved a compatibility issue between v1 API endpoints running R code and the latest Domino Standard Environments.
• Fixed an issue where attempting to schedule a run could result in an error if the project had a previously scheduled run from past versions of Domino.

Infrastructure

• Connections to the Dispatcher Admin UI are now routed through the Domino Frontend. Previously, connections to this UI bypassed the Frontend.

 

2.9.0 (August 22, 2018)

Breaking changes

• Previously, when Domino hosted your model as an API endpoint, your project files were loaded onto the host machine at /project. Now, project files will be loaded at /mnt/<username>/<project_name> to be consistent with the behavior of Domino runs. An environment variable named DOMINO_WORKING_DIR is now set on model hosts, and will always contain the path to your project files. If you have models that depend on absolute paths to /project, you should update them before launching them in Domino 2.9.0.

Known issues

• If you stop a currently running App, switch it to run on a different hardware tier, then launch it, the App status panel will incorrectly show it running on the old hardware tier. Refreshing the page will update the panel, and show the correct hardware tier.

Features

• Running the Domino CLI with --version now also reports the version of Java that the CLI is using.
• The Domino CLI now supports Java 9.
• When creating a new app.sh file in a project, it will now contain commented code examples demonstrating how to launch applications for some common frameworks like Flask, Shiny, and Dash.
• When choosing an environment for a project from the project settings page, the list of environments in the menu is now alphabetized instead of chronological, to make it easier to find a specific environment.
• Model health checks can now be configured to start a specified duration after the model is launched, to avoid an infinite restart loop if your model requires additional time before it can serve requests. Use the Initial delayfield to set the desired duration.

• Timeout durations for models are now configurable to be higher than the previous default of 60 seconds. For AWS deployments, when changing this timeout you must also edit the idleTimeout setting on the Elastic Load Balancer (ELB) that serves model requests, as it also defaults to 60 seconds. See the AWS documentation to learn more.

  

Issues resolved

• Fixed a bug that caused the Domino CLI to always throw an error the first time a user ran update-check.
• Fixed an issue that could cause on-premise deployments of Domino to hang while pulling external Git repositories.
• Fixed an issue where copying a project you did not own would produce a copy with incorrect permissions.

 

2.8.1 (August 1, 2018)

Issues resolved

• Fixed an issue where an overflowing message buffer could crash the dispatcher.
• Improved validation on some dispatcher parsing operations.

 

 

2.6.5 (July 27, 2018)

Issues resolved

• Fixed an issue where an overflowing message buffer could crash the dispatcher.

 

Issues resolved

• Fixed an issue where the # character in filenames was producing some invalid URLs in the Domino application.
• Domino now correctly handles SSH connections to Git servers on nonstandard ports.
• Requests to the API that result in a 400 Bad Request error will now return application/json instead of HTML.

Beta endpoints

• Domino 2.8.0 introduces some v4 beta API endpoints for interacting with users, organizations, and projects. Visit the redesigned API documentation site to learn more.

 

2.6.4 (July 23, 2018)

Features

• Model health checks can now be configured to start a specified duration after the model is launched, to avoid an infinite restart loop if your model requires additional time before it can serve requests. Use the Initial delay field to set the desired duration.
• Timeout durations for models are now configurable to be higher than the previous default of 60 seconds. For AWS deployments, when changing this timeout you must also edit the idleTimeout setting on the Elastic Load Balancer (ELB) that serves model requests, as it also defaults to 60 seconds. See the AWS documentation to learn more.

 

2.7.1 (July 2018)

Issues resolved

• Fixed compatibility issues with Domino 2.6 and Jupyter Notebooks running versions of Jupyter older than 4.2.
• Resolved an issue where executors were sometimes being put into Maintenance Mode while stopped.

 

2.6.3 (July 2018)

NOTE

This version patches issues in prior versions of Domino 2.6, but is not the latest release of Domino. New deployments should use Domino 2.7+

Issues resolved

• Fixed compatibility issues with Domino 2.6 and Jupyter Notebooks running versions of Jupyter older than 4.2.
• Added support for connecting to Git servers via SSH on ports other than the default (port 22).

 

2.7.0 (June 2018)

New features

• The Account Settings page for user accounts now includes several new fields:

  • Added Project Environment Default. Users can use this field to set an environment to be the default for new projects they create, instead of using the deployment default.

  • Added Workspace Settings. Users can now configure their workspaces to shut down automatically after a specified runtime. New projects will inherit this setting from the user that creates them.

    

• The Domino search field now supports searches for exact matches on quoted text.
• When downloading the Domino Command Line Interface (CLI) from a deployment, the URL needed to log in to that deployment is now displayed under the download button.

Issues resolved

• Error messages related to cloning and fetching external Git repositories have been improved.
• Duplicating an environment now creates a copy of the original’s latest active revision, and preserves all metadata and logs.
• Models being deployed will now report availability sooner.
• Fixed a bug where capital letters in the middle of a word in a search query would split the query into two terms.
• Git repositories that have been cloned onto an executor but have not been used by a run for more than 1 week will now be automatically cleaned up to save disk space.
• Fixed an issue where runs that produces many file changes or large file changes could take a long time to finish when shutting down.
• Domino now correctly handles SSH connections to Git servers on nonstandard ports.

Infrastructure changes

• Executors now have a health check that will mark them as unhealthy if they are unable to reach the fluentd logging service for more than 5 minutes. The duration associated with this health check is configurable.

 

2.6.2 (June 2018)

New features

• If you have added an external git repository to your project, you can now publish a model using code in that repository. When specifying which file and function to use for the model, supply a full path to the file as it would appear in a Domino workspace, like: /repos/repo-name/filename.py.

Issues resolved

• Fixed an issue where the date picker UI for date parameters on launchers was not entering the selected value.

• Environment variable values can no longer overflow their field. Long values will be truncated with an ellipsis. Users can click to expand the field to multiple lines and see the full value.

  

• Fixed an issue where inviting users to collaborate on a project in deployments using SSO or LDAP would email a link to the sign-up page instead of the correct authentication portal.
• Performance of the Model Overview interface has been significantly improved.
• Resolved an issue where the select all checkbox in the header of the Domino file browser would sometimes not work correctly.
• Fixed an issue where the title of a run in the run detail pane was sometimes displaying with incorrect padding.

 

2.6.1 (May 2018)

New features

• The workspace UI now shows a full path to modified files when syncing external repositories.

  

• Updated the sign-up page for GDPR compliance.

Issues resolved

• Resolved an issue where runs could take longer than expected to stop.
• Fixed where UI elements on some pages were not rendering correctly in Internet Explorer 11.
• Previously, syncing a workspace with symlinks to non-existent directories or unmounted directories could cause the sync to fail. Syncs now skip these unresolvable symlinks.
• Fixed an issue where adding environment variables to a compute environment could cause the build to fail due to incorrect decoding of certain characters.
• Fixed an issue with Domino CLI 2.6.0 where incorrect default logging settings could lead to very verbose logs.

2.6.0 (May 2018)

New features

 

• When pushing to external repositories from the Workspace UI, all Git operations performed by Domino are logged and displayed in the Logs tab of the Session Overview.
• When loading a new Workspace on an existing executor with cached clones of external repositories, Domino now automatically performs a git fetch on those repositories to ensure newly created branches in remote are accessible in the Workspace.
• Applying the tag release to a run will prevent the run from being archived. This can be used to prevent archival of project states that other projects import and depend on.

Issues resolved

• In version 2.5.2, a feature for automatically stopping instances that had been in Maintenance Mode for a specified time was added to Domino. However, Domino would only stop such instances if they responded to status requests. Domino will now stop these instances even if they do not respond to status requests.

Infrastructure changes

• Following the introduction in Domino 2.5.2 of automatic shutdown of executors in Maintenance Mode, we’ve removed the ability to set a maximum number of Maintenance Mode executors.

 

2.5.2 (May 2018)

This release directly follows Domino 2.5.0.

New Git features available in Workspace UI

• Previously, users who wanted to push to their remote Git repositories had to do so manually through the workspace command line. In version 2.5.2+, Domino is now able to commit and push to remote Git repositories automatically through the improved workspace UI. See all the details in Git repositories in Domino.

• The Session Overview panel now shows pending changes in Git repositories file-by-file, and each repository has a checkbox that controls whether changes are committed when the user performs a Full Sync:

  

  When committing, the modal window now lists all repositories with changes set to commit, and Domino applies the commit message entered by the user to both the project revision and the commit it makes to each repository. If no commit message is entered, Domino will default to Committed from Domino:

  

  Attempting to stop a workspace while there are uncommitted changes shows a UI similar to the Session Overview, with a list of all modified files in changed repositories. Users can click the checkboxes next to the listed repositories to control which are committed to:

  

  The notification that appears when Domino encounters a conflict upon pushing a new commit to a Git repo has been changed from a small toast to a modal window with clearer explanation of what occurred:

  

• The description text in the Git Credentials panel of the Account Settings page has been expanded to describe when to generate a Personal Access Token versus an SSH key. This description text will always display. It is no longer hidden once a credential has been added.
• Previously, Domino would not clone submodules of any added repositories during a run or workspace session. Domino will now clone those modules, but it will not commit changes to them when pushing changes to the containing repository.
• The files tab in Jupyter workspaces will now include a ../ link so that users can open the parent of the current directory. When clicked from /mnt, this will open the executor’s filesystem root and allow the user to access Git repositories in /repos.

Other new features

• Adding a collaborator to a project that includes Git repositories now displays a message notifying the user that the new collaborator will need access to those repositories in the Git service before they can work with the project.
• By default, when adding collaborators to a project that is part of an organization, Domino will show autocomplete results for users that are not members of the organization. It is now possible to prevent this by settingcom.cerebro.domino.frontend.restrictCollaboratorsToOrganizations to true in the Central Config. With that setting enabled, only users who are members of the organization will show up as autocomplete results when adding collaborators to projects in that organization.
• Previously, if a user had set the active revision of an environment to something other than the latest, there was no way to get the environment to return to the previous behavior of always using the latest revision. If a revision has been manually set, there will now be a button on the Revisions tab to Set Active Revision to Latest that restores the original behavior.
• Email notifications for new comments in Domino now include the name of the user who wrote the comment.
• The interface for scheduling a run now displays the timezone that Domino uses for executing scheduled runs.
• Domino CLI 2.5.2+ supports logging in with your Domino API key, to support deployments that use Single Sign-On. When SSO is enabled, the CLI will prompt users to enter their Domino API key, which is visible in Account Settings.

Issues resolved

• An issue that was preventing comments from being archived under some conditions has been fixed. Comments should now be reliably archived.
• The “check out our product tour video” link in the quick-start project created for new users has been fixed to point to the correct URL.
• Fixed an issue where launchers could sometimes fail to delete.
• The web application now checks to see if cached dependencies are of the correct version. Cached dependencies are cleared and the correct version is downloaded where necessary, preventing users from seeing a stale interface after upgrading Domino.
• Hardware tier costs displays have had their precision increased from two decimal places to four decimal places. Previously, very low running costs like $0.0015 could show up as $0.00.

Infrastructure changes

• Improvements to the Kubernetes system drivers Domino uses when building environment images will improve build times significantly. The new drivers will be used automatically on new deployments of Domino 2.5.2+, but older deployments will require manual intervention to switch to the new drivers on upgrade.
• Instances that are placed in Maintenance Mode will now be automatically stopped after 2 hours of idle time by default. This value is configurable by admins to be longer or shorter.
• The executor template for new deployments of 2.5.2+ will run Ubuntu 14.04 and CUDA 8.0 by default. Support for Ubuntu 16.04 is available.
• Amazon Machine Images used for Domino hosts and executors now support Enhanced Networking with the Elastic Network Adapter.

 

2.5.0 (April 2018)

API

• New API endpoints are available in this release related to model publishing. It is now possible to publish models and get information about existing models through the 2.5.0 API and CLI.
  
  Check out the API docs to learn more, or install the Domino CLI from a deployment on version 2.5+ to try these new commands:
  
  
  • publish-model: Creates and publishes a model for a project
  • project-models: Get all models using a project
  • publish-model-version: Publish new version for a model
  • latest-model-version: Gets the latest model version for a model

Note: The format of these endpoints is likely to change. The current specification will not have long term support beyond Q3 2018.

Application

• Fixed an issue where saving edits to a hardware tier could create a copy of the hardware tier with the new settings, instead of modifying the settings for the intended tier.
• The custom email notification feature has been changed to only use a custom email.html template file if it appears in the results of the run generating a notification. Previously, this feature would use a custom template if it was found anywhere in the latest project commit.
• The file size of a major JavaScript bundle loaded by the web application has been reduced by ~85%. This should improve
  UI load times.
• Previously, when launching a workspace or scheduling a run, users would see a dropdown menu to select a hardware tier
  that looked like this:
  
  
  
  The project default option has been made more explicit in this menu, and text has been added explaining that once this option is set for the workspace or scheduled run, changing the default hardware in the project settings will not override the listed hardware. The menu now looks like this:
  
  
  

Infrastructure

• Previously, some executors could run out of disk space due to incomplete clean-up of unused images and data from past runs. Jobs that perform periodic removal of unused images have been made more thorough to prevent this.
• Fixed an issue where attempting to publish to an archived model could stall the Dispatcher.

2.4.2 (March 2018)

Application

• The dialog that alerts the user to uncommitted changes in non-Domino Git repos has been redesigned for clarity.

• Creating a duplicate of a compute environment no longer sets an erroneous active revision for that environment.

Command Line

• Fixed an issue where the Domino CLI was failing to find the correct version of Java.

Infrastructure

• Fixed an issue where GPU hardware was not mounting correctly on some executors.
• The deployment tool can now perform a quick automatic backup, and has a more thorough configuration wizard.

2.4.1 (February 2018)

Continuing upon the theme of the 2.4 release, this point release is primarily a maintenance release. Below are major changes in this version:

Infrastructure

• Improvements to the Domino logging architecture for performance and stability

Application

• For reproducibility: improved link from commit messages for project files to the run associated with that commit.
• For environments: better communication of environment revision status.

2.4 (February 2018)

This release focuses on improving overall stability of the Domino application and lays the foundation for future improvements. Below are major changes in this version.

Models & apps

• Support for publishing large models - up to 8gb.
• Apps can now be shared publicly without exposing the project/code publishing the app. You can do this on the App tab of Publish by selecting the checkbox under the “Publicly Visible” column.

Admin

• Admins can fully clone hardware tier settings.

Infrastructure

• Substantial upgrade to Kubernetes for on premise Domino deployments, which encompasses general stability improvements and the option of high availability for Kubernetes.

Fixes

• Fix for issues with blank screens and erroneous 404 messages when starting a workspace.
• Performance improvement to prevent long run history from consuming excessively high CPU on Domino frontends.
• System logs now automatically rotate to prevent high disk usage issues.
  
  

2.3 (December 2017)

Workspaces

“Workspaces” have been added to the left hand navigation bar within projects. Users can launch new workspaces and access active and completed workspaces directly from this “Workspaces” link.  Workspaces also remain accessible from within the “Runs” page.

When stopping a workspace from within a running workspace, Domino now displays a prominent overlay indicating to the user that the workspace is being stopped.

Hardware tiers

When selecting a hardware tier for a project or when starting a new workspace within a project, users can now see the expected queue time for each hardware tier prior to making a selection.

Project and file revisioning

To alleviate any confusion when viewing an older version of a project or file, Domino will now change the display color of the page and display a message indicating that an older version is being viewed.

 

Environments

Users may now reuse environment names from previously archived environments. It is also possible to click from the project settings page directly to the active environment’s management page.

When editing or authoring dockerfile instructions in an environment definition, the text input fields will now auto-expand to fit contents.  Users will also now be able to simply click the "R Package" or "Python Package" buttons below the dockerfile instructions input field to insert template commands for installing packages of each type.  

Model Manager

Users now have improved visibility into instance-level deployment status and failures.

Importing git repos

User interface improvements for importing git repositories.

2.2 (late September 2017)

Projects UX Improvements

The files page in projects got an overhaul with much needed file management features like rename and move. We also made it easier to discover and manage git integrations and imported projects from the file page.

Runs will now display more information when they are queued -  the reason for queuing is shown and where possible, suggestions are provided to reduce queue time.

Account Management 

Users can now change their email, name and username. Administrators can deactivate and reactivate users. The accounts of users who leave the company or sign up without authorization can be deactivated, and Admins are also able to transfer scheduled runs that were connected to disabled accounts.

Model Manager Improvements

In this release we added beta support for models larger than 500 MB. We also made several changes to make deployments smoother and reduce chances for user confusion and also added several features for administration of the models infrastructure.

2.1 (early August 2017)

Compute Environments V2 - General Availability

The new Compute Environments are now available for all customers that have the Kubernetes infrastructure installed.

• Environments are versioned
• Environment versions are built once and then cached. This leads to more reliable performance leading to less time spent at the “Building” run state.
• Past runs can be re-executed with the same environment as originally leading to better reproducibility
• Environments can be used with Models (see below) to create immutable, reproducible, versioned models. 
• Documentation: V2 Compute Environments

 

Model Manager - General Availability

We have done a complete re-architecture of our “API Endpoints” functionality, which allows teams to deploy Python and R models in seconds as horizontally-scalable, high-availability API endpoints.

• The new architecture supports web-scale use cases at low latencies
• Sophisticated promote-to-production workflow
• Provides improved security and access controls with “Models” now treated as a first-class entity, distinct from the Projects that developed them

We have the following major updates in this particular release:

• Resource management improvements to reduce chances of models not getting enough memory to startup
• Models from projects that have imported projects will now also import those projects by default.
• Models can now support cross origin requests and sample Javascript code was added for this.
• Models can now take request bodies of upto 10MBs.
• Documentation: Model Manager Overview

*Please contact your customer success manager for help enabling this and beta-testing feature.

 

Configurable interactive session tools - General Availability

Many of our users have asked for custom interactive session tools beyond the current Domino offering of Jupyter, RStudio, PySpark, and Zeppelin.  This new functionality gives Domino the flexibility to support any web based tool like JupyterLab.  Users can configure the tools available to a project via its Environment (v2 only), making it easy to:

• Upgrade to a newer version of currently supported Domino notebooks like Jupyter or RStudio
• Add new web based tools like sqlpad and JupyterLab
• Manage the standard default tools for a team or organization across all projects

See our support article for more information or contact your CSM.

 

SAS Studio support

Through the new functionality around configuring interactive session tools, Domino users can configure environments to make SAS Studio available in projects. This means SAS Studio will launch and sync back to Domino along with the other Domino-supported tools, such as Jupyter Notebooks and RStudio. Customers will need a SAS for Containers license in order to use this feature, and will need to work with their Domino CSM.

 

Direct run support for SAS scripts in Domino

Users can now execute SAS scripts in Domino via web UI and CLI by simply choosing a file to execute, just as they are already able to do with R and Python.

 

Limit hardware tiers by organization

Domino administrators are now able to limit access to specific hardware tiers by organization. This functionality can come in very handy granting access to a specialized set of resources for large projects or teams that need more horsepower.

 

 

 

2.0 (early July 2017)

 

Model Manager (beta)

We have done a complete re-architecture of our “API Endpoints” functionality, which allows teams to deploy Python and R models in seconds as horizontally-scalable, high-availability API endpoints.

• The new architecture supports web-scale use cases at low latencies
• Sophisticated promote-to-production workflow
• Provides improved security and access controls with “Models” now treated as a first-class entity, distinct from the Projects that developed them

*Please contact your customer success manager for help enabling this feature.

Shared Storage Support 

Domino now support shared storage for imported projects, significantly speeding up the use of data projects imported into experimentation projects. Users can manage the space being used in their shared storage through the Domino Admin interface.

Faster Finishing Times 

We've made some changes under the hood to significantly improve run finishing times.

Security Improvements 

We've made some improvements to user account security, including increasing password complexity requirements.

 

1.59 (June 2017)

Redesigned Interactive Sessions screen

We have redesigned and enhanced our Interactive Sessions screen to make it easier to use and sync with Domino. Some of the new functionality includes:

• Improved status messaging, including surfacing when file changes in the session have yet to be committed to Domino
• The ability to submit a commit message when stopping and committing changes from within an interactive session
• An improved filter on the "files" section of your project to make it easier to find the revision you're looking for

 

 

1.56 (late April 2017)

Technology preview*: Configure new Interactive Session tools

Many of our users have asked for custom interactive session tools beyond the current Domino offering of Jupyter, RStudio, PySpark, Zeppelin and H2O notebooks.  This new functionality gives Domino the flexibility to support any web based tool like sqlpad or JupyterLab.  Contact your customer success manager if you would like use a new tool in Domino.

 

Technology preview*: New Model Management

We have done a complete re-architecture of our “API Endpoints” functionality, which allows teams to deploy Python and R models in seconds as horizontally-scalable, high-availability API endpoints.

• The new architecture supports web-scale use cases at low latencies
• Sophisticated promote-to-production workflow
• Provides improved security and access controls with “Models” now treated as a first-class entity, distinct from the Projects that developed them
• Read about it in our Domino 2.0 blog post

 

The following capabilities are also in technology preview:*

• Environment Management V2

 

We have introduced Data as a new area of the product.

The addition of "Data" as first-class entity is a new concept we have introduced to simplify the data workflow for our data scientists and data science teams.

• Easily create data sets from scratch or from within an existing project
• Keep an inventory of all data sets in one location and easily find data sets available to you
• Data Sets are automatically configured to "export" files so that projects can easily import them

 

User Experience Improvements

• You can now see repository branch information without having to click to edit:

• Made the save button more intuitive when editing a repository:

• Results Consumers can now leave comments to provide feedback on files in a project
• We fixed the drop target for uploading files so that it is now much easier to drag & drop files into a project

 

Infrastructure Improvements

• Fixed a bug with pip-installs of private Github repos where git domain credentials were not working with no repository enabled
• Fixed a bug where users could not batch run a Jupyter notebook that was nested in a folder
• Fixed a bug where emails sent to invite collaborators to a project were not rendering custom messages with special characters properly

*Please contact your customer success manager for help enabling these features

---

1.55 (mid April 2017)

The following capabilities are in technology preview*:

• Environment Management v2

 

User Experience Improvements

• Continued improvements to our technology preview of Environment Management v2
• We have added Notebook Settings that give you the option to automatically shut down a notebook session after a set amount of time (does not apply to scheduled jobs or batch runs):

• We fixed a UI issue with .zip and .gz files so that we no longer attempt to render these file types
• Fixed a bug where navigating to a run URL was not directing you to the specified run

Infrastructure Improvements

• Fixed a bug where Kerberos authentication was not working for collaborators
• Fixed a bug where getting the status of a repository took a long time and blocked the ability to stop the run

*Please contact your customer success manager for help enabling these features

---

1.54 (late March 2017)

The following capabilities are in technology preview*:

• Environment Management v2

Two-factor Authentication is now available for all users and deployments.

This release introduced the ability for Administrators to require 2FA for specific users or entire deployments.  Contact your customer success manager if you would like this enabled in your account.

User Experience Improvements

• Continued improvements to our technology preview of Environment Management v2
• We removed the requirement for email when creating a new organization:

Infrastructure Improvements

• Fixed a bug in our Git support where the repository did not finish cloning before the run started

*Please contact your customer success manager for help enabling these features

---

1.53 (mid March 2017)

The following capabilities are in technology preview*:

• Environment Management v2
• Two-factor authentication is now available

User Experience Improvements

• Continued improvements to our technology preview of two-factor authentication
• Results Consumers can now see the API Endpoint Publish page with the status and version of any published endpoints as well as instructions for how to execute them:
  

 

• Moved the "Collapse Setup Output" option to the top of the page on the console output tab of the runs dashboard to make it easier to navigate to the logs and view results button at the bottom of the page:
  

 

• Fixed a bug where the link to an imported dataset in the runs details page was navigating to the wrong location
• Fixed a bug so that now when you click "Discard" from the run pane, there is a confirmation modal just in case you were not intending to discard your results:
  

 

*Currently limited to customers on our cloud offering. Please contact your customer success manager for help enabling these features

---

1.52 (Late February 2017)

The following capabilities are in technology preview*:

• Environment Management v2
• two-factor authentication (2FA)

User Experience Improvements

For projects with an attached Git repository

• Users now have the ability to specify the repository reference (commit id, branch, tag) directly from the advanced batch run dialog
• From the runs dashboard, when the user selects "Re-run with Original Version" we use the originally specified repository reference
• From the runs dashboard, when the user selects "Re-run with Latest Version" we use the most up-to-date repository reference

*Currently limited to customers on our cloud offering. Please contact your customer success manager for help enabling these features

---

1.51 (mid February 2017)

All Domino-managed cloud environments now have our new first-class Git integration enabled. This release introduced the ability the to specify a branch, tag, commit, or custom git reference along with stability improvements. Thank you again to all of our beta testers!

The following capabilities are in technology preview*: Environment Management v2

User Experience Improvements

• Outputs in the interactive run tab now wrap so users do not have to scroll horizontally to see full output logs.
• Continued improvements to our technology preview of V2 environments including the ability to change the visibility of an environment after it has been created. (Environments can be owned by a user, organization, or be globally accessible to all users.)

Infrastructure Improvements

• Domino now logs the timestamps related to run states to enable administrators to perform meta-analysis on the health of their Domino cluster.

* Please contact your customer success manager for help enabling these features

---

1.50 (early February 2017)

The following capabilities are in technology preview*:

• Environment Management v2
• Improved Git Integration and Support

User Experience Improvements

• Continued improvements to our technology preview of new Git support including better error messages and styling updates of the run’s details pane
• Continued improvements to our technology preview of V2 environments including user interface tweaks around navigation (including adding “Environments” to the top blue navigation bar to be more discoverable) and around how we treat archived environments. We also fixed a bug where environments with VPN were not able to be edited by non-administrators
• We have moved our notification banners to the top right of the screen so the navigation bar is always accessible
• Fixed a bug where a scheduled run could not be edited

Infrastructure Improvements

• Domino administrators can now save time by overriding hardware tier hard drive disk sizes without having to create a new AMI. We’ve documented this process in our Cluster Controls knowledge base article
• Added additional garbage collection functionality to help ensure executor disk drives are clean and have enough room for new runs

* Please contact your customer success manager for help enabling these features

---

1.49 (late January 2017)

The following capabilities are in technology preview*:

• Environment Management v2
• Improved Git Integration and Support

User Experience Improvements

• Improvements to the new environment management system including the ability to set environment variables and various user experience improvements
• Improvements to git integration including the reconciliation of legacy and new Git Credentials on users’ account settings page
• Added logic to ensure preparation and build logs always stream to a user
• Jupyter startup logs no longer show up in red as if they were an error
• You can now remove run tags

Infrastructure Improvements

• Added configuration option to set the minimum amount of free space on an executor
• Fixed an edge case where a successful run would be marked as “Failed”
• Fixed an issue in the Domino Client (command line client) for Mac users
• Fixed an issue where executor termination timeouts were not being acted on

* Please contact your customer success manager for help enabling these features

---

1.48 (early January 2017)

Technology preview*: New environment management

• We rebuilt Environments from the ground-up to support future expansion of Domino. Supported by new infrastructure for increased reliability. 
• Improved linking between environments, runs, and projects.
• Environment construction is more efficiently cached for faster and more reliable performance leading to less time spent at the “Building” run state
• Documentation: V2 Compute Environments
• Related blog post: Enabling Data Science Agility with Docker

UX Improvements

• Re-organized the Projects Overview screen to include tabs for easier navigation for users with many projects
• Related to the First-class Git integration* introduced in 1.47, we added the ability to authenticate using SSH keys and improved the documentation:
• Adding a Git repository to a Domino Project
• Authenticating with your Git repository
• Fixed a bug where run output was not always displayed in the run details pane

Infrastructure Improvements

• Added the ability for admins and support users to reorder the run queue from the Dispatcher view
• Improved Domino Client (command line client) stability and made errors more user-friendly

* Please contact your customer success manager for help enabling this feature

---

1.47 (mid December 2016)

Technology preview*: First-class Git integration and support

For teams that rely on Git management systems, we wanted to support their experimental workflows

• Public/Private GitHub (Enterprise) repository support from the Files page in a project
• If using private repos, users can specify a Personal Access Token from the Accounts settings page (Git Domain Credentials)
• Runs will alert and can be cancelled if Git repos have uncommitted changes when run is stopped

UX Improvements

• New feature flag system to help Domino administrators enable features both globally and for specific users

Infrastructure Improvements

• Results consumers can now call API Endpoints with their API key
• API Endpoints now respond to cross-origin requests
• API Endpoints now support Python 3 through a feature flag*
• Miscellaneous security and stability improvements

* Please contact your customer success manager for help enabling this feature

---

1.46 (early December 2016)

UX Improvements

• Excel files are now rendered in the browser
• Project import settings have been moved to the "Files" tab
• You can now SSH into batch runs
• Added note to Access & Sharing page clarifying that organizations can be added as collaborators to projects

Infrastructure Improvements

• Improved executor and log retrieval reliability and performance
• Improved reliability of connections for downloading and uploading project files
• Fixed edge case where review requests were unable to be merged

---

1.45 (early November 2016)

Improved experience for results consumers featuring full-page file sharing and an improved versioning UI

UX Improvements

• Added progress indicator to console output for runs during the “Preparing” stage; this is useful for projects with many and/or large files
• We now prompt users to confirm that they want to archive a comment
• Moved the ability to rename a project to the Settings page
• Added an R (httr) example to the API endpoints examples

Infrastructure Improvements

• API endpoint stability improvements
• Improved executor stability and ability to recover from errors
• Domino admins can now specify an AWS region when using SES for email
• Domino admins can now specify user data for hardware tiers

---

1.44 (late October 2016)

Structured Statistics Improvements

Domino users can use structured statistics (e.g. R^2, p-value) to evaluate the performance of experiments. Two enhancements to the dominostats.json facilitate easier consumption of results:  

• dominostats.json rendered as a table in results pages and the results dashboard
• dominostats.json visually diff’ed in runs comparison

Easier Access to Published Applications

Domino allows users to create web applications for easy consumption of data science results by other users. We now directly link to published apps from the Project Overview page so it is easier to discover and consume models these information products.

Enhancements & Bug Fixes

• Improved Markdown file rendering format
• Warn project owners and collaborators when they attempt to stop a run they didn't start
• Added a way for admins to create password reset links
• Bug fixes for SSH for on-premise deployments
• Fixed “Invite Pending” collaborator status to not be case-sensitive
• Fixed an issue where HTML special characters would be rendered incorrectly in the file comparison view
• Fixed an issue where the Domino CLI would fail to upload in projects over a certain number of files

---

1.43 (early October 2016)

Organization Ownership Transfer
Organization owners can now transfer ownership of the organization to another member.

Enhanced Kerberos Support
New user-specific keytab support, allowing users to authenticate as themselves when connecting to Kerberos-secured systems, like YARN.

Enhancements & Bug Fixes

• SSH access tweaks: fixed an issue where users couldn’t connect in certain network configurations, and SSH sessions now automatically start in the Domino working directory and have basic environment variables set
• Tweaked project entitlements for collaborators: non-owners can now no longer see certain aspects of the project configuration.
• Users can no longer archive preparing runs (which could create a situation in which is was impossible to stop those runs)
• Added a new Domino API endpoint to upload a file
• Fixed an error when forking a project using a pre-existing name.
• You can now access the user who started the run as an environment variable
• Fixed an issue where runs started from the previous commits would use the wrong starting commit 
• Modal windows can now be dismissed using the escape key
• Fixed a bug where HTML files hosted in Domino could not source other files within the project
• Added a new read-only "support staff" role who has all the read privileges of the original "support staff" role but cannot do any of the write actions
• Fixed an issue where, in a large review request, the “too many files” warning message was misleading
• Fixed a bug where the Domino CLI failed when encountering git submodules

 

---

 

1.42 (late September 2016)

LDAP Integration Improvements
With LDAP/Microsoft Active Directory support, Domino allows users to log into their private Domino deployments using their Windows credentials. This allows Domino administrators to centrally administer user accounts.

Domino has integrated LDAP / Active Directory for some time, but in this release, we have rewritten our implementation from scratch to make this connector more robust and to fix some specific issues, including:

• Making the LDAP login failure message configurable
• Ensuring quick-start projects are created for LDAP users by default

Kerberos Support for Hadoop / Spark Clusters
Domino now supports Kerberized authentication for YARN clusters, making Hadoop and Spark workloads function much better through Domino.

With this functionality, users can now attach a Kerberos keytab to Projects. Runs executed in this Project will automatically authenticate as that specified Kerberos principal.

Enhancements and Bug Fixes

• Tweak project entitlements for result consumers: they can no longer see certain aspects of the project configuration
• Expose the hardware tier that a run is executing on both as an environment variable and also via the API
• Fix an issue where the CLI download link was misconfigured
• Overhaul how public projects handle runs started by anonymous users
• Small interface enhancements: fixed an issue when clicking organization name from the account settings page would scroll to the incorrect location and fixed the formatting of notebook control buttons when in embedded mode 
• Fix incorrect documentation link on App Publishing screen 

 

---

1.41 (early September, 2016)

Enhancements

• (AWS Mode) Added the ability to tag launched instances with a dynamically computed expiration date
• Prevent user from creating an environment with an empty name
• Clarify file size limits when uploading files through the browser
• Make email configuration simpler by automatically cleaning up certain settings
• Improve how cached files are handled on Executors, making out of space errors much less likely to affect user Runs

Bug fixes

• Fix an issue that would cause project creation to fail nondeterministically

---

1.40 (late August 2016)

Enhancements

• Prevent user from inputting invalid Git host in the Git authentication integration panel
• Managing the space used by the working directory of all Executors is now centralized in the Admin section. (Previously it was necessary to log into each Executor individually.)

Bug fixes

• Fixed an issue with noisy but harmless alerts when restarting the Dispatcher node
• Fixed an issue in EC2 mode where Domino executors could not boot when no public hostname was set
• Fixed an issue where Domino runs would fail if many runs completed at nearly all the same time (DOM-1659)

---

1.39 (mid-August 2016)

New features

• Domino now supports connecting to Spark clusters using a YARN backend.
• We've extended full Domino support for Spark through Zeppelin notebooks. Users can now interact with their Spark clusters using Jupyter, RStudio, and Zeppelin through Domino.

Enhancements

• Users can create folders in projects through the Files tab

Bug fixes

• Under certain circumstances, anonymous users could not execute runs in projects that had "allow anonymous execution" enabled.  This is now fixed.
• Loading the settings page of projects using a deleted custom environment now works
• Fixed an issue where image overlay in run comparisons did not work in Firefox

---

1.38 (early August 2016)

New features

• Domino now allows for direct SSH access. Users can SSH into the executor environment where their code is running. This feature provides users all the power of UNIX / command line tools to augment the work they were doing inside a batch script or an interactive session (for example, to act as a secondary interface to access data, code, and git repos). Note that this feature must be enabled by an admin, and is currently available for on-premises deployments only.

Enhancements

• When Spark integration is enabled, a run will fail if spark-defaults.conf is not writable. In the past, runs would continue in these circumstances.

• When a user requests to stop a run and discard the results, Domino requests confirmation from the user before continuing.

• Users with read-only access to a project can now submit review requests. Previously, these users could fork projects but not merge them, and only users with contributor access to the original project could submit review requests.

• Admins can now set the total number of files rendered during merges. Previously, this was capped at 250. Additionally, forking and merging is now faster, even with a large number of rendered files.

Bug fixes

• Domino now properly ignores casing when ordering files on the File Browse page.

• The Users page has been redesigned and optimized to improve performance.

 

---

1.37 (mid-July 2016)

New features

• Domino users can now set their notebook working directory from the Domino web interface. This option can be configured in the Environment variables section of the Settings screen.
• Users can also select environments from an automatically-generated drop-down list of all their organization’s available environments. This list includes all environments to which the user has access, regardless of which organization controls each environment, and can be found in the Compute environment section of the Settings screen.
• Administrators can now migrate logs between Elasticsearch and Mongo. This can be accomplished within the Admin section by selecting Migrate Run Logs from the Advanced menu. From there, search for the appropriate logs using the run ID.

Enhancements

• Domino can now execute a scheduled job before the previous scheduled job ends. This enables users to run scheduled jobs in quick succession, when necessary. Previously, Domino would wait to launch the second scheduled job until the first one was complete.
• It is now possible to configure a range of ports for Domino to use with Spark. This addresses issues seen with certain types of firewalls inadvertently blocking access to Domino.

Bug fixes

• It is now possible to download files with names that include commas or nonstandard characters directly from the Domino UI.

 

---

1.36 (early July 2016)

New features

• Users can now easily access and use SparkR from within RStudio. For details on this new feature, visit the Domino blog: https://blog.dominodatalab.com/enhanced-apache-spark-integration/
• Docker runs are now subject to resource constraints. This helps keep memory usage under control during Docker runs. These constraints can be configured by your organization’s Domino administrator. For more details on configuring Docker resource constraints, contact Domino’s Customer Success team.

Enhancements

• Admins will receive a warning from the Dispatcher dashboard if an executor instance is unreachable. Previously, no notice was provided.
• An explanation of Spark configuration options has been added to the Spark configuration page, along with a link to more detailed descriptions of those options.

 

---

1.35 (late June 2016)

Enhancements

• The user interface of the File Detail page has been enhanced to improve clarity and provide for a more intuitive user experience with regard to notebooks. The buttons for launching notebooks and running files have been moved and redesigned to improve visibility.

 

Additionally, the inline file actions have also been reordered to help deliver a more consistent user experience across the browsing and detail views.

• Users can now easily add multiple email addresses at once to an organization. Simply separate each address with a comma, space, or tab. Previously, users had to re-click on the Members tab after adding each new email.

• Users can also add multiple collaborators to a project at once. Previously, after adding each collaborator, users were taken back to the Hardware and Environment tab, instead of remaining on the Access and Sharing tab.

Bug fixes

• For RStudio interactive sessions, the Open Session button has been moved to the bottom of the console log to improve visibility. Previously, this button was at the top of the log, and it was often pushed out of view as lines were added to the log.

 

---

1.34 (early June, 2016)

New features

• Users can now stop runs without saving the changes generated by those runs. This means Domino users can engage in more experimentation and engagement of “what if” scenarios without worrying about overwriting anything in the process.

Click the “Stop & Discard Changes” button to stop the run without saving anything.

• Users now have the ability to archive comments. This will allow users to “clean up” comment threads as discussions move in different directions while still retaining a level of auditability, resulting in cleaner, less cluttered threads.
• Domino now provides PySpark support to Spark standalone clusters. Users can now launch PySpark notebooks and run commands in these environments.
• When comparing runs, users can now directly compare the Rmd code used for each run.

Enhancements

• Domino’s “Add or edit a scheduled run” tab now includes a link to the accepted format for custom cron strings. This is important for users who are using custom expressions to schedule runs.

Bug fixes

• The “File Details” page now includes a link that enables users to quickly view the run that generated a given output file. The link had not been available in the most recent previous release.

 

---

1.33 (late May, 2016)

New features

• It is now easier for users to change project names after they’ve been created. This allows users to update a project’s name as it evolves, in order to better reflect its nature. This can be done by clicking on the Rename link in the Project Overview page.
• Domino admins can now set a default environment for users based on membership in organizations. This approach will make it easier for those users to collaborate seamlessly.
• Users can now preview comments in real-time, enabling them to take advantage of the more advanced features in Domino’s commenting system without having to worry about posting comments that include formatting mistakes.
• When building a launcher, users can now create a checkbox toggle so that end-users can pass a TRUE/FALSE value to scripts. Checkboxes can be created via the “Type” drop-down list box in the “Parameter” section of the New Launcher screen.

Enhancements

• Domino now provides users with enhanced abilities to layer custom docker files over base images.
• The Domino CLI is now bundled with installs, in order to ensure compatibility. It can also be downloaded via the support site, if necessary.
• When logging in via the CLI, cloud prod users will have to specify the host they are logging into. This is done by typing domino login $HOST instead of simply domino login.

 

---

1.32 (mid-May, 2016)

New features

• A new user interface in Domino’s Admin section gives users the ability to configure SMTP for on-premises deployment themselves. Previously, only Domino’s engineers could do this.
• Users can now create new environments by cloning existing ones. Previously, new Domino environments could only be built from scratch. Both admin- and non-admin-level users can clone their own environments; however, only admin-level users can clone global environments.

Enhancements

• Domino now provides users with more detailed error messages, giving them an easy way to report the full stack trace of the exception back to Domino’s engineers.
• Domino’s CLI version management has been improved and streamlined to ensure the correct version of the CLI is always downloaded.

Bug fixes

• When a user makes a file content change through the UI, there is no longer a delay before those changes are visible. Once a change is committed, it appears instantly.
• Domino’s scheduling policy has been adjusted to better balance loads across all eligible executors. Previously, it was possible in some situations for a single executor to become overloaded, while others sat idle.

---

1.31 (early May, 2016)

New features

• Users can now publish apps from their projects, in the same way they can publish API endpoints. This enables them to use Domino as a hosting cloud for apps like Shiny or Flask. Users can take advantage of this feature to more easily share the results of an analysis with a non-technical audience. This feature is currently available as Alpha for our VPC and on-premises customers. Domino SaaS customers should contact us directly for access.
• Users can now compare different versions of files across time. This feature is built into the Files tab and provides a convenient way for users to see which files have changed, on a file-by-file basis. Previously, file comparisons in Domino could only be done from the Runs tab.
• Versioning in Domino is now easier. From inside the web UI, users can revert individual files from older runs to the current project without having to change each file manually. This can be done for previous runs as well.
• Users will now see the projects they own at the top of the Project Overview tab, with the other projects they are associated with listed below. This provides users with a cleaner, less overwhelming display of their current projects.
• Runs can now be scheduled for specific recurring days and times. For example, users can schedule runs to occur on the first Saturday of every month, at a time of day when database demand is low. This can be accomplished by including a custom trigger expression, using the syntax described here.
• Pre- or post-setup scripts can now access environment variables. This gives the user the power to customize things as root that require those variables. For example, users could customize their environments to automatically login to github when they launch Rstudio sessions. If you’d like to learn more about how this feature will help you accomplish more with Domino, contact us for more information.

 

---

1.30 (late April, 2016)

New features

• Admins can now easily track resource usage on a per-user basis by running a report. This tool is designed to help admins with capacity planning and chargeback. The Admin Usage Report is accessible in the Admin dashboard, and can be quickly configured to deliver specific information over specified time periods. Results are delivered in a .CSV file.
  
• Users can now publish apps from within their projects, in the same way they can publish an API endpoint. This enables users to share analyses with broader groups of non-technical users.
  
• Project owners will now receive email notifications whenever a collaborator is added to a project.
  

Enhancements

• Users can now keep forked projects synchronized with the original project. This makes it safer to work on complex, time-consuming features and reduces the need to worry about drift.

Bug fixes

• Stopped RStudio sessions are no longer reported as failed runs in the card view.
  
• Under certain circumstances, requests to stop runs were either not processed by Domino, or were processed but ineffective. With this release, these situations were addressed, and the process of stopping runs is now more robust and stable.

---

1.29 (late April, 2016)

New features

Enhancements

---

1.28 (early April, 2016)

Enhancements

---

1.27 (early-March, 2016)

Features

---

1.26 (late-February, 2016)

Features, Enhancements and Bug Fixes

---

1.24 & 1.25 (early-February, 2016)

Features

• An array of significant new additions to Domino Search functionality:
• Significantly improved search performance
• Users can now search for filenames and project tags, in addition to project names, descriptions, and discussions

• “File upload” parameters in Launchers can now accept multiple files at a time
• Users can run .rmd and .rhtml files directly — Domino will automatically process them as knitr templates
• Enhanced the “re-run” functionality to allow re-running against the exact past revision in addition to re-running the same command against the latest revision
  
• (On-Premises and VPC) Added support for a new “Librarian” role
• Librarians are meant to be curators of project metadata (e.g., tags) on behalf of the organization, ensuring that projects are tagged and categorized consistently.
• A Librarian has full ‘list equivalent’ access to all projects, even if a project is marked as private

• Add new tag management dashboard for Administrators and Librarians
• Administrators and Librarians can promote a standard tag to a new ‘approved’ tag type
• Add the ability for user to initiate direct searches from tag counts

Enhancements

• Significant enhancements throughout the Domino user interface
• Improve the user interface for editing and managing compute environments
• (On-Premises and VPC) Refine the user interface for managing central server configuration variables
• Enhanced the layout for the search results page to improve usability
• (On-Premises and VPC) Improved the general layout of the Dispatcher dashboard
• Made a number of existing features more discoverable through the UI, including Run Diagnostics Statistics (dominostats.json), ‘dominoignore’ (to exclude files from sync’ing) and ‘dominoresults’ (to control what shows up on the results page)

• Add efficiencies to page rendering for faster, more efficient interactions with the Domino Web application

Bug fixes

• Corrected the display of the number of active runs when the executor is not available
• Corrected the formatting of the endpoint code snippet
• Corrected the File Browse view so it renders properly when a project name is very long
• Fixed syntax highlighting for .m file rendering
• Corrected issues with margins on the search and projects overview pages
• Corrected issues preventing some runs of Jupyter notebooks
• Corrected stuttering issues using Jupyter on Chrome & Safari

---

1.23 (mid-January, 2016)

Features

• (On-Premises) Added basic support for project tagging as a way to create more organization around projects
• (Beta) Added support for “Reviews”
• (Beta) Added support for tagging Runs to better organize experiments on the Runs dashboard
• (Beta) R/Python package exports: a project can export its contents are a Python or R package that multiple other projects can import.

Enhancements

• Some moderate latency improvements to API Endpoints (more coming soon)
• Discussion page now shows full thread associated with each comment
• UI improvements to commenting (posting a comment no longer reloads the page)
• Rda files now render with their contents in the files/results view
• CSV files now render as interactive tables in the file and results view
• Improved UX on the project settings page
• Run diffing now provides an option to view image diffs in an "overlay" view for easier visual comparison

Bug fixes

• File upload window in web site didn’t work in Firefox
• Project overview page would report API Endpoints as “running” runs for a project
• RStudio sessions showed a scary but innocuous warning upon startup
• "?" help command didn't work in RStudio sessions

---

1.22 (mid-November, 2015)

Features

• "Data Imports" let you create shared, reusable data sets that other projects can import. More info.
• Allowing users to permanently install dependencies in Docker containers, to avoid long install times when running their scripts. More info.
• Improved organization support and management
• UI for creating and managing organizations directly
• Organization project page shows all of organization's projects
• Users can now transfer project ownership through the UI. More info.
• (On-Premises) we are now able to upgrade executors without stopping users' jobs, in most cases

Enhancements

• Improved UI for interactive notebook sessions. "Slide-out" pane lets you control syncing without taking up screen space
• Users now stay logged in for longer, as long as they are regularly using the site
• Jupyter notebook sessions now run on standard ports, making them more easily accessible behind corporate firewalls
• (Cloud) Allowing runs to save files that are more than 5GB
• Added support for @mentions in comments
• (On-Premises) Automatically checking and creating database indexes to improve performance
• (On-Premises) Support for using Amazon SES to send emails when deployed in a VPC environment
• (On-Premises) Support for adding custom tags to EC2 instances that Domino creates
• (On-Premises) Blobs are now compressed when they transfer, improving performance of file sync operations

Bug fixes

• Organization members get notifications as though they were project members
• Fixed a bug that would make it look like a notebook session never started, when it had simply taken a long time to start

---

1.21 (end-August, 2015)

New Features

• Project search
• Added support for spinning up Rodeo sessions
• Added support for Beaker notebook sessions
• ipynb file rendering in the browser (1.20 added this for on-premises deployments. 1.21 adds this for the cloud as well)
• User-specific environment variables
• Added a project-level view that shows all discussion on a project
• Added ability to export environment variables from one project and import them into another

Enhancements

• (On-Premises) Improved users dashboard provides a better sense of which users are active
• (On-Premises) centralized logs (executors, front-end, etc all feed to one place)
• Notification emails will include attachments even when using email.html template
• On the overview page, projects sorts by last updated
• UI improvements to make the "notebook" experience better
• Now able to run/execute Jupyter notebooks directly from the "view file" page
• Able to create a new documentation (README) file directly from the Documentation section of your project
• Rendering results files asynchronously for faster response
• Changed "re-run" behavior to use the latest version of the project (as opposed to the version at the time of the original run)
• Scheduled runs can now be edited only by the user who created them (or the project owner)
• Added a "report view" for the results dashboard that strips away all Domino UI and just shows the results themselves
• Improvements to the commenting UI
• Added ability to purge logs for past API endpoint releases

Bug fixes

• Now able to launch scripts from the files view for files in subdirectories
• Fixed several bugs related to runs search
• "Expanded" file view won't try to render binary files anymore
• Fixed a bug that would cause excessive memory use when viewing a file with lots of revisions
• Fixed bugs related to sanitizing inputs on several text input boxes

 

---

 

1.20 (mid-July, 2015)

New Features

• IPython Notebook improvements.
• Upgraded to Jupyter, including Python, R and Julia kernels, as well as Terminal access
• (On-Premises) Rendering notebooks directly in the file view
• Better support for batch running of notebooks
• Added a “download only” sync option for a running notebook (to pull down new changes into your notebook session without uploading your local changes)
• Better UI for working with Notebooks 
  
  
• Added support for GPU instances
• Added Spark in our base container, so you can more easily run local clusters or connect to your own cluster

Enhancements

• (On-Premises) RStudio starts up with correct working directory
• (On-Premises) Docker image updates now automatically deploy across your cluster
• (On-Premises Admins can set the target executor UI
• (On-Premises) Dispatcher dashboard now updates without a page refresh
• Support for mathjax formatting in comments
  
  
• The Run Number can now be accessed via the DOMINO_RUN_NUMBER environment variable from your code.
• Allow personal plan users to have collaborators
• Comparison view makes better use of horizontal space
• Markdown files render in the file view
• YAML files now render properly in the comparison view
• Added a way to specify a title for a scheduled run
• Added a “failure only” notification level
• Now recording timestamps in the CLI log file
• Added diagnostic stats to the Run objects returned by runs_list() in the REST API
• Increased the max notification attachment size
• File view now shows commit list

Bug fixes

• Documentation page for public projects can now be accessed by anonymous users
• Last several lines in the file editor would be truncated
• dominostats.json won’t be attached to results notification emails anymore
• Now able to comment on a running run
• Comparing a run that wasn’t finished would cause an error — not anymore
• Will now show stdout for Notebook sessions if any setup (e.g., installing requirements) fails
• Run button wasn’t showing up for files with spaces in their names
• Race condition with run numbering
  
  

---

1.19 (early-June, 2015)

New Features

• Commenting and discussion! You can now comment on runs, results and comparison.
• You can now sync file changes from a running Notebook session, so you can get new files into your running notebook environment
• (On-Premises) blobs are now compressed in the blob store, reducing storage requirements

Enhancements

• Added API Endpoint examples in other languages
• You can now create a scheduled run from an existing Run (on the Run's "details" tab)
• Project owners can change collaborators' notification settings
• Added an ability to run more file types from the file browse view
• Improvements to comparison views, better handling of wider content types
• Comparison view highlights differences between the runs' commands
• Commands in the R package no longer display a warning when first run

Bug fixes

• Windows installer now works even if Java isn't already installed
• Will now prevent you from publishing an API Endpoint if the function name is blank
• Handle extra whitespace at the end of API Endpoint file/function names
• Fixed a broken contact link
• Setting MTU to 1500 on all EC2 instances types, addressing a problem that happens on c3 instance types where the MTU is too high and causes some database operations to hang

  

---

1.17.1 (mid-May, 2015)

• Added a new "launcher only" collaborator access level, letting you enable users to access launchers without viewing any underlying files in a project.
• Improved performance in the web UI when browsing projects with many files

 

1.17 (mid-May, 2015)

New Features

We added two powerful new features to make it easier to develop your models. Check out our guide on using these together for Model Tuning & Experimentation.

• "Run Comparison" shows you side-by-side differences between inputs and results of two runs
• "Diagnostic Statistics" let you track structured data about your runs, e.g., AUC

Enhancements

• Project collaborators can manage environment variables
• Project owners can change project environment
• (On-Premises) Admin pages have a more consistent look and feel
• "Archive project" description is more accurate
• Moved "Manage Organization" link to Account page
• Separate tabs for run output, details, and performance graphs to make the UI more humane
• Able to "pause" scheduled runs
• (On-Premises) date format in log files is more humane
• The next occurrence of a scheduled run won't happen until the previous one has succeeded

Bug fixes

• Now able to use a URL to access a run even if it isn't on the first page of the Runs Dashboard
• Notebook sessions will now be named sensibly even if the starting user doesn't have a "name" on their account

---

1.16.1 (late-April, 2015)

Enhancements

• Able to view directory sizes through the Files view on the web interface
• Able to delete files through the files view on the web interface
• (On-Premises) Admin UI now allows viewing and clearing out cached run directories
• (On-Premises) improved log-rolling behavior to reduce log file sizes
• Small enhancements to the Launchers UI

Bug fixes

• Python API Endpoint scripts running in a subdirectory can now load load modules normally
• Couldn't start a batch run of an ipynb file that was in a subdirectory

---

1.16 (mid-April, 2015)

Enhancements

• Added a new Documentation section for each project, that will render any README (or README.md) file in the project
• Able to create a Run record from work done locally, using domino run --local "<command>"
• Automatically title Notebook sessions with the user who started them

Added domino.sync to our R package. Get the updated package by running

• install.packages("domino", repos='http://cran.r-project.org', type="source")
• Collaborators can't stop other collaborators' runs.
• (On-Premises) Added a better UI to allow admins to create and manage Organizations
• (On-Premises) Dispatcher dashboard shows CPU/Memory usage for in-flight runs
• (On-Premises) Can stop a run directly from the Dispatcher dashboard
• (On-Premises) Added functionality for Domino Admins to execute queries directly against the meta-data database

Bug Fixes

• Fixed an issue where reported CPU usage would sometimes be negative
• Can now run files with parentheses in the file name
• CPU/Memory profiling now works properly
• On certain browsers, the file revision list wasn't visible on the "view file" page

---

1.15 (early April, 2015)

Features

• The Runs Dashboard now shows CPU and memory usage over time for each run (rather than just an instantaneous snapshot)
• (On-Premises) Admins can now define and manage their cluster through the UI

Enhancements

• Fine-grained control over which results to display on the web. You can now control which files will be displayed as “results” by explicitly listing them in a “.dominoresults” file in your project. Learn more.
• Run numbering: Runs now have an auto-incrementing human-readable number, so you can more easily refer to them.

Bug Fixes

• Domino client would create a lot of files in the system’s temp directory

---

Version 1.14 (mid Feb, 2015)

• Fixed issue where files that weren't actually changed were appearing on the Results Dashboard
• In on-premise mode, allow alert recipients to be configured
• For public projects, anonymous users can now use run launchers
• R Notebooks now support plotly interactive charts
• Added (very) alpha support for Scala Notebooks
• Improved performance of rendering results dashboards
• Assorted API endpoints improvements:
  • Keep active release serving if a newer but broken one is published
  • Mitigated issue with R endpoints where concurrent requests would occasionally fail
  • Add ability to unpublish an endpoint
  • Dramatically improved our ability to upgrade endpoint functionality, so upgrades should be significatly easier, faster, and safer

---

Version 1.13 (mid Jan, 2015)

• Domino-specific environment setup logging is now visually separated on the runs dashboard.
• Fixed issue where downloading files with certain extensions via the browser would not get unzipped properly
• Make it easier to republish endpoint servers
• Fixed issue in R notebooks where a single cell failure would bring down the entire notebook
• Separate setup-specific logs from logging from main script
• Various improvements to our internal infrastructure

---

Version 1.12 (late Dec, 2014)

• Added new project mode where results of runs are not merged back to the main line. This should improve an experimentation workflow in the following ways:

  • Clarifies which run generated which result files
  • Intermediate files won't pollute the project
  • Result files don't need to be downloaded to the client as often which saves on download time and also makes resetting much less likely

  This setting is available on the project's setting page.

• For users on our Business plans, we've added the ability for you to modify the environment your runs are executed in. For instance, you can install packages and start services your code requires. Please contact us if you'd like more details.
• Existing scheduled runs can be edited
• From the "Edit file" screen, you can now directly save and run the file with one click
• Values of project environment variables can now be shown
• Added API access (and Python bindings) to start batch runs
• Fixed issue where installing packages in an API Endpoint server file would fail if a CRAN repo wasn't specified
• (Finally) fixed extremely annoying and confusing bug where clicking in the title of the run didn't also select the run

---

Version 1.11 (early Dec, 2014)

• Scheduled runs can override the project hardware tier
• Stability and performance improvements
• Improvements to API Endpoints functionality:
  • User-visible log of endpoint startup, to make debugging easier
  • Improved JSON to R/Python object conversions
  • Return elapsed time and commit ID in response automatically

---

Version 1.7 - 1.10 (Aug - Nov, 2014)

We've been so busy adding new features that we forgot to update the release notes. Highlights from the last couple months include:

• "Secure environment variables" let users securely store sensitive passwords and keys and inject them safely into their code at runtime
• Significantly improved performance of the CLI when working with projects that contain many files
• Fixes for two major system-level security issues: Shellshock and POODLE
• Improved CLI help functionality
• Made "search" on the runs dashboard work better
• Added support to run IPython Notebooks in “batch mode” — so they can be scheduled, deliver alerts, etc
• Improved email notification formatting
• Launchers remember most recently used values
• Launchers can be defined to use a specific hardware tier
• Layout improvements to the runs dashboard
• Added a weekday-only option for scheduled runs
• Improvements to IPython Notebook support to make it more usable
• Added beta support for interactive "R Notebooks"
• Improved auto-scaling of our cluster so runs should be "queued" less often
• Lots of minor bug fixes

---

Version 1.6 (Late June, 2014)

New features and enhancements

• Add human-readable descriptions to parameter values in dropdown in Run Launchers, so launchers are better documented for end-users
• Console error output is now correctly interleaved, so users won’t be confused as to when an error occurred
• All uploads and downloads from the client happen multi-threaded, so transfers should happen much faster
• Rearchitected the run scheduler so now runs should spend much less time “queued”
• You can now edit (small) files directly in the browser
• Added new sync CLI command that is much less annoying than download/upload
• Reorganized notification settings to make more sense
• Made writing the code-part of the Run Launchers easier by more automatically handling parameter values for the programmer
• Scheduled runs have a notification list
• Download an entire folder as a zip from the web site (Enterprise deployments only)