4.2.3 (July 2020)¶
- Improved logging in the Image Cache Agent.
- Fixed an issue that prevented file uploads through the Domino CLI.
- Fixed an issue where the Scheduled Jobs page failed to load if a job could not find a hardware tier.
- Fixed an issue that caused Workspace & App links in the Compute & Spend report to return errors, preventing access to the associated job.
- Fixed an issue that caused the /health endpoint to return a 404 incorrectly.
- Fixed an issue where Spark worker storage would not be provisioned unless the value for the storage size was modified. The default storage of 30GiB is now created without requiring custom input.
4.2.2 (May 2020)¶
- Fixed an issue where collaborators attempting to start workspaces in projects they did not own would get redirected to the wrong URL, resulting in 404.
4.2.1 (May 2020)¶
- Improved performance of the files browser in the UI
- Fixed an issue where user-uploaded custom certificates were not being used when connecting to Git servers for cloning and working with externally hosted repositories.
- Domino 4.2.1 is supported by fleetcommand-agent v23 or greater. See the fleetcommand-agent release notes for breaking changes and new options.
4.2.0 (May 2020)¶
Domino 4.2 introduces the ability to launch and work with on-demand Spark clusters backed by the Domino compute grid. When setting up an environment, you can now use a base image with Spark worker and client components installed, such as
bitnami/spark:2.4.5-debian-10-r84and then mark the environment as ready for use with Domino managed Spark.
Once your environment is configured, you can attach on-demand spark clusters to jobs and workspaces that use that environment. The cluster and clients will be automatically configured, and you can use PySpark or spark-submit in your job or workspace code to interact with the cluster.
In Domino 4.2, if a workspace stops or shuts down unexpectedly without syncing files, and the attached volume enters a salvaged state, the user will automatically be prompted to start a recovery workspace that will reconnect to the salvaged volumes for syncing.
Domino in AWS now supports custom KMS key encryption of S3 stores.
The Keycloak authentication service deployed alongside Domino 4.2 comes pre-configured with a SAML identity provider that has valid default user attribute mappers, plus pre-configured client mappers for AWS credential propagation and organization or role mappings.
New API endpoints have been introduced for working with Model APIs. You can now use the API to export a Model API image in a Sagemaker-compatible format directly to your own container registery, and there are also new endpoints for starting, stopping, and getting the deployment status of Model APIs.
Domino projects can now integrate with Atlassian Jira to link Domino work to Jira issues and projects.
To enable this feature, a Domino administrator must configure a Jira integration. From the admin portal, click Advanced > Jira Configuration, then supply your Jira URL to start the integration.
Once a Jira integration has been added, users can go to the Manage tab of a project overview to authenticate to the Jira service and connect the Domino project to a Jira issue. Users can then link Domino project goals to Jira subtasks, and comments and project status changes will automatically be recorded in Jira.
The user interface for workspaces has been redesigned to support new features like separate interface tabs for the Spark UI when using on-demand Spark clusters.
The workspaces dashboard has also been redesigned for simplicity and readability.
The process for launching a new workspace is now started from the + New Workspace button at top right. This button opens a redesigned dialog for starting a workspace.
Performance improvements to the workspace startup flow have reduced the minimum time to start a workspace, and additional progress information is now shown during startup.
A number of issues related to reverse proxy and subdomain access to workspaces have been fixed.
The default resource requests for Domino platform services have been tuned to provide baseline capacity for orchestrating 300 concurrent executions. Read the infrastructure sizing overview to learn more.