Bug 1779338

Summary:	[RFE] Configure director deployed glance with ability to copy existing images across multiple stores
Product:	Red Hat OpenStack	Reporter:	John Fulton <johfulto>
Component:	puppet-glance	Assignee:	Alan Bishop <abishop>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Abrams <mabrams>
Severity:	high	Docs Contact:	Chuck Copello <ccopello>
Priority:	high
Version:	16.0 (Train)	CC:	abishop, gfidente, jjoyce, jschluet, jvisser, pgrist, slinaber, tvignaud
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-04 21:58:37 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:	1758416
Bug Blocks:	1802772

Description John Fulton 2019-12-03 19:11:25 UTC

As per bz1758416 Glance is going to get the ability to copy existing images across multiple stores. This bz tracks the TripleO changes required so that our customers can deploy Glance with this feature configured. This is also related to bz 1758420.

Comment 2 Giulio Fidente 2019-12-09 18:42:12 UTC

the import plugin list should already be configurable in tripleo using [1]

1. https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/glance/glance-api-container-puppet.yaml#L137

Comment 3 John Fulton 2019-12-09 18:45:12 UTC

(In reply to Giulio Fidente from comment #2)
> the import plugin list should already be configurable in tripleo using [1]
> 
> 1.
> https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/
> glance/glance-api-container-puppet.yaml#L137

However, this bug still needs to track support for changes to entry_points.txt, other config related issues we discover as the new feature is implemented, and the testing of of multistore import.

Comment 6 Alan Bishop 2020-03-04 21:07:34 UTC

(In reply to John Fulton from comment #3)
> (In reply to Giulio Fidente from comment #2)
> > the import plugin list should already be configurable in tripleo using [1]
> > 
> > 1.
> > https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/
> > glance/glance-api-container-puppet.yaml#L137
> 
> However, this bug still needs to track support for changes to
> entry_points.txt, other config related issues we discover as the new feature
> is implemented, and the testing of of multistore import.

TripleO isn't involved in setting glance's entry points. Glance itself will take care of this via [2].

[2] https://opendev.org/openstack/glance/src/branch/master/setup.cfg#L88

I confirm Giulio's point that TripleO already provides a means for setting the list of enabled import methods. Unless we've missed something, I think the director is all set to handle this feature.

Leaving this BZ ON_DEV seems misleading, especially if it's tracked as a blocker. One idea might be closing it WORKSFORME, and reopening it if we identify additional work.

Comment 7 John Fulton 2020-03-04 21:44:42 UTC

(In reply to Alan Bishop from comment #6)
> (In reply to John Fulton from comment #3)
> > (In reply to Giulio Fidente from comment #2)
> > > the import plugin list should already be configurable in tripleo using [1]
> > > 
> > > 1.
> > > https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/
> > > glance/glance-api-container-puppet.yaml#L137
> > 
> > However, this bug still needs to track support for changes to
> > entry_points.txt, other config related issues we discover as the new feature
> > is implemented, and the testing of of multistore import.
> 
> TripleO isn't involved in setting glance's entry points. Glance itself will
> take care of this via [2].
> 
> [2] https://opendev.org/openstack/glance/src/branch/master/setup.cfg#L88
> 
> I confirm Giulio's point that TripleO already provides a means for setting
> the list of enabled import methods. Unless we've missed something, I think
> the director is all set to handle this feature.
> 
> Leaving this BZ ON_DEV seems misleading, especially if it's tracked as a
> blocker. One idea might be closing it WORKSFORME, and reopening it if we
> identify additional work.

Any objection to closing this bug as a duplicate of 1598716 ?

Comment 8 John Fulton 2020-03-04 21:58:37 UTC


*** This bug has been marked as a duplicate of bug 1598716 ***