Open Stack

On 10/07/2014 02:52 PM, Jonathan Proulx wrote:
> Hi All,
>
> I'm installing a new storage backend to my cinder environment and
> would *really* like to move my existing volumes to it.
>
> I did this once before moving from LVM on a storage nod to a SAN based
> solution with the cinder volume service running on the controller
> node.  for that case:
>
> cinder migrate <uuid> <new-node>
>
> worked just fine. The migration I want to do involves two backends on
> the same cinder-volume server.  Looking in the database I tried:
>
> cinder migrate <uuid> <same-node>@<new-backend>
>
> which did put the volume in to "migration_status=starting" with no
> error, but 3hr later doesn't seem to have done anything else.
>
> Is this supposed to work or am I just being crazy?
>
> volume server is Icehouse on Ubuntu14.04 the source backend is eqlx
> the destination is rbd.

Volume migration does not work for rbd in Icehouse. It should land in
Kilo:

https://blueprints.launchpad.net/cinder/+spec/generic-volume-migration

Josh