Open Stack

In nova-api, both vm_states.DELETED and vm_states.SOFT_DELETED states are
mapped to the 'DELETED' status. Thus although nova-api supports filtering
instances by instance status, we cannot get instances which are in
'soft-deleted' status, like:

nova list --status SOFT_DELETED

So does it make sense to seperate out 'soft-deleted' instances from
'deleted' ones in the api level?

To achive this, we can modify the state-status mappings in nova-api to map
vm_states.SOFT_DELETED to a dedicated status(like SOFT_DELETED) and vice
versa. Of course, some modification should be token in the instance filter
logic.

Could anyone give some opinions before I am working on it?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130630/befecba4/attachment.html>