<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 06/18/2015 07:08 AM, Deepak Shetty wrote:<br>
<blockquote
cite="mid:CAOXiiMkDyaYm20P2GtEWOcVHb7aqJJrkDanoUiCUL=-xCcGfHw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jun 18, 2015 at 8:43 AM, Ben
Swartzlander <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ben@swartzlander.org" target="_blank">ben@swartzlander.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class=""> On
06/03/2015 12:43 PM, Deepak Shetty wrote:<br>
<blockquote type="cite">
<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
moz-do-not-send="true"
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>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<br>
</span> Transferring shares between tenants is not
something we've discussed before. The cinder project
allows transferring of volumes but its easier for them
to implement that feature because they don't have the
concepts of share networks and share servers to tie the
share to a tenant.<br>
<br>
We implemented "public shares" which allows a similar
use case where 1 tenant can allow others to read/write
to a share and should address many of the same use cases
that share transferring would address.<span
class="HOEnZb"><font color="#888888"><br>
<br>
-Ben</font></span>
<div>
<div class="h5"><br>
<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<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><font color="#888888">
<div><br>
</div>
<div>Valeriy</div>
</font></span>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun,
May 31, 2015 at 4:23 PM, Deepak
Shetty <span dir="ltr"><<a
moz-do-not-send="true"
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
moz-do-not-send="true"
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
moz-do-not-send="true" 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>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I agree that 'share transfer' (like volume transfer of
cinder) would be more complex, but shouldn't be
impossible.<br>
</div>
<div>IIUC Its eq to creating a new share for the destination
tenant (which is same as create share for that tenant) and
then copy data (or allow backend to optimize if possible)
then delete the source share <br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Yes, we can implement a share transfer, but I'm arguing that we
don't need to. Such a feature would be a lot of effort to implement
for (arguably) little gain.<br>
<br>
<blockquote
cite="mid:CAOXiiMkDyaYm20P2GtEWOcVHb7aqJJrkDanoUiCUL=-xCcGfHw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<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>
<div class="gmail_extra">
<div class="gmail_quote">
<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>
<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>
</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>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Didn't knew this.... just wondering, this means the
public share can be accessed by multiple tenants ? Doesn't
that break the tenant isolation ?<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
<br>
Yes this was the point of public shares. It doesn't break tenant
isolation any more than a feature like share transfer would. It's
optional and you have to turn it on explicitly on a per-share basis.
Also, the most common application for public shares would be in a
read-only mode, so the possibility for bad things to happen is very
small.<br>
<br>
<br>
<blockquote
cite="mid:CAOXiiMkDyaYm20P2GtEWOcVHb7aqJJrkDanoUiCUL=-xCcGfHw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>thanx,<br>
</div>
<div>deepak<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<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>
<div class="gmail_extra">
<div class="gmail_quote">
<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>
</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"><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
moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a
moz-do-not-send="true"
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
moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
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>
<br>
<fieldset></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a moz-do-not-send="true" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a moz-do-not-send="true"
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 moz-do-not-send="true"
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>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>