Oh sorry. I don't think I was clear on the auth question. What I meant was if the admin.keyring and keys for the osd:s are really necessary in a private ceph-cluster. On Mon, Jun 11, 2012 at 2:40 PM, Wido den Hollander <wido@xxxxxxxxx> wrote: > Hi, > > > On 06/11/2012 02:32 PM, John Axel Eriksson wrote: >> >> Is there a point to having auth enabled if I run ceph on an internal >> network, only for use with radosgw (i.e the object storage part)? >> It seems to complicate the setup unnecessarily and ceph doesn't use >> encryption anyway as far as I understand, it's only auth. >> If my network is trusted and I know who has access (and I trust them) >> - is there a point to complicate the setup with key-based auth? >> > > The RADOS Gateway uses the S3 protocol and that requires authentication and > authorization. > > When creating a bucket/pool and storing objects, it has to be mapped to a > users inside the RADOS GW. > > I don't know what your exact use-case is, but if it's only internal, isn't > it a possibility to use RADOS natively? > > >> Also, when PUTting something through radosgw, does ceph/rgw return as >> soon as all data has been received or does it return >> when it has ensured N replicas? (I've seen quite a delay after all >> data has been sent before my PUT returns). I'm using nginx (1.2) by >> the way. > > > iirc it returns when all replicas have received and stored the object. > > Wido > >> >> Thanks! >> >> John >> -- >> 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 -- 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
