Re: Delete a Pool - how hard should be?

[Max Cuttins <max@xxxxxxxxxxxxx>]

Il 06/03/2018 16:23, David Turner ha scritto:

That said, I do like the idea of being able to disable buckets, rbds, pools, etc so that no client could access them. That is useful for much more than just data deletion and won't prevent people from deleting data prematurely.

To me, if nobody can access data for 30 days and the customer didn't call me within those days, it's ok to delete definitly the data.
Which is the way should be.
Make easy to the admin delete data when he really wants.
Make possible to the user to stay some days without it's data till these data is obsolete and useless.
The autopurge of the trash of your mailbox works in the sameway and seems to me a reasonable way to handle precious data such personal emails.

It could be added as a requisite step to deleting a pool, rbd, etc. The process would need to be refactored as adding another step isn't viable.

This feature is much more complicated than it may seem on the surface. For pools, you could utilize cephx, except not everyone uses that... So maybe logic added to the osd map. Buckets would have to be completely in rgw. Rbds would probably have to be in the osd map as well. This is not a trivial change.

Mine was just a "nice-to-have" proposal.
There is no hurry in implement a secondary feature such this one.

About the logic is it possible to use something like this:

• snapshot the pool with a special poolname
  
• remove the original pool
• give the possibility to restore the snapshot with it's original name.

I think this should suddenly stop all the connection to the original pool but leave all the data intact.
Maybe.

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com