Open Stack

I'm mostly responding to russelb's comments here, and would love to hear other opinions: https://blueprints.launchpad.net/nova/+spec/show-deleted-instances

Essentially, if we have the data, should we expose it to users?  It certainly makes sense to expose it to admins, who have some concept of what a deployment's retention period is, etc.

I think there is value in exposing it to end users, as the deleted instances are already available when using the changes-since parameter - if the data has been moved and doesn't show up in a changes-since call, then you shouldn't be able to show it, I think that is conceptually sound.

Gabe

On Apr 29, 2013, at 3:39 PM, Andrew M <ramielrowe at gmail.com<mailto:ramielrowe at gmail.com>> wrote:

Hello,

I'm working on a project that is cataloging and verifying the notifications being emitted by Nova. One of the functions of this system is to pull data from an alternate data source when notifications may have been missed/dropped. I'm thinking of using the Nova API as this source, but I've run into an issue. Currently the Nova API returns 404's on shows of deleted instances even if there is data in the database (thanks to soft-deletes).

I'm wondering what the reason was for this behavior and would it be a good idea to perhaps return that data if a query param is set (something like 'show_deleted=true').


--Andrew
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto: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/20130507/011185f8/attachment.html>