I think this needs a spec (possibly a spec lite if you can easily address the questions below in a spec-lite). Here's some info if you haven't written a glance spec before: https://docs.openstack.org/glance/latest/contributor/blueprints.html
You can ask in #openstack-glance or put an item on the agenda for the weekly glance meeting if you have any questions or need some help. These questions are in no particular order: - is this an operator action, or intended for end users? - do you have any info about how widely used this feature would be? One reason not to use it is that pulling an image from an external source is going to increase instance boot times by a significant factor. glance- cache doesn't help because it distinguishes images by image_id, not location, so if 18 different users have their own images each with location 'http://my.image.server/image21', glance is going to think these are 18 different images, and download each one from my.image.server. - if allowed to end users, you'll probably want to restrict what URLs are allowed. There are white/blacklists implemented for the 'web- download' method. Would it make sense to use those same lists for this method, or should there be a separate set of lists? Or would this operation only be used with an http server internal to the cloud? That's all I can think of at the moment. Erno has set the spec freeze late for Rocky, so that it will happen after the Vancouver summit. So it would be a good idea to have the spec ready before the summit so that it could be discussed with other operators there. ** Changed in: glance Importance: Undecided => Wishlist ** Changed in: glance Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1756465 Title: Need glance v2 way to register image by location Status in Glance: Opinion Bug description: The release notes for Queens state "With the introduction of the web- download import method, we consider the Image Service v2 API to have reached feature parity with the DEPRECATED v1 API in all important respects.", but v2 does NOT provide any way to register an image by location. Before v1 gets removed, there needs to be something similar to web- download, but referencing the remote URL, rather than copying from it - web-location?. This may be considered insecure on the internet, but for a private cloud on a protected intranet, it's acceptable, and more efficient when multiple glance instances need to make use of images that are already published on an internal HTTP server. See also bug 1750892, which could enable a workaround, but it's cumbersome, and requires the location to be exposed, which could present other security issues (even on an intranet). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1756465/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
