Self-Service Environment Policies will allow any Project Manager to define and manage their own environment polices. The Self-Service Environment Policies feature simplifies creation and management tasks because self-service policies are global. Self-service policies are associated directly to a project and can be used for any blueprint by any organization.
- Environment Policy: Defines the amount of time the end-users will have the use of the environment. The environment’s life time is set according to the environment policy associated with it: during the Run time, the environment will be up with all machines running. During the Storage time, the environment will be archived and can be made accessible by extending it from the environment details page. After the environment storage time expires, the environment is securely deleted
- Blueprint: A master or baseline template that may contain machines, storage, networking, pre-installed software, company branding and use case collateral from which all environment instances are created
- Organizations: Organizations are Project Member user groups that can invite End Users and Run environments in their specific organizations. Project Managers can add different organizations (whether partners/re-sellers or different business units), each one headed by a Team Manager. Team Managers of a specific organization are limited to the scope of their own team, only Project Managers can oversee all activities across all organizations in their project(s)
To create a new Environment Policy follow these steps (Note: Requires the Project Manager Role)
1. From the CloudShare Dashboard, navigate to Management > Policies
2. Click the Create Environment Policy button
3. Complete the following:
- From the Name field, provide a descriptive name that your users can understand
- From the Projects list, select those entries that you would like this policy to be applied to (multi-select by holding down the Ctrl)
- From the Duration field:
- Runtime Lease - specify the amount of time (days, hours or minutes) that the environment will be in the Running state with all the machines accessible (must be equal to or less than the storage lease)
- Storage Lease - specify the amount of time (days, hours or minutes) that the environment will live before being securely deleted (total lifecycle of the environment)
- Environment Inactivity Handling
- Suspend the environment after XX minutes – Allows you to specify the value in minutes before inactivity handling is triggered
- Delete the environment after XX minutes – Allows you to specify the value in minutes before the delete action is triggered
- Always On – the environment will continue to RUN whether it senses activity or not for the lease duration specified above or unless manually extended
4. Click the Create button
You also have the ability to edit any existing policies. However, modifying an existing policy will not affect the environments which have already started. This means, although the platform allows you to modify an existing policy, these updates will not apply on the environments that are currently running as they retain their original timers. The edited policies will apply on any new environments which start after the policy has been modified and saved. For example, you may edit an existing policy to have a different value for its Inactivity Suspend timer, but this new setting will apply only as you start (Run) a new instance of the environment.
For more information, please see this blog post.
PS: Note - this change does not affect custom environment policies which are used with our Single-Sign-On (SSO) API or Classroom Training.