From: "Marc Roos" <M.Roos@f1-outsourcing.eu>
To: response <response@ifastnet.com>, tri <tri@postix.net>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
ceph-users <ceph-users@ceph.io>,
"icepic.dz" <icepic.dz@gmail.com>
Subject: RE: [ceph-users] Re: Understanding what ceph-volume does, with bootstrap-osd/ceph.keyring, tmpfs
Date: Tue, 22 Sep 2020 21:17:54 +0200 [thread overview]
Message-ID: <"H00000710017cef1.1600802274.sx.f1-outsourcing.eu*"@MHS> (raw)
At least ceph thought you the essence of doing first proper testing ;)
Because if you test your use case you either get a positive or negative
result and not a problem.
However I do have to admit that ceph could be more transparent with
publishing testing and performance results. I have already discussed
this with them on such a ceph day. It does not make sense to have to do
everything yourself eg the luks overhead and putting the db/wal on ssd,
rbd performance on hdds etc. Those can quickly show if ceph can be a
candidate or not.
-----Original Message-----
From: Kevin Myers [mailto:response@ifastnet.com]
Cc: Janne Johansson; Marc Roos; ceph-devel; ceph-users
Subject: Re: [ceph-users] Re: Understanding what ceph-volume does, with
bootstrap-osd/ceph.keyring, tmpfs
Tbh ceph caused us more problems than it tried to fix ymmv good luck
> On 22 Sep 2020, at 13:04, tri@postix.net wrote:
>
> The key is stored in the ceph cluster config db. It can be retrieved
> by
>
> KEY=`/usr/bin/ceph --cluster ceph --name
> client.osd-lockbox.${OSD_FSID} --keyring $OSD_PATH/lockbox.keyring
> config-key get dm-crypt/osd/$OSD_FSID/luks`
>
> September 22, 2020 2:25 AM, "Janne Johansson" <icepic.dz@gmail.com>
wrote:
>
>> Den mån 21 sep. 2020 kl 16:15 skrev Marc Roos
<M.Roos@f1-outsourcing.eu>:
>>
>>> When I create a new encrypted osd with ceph volume[1]
>>>
>>> Q4: Where is this luks passphrase stored?
>>
>> I think the OSD asks the mon for it after auth:ing, so "in the mon
DBs"
>> somewhere.
>>
>> --
>> May the most significant bit of your life be positive.
>> _______________________________________________
>> ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an
>> email to ceph-users-leave@ceph.io
> _______________________________________________
> ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an
> email to ceph-users-leave@ceph.io
next reply other threads:[~2020-09-22 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 19:17 Marc Roos [this message]
[not found] <CAA6-MF_47O1p0Rd-_jhKfwW6s1LKYrnj7tgu07=i8NQzUzCSZQ@mail.gmail.com>
[not found] ` <H00000710017cb1c.1600697698.sx.f1-outsourcing.eu*@MHS>
2020-09-22 12:04 ` [ceph-users] Re: Understanding what ceph-volume does, with bootstrap-osd/ceph.keyring, tmpfs tri
2020-09-22 16:29 ` Kevin Myers
2020-09-30 18:25 ` Marc Roos
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='"H00000710017cef1.1600802274.sx.f1-outsourcing.eu*"@MHS' \
--to=m.roos@f1-outsourcing.eu \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.io \
--cc=icepic.dz@gmail.com \
--cc=response@ifastnet.com \
--cc=tri@postix.net \
/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.