<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 2, 2015 at 4:42 PM, Valeriy Ponomaryov <span dir="ltr"><<a href="mailto:vponomaryov@mirantis.com" target="_blank">vponomaryov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Deepak,<div><br></div><div>"transfer-*" is not suitable in this particular case. Usage of share networks causes creation of resources, when "transfer" does not. Also in this topic we have "creation" of new share based on some snapshot.</div></div></blockquote><div><br></div><div>In the original mail it was said:<br>"<br><div>From user point of view, he may want to copy share and use its copy in different network and it is valid case. </div><div>"<br></div><div>So create share from snapshot, then transfer that share to a different tenant , doesn't that work ?<br><br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span class=""><font color="#888888"><div><br></div><div>Valeriy</div></font></span><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 31, 2015 at 4:23 PM, Deepak Shetty <span dir="ltr"><<a href="mailto:dpkshetty@gmail.com" target="_blank">dpkshetty@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Thu, May 28, 2015 at 4:54 PM, Duncan Thomas <span dir="ltr"><<a href="mailto:duncan.thomas@gmail.com" target="_blank">duncan.thomas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span>On 28 May 2015 at 13:03, Deepak Shetty <span dir="ltr"><<a href="mailto:dpkshetty@gmail.com" target="_blank">dpkshetty@gmail.com</a>></span> wrote:<br></span><div class="gmail_extra"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Isn't this similar to what cinder transfer-* cmds are for ? Ability to transfer cinder volume across tenants<br></div>So Manila should be implementing the transfer-* cmds, after which admin/user can create a clone<br></div>then initiate a transfer to a diff tenant  ?<br></div><div class="gmail_extra"><br clear="all"></div></blockquote><div><br></div></span><div>Cinder doesn't seem to have any concept analogous to a share network from what I can see; the cinder transfer commands are for moving a volume between tenants, which is a different thing, I think. <br></div></div></div></div></blockquote><div><br></div></div></div><div>Yes, cinder doesn't have any eq of share network. But my comment was from the functionality perpsective. In cinder transfer-* commands are used to transfer ownership of volumes across tenants. IIUC the ability in Manila to create a share from snapshot and have that share in a different share network is eq to creating a share from a snapshot for a different tenant, no ? Share networks are typically 1-1 with tenant network AFAIK, correct me if i am wrong </div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div></div><span><font color="#888888"><br><span><font color="#888888">-- <br><div>Duncan Thomas</div>
</font></span></font></span></div></div><span>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></span></blockquote></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" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote></div>
</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" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>