Flexible Budgets

Overview

With Rescale’s Flexible Budgets, you can maintain control of your usage on Rescale and ensure that the desired usage limits are not exceeded. The usage can be budgeted in terms of either Cost or Corean individual processing unit within a multicore processor o... More Hour usage. Cost and Core hour budgets can be set simultaneously to track usage for the same target in a given period.

Cost Budgets monitor different types of charges generated for usage on Rescale (i.e., compute, platform, IP address, workstationA workstation is a powerful computer system designed for pro... More license, software, data transferThe movement of data between different storage systems, loca... More, storage, license proxy, license hosts, etc.). The Charge Type field allows for independent budgeting of some charge types, including Compute, Software, and License.

Core Hour Budgets monitor the core hours generated for the usage of compute resources on Rescale. Compute core hour usage is generated by Jobs, Workstations, or HPSes. Core hour budgets are especially useful for scenarios where existing computing resources are shared among users and no real-time cost charges are generated, such as in the case of On-demand Reserved (ODR), Bring-your-own-compute (BYOC), or Hybrid usage.

Budgets can be created for various targets, namely:

1. Member Budget – A member budget controls the spending for a specific user. All charges associated with a user are covered by it. This budget can be set by the individual user, the WorkspaceWorkspaces allow rescale customers to create dedicated teams... More Admin, or the Organization Admin.
2. Workspace Budget – A workspace budget controls the spending for a specific workspace. All charges associated with a workspace are covered by it. This budget can be set by the workspace admin or the organization admin.
3. Organization Budget – An organization budget controls the spending for multiple workspaces of an organization. All charges associated with the workspaces are covered by it. Workspaces can be added to or removed from this budget as needed. The organization admin manages these budgets.
4. Project Budget – A project budget controls the spending for a specific project. Since only Jobs, Workstations, and HPS can be assigned to projects, a project budget only covers charges directly associated with them (i.e., compute, platform, IP address, workstation license, and software). This budget can be set by the workspace admin or the organization admin.

When a budget is set by a higher-level entity, it cannot be modified by the lower-level entity; for example, a member budget set by an organization admin cannot be modified by the individual user or the workspace admin.

If multiple budgets apply to a given target, the most restrictive budget takes effect. The restrictiveness of a budget depends on 2 factors: (1) the budget amount and (2) the level. A budget with a smaller amount is more restrictive, and in terms of target, a member budget is the most restrictive, followed by the workspace and project budgets.

Creating Budgets

The workspace or organization admins can navigate to the Teams > Members tab to set member budgets and to the Teams > Project tab to set project budgets.

Alternatively, from the Financials > Budgets tab, an organization or workspace admin can set budgets at various levels.

If an individual user would like to set a budget for themselves, they can do so by navigating to the User Profile Settings > Budgets page.

Budget Type

Budgets on Rescale can be created for a set period or in a recurring manner. Recurring budgets can be set on a monthly, quarterly, or annual basis.

One-Time Budgets

One-time budgets allow setting a non-recurring budget. In the example below, the budget will expire in 2 months from the start date.

If the end date is not set, then the budget will stay in effect indefinitely. If the start date is not set, then the budget will cover all charges since the beginning of the creation of the account. If both start and end dates are not set, then the budget covers all time usage.

Periodic Budgets

Periodic budgets allow setting a recurring budget that refreshes on a set period. The supported periods are monthly, quarterly, and annual. Periodic budgets are effective from the current period and can have optional end dates.

Monthly

The example below shows a Monthly budget set for 6 months. This budget will enforce a $1,000.00 limit each month for six months.

If no end date is set, the $1,000.00 budget limit is enforced for every month, continuing indefinitely.

Quarterly

The example below shows a Quarterly budget set for 4 quarters. This budget will enforce a $100,000.00 limit each quarter for four quarters.

If no end date is set, the $100,000.00 budget limit is enforced for every quarter, continuing indefinitely.

Annually

The example below shows an Annual budget set for 3 years. This budget will enforce a $300,000.00 limit each year for three years.

If no end date is set, the $300,000.00 budget limit is enforced for every year, continuing indefinitely.

Charge Type

Cost budgets can be created to cover some specific types of charges. This is helpful to track charges for usage of specific resources, such as software on-demand license or compute.

The following options are supported:

1. All – Covers all types of charges as described here.
2. Software – Covers software on-demand license (ODL) charges for a specific software.
3. Compute – Covers compute and IP Address charges.
4. Compute & License – Covers compute, IP Address, platform license, and workstation license charges.

Strict Budgets

Note: Using Strict Budgets may result in the termination of running workloads.

If the Strict Budget setting is set to ON, actively running jobs, workstations, or HPS will be immediately terminated if the budget is exceeded. Additional jobs that are submitted will be queued until the budget can support additional jobs.

If the Strict Budget setting is set to OFF, actively running jobs, workstations, or HPS will run to completion if the budget is exceeded. Additional jobs that are submitted will be queued until the budget can support additional jobs.

Budget Preconditions

When a user submits a workloadWorkload refers to the amount and type of computing tasks or... More (job, workstation, or HPS) on the Rescale platform, a budget precondition check is run to determine if the workload’s charges can be covered by the budget.

If the target entity has enough budget to cover the charge for the first hour of the workload, it is allowed to run. The wall time setting is not taken into consideration during the precondition. In case the budget is not enough, the workload fails to launch under this precondition.

If the budget is set to Strict and runs out while a workload is running, the workload is terminated.

Budget Notifications

Rescale sends notifications to customers when the budgets are running low. By default, budget notifications are sent when the budget consumption is at 50%, 80%, and 100%. Budget notifications are not configurable in terms of the percentage consumption at which they go out, however, they can be turned on/off from the User Profile Settings > Notifications page.

Notification receivers

Notifications are sent to different users depending on the type of budget.

• Member-level budget notifications are sent to the member whom the budget targets, along with the workspace admin.
• Workspace-level budget notifications are sent to the workspace admin and organization admin.
• Project-level budget notifications are sent to the workspace admin and organization admin.

Additionally, if the budget target (member, project, workspace) is associated with a partner, then active partner admins also receive the notifications.

Links to Organization Budgets Page

Use the following table of links for the region-specific Organization Budgets pages:

Platform Region	Organization Budgets Page
United States	US Platform Budgets Page
European Union	EU Platform Budgets Page
Japan	JP Platform Budgets Page
South Korea	KR Platform Budgets Page