Flexible plans - Revision history

Favyen Bastani: Replaced content with "Flexible plans are no longer supported. All VMs are now somewhat flexible, in the sense that you can pay on-demand for additional CPU performance. See Burstable Resource..."

2018-08-10T19:59:25Z

Replaced content with "Flexible plans are no longer supported. All VMs are now somewhat flexible, in the sense that you can pay on-demand for additional CPU performance. See Burstable Resource..."

Favyen Bastani at 20:18, 6 January 2016

2016-01-06T20:18:44Z

Favyen Bastani at 22:58, 5 January 2016

2016-01-05T22:58:48Z

Favyen Bastani at 01:19, 1 May 2015

2015-05-01T01:19:31Z

Favyen Bastani at 15:33, 18 March 2015

2015-03-18T15:33:20Z

Favyen Bastani at 17:27, 9 February 2015

2015-02-09T17:27:18Z

Favyen Bastani: /* Metering */

2015-01-26T03:58:15Z

‎Metering

Favyen Bastani at 03:47, 26 January 2015

2015-01-26T03:47:57Z

Favyen Bastani at 03:24, 26 January 2015

2015-01-26T03:24:28Z

Favyen Bastani at 03:24, 26 January 2015

2015-01-26T03:24:19Z

@@ Line 1: / Line 1: @@
-'''Flexible plans''' have a base cost for fixed memory and storage resources, but CPU and bandwidth are billed based entirely on usage. These plans are marked "Flexible" in the plan list (from "Flexible 2048" to "Flexible 32768"). Unlike other plans, you can use allocated CPU cores on Flexible plans as much or as little as desired.
+Flexible plans are no longer supported. All VMs are now somewhat flexible, in the sense that you can pay on-demand for additional CPU performance. See [[Burstable Resources]], "Paying for CPU Performance above the Baseline".
-−
-Pricing is as follows:
-−
-* '''Base cost''': this is the hourly pricing for the fixed memory and storage resources displayed at https://dynamic.lunanode.com/info (which does not include any CPU or bandwidth resources).
-* '''CPU''': $16.00 per CPU-core-month, billed by percent usage per hour. For example, if you use 20% of each of four cores over one week, then the total CPU charge is 0.2 * 4 * (16/4) = $3.20 (in addition to the base cost and any bandwidth charges). Similarly, the maximum monthly CPU charge is $16.00 multiplied by the number of available virtual cores. Note: $16.00 per CPU-core-month is roughly equivalent to $0.0222 per CPU-core-hour.
-* '''Bandwidth''': $0.003/GB -- this is the same as our excessive bandwidth rate, and charges in the panel will appear under excessive bandwidth category.
-−
-Note: Flexible plans are currently only available on local storage. The panel will display an error if you attempt to boot a volume-backed instance with a Flexible plan.
-−
-== Metering ==
-−
-CPU time is calculated based on data in /proc/<pid>/stat for the KVM process and /proc/stat for global usage. The utime and stime fields in /proc/<pid>/stat are added to calculate VM clock ticks. This is compared to sum of user, system, and idle field in /proc/stat to calculate global clock ticks. The percent usage, then, is VM clock ticks divided global clock ticks, multiplied by the number of CPU cores on the compute node. See http://man7.org/linux/man-pages/man5/proc.5.html for details.
-−
-Bandwidth is the sum of outgoing and incoming traffic that passes through the gateway router. This does not include internal traffic between VMs.
-−
-Note that bandwidth is billed as part of the bandwidth pool system, so this really works by having Flexible plans add 0 bandwidth to the account-wide per-region pool. If you have non-flexible virtual machines as well in the same region (e.g. Toronto, Montreal), then you will be able to use unused bandwidth from those VMs on the current calendar month without being charged.

@@ Line 1: / Line 1: @@
-'''Flexible plans''' are a feature currently in beta where you pay a base cost for fixed memory and storage resources, but CPU and bandwidth are billed based entirely on usage. These plans are marked "Flexible" in the plan list (from "Flexible 2048" to "Flexible 32768"). Unlike other plans, you can use allocated CPU cores on Flexible plans as much or as little as desired.
+'''Flexible plans''' have a base cost for fixed memory and storage resources, but CPU and bandwidth are billed based entirely on usage. These plans are marked "Flexible" in the plan list (from "Flexible 2048" to "Flexible 32768"). Unlike other plans, you can use allocated CPU cores on Flexible plans as much or as little as desired.
 Pricing is as follows:
@@ Line 6: / Line 6: @@
 * '''CPU''': $16.00 per CPU-core-month, billed by percent usage per hour. For example, if you use 20% of each of four cores over one week, then the total CPU charge is 0.2 * 4 * (16/4) = $3.20 (in addition to the base cost and any bandwidth charges). Similarly, the maximum monthly CPU charge is $16.00 multiplied by the number of available virtual cores. Note: $16.00 per CPU-core-month is roughly equivalent to $0.0222 per CPU-core-hour.
 * '''Bandwidth''': $0.003/GB -- this is the same as our excessive bandwidth rate, and charges in the panel will appear under excessive bandwidth category.
 Note: Flexible plans are currently only available on local storage. The panel will display an error if you attempt to boot a volume-backed instance with a Flexible plan.

@@ Line 3: / Line 3: @@
 Pricing is as follows:
-* '''Base cost''': this is the hourly pricing for the fixed memory and storage resources displayed at https://dynamic.lunanode.com/info.php (which does not include any CPU or bandwidth resources).
+* '''Base cost''': this is the hourly pricing for the fixed memory and storage resources displayed at https://dynamic.lunanode.com/info (which does not include any CPU or bandwidth resources).
 * '''CPU''': $16.00 per CPU-core-month, billed by percent usage per hour. For example, if you use 20% of each of four cores over one week, then the total CPU charge is 0.2 * 4 * (16/4) = $3.20 (in addition to the base cost and any bandwidth charges). Similarly, the maximum monthly CPU charge is $16.00 multiplied by the number of available virtual cores. Note: $16.00 per CPU-core-month is roughly equivalent to $0.0222 per CPU-core-hour.
 * '''Bandwidth''': $0.003/GB -- this is the same as our excessive bandwidth rate, and charges in the panel will appear under excessive bandwidth category.

← Older revision		Revision as of 01:19, 1 May 2015
Line 17:		Line 17:
	Bandwidth is the sum of outgoing and incoming traffic that passes through the gateway router. This does not include internal traffic between VMs.		Bandwidth is the sum of outgoing and incoming traffic that passes through the gateway router. This does not include internal traffic between VMs.

−	Note that bandwidth is billed as part of the bandwidth pool system, so this really works by having Flexible plans add 0 bandwidth to the account-wide pool. If you have non-flexible virtual machines as well, then you will be able to use unused bandwidth from those VMs on the current calendar month without being charged.	+	Note that bandwidth is billed as part of the bandwidth pool system, so this really works by having Flexible plans add 0 bandwidth to the account-wide per-region pool. If you have non-flexible virtual machines as well in the same region (e.g. Toronto, Montreal), then you will be able to use unused bandwidth from those VMs on the current calendar month without being charged.

@@ Line 4: / Line 4: @@
 * '''Base cost''': this is the hourly pricing for the fixed memory and storage resources displayed at https://dynamic.lunanode.com/info.php (which does not include any CPU or bandwidth resources).
-* '''CPU''': $16.00 per CPU-core-month, billed by percent usage per hour. For example, if you use 20% of each of four cores over one week, then the total CPU charge is 0.2 * 4 * (16/4) = $3.20 (in addition to the base cost and any bandwidth charges). Similarly, the maximum monthly CPU charge is $16.00 multiplied by the number of available virtual cores.
+* '''CPU''': $16.00 per CPU-core-month, billed by percent usage per hour. For example, if you use 20% of each of four cores over one week, then the total CPU charge is 0.2 * 4 * (16/4) = $3.20 (in addition to the base cost and any bandwidth charges). Similarly, the maximum monthly CPU charge is $16.00 multiplied by the number of available virtual cores. Note: $16.00 per CPU-core-month is roughly equivalent to $0.0222 per CPU-core-hour.
 * '''Bandwidth''': $0.003/GB -- this is the same as our excessive bandwidth rate, and charges in the panel will appear under excessive bandwidth category.

← Older revision		Revision as of 03:58, 26 January 2015
Line 15:		Line 15:
	CPU time is calculated based on data in /proc/<pid>/stat for the KVM process and /proc/stat for global usage. The utime and stime fields in /proc/<pid>/stat are added to calculate VM clock ticks. This is compared to sum of user, system, and idle field in /proc/stat to calculate global clock ticks. The percent usage, then, is VM clock ticks divided global clock ticks, multiplied by the number of CPU cores on the compute node. See http://man7.org/linux/man-pages/man5/proc.5.html for details.		CPU time is calculated based on data in /proc/<pid>/stat for the KVM process and /proc/stat for global usage. The utime and stime fields in /proc/<pid>/stat are added to calculate VM clock ticks. This is compared to sum of user, system, and idle field in /proc/stat to calculate global clock ticks. The percent usage, then, is VM clock ticks divided global clock ticks, multiplied by the number of CPU cores on the compute node. See http://man7.org/linux/man-pages/man5/proc.5.html for details.

−	Bandwidth is the sum of outgoing and incoming traffic that passes the gateway router. This does not include internal traffic between VMs.	+	Bandwidth is the sum of outgoing and incoming traffic that passes through the gateway router. This does not include internal traffic between VMs.
		+
		+	Note that bandwidth is billed as part of the bandwidth pool system, so this really works by having Flexible plans add 0 bandwidth to the account-wide pool. If you have non-flexible virtual machines as well, then you will be able to use unused bandwidth from those VMs on the current calendar month without being charged.

← Older revision		Revision as of 03:47, 26 January 2015
Line 10:		Line 10:

	Note: Flexible plans are currently only available on local storage. The panel will display an error if you attempt to boot a volume-backed instance with a Flexible plan.		Note: Flexible plans are currently only available on local storage. The panel will display an error if you attempt to boot a volume-backed instance with a Flexible plan.
		+
		+	== Metering ==
		+
		+	CPU time is calculated based on data in /proc/<pid>/stat for the KVM process and /proc/stat for global usage. The utime and stime fields in /proc/<pid>/stat are added to calculate VM clock ticks. This is compared to sum of user, system, and idle field in /proc/stat to calculate global clock ticks. The percent usage, then, is VM clock ticks divided global clock ticks, multiplied by the number of CPU cores on the compute node. See http://man7.org/linux/man-pages/man5/proc.5.html for details.
		+
		+	Bandwidth is the sum of outgoing and incoming traffic that passes the gateway router. This does not include internal traffic between VMs.

← Older revision		Revision as of 03:24, 26 January 2015
Line 9:		Line 9:
	Flexible plans are still in beta, which means they are subject to updates in pricing or resources (including termination of the plan). If any updates are planned, we will send an email notification at least two weeks before the update takes effect.		Flexible plans are still in beta, which means they are subject to updates in pricing or resources (including termination of the plan). If any updates are planned, we will send an email notification at least two weeks before the update takes effect.

−	Note: Flexible plans are currently only available as local storage. The panel will display an error if you attempt to boot a volume-backed instance with a Flexible plan.	+	Note: Flexible plans are currently only available on local storage. The panel will display an error if you attempt to boot a volume-backed instance with a Flexible plan.