cluster_billing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cluster_billing [2015/10/23 21:09] mgstauff [Storage] |
cluster_billing [2017/01/05 19:18] (current) mgstauff [Storage] |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| - Storage - disk space usage | - Storage - disk space usage | ||
| - | - // | + | - //Project |
| - | Users of the CfN cluster are assigned to one or more // | + | Users of the CfN cluster are assigned to one or more //Project |
| - | ** There is no charge per user assigned to a //Billing Entity//.** Charges are based just on cumulative disk usage and // | + | ** There is no charge per user assigned to a //Billing Entity//.** Charges are based just on cumulative disk usage and //Project |
| ==== Billing Entity ==== | ==== Billing Entity ==== | ||
| - | A //Billing Entity// is typically a PI or research center that can be billed for cluster usage. A //Billing Entity// is responsible for all disk space and // | + | A //Billing Entity// is typically a PI or research center that can be billed for cluster usage. A //Billing Entity// is responsible for all disk space and //Project |
| ==== Storage ==== | ==== Storage ==== | ||
| Disk space is organized into project trees, consisting of a directory and all its sub-directories (e.g. / | Disk space is organized into project trees, consisting of a directory and all its sub-directories (e.g. / | ||
| - | Project trees can be setup as a shared directory for all users within a lab and/or within a project. Or, project trees can be setup for each user within a lab or project. However, the shared tree approach is preferred for easier management, maintenance and to facillitate | + | Project trees can be setup as a shared directory for all users within a lab and/or within a project. Or, project trees can be setup for each user within a lab or project. However, the shared tree approach is preferred for easier management, maintenance and to facilitate |
| All storage is on dedicated enterprise-grade hardware RAIDs utilizing RAID-6 for redundancy. | All storage is on dedicated enterprise-grade hardware RAIDs utilizing RAID-6 for redundancy. | ||
| + | |||
| + | You may want to archive your data off of the cluster to save costs. If so, we have [[dataarchving|some suggestions here]] | ||
| === Backup === | === Backup === | ||
| - | All storage is backed up to tape on a quarterly basis and tapes are stored off-site. | + | All storage is backed up to tape on a near-quarterly basis (at least 3 times per year) and tapes are stored off-site. |
| === Non-cluster Archiving & Cold Storage === | === Non-cluster Archiving & Cold Storage === | ||
| [[dataarchving|See here]] for suggestions on archiving your data off of the CfN cluster. | [[dataarchving|See here]] for suggestions on archiving your data off of the CfN cluster. | ||
| - | ==== Slot Groups | + | ==== Project |
| - | A // | + | A //Project |
| + | |||
| + | One slot is a quota of 1 cpu core and 6GB RAM (3GB on the ' | ||
| + | |||
| + | Each //Project Slot Quota// sets an aggregate slot quota for all users assigned to the //Project Slot Quota//. This quota limits the aggregate | ||
| - | Each //Slot Group// sets an aggregate slot quota for all users assigned to the //Slot Group//. This quota limits the aggregate number of concurrent slots used by all the users in the //Slot Group// | + | There is an individual limit of 40 slots for each user with a //Project |
| For example: | For example: | ||
| - | ^Slot Group Name | picsl| | + | ^Project |
| ^Users | mgstauff, pcook, jtduda| | ^Users | mgstauff, pcook, jtduda| | ||
| - | ^Sub-group1|mgstauff| | ||
| - | ^Sub-group2|pcook, | ||
| ^Aggregate quota|80| | ^Aggregate quota|80| | ||
| - | ^Sub-group1 | + | ^mgstauff |
| - | ^Sub-group2 | + | ^pcook, jtduda |
| - | In this example, the three users can together never use more than 80 slots at the same time. In addition, user mgstauff can never use more than 20, and users pcook and jtduda can each never user more than 50. Note that even though pcook and jtduda have 50-slot quotas, if pcook were already using 50 slots, then jtduda could only use 30 slots with any jobs he submitted at that time. | + | In this example, the three users can together never use more than 80 slots at the same time. In addition, user mgstauff can never use more than 20, and users pcook and jtduda can each never user more than 40. Note that even though pcook and jtduda have 40-slot quotas, if pcook were already using 40 slots, and mgstauff were using 15, then jtduda could only use 25 slots with any jobs he submitted at that time. |
| - | A //Billing Entity// may decide to create individual // | + | A //Billing Entity// may decide to create individual //Project |
| ==== Users Working for Multiple Labs/ | ==== Users Working for Multiple Labs/ | ||
| Line 52: | Line 56: | ||
| The data for the different labs/ | The data for the different labs/ | ||
| - | === Slot Groups | + | === Project |
| - | A single user can belong to multiple | + | A single user can belong to multiple |
| ---- | ---- | ||
| Line 67: | Line 71: | ||
| It provides: | It provides: | ||
| * 150 GB Disk Space | * 150 GB Disk Space | ||
| - | * One // | + | * One //Basic Project |
| * Unlimited number of assigned users | * Unlimited number of assigned users | ||
| * Additional disk space is priced as described below. | * Additional disk space is priced as described below. | ||
| Line 73: | Line 77: | ||
| It does not provide: | It does not provide: | ||
| * Flexible per-user sub-quotas | * Flexible per-user sub-quotas | ||
| - | * Dyanmic | + | * Dynamic |
| - | === Storage - $700 / TB / year === | + | === Storage - $700 / TB / year ( $400 / TB / year above 8TB ) === |
| - | * Additional storage (beyond the 150GB included in Basic Account) is charged pro rata at $700 per terabyte. | + | * Additional storage (beyond the 150GB included in Basic Account) is charged pro rata at $700 per terabyte, for the first 8TB. After 8TB, the charge is $400/TB. |
| * Charges are based on average weekly usage over the billing cycle. There' | * Charges are based on average weekly usage over the billing cycle. There' | ||
| * Multiple data directories can be assigned to a single //Billing Entity// | * Multiple data directories can be assigned to a single //Billing Entity// | ||
| - | * Available to both Basic Accounts and to //Billing Entities// that opt for High-Speed Slot Groups. | + | * Available to both Basic Accounts and to //Billing Entities// that opt for High-Speed |
| + | * You may want to archive your data off of the cluster to save costs. If so, we have [[dataarchving|some suggestions here]] | ||
| - | === High-speed Slot Groups | + | === High-speed |
| - | * Additional // | + | * Additional //High-Speed Project |
| - | * // | + | * High-speed |
| * Unlimited number of assigned users | * Unlimited number of assigned users | ||
| * Flexible sub-quotas for any number of assigned users (see example above). | * Flexible sub-quotas for any number of assigned users (see example above). | ||
| - | * The maximum individual per-user base quota in a slot group is 50 (to help avoid individual users from dominating the cluster) | + | * The maximum individual per-user base quota in a High-speed Project Slot Quota is 50 (to help avoid individual users from dominating the cluster) |
| * Dynamic quotas - every user's slot quota is increased when the cluster has idle computing power. Dynamic quota increases are proportional to each user's base quota. | * Dynamic quotas - every user's slot quota is increased when the cluster has idle computing power. Dynamic quota increases are proportional to each user's base quota. | ||
| - | * Quarterly billing for Slot Groups | + | * Quarterly billing for Project |
| + | * [[slot_usage_reports|Slot Usage Reports]] are provided to help decide how many slots to request for a group. | ||
| - | * NOTE: We have tried to design the Slot Group system to be simple, flexible, affordable and to help researchers avoid the scenario in which they ask " | + | * NOTE: We have tried to design the Project |
| ==== Billing Cycle ==== | ==== Billing Cycle ==== | ||
| - | Billing will be conducted quarterly and published as a [[disk usage billing report]] and [[slot usage billing report]]. | + | Billing will be conducted quarterly and published as a [[disk usage billing report]] and [[slot usage billing report]]. Slot usage details are reported under [[slot_usage_reports|Slot Usage Reports]]. |
| **NOTE** __The first billing cycle will begin 7/1/2015, with charges applied 10/1/2015. For the first cycle, storage amounts won't be tracked weekly until 9/1/2015, to give labs time to clean up disk space.__ | **NOTE** __The first billing cycle will begin 7/1/2015, with charges applied 10/1/2015. For the first cycle, storage amounts won't be tracked weekly until 9/1/2015, to give labs time to clean up disk space.__ | ||
| Line 103: | Line 109: | ||
| * 1-2 regular users, few casual users | * 1-2 regular users, few casual users | ||
| * $100 | * $100 | ||
| - | * $1440 48-slot // | + | * $1440 48-slot |
| * $1400 2.15 TB total storage | * $1400 2.15 TB total storage | ||
| * --------- | * --------- | ||
| Line 111: | Line 117: | ||
| * 4 regular users, several casual users | * 4 regular users, several casual users | ||
| * $100 Mandatory Basic Account | * $100 Mandatory Basic Account | ||
| - | * $2880 96-slot // | + | * $2880 96-slot |
| * $2800 4.15 TB total storage | * $2800 4.15 TB total storage | ||
| * --------- | * --------- | ||
| Line 119: | Line 125: | ||
| For comparison, you may want to check [[http:// | For comparison, you may want to check [[http:// | ||
| + | |||
| + | |||
cluster_billing.1445634552.txt.gz · Last modified: 2015/10/23 21:09 by mgstauff
