<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 10, 2015 at 9:54 PM, hao wang <span dir="ltr"><<a href="mailto:sxmatch1986@gmail.com" target="_blank">sxmatch1986@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="font-size:14px">@Duncan and John, I have a idea about this issue, if volume is in-use but the instance which it's attached to is power-off, so can we avoid </span><span style="font-size:14px">data corruption? If it's true, cinder could free the "available" restriction, let user decide if they want to restore the boot disk, and they should shut down the instance first and then restore volume.</span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2015-08-11 11:30 GMT+08:00 hao wang <span dir="ltr"><<a href="mailto:sxmatch1986@gmail.com" target="_blank">sxmatch1986@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">@Duncan and John, thank you both and I have understood this. The reason I ask this question is we can't restore the boot volume of instance which is boot-from-volume, since Nova can't detach the boot disk now. So we need to figure out a way to solve this issue.<div><br></div><div>Maybe we should let nova can detach the boot disk, but there are also some problems, like "what state should be set after detach the boot disk? Can user reboot/stop/migrate the instance after detach the boot disk? etc".</div><div><br></div><div>Anyway, I feel it may be a long way to solve this issue properly.</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-08-11 0:13 GMT+08:00 John Griffith <span dir="ltr"><<a href="mailto:john.griffith8@gmail.com" target="_blank">john.griffith8@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Aug 10, 2015 at 3:47 AM, hao wang <span dir="ltr"><<a href="mailto:sxmatch1986@gmail.com" target="_blank">sxmatch1986@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Sorry if I missed something, since now we have supported backup in-use volumes in L, so I wonder is there some plan or design to support restoring on-line volumes. <div><br></div><div>Thanks.<span><font color="#888888"><br clear="all"><div><br></div>-- <br><div><pre>Best Wishes For You!</pre></div>
</font></span></div></div>
<br></div></div><span>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></span></blockquote></div><div style="font-family:monospace,monospace">No, a restore operation is going to require that the volume be taken offline for a number of reasons. Even with multi-attach if/when it ever becomes a reality you can't write to the volume while it's in use by another Instance (corruption, file system updates etc etc) unless you're using a shared FS or clustered File System. </div><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace">That's a use case that I don't think has a ton of value and it's not compelling enough to introduce all of the issues that come along with it IMO.</div><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace">Thanks,</div><div style="font-family:monospace,monospace">John</div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><pre>Best Wishes For You!</pre></div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><pre>Best Wishes For You!</pre></div>
</div>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><div class="gmail_default" style="font-family:monospace,monospace">Wouldn't a detach be less impact than powering off the instance? I don't understand why this is desired? Is there a compelling reason perhaps that I'm not aware of for this?</div><div class="gmail_default" style="font-family:monospace,monospace"></div><div class="gmail_default" style="font-family:monospace,monospace">Oh... maybe you are thinking specifically for the boot from volume case here? </div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">I guess if that's the case I could see why you may desire to keep the instance ID etc after a restore. Although I wish we could all just agree that things in Clouds are dynamic and things like their ID can change and just deal with it. For point in time recovery type things I still think snapshots are great, for full DR, backups are preferred and with full DR scenarios I don't think it's unreasonable to require a little extra effort.</div><br></div></div>