Delete a Pool - how hard should be?

[Max Cuttins <max@xxxxxxxxxxxxx>]

I think this is a good question for everybody: How hard should be delete a Pool?

We ask to tell the pool twice.
We ask to add "--yes-i-really-really-mean-it"
We ask to add ability to mons to delete the pool (and remove this ability ASAP after).

... and then somebody of course ask us to restore the pool.

I think that all this stuff is not looking in the right direction.
It's not the administrator that need to be warned from delete datas.
It's the data owner that should be warned (which most of the time give it's approval by phone and gone).

So, all this stuff just make the life of administrator harder, while not improving in any way the life of the Data Owner.
Probably the best solution is to ...do not delete at all and instead apply a "deleting policy".
Something like:

ceph osd pool rm POOL_NAME -yes
-> POOL_NAME is set to be deleted, removal is scheduled within 30 days.

This allow us to do 2 things:

• allow administrator to don't waste their time in CML with true strange command
  
• allow data owner to have a grace period to verify if, after deletion, everything works as expected and that data that disapper wasn't usefull in some way.

After 30 days data will be removed automatically. This is a safe policy for ADMIN and DATA OWNER.
Of course ADMIN should be allowed to remove POOL scheduleded for deletion in order to save disk spaces if needed (but only if needed).

What do you think?

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