Bug 1164520

Summary:	[RFE][glance]: Create and use configuration file for glance-manage
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-glance	Assignee:	Flavio Percoco <fpercoco>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	adahms, ddomingo, eglynn, fpercoco, markmc, scohen, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/glance/+spec/create-glance-manage-conf
Whiteboard:	upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-glance-2015.1.0-6.el7ost	Doc Type:	Enhancement
Doc Text:	Previously, the glance-manage utility was configured using 'glance-api.conf' or 'glance-registry.conf'. This release features a new configuration file named 'glance-manage.conf', which can be used to configure glance-manage. You can still use 'glance-api.conf' and 'glance-registry.conf' to configure glance-manage, but any 'glance-manage.conf' settings will take precedence.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:16:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-11-16 05:05:08 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/create-glance-manage-conf.

Description:

Currently glance-manage uses glance-registry and glance-api's configuration files for different values and ends up attempting to log to glance-api's log file. This can lead to permissions errors when trying to use glance-manage as a separate user on the system. It would be better if glance-manage had its own configuration file so that it could be configured without also affecting glance-registry and glance-api.

Specification URL (additional information):

None

Comment 9 errata-xmlrpc 2015-08-05 13:16:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548