Isn't this similar to what cinder transfer-* cmds are for ? Ability to transfer cinder volume across tenants So Manila should be implementing the transfer-* cmds, after which admin/user can create a clone then initiate a transfer to a diff tenant ? On Wed, May 27, 2015 at 6:08 PM, Valeriy Ponomaryov < vponomaryov at mirantis.com> wrote: > Hi everyone, > > At last IRC meeting > <http://eavesdrop.openstack.org/meetings/manila/2015/manila.2015-05-14-15.00.log.html> was > raised following question: > > "Whether Manila should allow us to create shares from snapshots with > different share networks or not?" > > What do users/admins expect in that case? > > For the moment Manila restricts creation of shares from snapshot with > share network that is different than parent's. > > From user point of view, he may want to copy share and use its copy in > different network and it is valid case. > > From developer point of view, he will be forced to rework logic of share > servers creation for driver he maintains. > > Also, how many back-ends are able to support such feature? > > Regards, > Valeriy Ponomaryov > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150528/a7964868/attachment.html>