yahoo-eng-team team mailing list archive

[Mark Washenberger <1135537@xxxxxxxxxxxxxxxxxx>]

After giving this some thought, I don't think we should fix this bug by
simply porting the cache management to v2.

Cache management is an inherently local action, and doesn't make sense
living alongside the v2 api which reports status for coarser entities
like regional store or the glance db.

Rather than fixing this bug, I think we should put together a blueprint
for exposing cache management outside of the main glance api.

** Changed in: glance
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1135537

Title:
  cache management API is hardcoded under /v1

Status in OpenStack Image Registry and Delivery Service (Glance):
  Won't Fix

Bug description:
  The cachemanagement API is hardcoded to use v1:

  https://github.com/openstack/glance/blob/master/glance/api/middleware/cache_manage.py#L36

  whereas if the v2 API is enabled, but not v1, this is problematic as
  clients would want to use v2 across the board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1135537/+subscriptions