Hi Massimo,
Thanks for providing more information. As you can see from David's blog
and the script (https://github.com/dmsimard/migrate-glance-backend). The
most tricky part is how to keep current image id, otherwise, all the
existing instances will fail to rebuild. The way I'm suggesting can
First of all thanks for your help
This is a private cloud which is right now using gluster as backend.
Most of the images are private (i.e. usable only within the project),
uploaded by the end-users.
Most of these images were saved in qcow2 format ...
The ceph cluster is still being
Hi Massimo,
Though I don't have experience on the migration, but as the glance RBD
driver maintainer and image service maintainer of our public cloud
(Catalyst Cloud based in NZ), I'm happy to provide some information.
Before I talk more, would you mind sharing some information of your
Oh, hey, that's my blog.
Happy to answer questions as much as my memory allows.. I haven't revisited
this particular topic, it was a one-time thing for me.
I would certainly hope for there to be a better way by now, almost two
years later!
Curious to see if other operators have any insight to
Hi
In our Mitaka cloud we are currently using Gluster as storage backend for
Glance and Cinder.
We are now starting the migration to ceph: the idea is then to dismiss
gluster when we have done.
I have a question concerning Glance.
I have understood (or at least I hope so) how to add ceph as
