openstack team mailing list archive

[Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>]

Awesome!

Impressive work everyone!

-S

________________________________
From: openstack-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx [openstack-bounces+sandy.walsh=rackspace.com@xxxxxxxxxxxxxxxxxxx] on behalf of Ewan Mellor [Ewan.Mellor@xxxxxxxxxxxxx]
Sent: Friday, March 25, 2011 7:23 AM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: [Openstack] vSphere support merged

The hypervisor-vmware-vsphere-support blueprint merged yesterday, so Nova can now use VMware’s hypervisors on the compute nodes.  This brings the OpenStack compute options to seven: vSphere, XenServer/Xen Cloud Platform, Xen,  Hyper-V, KVM, QEMU, and UML.  LXC isn’t far behind, which will make eight.

I don’t normally go all Oscar Ceremony over a branch merge, but this was 5000 lines of code and over 3 months of effort, so I thought that a few thank-yous were in order:


·         Neeraj Koul, Rochanglien Infimate and Sateesh Chodapuneedi for the code itself and for the automated QA systems.

·         Ravi Gururaj and Milind Barve for project requirements, management and sponsorship.

·         Armando Migliaccio and Salvatore Orlando for extensive peer review before we brought the branch to the community.

·         Jay Pipes, Rick Harris and Rick Clark for the multiple review phases after that.

·         Anne Gentle for assistance with documentation.

·         Søren Hansen for updating the Hudson environment at short notice to get the merge completed.

·         Thierry Carrez for release management and keeping us on track.

Thanks everyone,

Ewan.



Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.