Years from now, your grandchildren will look at you incredulously when you explain that there was once a time when computers sat there sucking up idle energy, and it took even more energy to cool them while they were busy doing nothing. And this is to say nothing about the fact that most of this energy came from non-renewable sources!
Everyone understands that one of the big advantages of virtualization and the cloud is the optimization of energy consumption. It’s appealing to providers because it lowers costs, and to customers because it’s a hassle-free way to be environmentally conscious. But as the day-to-day conservation achieved by server consolidation becomes commonplace, customers and watch dog organizations demand even more. As we’ve seen with the recent interaction between Greenpeace and Amazon, there is a strong feeling emerging that every little bit helps.
You can do your part by using Embotics® vCommander™ power schedules, which allow you to set schedules to power up services at a time you choose, and later power them down. Usually, we see something like VMs being powered on around 07:30 and powered off around 18:30, bookending the typical workday. A power schedule is not a policy enforcing services be powered down, so you aren’t ever preventing people from using their machines when they are needed, and you can also provide Service Portal users permission to switch power schedule groups, in case they need to override a scheduled power event.
In addition to using power schedules, Embotics also encourages administrators to allow users to view the rightsizing recommendations, which contribute by optimizing resources even further. If a VM only needs 1 vCPU and 1GB of memory, why let it run with more? If you extrapolate this kind of over-provisioning across a large number of machines, you may soon find that you’re running more power hungry hosts than you need!
There’s almost always room to conserve energy, so let’s green those clouds, and save some money at the same time!