unsubscribe
Send ceph-users mailing list submissions to
ceph-users@xxxxxxx
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
ceph-users-request@xxxxxxx
You can reach the person managing the list at
ceph-users-owner@xxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ceph-users digest..."
Today's Topics:
1. Re: upmap supported in SLES 12SPx (Ilya Dryomov)
2. Re: upmap supported in SLES 12SPx (Thomas Schneider)
3. Re: upmap supported in SLES 12SPx (Ilya Dryomov)
4. Re: Using same instance name for rgw (Eric Choi)
5. Re: RGW Passthrough (Casey Bodley)
----------------------------------------------------------------------
Date: Mon, 16 Sep 2019 16:56:19 +0200
From: Ilya Dryomov <idryomov@xxxxxxxxx>
Subject: Re: upmap supported in SLES 12SPx
To: Thomas Schneider <74cmonty@xxxxxxxxx>
Cc: Konstantin Shalygin <k0ste@xxxxxxxx>, ceph-users
<ceph-users@xxxxxxx>
Message-ID:
<CAOi1vP-YzuMeL-u=hPDMr6fSTWd+F7RXX61kfO9609pxv98qNw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
On Mon, Sep 16, 2019 at 4:40 PM Thomas Schneider <74cmonty@xxxxxxxxx> wrote:
>
> Hi,
>
> thanks for your valuable input.
>
> Question:
> Can I get more information of the 6 clients (those with features
> 0x40106b84a842a42), e.g. IP, that allows me to identify it easily?
Yes, although it's not integrated into "ceph features". Log into
a monitor node and run "ceph daemon mon.a sessions" (mon.a is the name
of the monitor, substitute accordingly).
Thanks,
Ilya
------------------------------
Date: Mon, 16 Sep 2019 17:10:37 +0200
From: Thomas Schneider <74cmonty@xxxxxxxxx>
Subject: Re: upmap supported in SLES 12SPx
To: Ilya Dryomov <idryomov@xxxxxxxxx>
Cc: Konstantin Shalygin <k0ste@xxxxxxxx>, ceph-users
<ceph-users@xxxxxxx>
Message-ID: <79b342ac-be00-e3e7-cbec-b6c96d3a0a59@xxxxxxxxx>
Content-Type: text/plain; charset=utf-8
Wonderbra.
I found some relevant sessions on 2 of 3 monitor nodes.
And I found some others:
root@ld5505:~# ceph daemon mon.ld5505 sessions | grep 0x40106b84a842a42
root@ld5505:~# ceph daemon mon.ld5505 sessions | grep -v luminous
[
"MonSession(client.32679861 v1:10.97.206.92:0/1183647891 is open
allow *, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.32692978 v1:10.97.206.91:0/3689092992 is open
allow *, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.11935413 v1:10.96.6.116:0/3187655474 is open
allow r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.3941901 v1:10.76.179.23:0/2967896845 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.28313343 v1:10.76.177.108:0/1303617860 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.29311725 v1:10.97.206.94:0/224438037 is open
allow *, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.4535833 v1:10.76.177.133:0/1269608815 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.3919902 v1:10.96.4.243:0/293623521 is open allow
r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.35678944 v1:10.76.179.211:0/4218086982 is open
allow r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.35751316 v1:10.76.179.30:0/1348696702 is open
allow r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.28246527 v1:10.96.4.228:0/1495661381 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.3917843 v1:10.76.179.22:0/489863209 is open allow
r, features 0x27018fb86aa42ada (jewel))",
"MonSession(unknown.0 - is open allow r, features 0x27018eb84aa42a52
(jewel))",
]
Would it make sense to shutdown these clients, too?
What confuses me is that the list includes clients that belong to the
Ceph cluster, namely 10.97.206.0/24.
All nodes of the Ceph cluster are identical in terms of OS, kernel, Ceph.
Regards
Thomas
Am 16.09.2019 um 16:56 schrieb Ilya Dryomov:
> On Mon, Sep 16, 2019 at 4:40 PM Thomas Schneider <74cmonty@xxxxxxxxx> wrote:
>> Hi,
>>
>> thanks for your valuable input.
>>
>> Question:
>> Can I get more information of the 6 clients (those with features
>> 0x40106b84a842a42), e.g. IP, that allows me to identify it easily?
> Yes, although it's not integrated into "ceph features". Log into
> a monitor node and run "ceph daemon mon.a sessions" (mon.a is the name
> of the monitor, substitute accordingly).
>
> Thanks,
>
> Ilya
------------------------------
Date: Mon, 16 Sep 2019 17:36:35 +0200
From: Ilya Dryomov <idryomov@xxxxxxxxx>
Subject: Re: upmap supported in SLES 12SPx
To: Thomas Schneider <74cmonty@xxxxxxxxx>
Cc: Konstantin Shalygin <k0ste@xxxxxxxx>, ceph-users
<ceph-users@xxxxxxx>
Message-ID:
<CAOi1vP9MsfoQFPNfUYPRn2MzS=5buZ-s2Jcorkym84K8hJ6cWw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
On Mon, Sep 16, 2019 at 5:10 PM Thomas Schneider <74cmonty@xxxxxxxxx> wrote:
>
> Wonderbra.
>
> I found some relevant sessions on 2 of 3 monitor nodes.
> And I found some others:
> root@ld5505:~# ceph daemon mon.ld5505 sessions | grep 0x40106b84a842a42
> root@ld5505:~# ceph daemon mon.ld5505 sessions | grep -v luminous
> [
> "MonSession(client.32679861 v1:10.97.206.92:0/1183647891 is open
> allow *, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.32692978 v1:10.97.206.91:0/3689092992 is open
> allow *, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.11935413 v1:10.96.6.116:0/3187655474 is open
> allow r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.3941901 v1:10.76.179.23:0/2967896845 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.28313343 v1:10.76.177.108:0/1303617860 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.29311725 v1:10.97.206.94:0/224438037 is open
> allow *, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.4535833 v1:10.76.177.133:0/1269608815 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.3919902 v1:10.96.4.243:0/293623521 is open allow
> r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.35678944 v1:10.76.179.211:0/4218086982 is open
> allow r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.35751316 v1:10.76.179.30:0/1348696702 is open
> allow r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.28246527 v1:10.96.4.228:0/1495661381 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.3917843 v1:10.76.179.22:0/489863209 is open allow
> r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(unknown.0 - is open allow r, features 0x27018eb84aa42a52
> (jewel))",
> ]
>
> Would it make sense to shutdown these clients, too?
>
> What confuses me is that the list includes clients that belong to the
> Ceph cluster, namely 10.97.206.0/24.
> All nodes of the Ceph cluster are identical in terms of OS, kernel, Ceph.
The above output seems consistent with your "ceph features" output: it
lists clients with features 0x27018eb84aa42a52 and 0x27018fb86aa42ada.
Like I said in my previous email, both of these support upmap.
If you temporarily shut them down, set-require-min-compat-client will
work without --yes-i-really-mean-it.
Thanks,
Ilya
------------------------------
Date: Mon, 16 Sep 2019 16:05:47 -0000
From: "Eric Choi" <eric.yongjun.choi@xxxxxxxxx>
Subject: Re: Using same instance name for rgw
To: ceph-users@xxxxxxx
Message-ID: <156864994756.18.7543223789861447910@mailman-web>
Content-Type: text/plain; charset="utf-8"
bump. anyone?
------------------------------
Date: Mon, 16 Sep 2019 12:22:16 -0400
From: Casey Bodley <cbodley@xxxxxxxxxx>
Subject: Re: RGW Passthrough
To: ceph-users@xxxxxxx
Message-ID: <fdf93930-794e-b2d0-46ee-5288a4d91605@xxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Robert,
So far the cloud tiering features are still in the design stages. We're
working on some initial refactoring work to support this abstraction
(ie. to either satisfy a request against the local rados cluster, or to
proxy it somewhere else). With respect to passthrough/tiering to AWS, we
could use help thinking through the user/credential mapping in
particular. We have a weekly 'RGW Refactoring' meeting on Wednesdays
where we discuss design and refactoring progress - it's on the upstream
community calendar, I'll send you an invite.
On 9/13/19 9:59 PM, Robert LeBlanc wrote:
> We are very interested in the RGW Passthrough mentioned for Octupus.
> What's the status and how can we help? We want to connect with AWS S3.
>
> Thank you,
> ----------------
> Robert LeBlanc
> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
>
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
------------------------------
Subject: Digest Footer
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
------------------------------
End of ceph-users Digest, Vol 80, Issue 54
******************************************
---------- Forwarded message ---------
From: <ceph-users-request@xxxxxxx>
Date: Mon, Sep 16, 2019 at 7:22 PM
Subject: ceph-users Digest, Vol 80, Issue 54
To: <ceph-users@xxxxxxx>
From: <ceph-users-request@xxxxxxx>
Date: Mon, Sep 16, 2019 at 7:22 PM
Subject: ceph-users Digest, Vol 80, Issue 54
To: <ceph-users@xxxxxxx>
Send ceph-users mailing list submissions to
ceph-users@xxxxxxx
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
ceph-users-request@xxxxxxx
You can reach the person managing the list at
ceph-users-owner@xxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ceph-users digest..."
Today's Topics:
1. Re: upmap supported in SLES 12SPx (Ilya Dryomov)
2. Re: upmap supported in SLES 12SPx (Thomas Schneider)
3. Re: upmap supported in SLES 12SPx (Ilya Dryomov)
4. Re: Using same instance name for rgw (Eric Choi)
5. Re: RGW Passthrough (Casey Bodley)
----------------------------------------------------------------------
Date: Mon, 16 Sep 2019 16:56:19 +0200
From: Ilya Dryomov <idryomov@xxxxxxxxx>
Subject: Re: upmap supported in SLES 12SPx
To: Thomas Schneider <74cmonty@xxxxxxxxx>
Cc: Konstantin Shalygin <k0ste@xxxxxxxx>, ceph-users
<ceph-users@xxxxxxx>
Message-ID:
<CAOi1vP-YzuMeL-u=hPDMr6fSTWd+F7RXX61kfO9609pxv98qNw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
On Mon, Sep 16, 2019 at 4:40 PM Thomas Schneider <74cmonty@xxxxxxxxx> wrote:
>
> Hi,
>
> thanks for your valuable input.
>
> Question:
> Can I get more information of the 6 clients (those with features
> 0x40106b84a842a42), e.g. IP, that allows me to identify it easily?
Yes, although it's not integrated into "ceph features". Log into
a monitor node and run "ceph daemon mon.a sessions" (mon.a is the name
of the monitor, substitute accordingly).
Thanks,
Ilya
------------------------------
Date: Mon, 16 Sep 2019 17:10:37 +0200
From: Thomas Schneider <74cmonty@xxxxxxxxx>
Subject: Re: upmap supported in SLES 12SPx
To: Ilya Dryomov <idryomov@xxxxxxxxx>
Cc: Konstantin Shalygin <k0ste@xxxxxxxx>, ceph-users
<ceph-users@xxxxxxx>
Message-ID: <79b342ac-be00-e3e7-cbec-b6c96d3a0a59@xxxxxxxxx>
Content-Type: text/plain; charset=utf-8
Wonderbra.
I found some relevant sessions on 2 of 3 monitor nodes.
And I found some others:
root@ld5505:~# ceph daemon mon.ld5505 sessions | grep 0x40106b84a842a42
root@ld5505:~# ceph daemon mon.ld5505 sessions | grep -v luminous
[
"MonSession(client.32679861 v1:10.97.206.92:0/1183647891 is open
allow *, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.32692978 v1:10.97.206.91:0/3689092992 is open
allow *, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.11935413 v1:10.96.6.116:0/3187655474 is open
allow r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.3941901 v1:10.76.179.23:0/2967896845 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.28313343 v1:10.76.177.108:0/1303617860 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.29311725 v1:10.97.206.94:0/224438037 is open
allow *, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.4535833 v1:10.76.177.133:0/1269608815 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.3919902 v1:10.96.4.243:0/293623521 is open allow
r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.35678944 v1:10.76.179.211:0/4218086982 is open
allow r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.35751316 v1:10.76.179.30:0/1348696702 is open
allow r, features 0x27018eb84aa42a52 (jewel))",
"MonSession(client.28246527 v1:10.96.4.228:0/1495661381 is open
allow r, features 0x27018fb86aa42ada (jewel))",
"MonSession(client.3917843 v1:10.76.179.22:0/489863209 is open allow
r, features 0x27018fb86aa42ada (jewel))",
"MonSession(unknown.0 - is open allow r, features 0x27018eb84aa42a52
(jewel))",
]
Would it make sense to shutdown these clients, too?
What confuses me is that the list includes clients that belong to the
Ceph cluster, namely 10.97.206.0/24.
All nodes of the Ceph cluster are identical in terms of OS, kernel, Ceph.
Regards
Thomas
Am 16.09.2019 um 16:56 schrieb Ilya Dryomov:
> On Mon, Sep 16, 2019 at 4:40 PM Thomas Schneider <74cmonty@xxxxxxxxx> wrote:
>> Hi,
>>
>> thanks for your valuable input.
>>
>> Question:
>> Can I get more information of the 6 clients (those with features
>> 0x40106b84a842a42), e.g. IP, that allows me to identify it easily?
> Yes, although it's not integrated into "ceph features". Log into
> a monitor node and run "ceph daemon mon.a sessions" (mon.a is the name
> of the monitor, substitute accordingly).
>
> Thanks,
>
> Ilya
------------------------------
Date: Mon, 16 Sep 2019 17:36:35 +0200
From: Ilya Dryomov <idryomov@xxxxxxxxx>
Subject: Re: upmap supported in SLES 12SPx
To: Thomas Schneider <74cmonty@xxxxxxxxx>
Cc: Konstantin Shalygin <k0ste@xxxxxxxx>, ceph-users
<ceph-users@xxxxxxx>
Message-ID:
<CAOi1vP9MsfoQFPNfUYPRn2MzS=5buZ-s2Jcorkym84K8hJ6cWw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
On Mon, Sep 16, 2019 at 5:10 PM Thomas Schneider <74cmonty@xxxxxxxxx> wrote:
>
> Wonderbra.
>
> I found some relevant sessions on 2 of 3 monitor nodes.
> And I found some others:
> root@ld5505:~# ceph daemon mon.ld5505 sessions | grep 0x40106b84a842a42
> root@ld5505:~# ceph daemon mon.ld5505 sessions | grep -v luminous
> [
> "MonSession(client.32679861 v1:10.97.206.92:0/1183647891 is open
> allow *, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.32692978 v1:10.97.206.91:0/3689092992 is open
> allow *, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.11935413 v1:10.96.6.116:0/3187655474 is open
> allow r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.3941901 v1:10.76.179.23:0/2967896845 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.28313343 v1:10.76.177.108:0/1303617860 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.29311725 v1:10.97.206.94:0/224438037 is open
> allow *, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.4535833 v1:10.76.177.133:0/1269608815 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.3919902 v1:10.96.4.243:0/293623521 is open allow
> r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.35678944 v1:10.76.179.211:0/4218086982 is open
> allow r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.35751316 v1:10.76.179.30:0/1348696702 is open
> allow r, features 0x27018eb84aa42a52 (jewel))",
> "MonSession(client.28246527 v1:10.96.4.228:0/1495661381 is open
> allow r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(client.3917843 v1:10.76.179.22:0/489863209 is open allow
> r, features 0x27018fb86aa42ada (jewel))",
> "MonSession(unknown.0 - is open allow r, features 0x27018eb84aa42a52
> (jewel))",
> ]
>
> Would it make sense to shutdown these clients, too?
>
> What confuses me is that the list includes clients that belong to the
> Ceph cluster, namely 10.97.206.0/24.
> All nodes of the Ceph cluster are identical in terms of OS, kernel, Ceph.
The above output seems consistent with your "ceph features" output: it
lists clients with features 0x27018eb84aa42a52 and 0x27018fb86aa42ada.
Like I said in my previous email, both of these support upmap.
If you temporarily shut them down, set-require-min-compat-client will
work without --yes-i-really-mean-it.
Thanks,
Ilya
------------------------------
Date: Mon, 16 Sep 2019 16:05:47 -0000
From: "Eric Choi" <eric.yongjun.choi@xxxxxxxxx>
Subject: Re: Using same instance name for rgw
To: ceph-users@xxxxxxx
Message-ID: <156864994756.18.7543223789861447910@mailman-web>
Content-Type: text/plain; charset="utf-8"
bump. anyone?
------------------------------
Date: Mon, 16 Sep 2019 12:22:16 -0400
From: Casey Bodley <cbodley@xxxxxxxxxx>
Subject: Re: RGW Passthrough
To: ceph-users@xxxxxxx
Message-ID: <fdf93930-794e-b2d0-46ee-5288a4d91605@xxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Robert,
So far the cloud tiering features are still in the design stages. We're
working on some initial refactoring work to support this abstraction
(ie. to either satisfy a request against the local rados cluster, or to
proxy it somewhere else). With respect to passthrough/tiering to AWS, we
could use help thinking through the user/credential mapping in
particular. We have a weekly 'RGW Refactoring' meeting on Wednesdays
where we discuss design and refactoring progress - it's on the upstream
community calendar, I'll send you an invite.
On 9/13/19 9:59 PM, Robert LeBlanc wrote:
> We are very interested in the RGW Passthrough mentioned for Octupus.
> What's the status and how can we help? We want to connect with AWS S3.
>
> Thank you,
> ----------------
> Robert LeBlanc
> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
>
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
------------------------------
Subject: Digest Footer
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
------------------------------
End of ceph-users Digest, Vol 80, Issue 54
******************************************
_______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
