I suspect that this is because we use glance-registry and glance-api's config files (https://github.com/openstack/glance/blob/453706b4b3a3d6d9c3b154a1fde59c34fc30234b/glance/cmd/manage.py#L267..L270) to configure glance-manage even though there's apparently the ability to have a glace-manage.conf file (https://github.com/openstack/glance/blob/453706b4b3a3d6d9c3b154a1fde59c34fc30234b/etc/oslo-config-generator/glance-manage.conf). Even if a glance-manage.conf file existed, it wouldn't be used at this point. I'm going to look to see how other services manage to have separate logs for this without having their own -manage.conf files.
I suspect that this is because we use glance-registry and glance-api's config files (https:/ /github. com/openstack/ glance/ blob/453706b4b3 a3d6d9c3b154a1f de59c34fc30234b /glance/ cmd/manage. py#L267. .L270) to configure glance-manage even though there's apparently the ability to have a glace-manage.conf file (https:/ /github. com/openstack/ glance/ blob/453706b4b3 a3d6d9c3b154a1f de59c34fc30234b /etc/oslo- config- generator/ glance- manage. conf). Even if a glance-manage.conf file existed, it wouldn't be used at this point. I'm going to look to see how other services manage to have separate logs for this without having their own -manage.conf files.