diff --git a/docs/release-notes.rst b/docs/release-notes.rst index dc9b405dfa7..66b4a99e005 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -6,6 +6,103 @@ Release Notes ############### +************** + Version 0.32 +************** + +Version 0.32.0 +============== + +**Release Date:** May 03, 2024 + +Notice: This release contains an important fix for a bug that poses data loss risk when using the +Experiment table in the project view in the WebUI. All users on affected versions are strongly +encouraged to upgrade as soon as possible. For more details, scroll down to ``Bug Fixes``. + +**Breaking Changes** + +- Python SDK and CLI: Password requirements are now enforced for all non-remote users. (The + requirements do not apply to remote users, since they use single sign-on.) Existing users with + empty or non-compliant passwords can still sign in. However, we recommend updating these + passwords to meet the new requirements as soon as possible. For more information, visit + :ref:`password-requirements`. + + This change affects the :meth:`~determined.experimental.client.Determined.create_user` and + :meth:`~determined.experimental.client.User.change_password` SDK methods and the ``det user + create`` and ``det user change-password`` CLI commands. + + When creating non-remote users at the CLI with ``det user create``, setting a password is now + mandatory. You can set the password interactively by following the prompts during user creation + or non-interactively with the ``--password`` option. + +**New Features** + +- Kubernetes: In the enterprise edition, add the ability to set up the Determined master service on + one Kubernetes cluster and manage workloads across different Kubernetes clusters. Additional + non-default resource managers and resource pools are configured under the + ``additional_resource_managers`` section (additional resource managers are required to have at + least one resource pool defined). Additional resource managers and their resource pools must have + unique names. For more information, visit :ref:`master configuration `. + Support for notebooks and other workloads that require proxying is under development. + +- API/CLI/WebUI: In the enterprise edition, route any requests to resource pools not defined in the + master configuration to the default resource manager, not any additional resource manager, if + defined. + +- Configuration: In the enterprise edition, add an ``additional_resource_managers`` section that + can define multiple resource managers following the same patteroas ``resource_manager``. Add + ``name`` and ``metadata`` fields to individual resource manager definitions. + +- WebUI: In the enterprise edition, add the ability to view resource manager name for resource + pools. + +**Improvements** + +- Configuration: The master configuration parameter ``observability.enable_prometheus`` now + defaults to ``true``. Consequently, Prometheus endpoints are enabled by default, which does not + affect clusters that do not use Prometheus. + +- Experiment metrics tracking: Add enhanced support for metrics with long names. Previously, + metrics with names exceeding 63 characters were recorded but not displayed in the UI or returned + via APIs. + +**Bug Fixes** + +- A bug was fixed impacting the selection functionality in the Experiments page. From version + 0.27.1 to version 0.31.0, this bug was causing actions to be applied to more experiments than are + visibly selected. For example, when using the **Select All > Actions > Move** sequence to + transfer all experiments from one project to another, the action may inadvertently include + experiments not only from the targeted project but also from other projects you have permissions + to edit. We urge all users on the affected versions to upgrade as soon as possible. The following + applies to versions 0.27.1 to 0.31.0: + + - There is a risk of data loss if, when attempting to delete a set of experiments, the action + inadvertently deletes a larger set than intended. + + - When role-based access control (an enterprise edition feature) is enabled, there is a risk of + a permissions leak if moving experiments from one project to another inadvertently includes + experiments from other workspaces. + + - This issue affects all bulk actions including delete, move, archive, unarchive, resume, pause, + kill, stop, and view in TensorBoard. + + - We strongly advise refraining from using the experiment table in the project view to take any + actions. + + - Workaround: To manage actions on a single trial, use the trial view in the WebUI. + Alternatively, for bulk actions affected by this issue, consider using the command-line + interface (CLI). You can also turn off the New Experiment List setting under the User Settings + > Experimental section. For more information visit Manage User Settings under :ref:`WebUI + `. + +- A bug was fixed impacting deployments using Amazon Aurora PostgreSQL-Compatible Edition + Serverless V1 as the database. Since version 0.28.1, deployments using Amazon Aurora + PostgreSQL-Compatible Edition Serverless V1 as the database have been at risk of becoming + unresponsive due to certain autoscaling errors. This issue affects multiple ``det deploy aws`` + deployment types, including ``simple``, ``vpc``, ``efs``, ``fsx``, and ``secure``. Installations + using AWS RDS, including ``det deploy aws --deployment-type=govcloud``, are not affected. We urge + all users with affected setups to upgrade as soon as possible. + ************** Version 0.31 ************** diff --git a/docs/release-notes/allow-and-require-user-passwords.rst b/docs/release-notes/allow-and-require-user-passwords.rst deleted file mode 100644 index 100beb61523..00000000000 --- a/docs/release-notes/allow-and-require-user-passwords.rst +++ /dev/null @@ -1,21 +0,0 @@ -:orphan: - -**Breaking Changes** - -- Python SDK and CLI: Enforce password requirements for all non-remote users: see - :ref:`password-requirements` - - - This applies to ``create_user``, ``User.change_password``, ``det user create``, and ``det - user change-password``. - - - This does not affect logging in with an existing user who already has an empty or - non-compliant password, but we recommend setting good passwords for such users as soon as - possible. - -- CLI: Require and allow passwords to be set when creating non-remote users with ``det user - create``. - - - This may be done interactively by following the prompts. - - This may be done noninteractively by using the ``--password`` option. - - This is not required when creating a user with ``--remote`` since Single Sign-On will be - used. diff --git a/docs/release-notes/aurora.rst b/docs/release-notes/aurora.rst deleted file mode 100644 index e92a133fe4d..00000000000 --- a/docs/release-notes/aurora.rst +++ /dev/null @@ -1,10 +0,0 @@ -:orphan: - -**Bug Fixes** - -- Since 0.28.1, all deployments using Amazon Aurora PostgreSQL-Compatible Edition Serverless V1 for - its database were at risk of becoming completely unresponsive whenever Aurora hits certain - autoscaling errors. Multiple ``det deploy aws`` deployment types (default ``simple``, ``vpc``, - ``efs``, ``fsx``, ``secure``) are affected. AWS installations using RDS are not affected, - including ``det deploy aws --deployment-type=govcloud`` deployments. We recommend all users - running affected setups to upgrade as soon as possible. diff --git a/docs/release-notes/det-deploy-ee.rst b/docs/release-notes/det-deploy-ee.rst deleted file mode 100644 index 6522932c606..00000000000 --- a/docs/release-notes/det-deploy-ee.rst +++ /dev/null @@ -1,6 +0,0 @@ -:orphan: - -**New Features** - -- CLI: Add the `--enterprise-edition` option for `det deploy local`, allowing users to easily - deploy enterprise images. diff --git a/docs/release-notes/enable-prometheus-default-true.rst b/docs/release-notes/enable-prometheus-default-true.rst deleted file mode 100644 index dc9723e71e3..00000000000 --- a/docs/release-notes/enable-prometheus-default-true.rst +++ /dev/null @@ -1,7 +0,0 @@ -:orphan: - -**Improvements** - -- Configuration: The master config parameter ``observability.enable_prometheus`` now defaults to - true. As a result, Prometheus endpoints will now be available by default. This will cause no - impact to clusters not using Prometheus. diff --git a/docs/release-notes/multirm-for-k8s.rst b/docs/release-notes/multirm-for-k8s.rst deleted file mode 100644 index 1445e8945cd..00000000000 --- a/docs/release-notes/multirm-for-k8s.rst +++ /dev/null @@ -1,21 +0,0 @@ -:orphan: - -**New Features** - -- Kubernetes: Add ability to set up the Determined master service on one Kubernetes cluster and - manage workloads across different Kubernetes clusters. Additional non-default resource managers - and resource pools are configured under the master configuration options - ``additional_resource_managers`` and ``resource_pools`` (additional resource managers are - required to have at least one resource pool defined). Additional resource managers and their - resource pools must have unique names. For more information, visit :ref:master configuration - . Support for notebooks and other workloads that require proxying is - under development. - -- WebUI: Add ability to view resource manager name for resource pools. - -- API/CLI/WebUI: Route any requests to resource pools not defined in the master configuration to - the default resource manager, not any additional resource manager, if defined. - -- Configuration: Add a ``name`` and ``metadata`` field to resource manager section in the master - configuration. Add an ``additional_resource_managers`` section that follows the - ``resource_manager`` and ``resource_pool`` configuration pattern.