Import plugins requires deployer to poke Glance code with internal details

[Erno Kuvaja]

To enable 3rd party import plugins deployer needs to touch glance/opts.py that is filled with internal details, thus making it risky for errors affecting the whole service. The plugin imports should be separated to their dedicated location for decoupling the details.

[Brian Rosmaita (brian-rosmaita)]

See, for example, https://review.openstack.org/#/c/527635/12/glance/opts.py@33

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/541740

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/541740
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=824badc1890206695eb335582a804d9ecabb4d67
Submitter: Zuul
Branch: master

commit 824badc1890206695eb335582a804d9ecabb4d67
Author: Erno Kuvaja <email address hidden>
Date: Wed Feb 7 14:57:06 2018 +0000

    Decouple Image Import Plugin Opts

    This change decouples Image Import Plugin Options from glance/opts.py
    so that the deployer who wishes to add 3rd party plugin does not
    need to inject the details to the file that is cluttered with all
    Glance internal details.

    Change-Id: Idc31dbb673efae224c97d2cafa4afa053e049c76
    Closes-Bug: #1747926

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/glance 16.0.0.0rc1 release candidate.