OpenStack Ditches Microsoft Hyper-V

judgecorp writes "The OpenStack open source cloud project has removed Hyper-V from its infrastructure as a service (IaaS) framework, saying Microsoft's support for its hypervisor technology is 'broken.' This will embarass Microsoft, as major partners such as Dell and HP support OpenStack, along with service providers such as Internap." Adds reader alphadogg, this "means the code will be removed when the next version of OpenStack, called Essex, is released in the second quarter."

Comments

But it is Microsoft's code.

[pavon]

Microsoft has been trying to push Hyper-V support into Linux, but their original driver code was complete shit, and it's just barely starting to get better. It's almost stable now, but not fully functional. So, yes it is fair to say that Hyper-V support is being removed from OpenStack because Microsoft's support for Hyper-V on Linux has been very poor.

Re:Maybe it's just too hard...

[Archangel Michael]

Here is the key passage from the article, should you read it.

“Ah, never mind. They really don’t care.”

The "They" is Microsoft, and the guy saying it is person Microsoft has a liaison for the project.

Also, it is too hard to maintain code you don't have control over. Microsoft drafted someone else to develop the code, that organization was bought by Citrix who owns Zen Hyper-V, a competing project. Again mentioned in the article.

So, this is not just normal Microsoft Bashing by /. (well, it is) this is something that Microsoft deserves. Microsoft better start focusing on core competencies to support of Enterprise Infrastructure and Windows or it is going to find itself shrinking rapidly.

Re:Maybe it's just too hard...

[TheLink]

HyperV has many more dependencies than other virtualization stuff.

For example,.if your host and management client are not in the same AD domain but you want to use MMC to remote manage a HyperV host (say you do not want to allow multiple people to remote desktop to the host), to configure the permissions and other stuff you often have to download and run an _unsupported_ tool: http://archive.msdn.microsoft.com/HVRemote

Or wade through 5 pages of stuff:
http://blogs.technet.com/b/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx

And even so, it often still doesn't work, e.g. the added firewall rules might not work for some stupid reason and you have to turn off the firewalls completely.

In contrast with VMware you need a lot few number of ports opened to do remote management, and you normally won't have problems getting remote management. In fact it's almost a "given" that you'd be mainly using remote management.

HyperV may also not work so well if you're not running Linux guests. Recently a colleague had a problem with a Linux guest- some (ICMP echo) frames/packets were being sent but not others (ARP replies)! I solved it by restarting the hyper-v virtual switch. Perhaps that HyperV server was not updated. Whatever it is, even vmware GSX server years ago caused me fewer problems than HyperV.

Re:Maybe it's just too hard...

[afidel]

When asked if he's happy with Microsoft's contributions to Linux, he said "I am very happy with their contributions. The work that they have done on their drivers is amazing. The original driver submission was over 20 thousand lines long. Two new drivers have been added to the codebase, and lots of cleanup, making the final line count around 7 thousand lines. link