I know in Vancouver we talked about no more soft delete and in Mitaka
lxsli decoupled the nova models from the SoftDeleteMixin [1].
From what I remember, the idea is to not add the deleted column to new
tables, to not expose soft deleted resources in the REST API in new
ways, and to eventually drop the deleted column from the models.
I bring up the REST API because I was tinkering with the idea of
allowing non-admins to list/show their (soft) deleted instances [2].
Doing that, however, would expose more of the REST API to deleted
resources which makes it harder to remove from the data model.
My question is, how were we thinking we were going to remove the deleted
column from the data model in a backward compatible way? A new
microversion in the REST API isn't going to magically work if we drop
the column in the data model, since anything before that microversion
should still work - like listing deleted instances for the admin.
Am I forgetting something? There were a lot of ideas going around the
room during the session in Vancouver and I'd like to sort out the
eventual long-term plan so we can document it in the devref about
policies so that when ideas like [2] come up we can point to the policy
and say 'no we aren't going to do that and here's why'.
[1]
http://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/no-more-soft-delete.html
[2]
https://blueprints.launchpad.net/nova/+spec/non-admin-list-deleted-instances
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
