Bug 1208799

Summary:	Split glance-api and glance-registry
Product:	Red Hat OpenStack	Reporter:	Flavio Percoco <fpercoco>
Component:	openstack-glance	Assignee:	hguemar
Status:	CLOSED UPSTREAM	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	dprince, eglynn, fpercoco, hguemar, nlevinki, scohen, yeylon
Target Milestone:	---
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1208798	Environment:
Last Closed:	2015-07-02 13:26:33 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:	1208798
Bug Blocks:

Description Flavio Percoco 2015-04-03 08:41:49 UTC

+++ This bug was initially created as a clone of Bug #1208798 +++

The current openstack-glance package ships both, glance-api and glance-registry. In order to better support distributed deployments, this package should be split in 2 packages, one for each service.

Please, refer to this thread for the upstream discussion. 

https://www.redhat.com/archives/rdo-list/2015-March/msg00146.html

Comment 3 hguemar 2015-04-03 13:39:05 UTC

agreed, needs to be fixed in delorean first (we haven't branched RDO yet)

Comment 4 Dan Prince 2015-04-17 13:04:01 UTC

Making this packaging change (in Delorean) can break end users quite badly.

Is there any benefit to it other than the fact that it would prevent an extra systemd script for one of the Glance servers getting installed (but not used). In other words would installing glance-registry or glance-api in isolation result in less dependencies getting installed if we do this split?

If not then I'm not sure this is worth it... and even then maybe it isn't worth breaking end users to save a dependency or two.