Bug 1779338 - [RFE] Configure director deployed glance with ability to copy existing images across multiple stores
Summary: [RFE] Configure director deployed glance with ability to copy existing images...
Keywords:
Status: CLOSED DUPLICATE of bug 1598716
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-glance
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Alan Bishop
QA Contact: Mike Abrams
Chuck Copello
URL:
Whiteboard:
Depends On: 1758416
Blocks: 1802772
TreeView+ depends on / blocked
 
Reported: 2019-12-03 19:11 UTC by John Fulton
Modified: 2020-03-04 21:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-04 21:58:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.