On Fri, 16 Jan 2015, Alex Elsayed wrote: > Wido den Hollander wrote: > > <snip> > > Is it a sane thing to look at 'features' which pools could have? Other > > features which might be set on a pool: > > > > - Read Only (all write operations return -EPERM) > > - Delete Protected > > There's another pool feature I'd find very useful: a WORM flag, that permits > only create & append (at the RADOS level, not the RBD level as was an > Emperor blueprint). > > In particular, I'd _love_ being able to make something that takes Postgres > WAL logs and puts them in such a pool, providing real guarantees re: > consistency. Similarly, audit logs and such for compliance. How would you want this to work? - If the bit is set, object creates are allowed, but not deletes? What about append? - Are you allowed to clear the bit with something like 'ceph osd pool set <pool> worm false' ? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
