I think you are referrign to backend-assisted migration, I am referring to the generic one (with the support put forth by Avishay of IBM)

The generic flow of migration shoudl work as far as backend provides support for
1) create volume
2) attach/detach volume

It may not be ideal, but should work using the 'dd' to do the copy of the data between src and dest volume. I am currently looking at this generic migrate only

On 03/11/2014 02:50 PM, Swapnil Kulkarni wrote:
Hi Deepak,

When you say you are using glusterfs as backend, you are using glusterfs
driver, is it correct?

Best Regards,
Swapnil Kulkarni
irc : coolsvap


On Tue, Mar 11, 2014 at 2:17 PM, Deepak C Shetty <deepa...@redhat.com
<mailto:deepa...@redhat.com>> wrote:

    Swapnil,
         The failure is not in the glsuter specific part of code
    IIUC its in the rpc/dispatcher area.. so shouldn't be gluster specific


    On 03/11/2014 01:06 PM, Swapnil Kulkarni wrote:

        Hi Deepak,

        I believe the migrate_volume is not implemented in glusterfs which
        causes above error. I have seen similar errors earlier. Currently
        implementing the migrate volume and testing it. I will push it
        upstream
        once successfully tested.

        Best Regards,
        Swapnil Kulkarni
        irc : coolsvap
        swapnilkulkarni2...@gmail.com
        <mailto:swapnilkulkarni2...@gmail.com>
        <mailto:swapnilkulkarni2608@__gmail.com
        <mailto:swapnilkulkarni2...@gmail.com>>
        +91-87960 10622(c)
        http://in.linkedin.com/in/__coolsvap
        <http://in.linkedin.com/in/coolsvap>
        *"It's better to SHARE"*



        On Tue, Mar 11, 2014 at 12:53 PM, Deepak C Shetty
        <deepa...@redhat.com <mailto:deepa...@redhat.com>
        <mailto:deepa...@redhat.com <mailto:deepa...@redhat.com>>> wrote:

             Hi All,
                      I am using devstack with cinder git head @
             f888e412b0d0fdb0426045a9c55e0b____e0390f842c


             I am seeing the below error while trying to do cinder
        migrate for
             glusterfs backend. I don't think its backend specific tho'
        as the
             failure is in the common rpc layer of code.

        http://paste.fedoraproject.____org/84189/45169021/

             <http://paste.fedoraproject.__org/84189/45169021/
        <http://paste.fedoraproject.org/84189/45169021/>>

             Any pointers to get past this is appreciated.

             thanx,
             deepak

             ___________________________________________________
             OpenStack-dev mailing list
             OpenStack-dev@lists.openstack.____org
             <mailto:OpenStack-dev@lists.__openstack.org
        <mailto:OpenStack-dev@lists.openstack.org>>
        
http://lists.openstack.org/____cgi-bin/mailman/listinfo/____openstack-dev
        <http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev>
        <http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>>





        _________________________________________________
        OpenStack-dev mailing list
        OpenStack-dev@lists.openstack.__org
        <mailto:OpenStack-dev@lists.openstack.org>
        http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev
        <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>


    _________________________________________________
    OpenStack-dev mailing list
    OpenStack-dev@lists.openstack.__org
    <mailto:OpenStack-dev@lists.openstack.org>
    http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev 
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>




_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to