Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1706910

Summary: [RFE] Add image cache operations into Glance API
Product: Red Hat OpenStack Reporter: Gregory Charot <gcharot>
Component: openstack-glanceAssignee: Abhishek Kekane <akekane>
Status: CLOSED MIGRATED QA Contact: msava
Severity: medium Docs Contact: Tana <tberry>
Priority: medium    
Version: 16.0 (Train)CC: akekane, athomas, cyril, dasmith, eglynn, gcharot, gfidente, msava, pgrist, scohen, udesale, vimartin
Target Milestone: AlphaKeywords: FutureFeature, Triaged
Target Release: 18.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-glance-26.0.1-0.20230427080209.285021b.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 00:40:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1712001    
Bug Blocks: 2077341    

Description Gregory Charot 2019-05-06 13:47:04 UTC
Description of problem:

Today the only way to manage the glance cache is to use glance-cache-manage local tool.
This raises several issues:
* No centralised way to manage cache; need to connect to each nodes.
* Requires ssh access and appropriates permissions to the glance cache node(s)

This RFE aims to include basic image cache management into the Glance API.

At a minimum:
* List glance cache nodes
* List cached images on a specific node
* Queue an image for caching on a specific node
* List queued images on a specific node
* Delete an image from the cache queue
* Purge an image from a specific node

Optionally:
* Purge all images from a specific node

Goal is to have feature parity with glance-cache-manage.

Targeted use cases: DCN with or without persistent storage at the edge.

Version-Release number of selected component (if applicable):

16

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 13 Abhishek Kekane 2019-08-29 07:01:31 UTC
*** Bug 1746705 has been marked as a duplicate of this bug. ***