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

2017-09-14 Thread Matt Riedemann
On 9/13/2017 10:31 AM, Morgenstern, Chad wrote: I have been studying how to perform failover operations with Cinder --failover. Nova is not aware of the failover event. Being able to refresh the connection state especially for Nova would come in very handy, especially in admin level dr scenar

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

2017-09-14 Thread Matt Riedemann
On 9/13/2017 9:52 AM, Arne Wiebalck wrote: On 13 Sep 2017, at 16:52, Matt Riedemann wrote: On 9/13/2017 3:24 AM, Arne Wiebalck wrote: I’m reviving this thread to check if the suggestion to address potentially stale connection data by an admin command (or a scheduled task) made it to the pla

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

2017-09-13 Thread Morgenstern, Chad
List Subject: Re: [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info? > On 13 Sep 2017, at 16:52, Matt Riedemann wrote: > > On 9/13/2017 3:24 AM, Arne Wiebalck wrote: >> I’m reviving this thread to check if the suggestion to add

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

2017-09-13 Thread Arne Wiebalck
> On 13 Sep 2017, at 16:52, Matt Riedemann wrote: > > On 9/13/2017 3:24 AM, Arne Wiebalck wrote: >> I’m reviving this thread to check if the suggestion to address potentially >> stale connection >> data by an admin command (or a scheduled task) made it to the planning for >> one of the >> upco

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

2017-09-13 Thread Matt Riedemann
On 9/13/2017 3:24 AM, Arne Wiebalck wrote: I’m reviving this thread to check if the suggestion to address potentially stale connection data by an admin command (or a scheduled task) made it to the planning for one of the upcoming releases? It hasn't, but we're at the PTG this week so I can th

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

2017-09-13 Thread Arne Wiebalck
Matt, all, I’m reviving this thread to check if the suggestion to address potentially stale connection data by an admin command (or a scheduled task) made it to the planning for one of the upcoming releases? Thanks! Arne On 16 Jun 2017, at 09:37, Saverio Proto mailto:ziopr...@gmail.com>> wr

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

2017-06-16 Thread Saverio Proto
Hello Matt, It is true that we are refreshing something that rarely changes. But if you deliver a cloud service for several years, at one point you might have to do these parameters changes. Something that should not change rarely are the secrets of the ceph users to talk to the ceph cluster. Goo

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

2017-06-08 Thread Matt Riedemann
On 6/8/2017 1:39 PM, melanie witt wrote: On Thu, 8 Jun 2017 08:58:20 -0500, 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 o

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

2017-06-08 Thread melanie witt
On Thu, 8 Jun 2017 08:58:20 -0500, 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 or need to be refreshed, like if your ceph

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

2017-06-08 Thread Matt Riedemann
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 or need to be refreshed, like if your ceph server IP changes, or you need to recycle some secret uui