Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Aug 27, 2013, at 18:52 , Russell Bryant 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 affects only one service (nova-compute) and one interaction point with Nova (the driver

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Tue, Aug 27, 2013 at 12:13 PM, Russell Bryant 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 to accomplish

Re: [openstack-dev] live-snapshot/cloning of virtual machines

> 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, a

Re: [openstack-dev] live-snapshot/cloning of virtual machines

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 > > wrote: > > > > > What about publishing the API as blacklisted by default? This way it > > > wo

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On 08/27/2013 12:04 PM, Tim Smith wrote: > > On Tue, Aug 27, 2013 at 8:52 AM, Russell Bryant > wrote: > > > What about publishing the API as blacklisted by default? This way it > > would be available only to users that enable it explicitly, while > still >

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On 08/27/2013 12:04 PM, Alessandro Pilotti wrote: > > > > On Aug 27, 2013, at 18:52 , Russell Bryant > > 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 o

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Tue, Aug 27, 2013 at 8:52 AM, Russell Bryant wrote: > > What about publishing the API as blacklisted by default? This way it > > would be available only to users that enable it explicitly, while still > > supporting the scenario described above. > > It still makes no sense to me to merge an A

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Aug 27, 2013, at 18:52 , Russell Bryant 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 affects only one service (nova-compute) and one interaction point with Nova (the dr

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On 08/27/2013 11:31 AM, David Scannell wrote: > > > > On Tue, Aug 27, 2013 at 10:34 AM, Russell Bryant > 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

Re: [openstack-dev] live-snapshot/cloning of virtual machines

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-

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Tue, Aug 27, 2013 at 10:34 AM, Russell Bryant 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 Havana, a

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Aug 27, 2013, at 17:34 , Russell Bryant mailto: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 Hav

Re: [openstack-dev] live-snapshot/cloning of virtual machines

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 r

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On Aug 27, 2013, at 16:48 , Russell Bryant mailto:rbry...@redhat.com>> wrote: On 08/26/2013 08:15 PM, Tim Smith wrote: Hi all, On Mon, Aug 19, 2013 at 11:49 PM, Bob Ball mailto:bob.b...@citrix.com> > wrote: I agree with the below from a XenServer perspective. A

Re: [openstack-dev] live-snapshot/cloning of virtual machines

On 08/26/2013 08:15 PM, Tim Smith wrote: > Hi all, > > On Mon, Aug 19, 2013 at 11:49 PM, Bob Ball > wrote: > > I agree with the below from a XenServer perspective. As with > vmware, XenServer supports live snapshotting and creating multiple > clones from

Re: [openstack-dev] live-snapshot/cloning of virtual machines

Hi all, On Mon, Aug 19, 2013 at 11:49 PM, Bob Ball wrote: > I agree with the below from a XenServer perspective. As with vmware, > XenServer supports live snapshotting and creating multiple clones from that > live snapshot. > > I understand that there is a XenAPI equivalent in the works and the

Re: [openstack-dev] live-snapshot/cloning of virtual machines

I agree with the below from a XenServer perspective. As with vmware, XenServer supports live snapshotting and creating multiple clones from that live snapshot. I understand that there is a XenAPI equivalent in the works and therefore would argue the API changes need to be accepted as a minimum.