[Openstack-operators] Move Persistent Ceph Volumes between Openstack Instances

Logan V. logan at protiumit.com
Fri Aug 7 18:48:08 UTC 2015


I recently needed to do this for a very limited number of volumes, so
I used this manual process:

-deattach the old volume from instance
-prep a volume in the new instance of the same size
- rbd mv pool/volume-$NEW_UUID pool/volume-$NEW_UUID-delete
- rbd mv pool/volume-$OLD_UUID pool/volume-$NEW_UUID
-safe to attach the volume in the new instance now to verify data if
necessary before deleting anything
- rbd rm pool/volume-$NEW_UUID-delete (this will clean up the empty
rbd that was created when you prepped the volume in the kilo env)

On Fri, Aug 7, 2015 at 12:48 PM, Brendan Johnson <bjohnson at paragusit.com> wrote:
> I am currently running a Juno based cloud and I am planning a migration to Kilo.   For a variety of reasons I am planning on setting up a parallel instance of Openstack using Kilo rather than directly upgrading the Juno instance.   Both instances will be sharing the same Ceph storage cluster for block storage.    I have some persistent Cinder volumes that I would like to migrate between instances and I was wondering what the best way to do this would be.
>
> The most straight forward way would be to create images from the volumes and then exports them from the Juno Glance and import them into the Kilo Glance and then create a volume based on the image.   The problem with this is that I am downloading the images and then uploading the images to the exact same Ceph storage pool just so the new Kilo instance of Openstack can create the appropriate database records.    It seems rather inefficient.
>
> Since I just need to make Glance and/or Cinder aware of the existing images in the Ceph storage cluster I was looking into trying to export records from the Juno MariaDB database relating to the images or volumes from either Cinder or Glance and then importing them into the Kilo MariaDB database.
>
> Does anyone have experience with doing this sort of selective export and import of database records between different Openstack instances?
>
> Is anyone aware of a better option beside the two I described above?
>
> Thanks,
>
> Brendan
>
> Brendan Johnson
> Director of Engineering and Product Research
> Paragus Strategic IT
> bjohnson at paragusit.com
>
>
>
>
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



More information about the OpenStack-operators mailing list