Daniel P. Berrange wrote:
FWIW, libvirt has pretty reasonable abilities to manage VMWare ESX servers,
and some very basic support for Hyper-V. It would be interesting to see if
the OpenStack libvirt driver can be developed to support these targets too.
If the libvirt VMWare/HyperV drivers are
On Thu, Feb 02, 2012 at 11:52:17AM +, Armando Migliaccio wrote:
To the best of my knowledge, the ESXi support is up to date. There may be
bugs, but which virt driver is perfect ;)?
Sateesh may know more, because he is the main contributor/maintainer from
Citrix.
However, as Vish
+1!!
On Feb 6, 2012 5:38 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, Feb 02, 2012 at 11:52:17AM +, Armando Migliaccio wrote:
To the best of my knowledge, the ESXi support is up to date. There may
be bugs, but which virt driver is perfect ;)?
Sateesh may know more,
Ewan Mellor wrote:
There's certainly no need to remove it. It's clearly not tier 1 like
XenServer and KVM, but it's in decent enough shape.
Good to hear :)
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list:
Vishvananda Ishaya wrote:
We don't need support from microsoft specifically. What we need is one
or more companies committed to:
a) actually using the Hyper-V driver
b) writing tests and fakes so that the existing functionality doesn't break
c) providing test hardware and jenkins
@lists.launchpad.net] On Behalf Of
Thierry Carrez
Sent: 02 February 2012 08:53
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Essex dead wood cutting
Thierry Carrez wrote:
Just as Nova enters feature freeze, it sounds like a good moment to
consider removing deprecated
@lists.launchpad.net
[mailto:openstack-
bounces+armando.migliaccio=eu.citrix@lists.launchpad.net] On Behalf Of
Armando Migliaccio
Sent: 02 February 2012 11:52
To: Thierry Carrez; openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Essex dead wood cutting
To the best of my
: [Openstack] [Nova] Essex dead wood cutting
Thierry Carrez wrote:
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
To: Wayne Walls
Cc: openstack@lists.launchpad.net
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
+sandy.walsh=rackspace@lists.launchpad.net] on
behalf
of Thierry Carrez [thie...@openstack.org]
Sent: Friday, January 27, 2012 11:23 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] [Nova] Essex dead wood cutting
Just as Nova enters feature freeze, it sounds like a good moment
To: Wayne Walls
Cc: openstack@lists.launchpad.net
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
, 2012 6:17 AM
To: Wayne Walls
Cc: openstack@lists.launchpad.net
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
-Original Message-
From: Thomas Goirand [mailto:tho...@goirand.fr]
Sent: Sunday, January 29, 2012 11:17 AM
To: Anne Gentle
Cc: Ewan Mellor; Thierry Carrez; openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Essex dead wood cutting
On 01/29/2012 12:04 PM, Ewan Mellor
On 28/01/12 02:23, Thierry Carrez wrote:
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:
- Hyper-V support (known broken and
On 01/28/2012 04:32 PM, Wayne Walls wrote:
snip
- 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
(http://www.redhat.com/promo/svvp) there has been a
-bounces+tim.bell=cern...@lists.launchpad.net] On
Behalf Of Sandy Walsh
Sent: 27 January 2012 16:45
To: Thierry Carrez; openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Essex dead wood cutting
I'll be taking the existing Zones code out of API and Distributed
Scheduler.
The new
On 01/29/2012 12:04 PM, Ewan Mellor wrote:
That includes Citrix XenServer, Red Hat RHEL and RHEV, Oracle VM,
Novell SLES, and VMware ESX.
Basically the answer is that you need a commercial hypervisor
(because SVVP certification takes weeks to do, and months up front to
get the drivers and
...@lists.launchpad.net] On Behalf Of
Sandy Walsh
Sent: 27 January 2012 16:45
To: Thierry Carrez; openstack@lists.launchpad.net
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
To: Thierry Carrez; openstack@lists.launchpad.net
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
On Jan 28, 2012, at 12:34 PM, Tim Bell wrote:
- What hypervisors are being used for running Windows guests (both Windows 7
and Windows Server) on top of OpenStack ?
- To what extent will Microsoft support problems reported with a Windows
guest running on a non-Microsoft hypervisor ?
- Are
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
@lists.launchpad.net] on behalf of
Thierry Carrez [thie...@openstack.org]
Sent: Friday, January 27, 2012 11:23 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] [Nova] Essex dead wood cutting
Just as Nova enters feature freeze, it sounds like a good moment to
consider removing deprecated, known
22 matches
Mail list logo
