On Thu, Jun 14, 2012 at 1:41 AM, Greg Farnum g...@inktank.com wrote:
On Wednesday, June 13, 2012 at 1:37 PM, Florian Haas wrote:
Greg,
My understanding of Ceph code internals is far too limited to comment on
your specific points, but allow me to ask a naive question.
Couldn't you be
On Wed, Jun 13, 2012 at 10:40 AM, Gregory Farnum g...@inktank.com wrote:
2) Client fencing. See http://tracker.newdream.net/issues/2531. There
is an existing blacklist functionality in the OSDs/OSDMap, where you
So I just managed to put into words another reason I like the key
rotation more
We've had some user reports lately on rbd images being broken by
misbehaving clients — namely, rbd image I is mounted on computer A,
computer A starts misbehaving, and so I is mounted on computer B. But
because A is misbehaving it keeps writing to the image, corrupting it
horribly.
To handle this,
Greg,
My understanding of Ceph code internals is far too limited to comment on
your specific points, but allow me to ask a naive question.
Couldn't you be stealing a lot of ideas from SCSI-3 Persistent
Reservations? If you had server-side (OSD) persistence of information of
the this device is in
On Wed, Jun 13, 2012 at 10:40 AM, Gregory Farnum g...@inktank.com wrote:
2) Client fencing. See http://tracker.newdream.net/issues/2531. There
is an existing blacklist functionality in the OSDs/OSDMap, where you
can specify an entity_addr_t (consisting of an IP, a port, and a
nonce — so
On Wed, Jun 13, 2012 at 10:40 AM, Gregory Farnum g...@inktank.com wrote:
2) Client fencing. See http://tracker.newdream.net/issues/2531. There
You know, I'd be really happy if this could be achieved by means of
removing cephx keys.
--
To unsubscribe from this list: send the line unsubscribe
On Wednesday, June 13, 2012 at 1:37 PM, Florian Haas wrote:
Greg,
My understanding of Ceph code internals is far too limited to comment on
your specific points, but allow me to ask a naive question.
Couldn't you be stealing a lot of ideas from SCSI-3 Persistent
Reservations? If you had
