Bug 929108 - [RFE] Put glance cache under a different prefix and port
Summary: [RFE] Put glance cache under a different prefix and port
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-glance
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Attila Fazekas
URL: https://blueprints.launchpad.net/glan...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks: 1062017
TreeView+ depends on / blocked
 
Reported: 2013-03-29 09:26 UTC by Flavio Percoco
Modified: 2016-04-26 15:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1062017 (view as bug list)
Environment:
Last Closed: 2015-06-30 19:47:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1135537 0 None None None Never

Description Flavio Percoco 2013-03-29 09:26:36 UTC
Description of problem:

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.

Steps to Reproduce:
1. Install Glance
2. Disable v1 in *-paste.ini files
3. Call any url related to the cache middleware.
  
Actual results:

$ curl -H "X-Auth-Token: $tok" http://10.130.50.34:9292/v1/cached_images | python -m json.tool
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 119 100 119 0 0 25142 0 --:--:-- --:--:-- --:--:-- 29750
{
    "versions": [
        {
            "id": "v2.0",
            "links": [
                {
                    "href": "http://10.130.50.34:9292/v2/",
                    "rel": "self"
                }
            ],
            "status": "CURRENT"
        }
    ]
}


Expected results:

It should return the list of cached_images (if cache is enabled)

Comment 3 Ayal Baron 2013-07-14 07:06:17 UTC
John, why isn't this a duplicate of multi-locations?

Comment 4 John Bresnahan 2013-07-15 19:50:54 UTC
(In reply to Ayal Baron from comment #3)
> John, why isn't this a duplicate of multi-locations?

Ayal,

That is an interesting question and one that I have pushed on upstream.  Idealling a cached location would be 'just another location' in the list of locations.  However the way that glance was architected leaves this quite futuristic.  In the short term the cache will have to continue sit on top.

Comment 11 Flavio Percoco 2015-06-30 19:47:49 UTC
There are many changes happening in Glance's API versioning and that includes glance-cache. I'm going to close this as UPSTREAM and recommend tracking it there.


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