<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
On Aug 27, 2013, at 16:48 , Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>></div>
</span></div>
</span></span></div>
<div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">On 08/26/2013 08:15 PM, Tim Smith wrote:<br>
<blockquote type="cite">Hi all,<br>
<br>
On Mon, Aug 19, 2013 at 11:49 PM, Bob Ball <<a href="mailto:bob.ball@citrix.com">bob.ball@citrix.com</a><br>
<<a href="mailto:bob.ball@citrix.com">mailto:bob.ball@citrix.com</a>>> wrote:<br>
<br>
I agree with the below from a XenServer perspective. As with<br>
vmware, XenServer supports live snapshotting and creating multiple<br>
clones from that live snapshot.<br>
<br>
I understand that there is a XenAPI equivalent in the works and<br>
therefore would argue the API changes need to be accepted as a minimum.<br>
<br>
<br>
Can nova technical leadership provide clarification on the current<br>
standing of this blueprint? Two hypervisor vendors have expressed plans<br>
for supporting this feature, and one has specifically requested that the<br>
API changes be merged, but it appears that both the API changeset [1]<br>
and novaclient support [2] have both been rejected pending libvirt<br>
support (which has assumedly been ruled out for the Havana release).<br>
<br>
[1] <a href="https://review.openstack.org/#/c/34036/">https://review.openstack.org/#/c/34036/</a><br>
[2] <a href="https://review.openstack.org/#/c/43777/">https://review.openstack.org/#/c/43777/</a>
<br>
<br>
<br>
In order to minimize the feature divergence between hypervisors, I'd<br>
also argue that we should accept the libvirt implementation even if<br>
it uses unsupported APIs - perhaps disabled by default with a<br>
suitable warning that it isn't considered safe by libvirt/QEmu.<br>
<br>
<br>
It's understandable that changes to the libvirt driver would be held<br>
back until libvirt/qemu-upstream support for live snapshotting is<br>
established (if ever), but given that other vendors whose release<br>
cadences don't necessarily align with the nova release schedule have<br>
expressed plans to support the interface it's unclear why lack of<br>
libvirt driver support would block the entire blueprint.<br>
</blockquote>
<br>
Two other driver maintainers have expressed interest in it, but AFAIK,<br>
there are not implementations of this feature ready for review and<br>
merging for these drivers. Given that's the case, it doesn't make any<br>
sense to me to merge the API with no ability to use it. I'm only saying<br>
it should wait until it can be merged with something that makes it usable.<br>
</blockquote>
<div><br>
</div>
<div>We are also planning to implement the live snapshot feature in the Hyper-V driver during the next release cycle. </div>
<div><br>
</div>
<div>I'm personally in favour of publishing the APIs in Havana, as this would provide a stable baseline at the beginning of the release cycle and also give the ability to users and third parties to backport the driver's feature to Havana (outside of the official
repo of course).</div>
<div><br>
</div>
<br>
<blockquote type="cite">-- <br>
Russell Bryant<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</body>
</html>