Tuesday, April 5, 2016

Green IT with Xen Orchestra and XenServer [feedly]



----
Green IT with Xen Orchestra and XenServer
// Xen Orchestra

This post is a sequel of our load balancing introduction with XenServer.

This time, we'll explore the Xen Orchestra density mode for your XenServer hosts. But why green IT? Because we are about to shutdown your useless hosts "on the fly" with our new load balancing mode!

Density mode

The goal of density mode is to detect XenServer hosts with a very small CPU load. You can set a custom threshold, by default it's an 10% average on all your CPUs.

For all hosts under this level, we'll choose the one with less memory usage, to migrate its VMs on either:

  • the pool master (which we won't shutdown anyway)
  • or the most busy (in RAM) host

This way, we'll "empty" the maximum number of XenServer machines. Of course, we'll avoid to saturate hosts with a heavy CPU load: we made a projection/estimation of CPU load impact on the targeted host.

And if you empty a XenServer host which has wake on LAN support, guess what? We can halt it!

Green IT

Let's take a simple example: we have 3 XenServer hosts with their VMs:

Step 1: The initial configuration before starting density mode

Step 2: The load balancer detects low CPU usage on both Host 2 and 3. VMs are migrated to Host 1 (Pool master)

Step 3: Host 2 and 3 are empty, thus halted by the load balancer. They will be restarted if we switch in performance mode (or manually if density is just disabled)

Energy saving

Let's say each XenServer host is using roughly 400W. In this case, you save energy for 2 hosts (thus 800W). And even using density mode for half of a day (12h), we'll save you 9600 Wh per day.

Why density only half of the day? Our load balancing feature can be triggered on schedule, it means if you don't need too much CPU power during the night, just activate density mode from 7PM to 7AM.

And what about cooling? A sleeping server won't heat your IT room, and with a PUE of 2, it will be 19200 Wh saved for one day1!

And for 1 year? Using official figures for commercial use and the average within US (0.0998 $/kWh), it means $700 saved, only on a very small infrastructure like this (3 hosts!). We could also count weekends to raise the total.

Another example

"But your example with a PUE of 2 is bad, in my DC got 1.30!". Yep, but your DC is probably hosting more than 3 hosts. Let's imagine you have 100 hosts then. If density mode allowing you to cut half of your hosts, even only half of the day, it means 312 kW2 saved. In one year, it's $11,360 removed from your energy bill. Not bad!

Load balancer scheduler

The density mode is already available, but the scheduler will be released soon, allowing you to switch from "performance" to "density" automatically when needed.

See you soon for other exciting stuff coming in Xen Orchestra!

  1. 800W *2 (PUE) = 1600W. Then 1600 * 12h = 19200 Wh (or 19kWh)

  2. 400W *50 (hosts) * 1.3 (PUE) = 26,000W, thus 26kW. For 12h, it means 312 kWh.


----

Shared via my feedly reader


Sent from my iPhone