Skip to content

scheduling: advanced scheduling controls #6047

Description

@bpmct

Currently, workspace schedules are only a recommendation and there is no way for admins to enforce a particular shutdown behavior on workspaces. #3630, #5600.

We have seen a decent amount of feedback that warrants us supporting both "max" and "default" TTL as they serve different use cases. For example, max TTL to enforce security patches, but default TTL to ensure workspaces quickly shut down when inactive.

Let's re-introduce the "max TTL" while also keeping the "default TTL" behavior for workspaces. This will allow workspaces to have the following behavior:

  • Workspaces will auto-shutdown after 2 hours of inactivity (default TTL), but cannot be alive for over 72 hours (max TTL).

Also, some admins may not want users to change the default TTL behavior of their workspaces. For example,

  • All workspaces on template x will auto shut down after 2 hours of inactivity. Users cannot change this behavior.

To summarize:

Activity

  1. added
    enterpriseEnterprise-license / premium functionality
    on Feb 6, 2023
  2. bpmct commented on Feb 6, 2023

    @bpmct
    MemberAuthor

    This does make the scheduling behavior a bit more complex, so perhaps we could add an "advanced" tab for users who specifically want these controls. This will also be an enterprise feature as it is related to managing workspaces at scale and enforcing policies.

  3. kylecarbs commented on Feb 6, 2023

    @kylecarbs
    Member

    Adding on to this, I think be cool if the screen was something like this:
    image

  4. changed the title [-]Advanced scheduling controls[/-] [+]scheduling: advanced scheduling controls[/+] on Feb 6, 2023
  5. added
    s1Bugs that break core workflows. Only humans may set this.
    on Feb 14, 2023
  6. bpmct commented on Mar 7, 2023

    @bpmct
    MemberAuthor

    Reopening, since the user-controlled scheduling controls hasn't been done

  7. reopened this on Mar 7, 2023
  8. removed
    s1Bugs that break core workflows. Only humans may set this.
    on Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enterpriseEnterprise-license / premium functionality

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions