Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 920982

Summary: [RFE] Glance Registry service deprecation
Product: Red Hat OpenStack Reporter: Flavio Percoco <fpercoco>
Component: openstack-glanceAssignee: Flavio Percoco <fpercoco>
Status: CLOSED ERRATA QA Contact: Giulio Fidente <gfidente>
Severity: unspecified Docs Contact:
Priority: high    
Version: 4.0CC: abaron, dron, eglynn, fpercoco, gfidente, hateya, mlopes, sclewis
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/glance/+spec/registry-db-driver
Whiteboard:
Fixed In Version: openstack-glance-2013.2-0.6.b2.el6ost Doc Type: Enhancement
Doc Text:
The glance-registry service is now optional for Image Service API v2 deployment. Excluding the glance-registry service reduces the latency of Image Service database activity, and reduces code duplication throughout Image Service. The Image Service registry can still be deployed for legacy support; or as a secure method for accessing the database, rather than the public glance-api service.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-19 23:59:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 988543    
Bug Blocks: 975499    

Description Flavio Percoco 2013-03-13 08:55:08 UTC
Keeping track of the work being done here:

https://blueprints.launchpad.net/glance/+spec/registry-db-driver

Comment 9 Scott Lewis 2013-08-01 17:08:39 UTC
Changed Priority to match upstream

Comment 15 Giulio Fidente 2013-12-12 17:15:31 UTC
verified using: openstack-glance-2013.2-4.el6ost.noarch

Comment 17 errata-xmlrpc 2013-12-19 23:59:44 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html