The glance-cache-manage binary can be operated by anyone with valid keystone credentials.
Using a vanilla devstack setup, here are the credentials I get:
OS_PASSWORD=secrete
OS_AUTH_URL=http://192.168.27.100:5000/v2.0
OS_USERNAME=demo
OS_TENANT_NAME=demo
With these creds, it appears I have full access to the cache management middleware through glance-cache-manage:
vagrant@devstack:~/devstack$ glance-cache-manage list-cached
Found 1 cached images...
ID Last Accessed (UTC) Last Modified (UTC) Size Hits
------------------------------------ ------------------- ------------------- -------------- ----------
38895dc9-1a15-4b4f-84e8-7312d963c5a2 0.0 1331683101.88 2254249 0
vagrant@devstack:~/devstack$ glance-cache-manage delete-cached-image 38895dc9-1a15-4b4f-84e8-7312d963c5a2
Delete cached image 38895dc9-1a15-4b4f-84e8-7312d963c5a2? [y/N] y
vagrant@devstack:~/devstack$ glance-cache-manage list-cached
No cached images.
This interface is designed to be used from remote hosts as well, so this creates a bit of a security issue. We should lock it down to just admins.
Just so I understand the impact correctly: is the cache management middleware active by default (or set active in default config files) ? What versions of Glance are exposed to this ?
I targeted to rc1 -- but it will only show in the subscribed people's list until we make it public.
Anyone working on a fix ? Please do not push to public review until we decide this should not be embargoed and coordinated between downstream stakeholders.