From: Wido den Hollander <wido@widodh.nl>
To: John Axel Eriksson <john@insane.se>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ceph questions regarding auth and return on PUT from radosgw
Date: Mon, 11 Jun 2012 14:51:35 +0200 [thread overview]
Message-ID: <4FD5E9D7.5010200@widodh.nl> (raw)
In-Reply-To: <CAMmJxtL_sGx6fSs2+CZet10JVDPJqebkqreJuHQzhgUxngM-nw@mail.gmail.com>
On 06/11/2012 02:41 PM, John Axel Eriksson wrote:
> 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.
I'd say: Yes
With keys in place you can ensure that a rogue machine starts bringing
down your cluster.
Scenario: You take a machine offline in a cluster, let it sit in storage
for some while and a couple of months later somebody wonders what that
machine does.
Plugs it into a switch, power and boots. Suddenly this old machine which
is way behind on software starts participating in your cluster again and
could potentially bring it all down.
But it could even be even more simple. You set up a second Ceph cluster
for some tests, but while playing with the 'rados' command you
accidentally connect to the wrong cluster and issue a "rmpool". Oops!
With auth in place you have a barrier against such situations.
Wido
>
> On Mon, Jun 11, 2012 at 2:40 PM, Wido den Hollander<wido@widodh.nl> 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@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-11 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 12:32 Ceph questions regarding auth and return on PUT from radosgw John Axel Eriksson
2012-06-11 12:40 ` Wido den Hollander
2012-06-11 12:41 ` John Axel Eriksson
2012-06-11 12:51 ` Wido den Hollander [this message]
2012-06-11 13:34 ` John Axel Eriksson
2012-06-11 15:08 ` Yehuda Sadeh Weinraub
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=4FD5E9D7.5010200@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=john@insane.se \
/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.