In association with heise online

01 February 2012, 16:23

Microsoft commits to OpenStack and OpenNebula Hyper-V support - Update

  • Twitter
  • Facebook
  • submit to slashdot
  • StumbleUpon
  • submit to reddit

Cloud MSFT icon Microsoft says it is committed to OpenStack and OpenNebula support for its Hyper-V hypervisor. The company has previously said it is working with both open source cloud projects to see its hypervisor technology supported, but in neither case has production quality support appeared.

Questions about Microsoft's plans for OpenStack were raised when one of the release managers for OpenStack's forthcoming "Essex" release questioned whether the support for the Microsoft hypervisor should be retained, as it was "known broken and unmaintained".

In October 2010, Microsoft had announced it was working with Cloud.com to develop the code to support Hyper-V on OpenStack. The current lack of functioning Hyper-V support in OpenStack does mean that few, if any, companies have deployed it in any meaningful way and that therefore the potential removal of the code would not affect many users. Microsoft is reported to have responded to the suggestion that the Hyper-V code be removed with the statement "Microsoft is committed to working with the community to resolve the current issues with Hyper-V and OpenStack".

Meanwhile, Microsoft has renewed its collaboration with the OpenNebula Project to further develop last year's prototype Hyper-V plugin for the cloud platform and offer a more stable version with more features. The Hyper-V Drivers for OpenNebula page on the project's site provides more information on plans for the stable and future releases.

Update – Despite Microsoft's statement, it appears that the OpenStack developers have gone ahead and removed Hyper-V support in an operation named "hypervsectomy". The comments on the change state that "Hyper-V has been unmaintained for several releases now", that it lacks a maintainer, and that no one has reported that it works, adding that "many improvements have been made across other hypervisor drivers that have not been done in the Hyper-V driver, so even if it worked, it would only expose a subset of the functionality that the other drivers do".

(djwm)

Print Version | Send by email | Permalink: http://h-online.com/-1426801
 


  • July's Community Calendar





The H Open

The H Security

The H Developer

The H Internet Toolkit