A Project Manager can define and manage environment policies. Environment policies are associated directly with a Project and can be used for any Blueprint and by any Team in the Project.
A Policy defines the amount of time users will be able to use the environment. An environment’s lifetime is set according to the Policy associated with it:
During runtime, the environment will be up with all machines running.
During storage time, the environment will be archived. It can be made accessible by extending it from its Environment Details page. After the environment storage time expires, the environment is securely deleted.
During suspension time, the environment is not active, but remains readily available and can be quickly accessed by an end user.
Only a user with the role of Project Manager or higher can create and manage environment policies.
To create a new Environment Policy as a Project Manager:
From the Resources menu, click Policies. The Policies page will be displayed.
At the top of the page, click Create Policy. The Create a new environment policy dialog is displayed:
In the Name field, provide a descriptive name for the Policy.
From the Projects dropdown list, select the Projects that this Policy should be applied to. To select multiple Projects, hold down the Ctrl key as you click.
In the Duration section, enter values for one or more of the following settings:
Runtime Lease - Specify the total time that the environment will remain in the Running state, with all the machines accessible. (This value must be less than or equal to the storage lease.)
Storage Lease - Specify the total time that the environment will remain available before it is securely deleted (This value equals the total life cycle of the environment.)
Suspension Time Before Deletion - (Optional) Activate this checkbox to specify the total time that the environment will remain in a Suspended state before it is securely deleted.
This option provides finer control over automatic deletion. Typically, it is most useful when you want to reduce the time that an environment is stored after it has been suspended automatically due to inactivity.
This option will also affect any environment that has exhausted its Runtime duration, but still has some Storage time remaining. CloudShare considers such an environment as Suspended and will delete it when the value entered in this field has been reached.
In the Environment Inactivity Handling section, choose one of the following options:
Suspend the environment after XX minutes – Enables you to specify a time period before Inactivity Handling is triggered.
Delete the environment after XX minutes – Enables you to specify a time period before a Delete action is triggered.
Environment Always On – Enables you to specify that the environment will not be subject to any Inactivity Handling actions.
Click Create. The new Policy will be created and added to the list of available Policies.
To effectively change one or more Policy values for an existing environment, first create a new Policy with the desired values and then, from the Environment Details page, click Change Policy to assign the newly-created Policy to that environment.
A Project Manager can edit an existing Policy, with the following limitations:
The Policy cannot currently be assigned to an active environment.
If the Policy is assigned to an environment, you can only change the value of the Inactivity Handling field.
If the assigned environment is currently running, this change will be applied so that it will only extend the current inactivity time (i.e., not shorter it). Any new environment or new instance will reflect the new Inactivity Handling time value specified in the change.