On Aug 27, 2013, at 18:52 , Russell Bryant
rbry...@redhat.commailto:rbry...@redhat.com wrote:
On 08/27/2013 10:53 AM, Alessandro Pilotti wrote:
That's IMO a different story: backporting a driver is usually quite
trivial as it affects only one service (nova-compute) and one
interaction point with
On 08/26/2013 08:15 PM, Tim Smith wrote:
Hi all,
On Mon, Aug 19, 2013 at 11:49 PM, Bob Ball bob.b...@citrix.com
mailto:bob.b...@citrix.com wrote:
I agree with the below from a XenServer perspective. As with
vmware, XenServer supports live snapshotting and creating multiple
On 08/27/2013 10:06 AM, Alessandro Pilotti wrote:
We are also planning to implement the live snapshot feature in the
Hyper-V driver during the next release cycle.
I'm personally in favour of publishing the APIs in Havana, as this would
provide a stable baseline at the beginning of the
On Tue, Aug 27, 2013 at 10:34 AM, Russell Bryant rbry...@redhat.com wrote:
On 08/27/2013 10:06 AM, Alessandro Pilotti wrote:
We are also planning to implement the live snapshot feature in the
Hyper-V driver during the next release cycle.
I'm personally in favour of publishing the APIs in
On 08/27/2013 10:53 AM, Alessandro Pilotti wrote:
That's IMO a different story: backporting a driver is usually quite
trivial as it affects only one service (nova-compute) and one
interaction point with Nova (the driver's interface). Between Havana and
Grizzly for example, the entire Hyper-V
On 08/27/2013 12:04 PM, Alessandro Pilotti wrote:
On Aug 27, 2013, at 18:52 , Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com
wrote:
On 08/27/2013 10:53 AM, Alessandro Pilotti wrote:
That's IMO a different story: backporting a driver is usually quite
trivial as it
On 08/27/2013 12:04 PM, Tim Smith wrote:
On Tue, Aug 27, 2013 at 8:52 AM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
What about publishing the API as blacklisted by default? This way it
would be available only to users that enable it explicitly, while
On Tue, Aug 27, 2013 at 12:13:49PM -0400, Russell Bryant wrote:
On 08/27/2013 12:04 PM, Tim Smith wrote:
On Tue, Aug 27, 2013 at 8:52 AM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
What about publishing the API as blacklisted by default? This way it
While it's true that there won't be an in-tree driver that supports
the API for this release cycle, we have a commercial driver that
supports it ( https://github.com/gridcentric/cobalt).
IMHO, out of tree virt drivers are completely out of scope here. We
change the virt driver API at will,
On Tue, Aug 27, 2013 at 12:13 PM, Russell Bryant rbry...@redhat.com wrote:
IMO, to be the healthiest project we can be, we must focus on what code
is actually a part of Nova. If you'd like to submit your changes for
inclusion into Nova, then we can talk.
That's ultimately what we're trying
- Original Message -
From: Daniel P. Berrange berra...@redhat.com
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Sent: Monday, August 19, 2013 5:24:59 AM
Subject: Re: [openstack-dev] [nova] live-snapshot/cloning of virtual
machines
On Mon, Aug 19, 2013 at 08:28
From: Shawn Hartsock [hartso...@vmware.com]
Sent: 19 August 2013 20:59
To: Daniel P. Berrange; OpenStack Development Mailing List
Subject: Re: [openstack-dev] [nova] live-snapshot/cloning of virtual machines
For what it's worth... this doesn't seem too bad to me...
I was planning
12 matches
Mail list logo
