Re: [Openstack-operators] [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

Oh, yes please! We've had to go through a lot of hoops to migrate ceph-mon's around while keeping their ip's consistent to avoid vm breakage. All the rest of the ceph ecosystem (at least that we've dealt with) works fine without the level of effort the current nova/cinder implementation

Re: [Openstack-operators] [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

> On 08 Jun 2017, at 17:52, Matt Riedemann wrote: > > On 6/8/2017 10:17 AM, Arne Wiebalck wrote: >>> On 08 Jun 2017, at 15:58, Matt Riedemann >> > wrote: >>> >>> Nova stores the output of the Cinder

Re: [Openstack-operators] [openstack-dev] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 08 Jun 2017, at 15:58, Matt Riedemann > wrote: Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making volume connections. This data can get out of whack