Bug 1004409

Summary: [RFE][glance]: Add cli option --log export list of deleted images and ID
Product: Red Hat OpenStack Reporter: Dafna Ron <dron>
Component: python-glanceclientAssignee: Flavio Percoco <fpercoco>
Status: CLOSED UPSTREAM QA Contact: nlevinki <nlevinki>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: eglynn, fpercoco, jruzicka, markmc, scohen, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://blueprints.launchpad.net/glance/+spec/log-deleted-images-info
Whiteboard: storage upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-17 13:37:22 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:

Description Dafna Ron 2013-09-04 14:56:46 UTC
Description of problem:

it would be helpful to users if we had a --log option for glance image-delete so that user can request a print of all the deleted images (names and ID) 

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

openstack-glance-2013.1.3-1.el6ost.noarch

How reproducible:

100%

Steps to Reproduce:
1. create several images 
2. delete all of the images in one command
3.

Actual results:

only if we fail to delete one of the images we would see a print on it else we have no output and no option to add it. 

Expected results:

I think in deleted images user might want a record of the images that were deleted and to be able to save them to file. 
I would also go as far as to ask that we will allow admin user to configure this option as default for the environment. 

Additional info:

Comment 1 Dafna Ron 2013-09-04 14:58:50 UTC
https://bugs.launchpad.net/glance/+bug/1220760

Comment 2 Flavio Percoco 2015-03-17 13:37:22 UTC
This is worth keeping just upstream and let the community take over on the details and implementation. closing.