yahoo-eng-team team mailing list archive

[iain MacDonnell <1756465@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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).

** Affects: glance
     Importance: Undecided
         Status: New

-- 
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:
  New

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