From: Wido den Hollander <wido@42on.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph keyring
Date: Mon, 25 Feb 2013 09:53:46 +0100 [thread overview]
Message-ID: <512B269A.5020503@42on.com> (raw)
In-Reply-To: <CAJH6TXgQ2Z_k=Prs625bbX1TWEwUmQRY8wsHhxM5OOU73fiWOg@mail.gmail.com>
On 02/20/2013 10:01 AM, Gandalf Corvotempesta wrote:
> I'm trying to configure RGW following this guide:
> http://ceph.com/docs/master/radosgw/config/
>
> I have some questions about keyring. Should keyring files copied on
> each cluster node?
> For example, these commands:
>
> sudo ceph-authtool --create-keyring /etc/ceph/keyring.radosgw.gateway
> sudo chmod +r /etc/ceph/keyring.radosgw.gateway
> sudo ceph-authtool /etc/ceph/keyring.radosgw.gateway -n
> client.radosgw.gateway --gen-key
> sudo ceph-authtool -n client.radosgw.gateway --cap osd 'allow rwx'
> --cap mon 'allow r' /etc/ceph/keyring.radosgw.gateway
> sudo ceph -k /etc/ceph/ceph.keyring auth add client.radosgw.gateway -i
> /etc/ceph/keyring.radosgw.gateway
>
> on which node should be ran and the generated keyfile, should be
> synced on each node?
> --
You need to copy the keyring file to the node where the RGW will be running.
The RGW will use the key to authenticate with the cluster.
Wido
P.S.: This would be something for the -users list.
> 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
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
prev parent reply other threads:[~2013-02-25 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 9:01 ceph keyring Gandalf Corvotempesta
2013-02-25 8:53 ` Wido den Hollander [this message]
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=512B269A.5020503@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@gmail.com \
/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.