From: Alex Elsayed <eternaleye@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: 'Immutable bit' on pools to prevent deletion
Date: Fri, 16 Jan 2015 18:31:46 -0800 [thread overview]
Message-ID: <m9chio$3lp$1@ger.gmane.org> (raw)
In-Reply-To: 54B7D2D6.4020503@42on.com
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.
next prev parent reply other threads:[~2015-01-17 2:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 14:46 'Immutable bit' on pools to prevent deletion Wido den Hollander
2015-01-15 15:39 ` Dan Van Der Ster
2015-01-15 15:52 ` Wido den Hollander
2015-01-15 15:45 ` Mike Dawson
2015-01-15 15:58 ` Yehuda Sadeh
2015-01-15 17:24 ` Sage Weil
2015-01-15 17:44 ` Sage Weil
2015-01-15 17:55 ` Gregory Farnum
2015-01-15 18:07 ` Sage Weil
2015-01-15 18:45 ` Gregory Farnum
2015-01-15 19:02 ` John Spray
2015-01-15 19:07 ` Sage Weil
2015-01-15 22:02 ` John Spray
2015-01-16 7:55 ` Wido den Hollander
2015-01-16 9:50 ` Sebastien Han
2015-01-16 10:55 ` Wido den Hollander
2015-01-16 14:46 ` Sage Weil
2015-01-19 19:32 ` Mykola Golub
2015-01-19 20:28 ` Sage Weil
[not found] ` <597309080.14312.1421421468640.open-xchange@websrv>
2015-01-16 20:45 ` Wido den Hollander
2015-01-17 2:31 ` Alex Elsayed [this message]
2015-01-17 13:11 ` Wido den Hollander
2015-01-17 16:24 ` Sage Weil
2015-01-17 19:09 ` Alex Elsayed
2015-01-17 23:28 ` David Zafman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='m9chio$3lp$1@ger.gmane.org' \
--to=eternaleye@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.