Bug 1700327 - [RFE] Improve glance cache client tooling
Summary: [RFE] Improve glance cache client tooling
Keywords:
Status: CLOSED DUPLICATE of bug 1710557
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-glance
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Cyril Roelandt
QA Contact: Mike Abrams
Tana
URL:
Whiteboard:
Depends On: 1635862
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-16 10:07 UTC by Gregory Charot
Modified: 2019-05-16 12:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-16 12:34:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gregory Charot 2019-04-16 10:07:11 UTC
Description of problem:

DCN architecture now leverages glance cache at the edge. In order to improve the user experience the glance cache client needs to be enhanced.

Today the glance cache can be managed with the glance-cache-manage commands
https://docs.openstack.org/glance/latest/cli/glancecachemanage.html

This RFE tracks the changes required to glance cache user management.


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

16

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Cyril Roelandt 2019-04-18 18:23:29 UTC
I think the main thing here is being able to list all Glance cache nodes. Once we've got that, everything else should be fairly easy. I'm not sure if there is already a way to list all the cache nodes in Glance, though.

Some of the operations listed in the Google docs seem to be already available. For instance, can't "List all cached images from a specific node" be done with "glance-cache-manage list-cached -H <NODE>"?

Comment 4 Gregory Charot 2019-05-16 12:34:53 UTC
Tooling will be improved with the use of an Ansible playbook + enhancements in glance in order to move cache operations into the API. Tracking these efforts separately.

*** This bug has been marked as a duplicate of bug 1710557 ***


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