Slashdot Mirror
Inside VMware's 'Virtual Datacenter OS'
snydeq writes "Neil McAllister cuts through VMware's marketing hype to examine the potential impact of VMware's newly pronounced 'virtual datacenter OS' — which the company has touted as the death knell for the traditional OS. Literally an operating system for the virtual datacenter, VDC OS is an umbrella concept to build services and APIs that make it easier to provision and allocate resources for apps in an abstract way. Under the system, McAllister writes, apps are reduced to 'application workloads' tailored through vApp, a tool that will allow developers to 'encapsulate the entire app infrastructure in a single bundle — servers and all.' The concept could help solve the current bugbear of programming, parallel processing, McAllister concludes, assuming VMware succeeds."
So it's not just vaporware, it's an "umbrella concept" that will be built into future products.
No folly is more costly than the folly of intolerant idealism. - Winston Churchill
The real nut of my questions is, what would we need to add to more conventional OS's (linux) to get the job done? For my money, the biggest problem is package interdependencies. IMHO much VM usage is actually just to address that issue. We need package management that isolates applications from each other, giving the appearance of a custom chroot environment for each, while silently sharing resources (such as .so's) that just happen to be the same in multiple applications.
I have used VDC OS. Ultimately it is just a convergence of the existing technologies Vmware has already been developing, upgraded to a new level. I can say, it is very, very nice and clean.
What it gives a data center manager is abstraction and ease of use. The physical way everything is deployed one-off into a datacenter, you need a new application, it involves buying new servers, racks, power and whatnot. If you need to move those servers to another center, or deal with business continuance and disaster recovery, it is a new discrete project.
With VDC, no more. You build all of that into the datacenter "OS", and when a new application comes along they are put into the VDC OS and they inherit everything, not just HA but BC, DR and all of the ease of use. If they don't want BC or DR, they don't pay into that bucket.
Need to move a Datacenter? Use the DR solutions in VDC OS, and you can do it in the middle of the day without your users noticing more than a slight 5-minute bump (or so--largely to let the network routes update).
VMware is so far beyond everybody else in the virutalization industry, it is almost comical to hear other people shout the battle cry of 'Xen' or 'Hyper-V'. Those are nice toys, but the surrounding tools are klunky and almost non-functional, leaving just the hypervisor. What VMware is trying to say with "VDC OS" is that the game already left the hypervisor, that is why everybody is all but giving the hypervisor away for free now.
I may sound like a fanboy, but after having worked in the datacenter for 15+ years I can say this technology really works, and its about time. We can now move the datacenter from the hobbiest market it has been in up to now, into the dialtone it should be.
Except from IBM of course.
vmware is simply the logical extension of what the OS should be doing anyway.
or put another way.
Those who don't buy IBM kit are condemned to reimpliment (badly, and for the rest of their lives) what IBM have been doing for decades.
Deleted
In this case, if you ONLY use VMWARE products throughout your organization, then you have configured your systems properly.
Sleep your way to a whiter smile...date a dentist!
We have IEEE and RFC for standardization of ethernet/switching and routing respectively. What standards exist for virtual environments? As commercial security vendors move into this space, we're headed back into a cycle of supporting multiple architectures. "Security Vendor X" must now understand how VMWare, Hyper-V, Xen, and other VM environments perform their networking. Virtualization of the entire OSI model renders the physical and data link layers obsolete. Why emulate them at that point? Not to say ethernet will disappear, but I can see a point where operating systems evolve branches that run in pure play virtual environments. Those offshoots will shed unnecessary things like MAC addresses as the VM vendors begin defining the new network standards themselves.
VM? LPAR? Parallel Sysplex? Haven't IBM mainframes been doing this since the '70s (okay, Parallel Sysplex has only been since the '90s)?
No doubt a "cloud" of UNIX boxes is harder to marshall than a couple of zSeries though.
And (for many of them) it's never going to get any easier.
It is too easy for them to just think of "one program, one OS, one machine".
Their app takes all the resources it sees from the OS it sees on the machine it sees.
So VMWare "solves" this by making it easy (for a price) for each app to believe that it has it's own machine. So the programmers can keep working they've always worked.
And after a few years when Microsoft follows VMWare, we'll have Microsoft DataCenter OS, abbreviated MS-DOS.
Disclaimer: I work for VMware, and I just came back from VMworld in Vegas (exhausted BTW).
In all my 5 years in the company, I must say that this is the most comprehensive re-thinking of the long-term strategy for virtualization I've seen to date. It brings a new sense of direction that matches where the markets are going.
I agree with most of the comments in this thread regarding the benefits of the VDC-OC, but this is just one part of this picture. IMHO, the biggest change is the "Federation with the Cloud" strategy, where a company may choose to use, move or spawn new or existing workloads directly into a service provider on-demand, maintaining the SLAs (from security to capacity) and then bring them back to the internal cloud if needed.
I mean, go a talk to a CFO or a COO, and they'll [most of the time] politely complain about IT being expensive, and not fast enough to react to the changes the company needs. Shared services are still seen as optional and many business units still prefer to implement their own thing. With this model, IT becomes a true utility, with a pay-as-you-go menu that implements a coherent chargeback model that will bring a smile to the guys in dark suits.
Even if VMware doesn't succeed in these efforts, the genie is out of the bottle and somebody else will make it happen.
Really interesting times to be in IT.