Hi,
I don't quite understand the issue yet, maybe you can clarify.
If I perform a "change volume type" from OpenStack on volumes
attached to the VMs the system successfully migrates the volume from
the source pool to the destination pool and at the end of the
process the volume is visible in the new pool and is removed from
the old pool.
Are these volumes root disks or just additional volumes? But
apparently, the retype works.
The problem encountered is that when reconfiguring the VM, to
specify the new pool associated with the volumes (performed through
a resize of the VM, I haven't found any other method to change the
information on the nova/cinder db automatically.
If the retype already works then what is your goal by "reconfiguring
the VM"? What information is wrong in the DB? This part needs some
clarification for me. Can you give some examples?
The VM after the retype continues to work perfectly in RW but the
"new" volume created in the new pool is not used to write data and
consequently when the VM is shut down all the changes are lost.
Just wondering, did you shut down the VM before retyping the volume?
I'll try to reproduce this in a test cluster.
Regards,
Eugen
Zitat von andrea.martra@xxxxxxxx:
Hello,
I configured different back-end storage on OpenStack (Yoga release)
and using Ceph (ceph version 17.2.4) with different pools (volumes,
cloud-basic, shared-hosting-os, shared-hosting-homes,...) for RBD
application.
I created different volume types towards each of the backends and
everything works perfectly.
If I perform a "change volume type" from OpenStack on volumes
attached to the VMs the system successfully migrates the volume from
the source pool to the destination pool and at the end of the
process the volume is visible in the new pool and is removed from
the old pool.
The problem encountered is that when reconfiguring the VM, to
specify the new pool associated with the volumes (performed through
a resize of the VM, I haven't found any other method to change the
information on the nova/cinder db automatically. I also did some
tests shut-off of the VM and modification of the xml through virsh
edit and startup the VM) the volume presented to the VM is exactly
the version and content on the retype date of the volume itself. All
data written and modified after the retype is lost.
The VM after the retype continues to work perfectly in RW but the
"new" volume created in the new pool is not used to write data and
consequently when the VM is shut down all the changes are lost.
Do you have any idea how to carry out a check and possibly how to
proceed in order not to lose the data of the vm of which I have
retyped the volume?
The data is written somewhere because the VMs work perfectly.
Thank you
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
