[openstack-dev] [nova] upgrade connection_info when Ceph mon IP changed

zhou.bin9 at zte.com.cn zhou.bin9 at zte.com.cn
Fri Apr 1 05:57:32 UTC 2016

Hi all:
    about https://bugs.launchpad.net/cinder/+bug/1452641 I submitted my 
solution https://review.openstack.org/#/c/289813/. 

VM startup or reboot failed when volume backend of ceph mon ip address 
changed. And this bug also happens when vm deployed with

volume backend of IPSAN, when IPSAN's iscsi ip address changed. In our 
product use, when we transfered our equipment to others' 

lab, the IP adress would changed all, including the volume backends' ip, 
and the pre-deployed instances would failed to start at all,

which troubled us to much. I proposed to check and refresh the ip address 
which recored in instance's block_device_mapping table,

Matt Riedemann pointed out that it's not a good idea to perform these 
checks each time to call call startup or reboot APIs, and give

good advice to fix this in nova-manage when this bug did happen.

    My question is: is it reasonable to call nova database, libvirt 
driver, rbd driver, cinder's api and so on in nova-manage to perferm

the check and refresh connection info in BDM and fix the bug, when volume 
backends' ip changed. Or any other reasonable solutions?

    Thank you.

    Best regards!

R&D Building, ZTE Plaza, #6 Huashen Ave. 
Yuhuatai District, Nanjing, P.R.China, 210012
T: +86 02552878587    M: +86 15062283989
E: zhou.bin9 at zte.com.cn
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160401/d850f799/attachment.html>

More information about the OpenStack-dev mailing list