Data Processing
Valdis's Weblog
Archives
« November 2009
MonTueWedThuFriSatSun
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
      
Today
Click me to subscribe
Search

Links
 

Today's Page Hits: 25

Locations of visitors to this page
« Wyse has a SunRay... | Main | Virtualisation,... »
Tuesday Oct 30, 2007
Virtualization - deadly when fashionable, saviour when qualifed.

Why are are we virtualising, is it to have fewer servers, then we are consolidating. Is it to improve server utilisation and efficiency.

We have systems that can run multiple applications, we have been doing this since 1980's. Ever heard of an OS scheduler.

Have we made the mistake to put each application on it's own server. Who bought all those small servers, why. Are we fixing the server sprawl problem.

So in the late 90's and early 2000's we consolidated to large servers. Then we thought that many smaller servers were cheaper and fasters. Now we have figured out that they were not. But we do not want to admit that big consolidated servers was the right idea. So we can put a a virtualisation spin on it and consolidate again.

As I have always said, rightsizing, downsizing and funsizing.

Now a couple questions that we should ask ourselves before we go down the virtualisation route.

Can we meet the peak workload requirements, if all applications need all resources simultaneously. When we consolidate we need to be careful. The finance types will probably look at average utilisation. But, do not use average utilisation as a measure, you need to be there for the peaks. Think about this, most metropolitan underground train systems are built to cope will peak loads not average passenger traffic.

Therefore virtualisation is all about capacity planning and understanding you application workload.

Now, do we also map all of our critical applications/services and make sure that they do not run on the same server, with many virtualized partitions. Lets no put all of our eggs in one basket, we have to spread our business critical apps accross servers, computer rooms sites etc.

Stragely enough we have been able to do this on single servers running one operating system where we use priority groups and memory fencing to increase utilisation for the last 30 years. What has changed ?

So if you do not want to spend lots of money to try this and if you want to try some new high performance, multiple core, low power servers. You can get virtualisation software here for free.

Virtualisation is not new, reduce your risks and costs.

http://www.sun.com/servers/coolthreads/ldoms/index.xml

Posted at 08:23PM Oct 30, 2007 by Valdis Filks in Technical  |  Comments[2]

Comments:

I don't really understand what LDOMs gains you over zones.

To my mind, zones are far more flexible (at runtime) than 'hard-partitioned' LDOMs.

Especially as you are probably going to be running Solaris in your LDOMs anyway.

Posted by Dick Davies on October 30, 2007 at 10:51 PM CET #

Zones are great for some tasks (as you mention they are flexible and are also lightweight) but LDoms allow you to have differing OSs/patch levels/metaclusters in each guest domain, provide greater isolation between guests using the hypervisor and overcome some limitations of Zones such as serving NFS.

But if Zones provide all the flexibility and functionality you need then I'd stick with them.

(It's not an either/or situation - you could create many Zones spread over a few LDoms if you like)

Posted by Liam Merwick on November 02, 2007 at 10:05 AM CET #

Post a Comment:
  • HTML Syntax: NOT allowed