Tuesday, April 21, 2009

Microsoft Mythbusters Top 10 VMware Myths

I had just read through some articles and watch the video from Microsoft about the top 10 VMware Myths today, I would like to share my thoughts about the video details published by Microsoft with unbiased opinions.

The guys talked about Live Migration on HyperV on the next release. As a customer, I am always believed that the software provider should only commit and tell the customers when their products are ready, and not always tell the customer WE ARE READY IN THE NEXT RELEASE. This only explain as your product is not ready, what about your next release is in 2 years time? That meant the products is not as promise as you publish to the customers. Please take note that VMware had supported Storage VMotion for current version, which is another step beyond of Live Migration.

Cluster File system from Microsoft today will be far behind if we compare with the fault tolerance in vSphere. This is only able to match with what VMware had been done in the pass and not creating new technology into their product. They should take more innovative to come out something that VMware doesn't.

HyperV is not scalable as VMware does? This could be right depend how you want this to be compared. In virtual infrastructure, HA and DRS are both important pieces in the production environment which promise the load balancing and High availability. ESX 3.5 support up to 32 ESX host per clusters, which I think HyperV is not comparable at all. I think HyperV is far behind in term of the technology which customers are demanding. They may able to target the crowd which plan for development, test and training environment to be virtualized on HypverV, but not mission critical production systems. You can easily run 1000 of web server in the front end without HA or clustering to serve your web site today, with additional load balancer in the market which auto redirect the traffic to the servers, therefore when 100 / 1000 servers are down, and your web should still reachable. There is nothing should be proud to tell the customer how many Virtual Machine from Hyper V is currently running the Microsoft website. To run a web server in virtual machine today, is very common and not big deal at all.

About reliability, if we compare the system uptime for Linux and windows, which machine will we rebooted most and patch it most? I think you and myself should have the right answer in the mind. Even if VMware is utilizing the similar amount of resource to power up the ESX, but do remember, VMware perform smartly in term of resources management. It will smartly manage the resources to give the maximum utilization of the hardware you invested, plus higher ratio of consolidation. Of course, it does provide flexibilities to reserve the right amount of resources if require.

HyperV has the advantage to run on any hardware you like. This is something that VMware does not provide, as we are required to follow the HCL from VMware for each version of ESX we deploy. In most case, will we actually run our production virtual infrastructure to serve business need on a custom made server? or a mixture parts from multiple vendor which didn't fully tested of compatible purpose? Most customers today will buy the servers from DELL, HP, IBM and etc, which provide the best compatible from technology from motherboards, memory, CPU, storage and etc, which had been certified and tested before they sell to the customers. This had significant improved the server life spend and productivity. Therefore, I will conclude this advantages from HyperV does not really concern myself to select them as the hypervisor in our data center.

Management wise, I think they are trying to over sell their system center, which is a big step to lock customers down to their so call SCCM for everything in your environment. Why will you need to have pure microsoft to run in your organization while there are plenty of products available to be more reliable, cheaper and efficient. In our environment, we are trying to avoid to run Microsoft as much as possible due to the costly licensing term they apply to the customers. We run 85% of our system in Linux environment today, and I should said SCCM is not the right tools to manage my physical or virtual environment. If you want me to choose between Altiris and SCCM, Altiris might be a better choice to myself. SCCM may meant more to the pure Microsoft platform environment usage.

There are certainly more comments I can put here regarding the video I watched, but I think is just too tired to write up everything here. I think you guys who read this should have your personal opinion. My thought here is meant for share and more towards my environment. You may think differently from myself as the environment that you run may be different. Enjoy the video.

Offline VM Migration auto convert RDM to VMDK format

Due to some reconfiguration work we performed on our Virtual Infrastructure, we had required to relocate some of the VM to a different datastore. These VMs which required to be moved had been attached with Raw Device Mapping (RDM). Previously I thought the offline storage migration will not move the RDM over to the datastore as RDM is referring to the raw device from the SAN storage.Actually I was planned to convert the RDM to VMDK which I planned to manual transfer the files I need from RDM to the new virtual disk I created.


In a test yesterday, we found that a offline VM migration will auto convert the RDM which attach to the virtual machine to the VMDK format when I selected the data store to be moved in offline mode. This was really surprise myself and simplify my work actually, as I do not require some manual file transfer from the RDM to the new virtual disk.

Oracle to buy Sun Microsystem

Break news today which shocked most of the IT folks as Oracle had announced to buy over Sun Microsystems for 9.50 a share. I am really shocked to see this as last week, we were still talked about the deal called off with the possible merging from Sun Microsystems with IBM, which may end up IBM monopolize some high end computing market. Oracle could make a good move by taking over Sun. This may direct or indirect many environment which related to Virtualization, Java and MYSQL which is the strength of Sun Microsystems. There are chances to reduce the dependency of Oracle to Redhat and Enterprise Linux and move over to Sun Solaris or open solaris. This is more positive VS the buy over that suggested by IBM previously.

Oracle is no longer a software company today. With buy over for Sun Microsystems, they will able to deliver the hardware, platform, software, database, virtualization and etc. I think they will be more aggressive strategy to move themselves into the virtualization and integration market which may end up competing themselves with their partner such as VMware. This will definitely heat up the market or virtualization and hypervisor competition.

6 cores limitation per socket for vSphere enterprise

As the new licensing model from VMware vsphere 4, it clearly show that you may require additional 620USD per sockets to entitle yourself for the enterprise plus if which come with 12 cores per sockets, host profiles, distribution switch and etc.

For existing enterprise users, they will no longer entitle everything as they did in the past due to the new scheme that will apply by vmware. There is a clause which stated by the official documentation released from vmware.

" vSphere Enterprise is available for USD$2,875 per one processor with up to six cores for use on a server with up to 256GB of memory. "


This clearly stated as six cores per sockets is the max you can go if you are previous or new enterprise customer. Here is the concern now, as six cores is in the market now, and soon we will see 8 cores and 12 cores in the market too. When the hardware technology improve and provide more cores per CPU, we will end up require to pay for additional charges to entitle the features due to this licensing model.

Personal point of view, to provide alternative licensing model with new features should be acceptable, but it shouldn't fix the limit for number of cores to be allowed in each CPU sockets licenses. A customer may end to pay more not because the new features they really need, it may just purely due to the maximum number of cores per socket is allowed. I hope VMware should reconsider the clause they had included in the release.

 
Site Meter