back to article VMware and partners to build uber-vCloud to take on Amazon

Rumors have been going around since late last year that server virtualization juggernaut and cloud wannabe VMware was working on building its own infrastructure public cloud, said to be called Project Zephyr, and it turns out to be true. Mostly. Maybe. In a financial analyst meeting held in New York by EMC, VMware's majority …

COMMENTS

This topic is closed for new posts.

Obvious strategy is obviously missing

Come on VMWare. Build the service that will allow us move VMs seamlessly between private ESX clouds and a scalable public cloud. Or, allow us to offload processing capability to a public cloud that will give businesses scalability at times of high demand. Put in place an encryption layer underneath the VMs to protect our sensitive data.

This is such an obvious next step for a company that has massive penetration within corporate networks, yet they persist in mucking around with their existing stupid solutions that are no better than existing public cloud providers. If we wanted public cloud functionality and only public cloud functionality, we'd go with AWS. And we probably will if VMWare don't get their act together.

0
0
Anonymous Coward

Re: Obvious strategy is obviously missing

"as Microsoft has had to bring down Windows server costs to compete better with open source Linux."

No they havn't - where did you get that from?! Microsoft fees have gone up!

The Munich experiment and various other studies long since demonstrated that Linux is only cheaper for very selected functions. Otherwise every company would be in the process of migrating - but in reality Microsoft's share of the server market is still growing...

0
0

Re: Obvious strategy is obviously missing

I think part of the problem is the obsession with VM mobility rather than application workload mobility. It's much easier to distribute load with an F5 GTM or equivalent between environments fairly seamlessly than it is to vMotion to another environment over limited bandwidth, then have all the challenges of overlay networking in order to retain IP addressing.

By all means develop Cloud Connector to move VMs around and translate between different hypervisor VM container formats, but the higher in the stack you do some of this stuff the easier it is, both to accomplish and especially to support and troubleshoot.

Disclaimer - I work for F5, I know there are other solutions available.

0
0
This topic is closed for new posts.

Forums