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

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

[Openstack-operators] Themed track in 2018 1st OpsMeetup

Hi operators, As discussed in the ops meetup team meeting [1], I like to ask the ML whether having a themed track in OpsMeetup (in APAC early 2018) would be a good idea to attract specific audiences (especially local audiences) to come to the meetup. The idea of themed track is to have a

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] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

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

Re: [Openstack-operators] Neutron not clearing up deleted routers

Ignore that now all, Managed to fix it by restarting the l3-agent. Looks like it must have been cached in memory. Thanks, On 08/06/17 18:07, Grant Morley wrote: Hi All, We have noticed in our neutron-l3-agent logs that there are a number of routers that neutron seems to think exist (

[Openstack-operators] Neutron not clearing up deleted routers

Hi All, We have noticed in our neutron-l3-agent logs that there are a number of routers that neutron seems to think exist ( but they no longer exist in the data base ) and it is constantly trying to delete them. However because they don't appear to exist, so neutron seems to get stuck in a

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

Re: [Openstack-operators] Problems with ec2-service on Ocata

Looks like setting: enable_proxy_headers_parsing=true in nova,conf helped. Actually it still doesn't work, but for other reasons (Expecting to find domain in project. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in

Re: [Openstack-operators] [openstack-dev] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

Ok - based on the responses in the thread here, I've re-proposed the global roles specification to keystone's backlog [0]. I'll start working on the implementation and get something in review as soon as possible. I'll plan to move the specification from backlog to Queens once development opens.

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

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

[Openstack-operators] [publiccloud-wg] Summary meeting 7th June

Hi folks, Here comes a summary from yesterdays meeting for the Public Cloud Working Group. The missing features document now got status and priority columns. Definitions for each column will be added during the week as well, but pretty self-explaining. We really encourage you all to add