>n Wed, 18 May 2016 14:30:00 -0500, Matt Riedemann wrote:
>>> While convenient as a workaround, I'm not in favor of the idea of adding
>>> something to the REST API so a user can force refresh the connection
>>> info - this is a bug and leaks information out of the API about how the
>>> cloud is co
On 5/18/2016 3:05 PM, melanie witt wrote:
On Wed, 18 May 2016 14:30:00 -0500, Matt Riedemann wrote:
While convenient as a workaround, I'm not in favor of the idea of adding
something to the REST API so a user can force refresh the connection
info - this is a bug and leaks information out of the
On Wed, 18 May 2016 14:30:00 -0500, Matt Riedemann wrote:
While convenient as a workaround, I'm not in favor of the idea of adding
something to the REST API so a user can force refresh the connection
info - this is a bug and leaks information out of the API about how the
cloud is configured. If y
On 5/16/2016 8:39 PM, zhou.b...@zte.com.cn wrote:
Hi all：
I got a problem described in
https://bugs.launchpad.net/cinder/+bug/1452641,
and my colleague got another similar problem described in
https://bugs.launchpad.net/nova/+bug/1581367.
It's all about the storage backend ip change. With
Hi all：
I got a problem described in
https://bugs.launchpad.net/cinder/+bug/1452641,
and my colleague got another similar problem described in
https://bugs.launchpad.net/nova/+bug/1581367.
It's all about the storage backend ip change. With the storage backend,
not only Ceph but also IPSA
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
