Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

On 2/14/2017 8:48 AM, Matt Riedemann wrote: OK so the NFS job would tickle it, but that might not be in the experimental queue for devstack (but it is in nova's experimental queue so we could hack this up to test it). I thought we were testing volume retype/migration now though? That calls

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

On 2/14/2017 7:48 AM, Duncan Thomas wrote: This is only used by the file based drivers, who need to call nova for assistance with attached snapshots. Most drivers won't use it, including the default, LVM. I can't comment on the test coverage, sorry. On 14 February 2017 at 13:01, Sean Dague

Re: [openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

This is only used by the file based drivers, who need to call nova for assistance with attached snapshots. Most drivers won't use it, including the default, LVM. I can't comment on the test coverage, sorry. On 14 February 2017 at 13:01, Sean Dague wrote: > After some of the

[openstack-dev] [cinder] [nova] confusion on where nova_catalog_admin_info is used in cinder

After some of the confusion around endpoints in devstack, we decided to simplify the endpoints registered in devstack to only the ones needed for development. Basically only register "public" interfaces unless there is something special about the service. https://review.openstack.org/#/c/433272/