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

Adin Scannell adin at scannell.ca
Tue Aug 27 18:07:38 UTC 2013

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

What you are seeing here is a part of the pain of maintaining a fork.  I
> am not OK with shifting part of that burden on to the upstream project
> when it doesn't help the upstream project *at all*.

We're not maintaining a fork, nor trying to shift burden. That's unfair. We
have a long term interest in the success of OpenStack, like everyone here.
We're not asking "upstream" to do anything. This isn't adversarial.

There are plenty of things that don't help nova directly, but certainly
enable a vibrant ecosystem. For example, having extensible APIs and
pluggable backends is critical to the philosophy and success of OpenStack
as a whole.

We absolutely understand that having solid, in-tree implementations is also
important. That's why as a part of the blueprint, there was a pan-community
effort made to create a libvirt implementation. Although that particular
effort has hit some speed bumps, merging the API extension would still
benefit members of the community by simplifying deployments (i.e. for us)
and Havana backports (i.e. needing to provide only an updated compute
driver w/ config change). Other hypervisor driver maintainers have also
expressed the desire to see it merged to speed and simplify development of
in-tree implementations moving forward. It's not just going to get dropped
on the floor.

In the end, I think that the need to have the reference implementation land
at the same moment should be balanced against community interests. Yes, we
really want to see the API in Havana, but it seems we're not alone. I would
understand holding off if there were substantial downsides to merging, or
if multiple hypervisor vendors had expressed a desire to see it not merged.
But that doesn't seem to be the case. Six months is a long time, and
ultimately the evolution of an open source ecosystem is just as important
as the code itself.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130827/9b5725a6/attachment.html>

More information about the OpenStack-dev mailing list