About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Domino 6.0.0 (November 2024) (LA)

New features

New Domino User Interface

Domino Data Lab introduces a new UI/UX to improve your core workflows. These changes are meant to align more closely with the data science lifecycle, helping users to move more intuitively through the product. As a part of this effort, the following has been introduced:

  • New User Interface: Domino has a new look and feel, with new navigation patterns and a dashboard experience to quickly get you into recent work. For more detail, see the New UI migration guide.

  • New Admin Interface: The Admin Panel navigation has been updated with a new visual appearance and improved menu organization.

  • New Documentation Interface: Domino Documentation has also been updated to mirror the new look and feel of the User and Admin interfaces, as well as modernize the design.

Domino Governance

Domino Governance automates and orchestrates the collection, review, and tracing of materials required to ensure compliance with internal and external policies.

It provides a single interface closely connected and integrated within a data scientist’s environment, ensuring smooth governance, version control, and compliance for all stakeholders involved.

Domino Governance enables customers to do the following:

  • Policy management: build policies from scratch or customize templates based on industry frameworks.

  • Automated evidence collection: evidence can be generated automatically, saving data scientists and validators time.

  • Global visibility: one place to see policies, status of compliance, and open actions across all projects and models.

Project Templates

Project Templates can be created from existing projects, reducing setup time and improving collaboration among data scientists. Create templates from the project page and keep them private or share with your team or organization.

Data Plane support for Datasets

Domino Nexus allows Datasets to be made local to a specific data plane. Admins can set up and manage Dataset Storage for users to create remote Datasets. Improvements include dataset permissions and the capability to perform file operations such as:

  • Uploading files

  • Previewing files (e.g., viewing the image or text)

  • Renaming files

  • Creating versioned snapshots of the Dataset

  • Downloading single or multiple files

  • Deleting files or deleting the entire snapshot or Dataset

  • Snapshot sizing

The size of Datasets will be updated when users upload or delete files. This information is accessible on the project’s Datasets overview page or when viewing an individual project.

Unified Audit Trail

Domino’s new Unified Audit Trail tracks user interactions and system events, allowing organizations to monitor data creation, viewing, and permission changes for better transparency and accountability.

Audit trails capture broader compliance events, such as changes to the following:

  • Datasets

  • Project configurations

  • User roles

  • Data access

Deploy Models to Sagemaker

Domino provides seamless model deployment to SageMaker. Leverage Domino’s flexible development experience to build your models before deploying them for production on SageMaker, while still maintaining centralized governance and tracking of all of your models. Administrators apply guardrails around cost, performance, and security, and the platform picks the resources needed to meet them.

Remote data plane monitoring

Remote data plane monitoring enables the collection of metrics from remote data planes; increasing the observability of remote workloads.

App secure identity propagation

App secure identity propagation allows apps to identify a Domino user making a request in order to provide differentiated services to users. Existing apps that host additional assets or secondary pages should adapt their root path as described in the App security section when secure identity propagation is turned on. Running applications will not be affected and will not need changes until they are restarted.

Improvements

Flows

Domino Flows has introduced a redesigned user interface that makes it easier to navigate Flow execution versions and their results. With this redesign comes several additional improvements:

  • Workflow definitions have a new graph view

  • Flow runs can be visualized with a graph that includes node status and outputs

  • Flows can be re-run with a new set of inputs

  • Authoring enhancements, including config for cache / retry behavior

  • Improved dataset usability when authoring and executing Flows

Flows Artifacts

Domino Flows has been updated to include support to Define Flow Artifacts. Flow Artifacts are defined by workflow authors and elevate outputs from flow executions to easily discover, reuse, and inspect them, including the lineage of how they were produced. Flow executions will now show artifacts and they can be further bookmarked to show at the project level.

Artifacts can be downloaded to workspaces using a code snippet generated within the execution view.

App secure identity propagation

App secure identity propagation allows apps to identify a Domino user making a request in order to provide differentiated services to users. Existing apps that host additional assets or secondary pages should adapt their root path as described in the App security section when secure identity propagation is turned on. Running applications will not be affected and will not need changes until they are restarted.

Other

Bug fixes

  • Workspace auto-deletion notifications and the deletion itself are now working correctly.

  • Downloading a Dataset file containing a space in its name no longer fails.

  • A small number of Domino executions were failing due to a transient issue in the underlying Kubernetes API version 1.28.3. This has been resolved.

  • An issue deploying with Rancher in 5.11 is resolved.

  • An issue with Kubecost upgrades is no longer present.

  • The Rename dataset’s file button was not available when the user navigated to the Dataset from the global Dataset page. This has been fixed.

  • The sample script for making asynchronous Domino endpoint requests contained an extra / at the end of the DOMINO_URL variable, causing an error. This has been resolved.

  • Links to Stack Trace and CPU Flame Graph in the Ray Cluster UI’s Cluster tab were broken. This has been resolved.

  • The section, Account Settings > Login Profile, was temporarily disabled for all users. This was resolved.

  • An issue with the cost-analyzer is no longer present.

  • An issue with connecting to the Starburst-powered JDBC Data Sources if the credentials contain special characters was resolved.

  • Some users encountered an issue where workspace auto-deletion notifications and the deletion itself may not have completed successfully. This issue has been resolved.

  • An issue with using /learn with wildcards inJupyter AI Lab 2.24 has been resolved.

  • When the Domino Job that corresponds to a Flyte DominoJobTask does not correctly produce all of the outputs defined in the task, the Flyte UI for the task may have incorrectly displayed "failed to run the job" and show "Allocation token required" in the logs. This has been resolved.

Known issues

  • Users cannot create and endpoint from a global model if they are not a collaborator on the model’s project.

  • Flows is only supported in Domino Cloud, AWS, and Azure. A future update will add support for Google Cloud and on-premises installs.

  • When annotating a Domino Flows sub workflow’s outputs as a Flows Artifact, the artifacts will not be properly exposed in the Artifacts UI for that Flow.

  • S3 buckets must have CORS enabled to use the View Latest Raw File button in the code file browser if the file is > 5 MB (com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes). As a workaround, use the Download button to download larger files and view them on your computer.

  • In Azure Blob Store deployments, Projects with many files may fail to sync through the Domino CLI. To work around this issue, do not disable file locking when prompted by Domino.

  • You cannot view the latest raw file if you click View Latest Raw File. In the navigation pane, go to Files and click a file to view its details.

  • When uploading a large file to the Azure blob store by syncing a Workspace, you may encounter a Java Out of Memory error from Azure if the file/blob already exists. To work around this issue, use the Domino CLI to upload the file to the Project.

  • Model Monitoring data sources aren’t validated. If you enter an invalid bucket name and attempt to save, the entry will go through. However, you won’t be able to see metrics for that entry, because the name points to an invalid bucket.

  • Domino instances that make use of Azure Blob Storage may experience stalled Jobs within Projects with many large files.

  • If you attach a Git repository to a DFS Project that points to a tagged release, the tag won’t be honored when building a Domino endpoint in that Project. The build log will show an error similar to the following, and the model will be built using the default branch of your Git repository instead of the tagged branch:

    Jul 05 2023 14:36:27 -0500 #10 6.481 WARN [d.r.d.GitRepoUpdater] could not parse ref: v1.3.0 checking out default branch correlationId="iA2qWrYSLQ" thread="main"

    To work around this issue, use the branch name when building Domino endpoints instead of the release tag.

  • If an admin resets a user’s password, it invalidates all the user’s authentication tokens, including tokens used for long-running tasks like Jobs, Workspaces, or Apps. The user must create a new password, log back into Domino, and restart all executions. This also applies to CLI authentication; the user must re-login to their Domino CLI.

  • External Endpoints in the Failed state will not always correctly rebuild and redeploy when updated. To work around this issue, spin up a new endpoint.

  • Updating the registered model/version of an External Endpoint will not always deploy the correct model to Sagemaker. Additionally, this update will sometimes break the UI for that Endpoint’s details page. To work around these issues, spin up a new endpoint.

  • External Endpoints in the Starting or Failed state will not expose their Instance Logs through Domino.

  • Running apps within VS Code workspaces may fail to be rendered through VS Code port proxy. This issue is fixed in 6.0.1 and 6.1.0.

  • If you have Domino Governance enabled, Jira Integration for Tasks is non-functional and will show a permissions error. If Domino Governance is not enabled, Tasks will function as expected.

Validated frameworks

The following versions have been validated with Domino 6.0.0. Other versions might be compatible but are not guaranteed.

See also the ddlctl and fleetcommand-agent Release Notes.

Upgrade notes

  • GKE users that provisioned their infrastructure with Domino’s terraform-gcp-gke module must apply the changes introduced for 5.7.0 as of terraform-gcp-gke v2.5.0 when upgrading to ensure firewall rules work properly.

  • GKE Kubernetes version compatibility is updated to 1.30 / 1.29.

  • OpenShift version compatibility is updated to 1.29 (OpenShift 4.16).

  • VPN support from within executions was updated to be disabled by default. Support can be enabled by setting the global config value com.cerebro.domino.computegrid.executions.allowVpn = true.

  • EKS users are recommended to update the AWS VPC CNI settings to enable ANNOTATE_POD_IP to prevent execution timeout errors when an image pull takes longer than 10 minutes. To bypass the validation check during an upgrade, pass --warn-only as a command line option to the installer.

  • For customers using the platform sizing guide, it is now recommended to use 16 core / 64 GB (or higher) platform node instances.

  • EKS users who provisioned their infrastructure with Domino’s terraform-aws-eks module must validate whether they want the new costs blob storage to be provisioned by default.

  • Upgraded PostgreSQL to 14.10.

  • Upgraded RabbitMQ to 3.13.4.

  • The new Data Plane version has advanced to a major release (now 4.1.1-3). As a result, the upgrade button will not function due to the version gap. To complete the upgrade successfully, a manual process is required. For details, refer to the upgrade the Data Plane section.