Hi Jim! I think that the plan is good. I think Cinder should not delete anything unless told to do so. You have to create the CPG space manually before Cinder can start using it, so it does no initialization. Do you have opportunity to test it, on some other CPG perhaps? We have the same setup with 3PAR here. With one miniature cluster for testing. If you don’t have the opportinity, I could, e.g. drop the Cinder database there and try importing a few volumes back.
Tomas From: Jimmy Colestock [mailto:jcolest...@gmail.com] Sent: Friday, February 03, 2017 4:54 PM To: Openstack Subject: [Openstack] Migrating cinder volumes to a new cluster Hello All, I want to migrate about 100 instances to a new cluster that are all backed by cinder volumes on an HP 3Par. My plan is: 1. Create the new cluster. 2. Connect cinder to the existing 3Par cpg 3. Manually update the cinder volume info in new cluster. 4. Terminate the instance in the old cluster 5. Launch an instance in the new cluster, attaching to the previously used volume. Anyone tried anything like this before? My biggest concern is attaching to the same CPG and to make sure cinder doesn’t re-iniialize the space or otherwise delete any of the existing volumes. Thanks in advance for any thoughts.. JC Jim Colestock jcolest...@gmail.com https://www.linkedin.com/in/jcolestock/
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
