From 4f3b43823818f226e106e5e9bfb9a25adb877a3d Mon Sep 17 00:00:00 2001 From: "QUALISYSTEMS\\nahum-t" Date: Mon, 19 Oct 2026 15:01:17 +0300 Subject: [PATCH 1/2] Docs: minimum lead time is set in Resource Manager (ticket #67934) - Domains window: new Properties-page step for Min. Lead Time. - Adding Domains: Minimum Lead Time section now leads with the Resource Manager field, states what is enforced, keeps the REST API as an alternative. - Edit domain API: fix copy-pasted description; clarify MinimumLeadTimeMinutes. - Release notes (2026.1): feature entry + bug fix for API reservations having been checked in seconds instead of minutes. Co-Authored-By: Claude Opus 5.5 (1M context) --- .../cloudshell-domains/adding-domains.md | 16 +++++++++++++--- .../cloudshell-domains/domains-window.md | 9 +++++---- docs/api-guide/cs-admin-rest-api/edit-domain.md | 4 ++-- docs/release-notes/whats-new.md | 6 ++++++ 4 files changed, 26 insertions(+), 9 deletions(-) diff --git a/docs/admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md b/docs/admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md index e9f4c4f337..c0b9734b19 100644 --- a/docs/admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md +++ b/docs/admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md @@ -20,8 +20,18 @@ Designated system administrators have limited permissions for performing domain 6. Next, set up the domain, as explained in [Domains Window](../../../admin/cloudshell-identity-management/cloudshell-domains/domains-window.md). -**Minimum Lead Time** +## Minimum Lead Time -You have the ability to establish a minimum lead time for reserving Sandboxes within a specific domain. This means that when this setting is configured, any sandbox reservations must be made for a date in the future, not for immediate use. +You can require sandboxes in a domain to be reserved ahead of time. When a domain has a minimum lead time: -To implement this, you need to adjust the `MinimumLeadTimeMinutes` parameter via a specific API call. Detailed instructions on how to make this API call can be found in [this guide](../../../api-guide/cs-admin-rest-api/edit-domain.md). +- Sandboxes can't be reserved to start immediately. The **Now** option isn't offered in the reservation dialog. +- A sandbox's start time must be at least the minimum lead time from the moment it's reserved. This applies to reservations made from the Portal and through the API. + +A value of 0 (the default) means no restriction. + +**To set the minimum lead time:** + +1. In Resource Manager, open the domain and select the **Properties** page (see [Domains Window](./domains-window.md#properties-page)). +2. In **Min. Lead Time**, enter the number of minutes (0 to 525600) and press **Enter**. + +You can also set it with the `MinimumLeadTimeMinutes` parameter of the [Edit domain](../../../api-guide/cs-admin-rest-api/edit-domain.md) Admin REST API call. diff --git a/docs/admin/cloudshell-identity-management/cloudshell-domains/domains-window.md b/docs/admin/cloudshell-identity-management/cloudshell-domains/domains-window.md index b67f2fce5c..d76977a2aa 100644 --- a/docs/admin/cloudshell-identity-management/cloudshell-domains/domains-window.md +++ b/docs/admin/cloudshell-identity-management/cloudshell-domains/domains-window.md @@ -41,13 +41,14 @@ The **Properties** page displays the current domain settings: the domain name, d :::note The default duration for a domain is indefinite. ::: -6. The **Resources** field displays the number of resources associated with the domain. Click the **Add Resource** button to find additional resources. -7. The **Reservations** field shows a real time summary of the domain's activity. -8. To add or remove groups from the domain, click the **Groups** tab. The **Groups** tab lists all groups associated with the domain. The **View Only** field is checked for any group with view-only access to the domain. To manage groups and their permission levels, see [Managing CloudShell Groups](../managing-users/managing-cloudshell-groups.md). +6. To require sandboxes in this domain to be reserved ahead of time, set **Min. Lead Time** to the number of minutes (0 to 525600, that is, up to one year). The value is saved when you press **Enter** or move to another field, and the text under the field describes the effect, for example *Sandboxes in this domain must be reserved at least 1 h 30 min in advance*. Set it to **0** to remove the restriction. For details, see [Minimum Lead Time](./adding-domains.md#minimum-lead-time). +7. The **Resources** field displays the number of resources associated with the domain. Click the **Add Resource** button to find additional resources. +8. The **Reservations** field shows a real time summary of the domain's activity. +9. To add or remove groups from the domain, click the **Groups** tab. The **Groups** tab lists all groups associated with the domain. The **View Only** field is checked for any group with view-only access to the domain. To manage groups and their permission levels, see [Managing CloudShell Groups](../managing-users/managing-cloudshell-groups.md). :::note You can also associate a group with a domain via the **Domains** area in the **Groups** tab. ::: -9. Click the **Topologies** tab to add or remove blueprints. The **Topologies** tab lists all blueprints associated with the domain. When you add a blueprint to a domain, the blueprint's resources, Apps and services are added as well. For additional information, see [Adding resources to a domain](./addingremoving-resources-from-a-domain.md#adding-resources-to-a-domain). +10. Click the **Topologies** tab to add or remove blueprints. The **Topologies** tab lists all blueprints associated with the domain. When you add a blueprint to a domain, the blueprint's resources, Apps and services are added as well. For additional information, see [Adding resources to a domain](./addingremoving-resources-from-a-domain.md#adding-resources-to-a-domain). ![](/Images/Admin-Guide/User-Management/The-Domain-window_2.png) :::note diff --git a/docs/api-guide/cs-admin-rest-api/edit-domain.md b/docs/api-guide/cs-admin-rest-api/edit-domain.md index 6f37b3f88a..c43dc62cef 100644 --- a/docs/api-guide/cs-admin-rest-api/edit-domain.md +++ b/docs/api-guide/cs-admin-rest-api/edit-domain.md @@ -6,7 +6,7 @@ sidebar_position: 6 ### Description -Gets a list of all domains in CloudShell +Updates a domain's settings. Only the parameters included in the request body are changed ### URL @@ -44,7 +44,7 @@ Example header format: | EndTime | (string) End time of domain's validity. When the end time is reached, the domain will be accessible but no longer in use. | | Archived | (bool) **true** to archive the domain. | | LicensePoolId | (string) Id of the license pool. Can be retrieved via [Get all license pools](./get-all-license-pools.md). | -| MinimumLeadTimeMinutes | (int) Determine how soon a sandbox can be ordered from the present time. For example, a minimum lead time of 60 would mean that the FROM field must be now + 60 minutes. | +| MinimumLeadTimeMinutes | (int) Minimum number of minutes between the time a sandbox is reserved and its start time. For example, 60 means the sandbox must start at least 60 minutes from now. 0 removes the restriction. Can also be set in Resource Manager (domain **Properties** page). | diff --git a/docs/release-notes/whats-new.md b/docs/release-notes/whats-new.md index b832b75680..a3f6af93eb 100644 --- a/docs/release-notes/whats-new.md +++ b/docs/release-notes/whats-new.md @@ -7,6 +7,11 @@ CloudShell Release History ## Version 2026.1 +### Minimum Lead Time in Resource Manager {#minimum-lead-time-rm} +A domain's minimum lead time can now be viewed and set in Resource Manager, on the domain's **Properties** page, instead of only through the Admin REST API. Enter the number of minutes; the text under the field describes the effect. See [Minimum Lead Time](../admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md#minimum-lead-time). + +Available in the next 2026.1 and 2026.2 patch releases. 2026.1 releases up to and including 2026.1.0.102 don't include it. + ### Blueprint Export/Import via the Automation API New `ExportBlueprint(topologyNames[])` and `ImportBlueprint(blueprintXml)` Automation API methods. Blueprints are exchanged as plain XML text, suitable for tracking in git — export is deterministic. The import payload cannot carry data models, drivers, scripts, inventory resources, or category definitions. Permissions match those for creating/editing a blueprint in the portal; no system-administrator role is required. @@ -130,6 +135,7 @@ Switching the active domain while a blueprint that doesn't exist in the new doma Available in CloudShell **2026.2.0.190036** and later. 2026.1 releases up to and including 2026.1.0.102 don't include this fix. ### Bug Fixes +- Fixed the domain minimum lead time being enforced in seconds rather than minutes for reservations made through the API. A domain set to 60 now requires sandboxes to start at least 60 minutes ahead, as the Portal already showed. - Fixed **Save as Blueprint** failing with an error when the blueprint a sandbox was originally created from had since been deleted. Global inputs are now read from the sandbox itself, so the save succeeds. - Fixed diagram PNG export hanging indefinitely on a "Please Wait" indicator in deployed builds. A required library was present in source but not marked as deployable content, so it 404'd in published builds; export now fails gracefully if the library is unavailable rather than hanging. - Fixed abstract resource resolution (QAC) failing on large inventories once the candidate-parent count exceeded 1024-clause query limit. Resolution now uses a single path-hierarchy terms query regardless of parent count, and real Elasticsearch failures are now surfaced instead of a misleading "wrong result type" error. From eccd8739a78ce2b318e08ccec1d38bf31151a3dd Mon Sep 17 00:00:00 2001 From: "QUALISYSTEMS\\nahum-t" Date: Mon, 26 Oct 2026 15:59:19 +0200 Subject: [PATCH 2/2] Min. Lead Time: shipped in 2026.2.0.34 - single whats-new entry in the 2026.2 section (was duplicated after #37), API seconds->minutes fix moved to 2026.2 bug fixes Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/release-notes/whats-new.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/docs/release-notes/whats-new.md b/docs/release-notes/whats-new.md index 87fb535284..a3e59db3a2 100644 --- a/docs/release-notes/whats-new.md +++ b/docs/release-notes/whats-new.md @@ -14,8 +14,8 @@ The Python and XML-RPC TestShell API methods `CreateReservation`, `CreateImmedia Available in CloudShell **2026.2.0.34** and later. -### Minimum Lead Time in Resource Manager -A domain's minimum lead time can now be set in Resource Manager, in the **Min. Lead Time** field on the domain's **Properties** page, instead of directly in the database. Available in CloudShell **2026.2.0.34** and later. +### Minimum Lead Time in Resource Manager {#minimum-lead-time-rm} +A domain's minimum lead time can now be viewed and set in Resource Manager, in the **Min. Lead Time** field on the domain's **Properties** page, instead of only through the Admin REST API. Enter the number of minutes; the text under the field describes the effect. See [Minimum Lead Time](../admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md#minimum-lead-time). Available in CloudShell **2026.2.0.34** and later; 2026.1 releases up to and including 2026.1.0.102 don't include it. ### SQL Server to PostgreSQL Migration Tool Included The CloudShell installation package now includes the SQL Server to PostgreSQL migration tool, in `CloudShell\Utilities\SqlServerToPostgresqlMigrator`, with a README. See [Migrating the Databases from SQL Server to PostgreSQL](../install-configure/cloudshell-suite/backup-restore/migrate-sql-server-to-postgresql.md). Available in CloudShell **2026.2.0.34** and later. @@ -36,6 +36,7 @@ Each Docker Execution Server release is also tagged with its release number, for Node.js, used by the Sandbox API Gateway and Server Proxy, was updated from 24.14.0 to 24.22.1 (Node.js October 2026 security release). Available in CloudShell **2026.2.0.34** and later. ### Bug Fixes +- Fixed the domain minimum lead time being enforced in seconds rather than minutes for reservations made through the API. A domain set to 60 now requires sandboxes to start at least 60 minutes ahead, as the Portal already showed. (2026.2.0.34) - Fixed `GetReservationDetails` timing out on sandboxes with many resources. Resource details are now queried more efficiently. (2026.2.0.34) - Fixed diagram connection lines staying attached to the old card size after changing the View Style, with `PreserveDiagramLayoutOnViewStyleChange` enabled. (2026.2.0.34) - Fixed **Save as Blueprint** failing for a work-order sandbox with connected routes or cables. (2026.2.0.34) @@ -50,11 +51,6 @@ Node.js, used by the Sandbox API Gateway and Server Proxy, was updated from 24.1 ## Version 2026.1 -### Minimum Lead Time in Resource Manager {#minimum-lead-time-rm} -A domain's minimum lead time can now be viewed and set in Resource Manager, on the domain's **Properties** page, instead of only through the Admin REST API. Enter the number of minutes; the text under the field describes the effect. See [Minimum Lead Time](../admin/cloudshell-identity-management/cloudshell-domains/adding-domains.md#minimum-lead-time). - -Available in the next 2026.1 and 2026.2 patch releases. 2026.1 releases up to and including 2026.1.0.102 don't include it. - ### Blueprint Export/Import via the Automation API New `ExportBlueprint(topologyNames[])` and `ImportBlueprint(blueprintXml)` Automation API methods. Blueprints are exchanged as plain XML text, suitable for tracking in git — export is deterministic. The import payload cannot carry data models, drivers, scripts, inventory resources, or category definitions. Permissions match those for creating/editing a blueprint in the portal; no system-administrator role is required. @@ -178,7 +174,6 @@ Switching the active domain while a blueprint that doesn't exist in the new doma Available in CloudShell **2026.2.0.190036** and later. 2026.1 releases up to and including 2026.1.0.102 don't include this fix. ### Bug Fixes -- Fixed the domain minimum lead time being enforced in seconds rather than minutes for reservations made through the API. A domain set to 60 now requires sandboxes to start at least 60 minutes ahead, as the Portal already showed. - Fixed **Save as Blueprint** failing with an error when the blueprint a sandbox was originally created from had since been deleted. Global inputs are now read from the sandbox itself, so the save succeeds. - Fixed diagram PNG export hanging indefinitely on a "Please Wait" indicator in deployed builds. A required library was present in source but not marked as deployable content, so it 404'd in published builds; export now fails gracefully if the library is unavailable rather than hanging. - Fixed abstract resource resolution (QAC) failing on large inventories once the candidate-parent count exceeded 1024-clause query limit. Resolution now uses a single path-hierarchy terms query regardless of parent count, and real Elasticsearch failures are now surfaced instead of a misleading "wrong result type" error.