This doesn't answer your specific question.  However there are two projects out 
there that are specifically for cleaning up projects and everything associated 
with them for removal.  They are: 

The coda project: https://github.com/openstack/osops-coda

Which given a tenant ID will cleanup all resources for the tenant before its 
removed.  This is a project that came out of HP and has been turned over to the 
Openstack-Operators group.

The second one is: https://github.com/openstack/ospurge

This project works on projects that have already been deleted from keystone but 
has orphaned resources (you can also use it on active projects as well).

___________________________________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy






On 1/25/16, 8:49 AM, "Thomas Blank - Hetzner Online AG" 
<[email protected]> wrote:

>Hey there,
>
>have you tried using the --property option of the openstack-client?
>You could filter images by their owner (openstack_project_id or name).
>
>"openstack image list --property owner=[openstack_project_id]"
>
>see:
>
>http://docs.openstack.org/developer/python-openstackclient/command-objects/image.html#cmdoption-image-list--property
>
>thomas blank,
>
>
>
>On 25.01.2016 16:19, Saverio Proto wrote:
>> Hello there,
>> 
>> I need to delete some users  and tenants from my public cloud. Before
>> deleting the users and tenants from keystone, I need to delete all the
>> resources in the tenants.
>> 
>> I am stucked listing the glance images uploaded in a specific tenant.
>> I cannot find the way, I always get either all the images in the
>> system, or just the ones of the active OS_TENANT_NAME
>> 
>> openstack help image list
>> usage: openstack image list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN]
>>                             [--max-width <integer>] [--noindent]
>>                             [--quote {all,minimal,none,nonnumeric}]
>>                             [--public | --private | --shared]
>>                             [--property <key=value>] [--long]
>>                             [--sort <key>[:<direction>]]
>> 
>> As a work around I can add a user with member role in the tenant, and
>> list in that way ... but, there is really no way to specifiy
>> --tenant=id in the openstack client ?
>> 
>> thank you
>> 
>> Saverio
>> 
>> _______________________________________________
>> OpenStack-operators mailing list
>> [email protected]
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> 
>
>_______________________________________________
>OpenStack-operators mailing list
>[email protected]
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to