openstack team mailing list archive

["Peter J. Pouliot" <peter@xxxxxxxxxxx>]

Having deployed an early OpenStack HyperV cloud, I'd say the following are some good places for MS to start:

A MS driven development effort to bring feature parity with other supported hypervisors.

A commitment to maintain the  HyperV components on an ongoing basis.

Contribution of resources to foster and help grow community participation and infrastructure.

Active participation within the OpenStack community and other OpenStack projects to support and promote interoperability.

An open mind.

pp

On Thu, Feb 02, 2012 at 01:49:59AM +0000, Sriram Subramanian wrote:
>    What kind of support from MS is needed to support Hyper-V in Openstack?
> 
>     
> 
>    From: openstack-bounces+sriram=computenext.com@xxxxxxxxxxxxxxxxxxx
>    [mailto:openstack-bounces+sriram=computenext.com@xxxxxxxxxxxxxxxxxxx] On
>    Behalf Of Rangababu Chakravarthula
>    Sent: Wednesday, February 01, 2012 6:17 AM
>    To: Wayne Walls
>    Cc: openstack@xxxxxxxxxxxxxxxxxxx
>    Subject: Re: [Openstack] [Nova] Essex dead wood cutting
> 
>     
> 
>    We use Ubuntu KVM + Libivrt and have helped several clients build private
>    clouds and all of them are using Windows guests (Win 2003, Win 2008, Win
>    7). For all the issues that we had with windows guests on KVM, we had to
>    figure out ourselves or get help from kvm community forums. MS would only
>    support if you use Windows 2008 Datacenter  or other commercial certified
>    hypervisors
> 
>    Ranga
> 
>    On Sat, Jan 28, 2012 at 3:32 PM, Wayne Walls <[1]wayne@xxxxxxxxxxxxx>
>    wrote:
> 
>    Greetings, Tim!  Took a quick stab, answers/comments in-line.
> 
>    Cheers,
> 
>    Wayne
> 
>    On 1/28/12 2:34 PM, "Tim Bell" <[2]Tim.Bell@xxxxxxx> wrote:
> 
>    >
>    >With the Hyper-V support  being phased out, I would be interested to
>    >understand:
>    >
>    >- What hypervisors are being used for running Windows guests (both
>    >Windows 7
>    >and Windows Server) on top of OpenStack ?
> 
>    The quick and dirty answer is KVM, and somewhere along the lines we'll see
>    Citrix XenServer join the race (hopefully sooner rather than later :)).
>    Plug for XenServer:  [3]http://wiki.openstack.org/XenServerDevelopment --
>    maybe Ewan/Anne has an update for when we'll see full blown
>    XenServer+OpenStack install guides?
> 
>    >- To what extent will Microsoft support problems reported with a Windows
>    >guest running on a non-Microsoft hypervisor ?
> 
>    I think this is a much harder question to answer, as in the past
>    ([4]http://www.redhat.com/promo/svvp) there has been a reciprocal
>    agreement
>    between RedHat and MS to support each others efforts on their own
>    respective virtualization platforms.  Seeing that a) Ubuntu+KVM/libvirt is
>    the current standard, and b) RedHat is not actively participating in the
>    OpenStack community it leaves us with a big question mark.   Any companies
>    out there that are running KVM clouds w/ Windows care to address this?  Do
>    you have customers that want to know how upstream KVM issues are handled?
> 
>    Citrix and Microsoft on the other hand have a fairly long standing
>    partnership, so anything MS products running on XenServer should see a
>    clear escalation path I'd think.
> 
>    >- Are there other sites who are affected by this proposal who would be
>    >willing to invest effort to maintain the Hyper-V support ?
> 
>    Is there a group that has taken ownership of this?  I know that Jordan
>    Rinke (Rackspace), Alex Landman and Peter Pouliot (Novell MS Interop Lab @
>    SUSE) spent a lot of time on Hyper-V in the Bexar/Cactus releases.  They
>    made pretty significant strides in that period, but the progress has since
>    subsided.  With the latest movement in the Hyper-V arena, especially
>    around them trying to get full Ubuntu and Debian support in there, does
>    that mean it's less and less likely MS will support their products or
>    competing HV's?
> 
>    >
>    >Tim Bell
>    >CERN
>    >
>    >-----Original Message-----
>    >From: openstack-bounces+tim.bell=[5]cern.ch@xxxxxxxxxxxxxxxxxxx
>    >[mailto:[6]openstack-bounces+tim.bell=[7]cern.ch@xxxxxxxxxxxxxxxxxxx] On
>    Behalf
>    >Of
>    >Sandy Walsh
>    >Sent: 27 January 2012 16:45
>    >To: Thierry Carrez; [8]openstack@xxxxxxxxxxxxxxxxxxx
>    >Subject: Re: [Openstack] [Nova] Essex dead wood cutting
>    >
>    >I'll be taking the existing Zones code out of API and Distributed
>    >Scheduler.
>    >The new Zones infrastructure is an optional component.
>    >
>    >-S
>    >________________________________________
>    >From: openstack-bounces+sandy.walsh=[9]rackspace.com@xxxxxxxxxxxxxxxxxxx
>    >[openstack-bounces+sandy.walsh=[10]rackspace.com@xxxxxxxxxxxxxxxxxxx] on
>    >behalf
>    >of Thierry Carrez [[11]thierry@xxxxxxxxxxxxx]
>    >Sent: Friday, January 27, 2012 11:23 AM
>    >To: [12]openstack@xxxxxxxxxxxxxxxxxxx
>    >Subject: [Openstack] [Nova] Essex dead wood cutting
>    >
>    >Just as Nova enters feature freeze, it sounds like a good moment to
>    >consider
>    >removing deprecated, known-buggy-and-unmaintained or useless feature code
>    >from the Essex tree.
>    >
>    >Here are my suggestions for removal:
>    >
>    >- Ajaxterm (unmaintained, security issues, replaced by VNC console)
>    >- Hyper-V support (known broken and unmaintained)
>    >
>    >I'm sure that everyone has suggestions on other dead wood that we should
>    >cut
>    >now rather than ship in Essex... please comment.
>    >
>    >--
>    >Thierry Carrez (ttx)
>    >Release Manager, OpenStack
>    >
>    >_______________________________________________
>    >Mailing list: [13]https://launchpad.net/~openstack
>    >Post to     : [14]openstack@xxxxxxxxxxxxxxxxxxx
>    >Unsubscribe : [15]https://launchpad.net/~openstack
>    >More help   : [16]https://help.launchpad.net/ListHelp
>    >
>    >_______________________________________________
>    >Mailing list: [17]https://launchpad.net/~openstack
>    >Post to     : [18]openstack@xxxxxxxxxxxxxxxxxxx
>    >Unsubscribe : [19]https://launchpad.net/~openstack
>    >More help   : [20]https://help.launchpad.net/ListHelp
>    >_______________________________________________
>    >Mailing list: [21]https://launchpad.net/~openstack
>    >Post to     : [22]openstack@xxxxxxxxxxxxxxxxxxx
>    >Unsubscribe : [23]https://launchpad.net/~openstack
>    >More help   : [24]https://help.launchpad.net/ListHelp
> 
>    _______________________________________________
>    Mailing list: [25]https://launchpad.net/~openstack
>    Post to     : [26]openstack@xxxxxxxxxxxxxxxxxxx
>    Unsubscribe : [27]https://launchpad.net/~openstack
>    More help   : [28]https://help.launchpad.net/ListHelp
> 
>     
> 
> References
> 
>    Visible links
>    1. mailto:wayne@xxxxxxxxxxxxx
>    2. mailto:Tim.Bell@xxxxxxx
>    3. http://wiki.openstack.org/XenServerDevelopment
>    4. http://www.redhat.com/promo/svvp
>    5. mailto:cern.ch@xxxxxxxxxxxxxxxxxxx
>    6. mailto:openstack-bounces%2btim.bell
>    7. mailto:cern.ch@xxxxxxxxxxxxxxxxxxx
>    8. mailto:openstack@xxxxxxxxxxxxxxxxxxx
>    9. mailto:rackspace.com@xxxxxxxxxxxxxxxxxxx
>   10. mailto:rackspace.com@xxxxxxxxxxxxxxxxxxx
>   11. mailto:thierry@xxxxxxxxxxxxx
>   12. mailto:openstack@xxxxxxxxxxxxxxxxxxx
>   13. https://launchpad.net/%7Eopenstack
>   14. mailto:openstack@xxxxxxxxxxxxxxxxxxx
>   15. https://launchpad.net/%7Eopenstack
>   16. https://help.launchpad.net/ListHelp
>   17. https://launchpad.net/%7Eopenstack
>   18. mailto:openstack@xxxxxxxxxxxxxxxxxxx
>   19. https://launchpad.net/%7Eopenstack
>   20. https://help.launchpad.net/ListHelp
>   21. https://launchpad.net/%7Eopenstack
>   22. mailto:openstack@xxxxxxxxxxxxxxxxxxx
>   23. https://launchpad.net/%7Eopenstack
>   24. https://help.launchpad.net/ListHelp
>   25. https://launchpad.net/%7Eopenstack
>   26. mailto:openstack@xxxxxxxxxxxxxxxxxxx
>   27. https://launchpad.net/%7Eopenstack
>   28. https://help.launchpad.net/ListHelp

> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp