Open Stack

I have a patch up for review on this:

https://review.openstack.org/#/c/35061/ 

However, this doesn't fix the vm_states.SOFT_DELETED mapping in 
nova.api.openstack.common so if you show an instance with 
vm_states.SOFT_DELETED, the response status will be 'DELETED'.

I'd like to see if there are any opinions on if this should come back as 
'SOFT_DELETED' or if everyone is OK with mapping soft-delete to 'DELETED' 
in the v3 API?

As far as the bug is concerned, I've at least done what I wanted which was 
to make the filtering work when searching on SOFT_DELETED and raise a 
BadRequest on unmapped status values to shore up the usability problem 
there.



Thanks,

MATT RIEDEMANN
Advisory Software Engineer
Cloud Solutions and OpenStack Development

Phone: 1-507-253-7622 | Mobile: 1-507-990-1889
E-mail: mriedem at us.ibm.com


3605 Hwy 52 N
Rochester, MN 55901-1407
United States




From:   Matt Riedemann/Rochester/IBM at IBMUS
To:     OpenStack Development Mailing List 
<openstack-dev at lists.openstack.org>, 
Date:   07/01/2013 04:14 PM
Subject:        Re: [openstack-dev] [Nova] Seperate out 'soft-deleted' 
instances       from 'deleted' ones?



For everyone's awareness, there is a bug related to this: 
https://bugs.launchpad.net/nova/+bug/1196255 



Thanks, 

MATT RIEDEMANN
Advisory Software Engineer
Cloud Solutions and OpenStack Development 

Phone: 1-507-253-7622 | Mobile: 1-507-990-1889
E-mail: mriedem at us.ibm.com 


3605 Hwy 52 N
Rochester, MN 55901-1407
United States





From:        Yufang Zhang <yufang521247 at gmail.com> 
To:        openstack-dev at lists.openstack.org, 
Date:        06/30/2013 10:01 AM 
Subject:        [openstack-dev] Seperate out 'soft-deleted' instances from 
       'deleted' ones? 



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._______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130715/0a0ab2ff/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130715/0a0ab2ff/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130715/0a0ab2ff/attachment-0001.gif>