Hi,
I'm using Pacific v16.2.10 container image, deployed by cephadm.
I used to manually build config file for rgw, deploy rgw, put config file in place
and restart rgw. It works fine.
Now, I'd like to put rgw config into config db. I tried with client.rgw, but the
config
is not taken by rgw. Also "config show" doesn't work. It always says
"no config state".
```
# ceph orch ps | grep rgw
rgw.qa.ceph-1.hzfrwq ceph-1 10.250.80.100:80 running (10m) 10m ago 53m
51.4M - 16.2.10 32214388de9d 13169a213bc5
# ceph config get client.rgw | grep frontends
client.rgw basic rgw_frontends beast port=8086
*
# ceph config show rgw.qa.ceph-1.hzfrwq
Error ENOENT: no config state for daemon rgw.qa.ceph-1.hzfrwq
# ceph config show client.rgw.qa.ceph-1.hzfrwq
Error ENOENT: no config state for daemon client.rgw.qa.ceph-1.hzfrwq
# radosgw-admin --show-config -n client.rgw.qa.ceph-1.hzfrwq | grep frontends
rgw_frontends = beast port=7480
```
Any clues what I am missing here?
Thanks!
Tony
Show replies by date
A few updates.
1. "radosgw-admin --show-config -n client.rgw.qa.ceph-1.hzfrwq" doesn't show
actual running config.
2. "ceph --admin-daemon
/var/run/ceph/69f94d08-2811-11ee-9ab1-089204adfafa/ceph-client.rgw.qa.ceph-1.hzfrwq.7.94254493095368.asok
config show" shows the actual running config.
3. All settings in client.rgw are applied to rgw running config, except for
rgw_frontends.
```
# ceph config get client.rgw rgw_frontends
beast port=8086
# ceph --admin-daemon
/var/run/ceph/69f94d08-2811-11ee-9ab1-089204adfafa/ceph-client.rgw.qa.ceph-1.hzfrwq.7.94254493095368.asok
config get rgw_frontends
{
"rgw_frontends": "beast endpoint=10.250.80.100:80"
}
```
The only place I see "10.250.80.100" and "80" is unit.meta. How is
that applied?
Found a workaround, remove rgw_frontends from config, restart rgw, rgw_frontends
goes back to default "port=7480". Add it back to config, restart rgw. Now
rgw_frontends
is what I expect. The logic doesn't make much sense to me. I'd assume that
unit.meta has
something to do with this, hopefully someone could shed light here.
Thanks!
Tony
________________________________________
From: Tony Liu <tonyliu0592(a)hotmail.com>
Sent: July 29, 2023 10:40 PM
To: ceph-users(a)ceph.io; dev(a)ceph.io
Subject: [ceph-users] configure rgw
Hi,
I'm using Pacific v16.2.10 container image, deployed by cephadm.
I used to manually build config file for rgw, deploy rgw, put config file in place
and restart rgw. It works fine.
Now, I'd like to put rgw config into config db. I tried with client.rgw, but the
config
is not taken by rgw. Also "config show" doesn't work. It always says
"no config state".
```
# ceph orch ps | grep rgw
rgw.qa.ceph-1.hzfrwq ceph-1 10.250.80.100:80 running (10m) 10m ago 53m
51.4M - 16.2.10 32214388de9d 13169a213bc5
# ceph config get client.rgw | grep frontends
client.rgw basic rgw_frontends beast port=8086
*
# ceph config show rgw.qa.ceph-1.hzfrwq
Error ENOENT: no config state for daemon rgw.qa.ceph-1.hzfrwq
# ceph config show client.rgw.qa.ceph-1.hzfrwq
Error ENOENT: no config state for daemon client.rgw.qa.ceph-1.hzfrwq
# radosgw-admin --show-config -n client.rgw.qa.ceph-1.hzfrwq | grep frontends
rgw_frontends = beast port=7480
```
Any clues what I am missing here?
Thanks!
Tony
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
When deploy rgw container, cephadm adds rgw_frontends into config db on daemon level. I
was adding settings on node level. That's why I didn't see my setting take
effect.
I need to put rgw_frontends on daemon level after deployment.
Thanks!
Tony
________________________________________
From: Tony Liu <tonyliu0592(a)hotmail.com>
Sent: July 29, 2023 11:44 PM
To: ceph-users(a)ceph.io; dev(a)ceph.io
Subject: [ceph-users] Re: configure rgw
A few updates.
1. "radosgw-admin --show-config -n client.rgw.qa.ceph-1.hzfrwq" doesn't show
actual running config.
2. "ceph --admin-daemon
/var/run/ceph/69f94d08-2811-11ee-9ab1-089204adfafa/ceph-client.rgw.qa.ceph-1.hzfrwq.7.94254493095368.asok
config show" shows the actual running config.
3. All settings in client.rgw are applied to rgw running config, except for
rgw_frontends.
```
# ceph config get client.rgw rgw_frontends
beast port=8086
# ceph --admin-daemon
/var/run/ceph/69f94d08-2811-11ee-9ab1-089204adfafa/ceph-client.rgw.qa.ceph-1.hzfrwq.7.94254493095368.asok
config get rgw_frontends
{
"rgw_frontends": "beast endpoint=10.250.80.100:80"
}
```
The only place I see "10.250.80.100" and "80" is unit.meta. How is
that applied?
Found a workaround, remove rgw_frontends from config, restart rgw, rgw_frontends
goes back to default "port=7480". Add it back to config, restart rgw. Now
rgw_frontends
is what I expect. The logic doesn't make much sense to me. I'd assume that
unit.meta has
something to do with this, hopefully someone could shed light here.
Thanks!
Tony
________________________________________
From: Tony Liu <tonyliu0592(a)hotmail.com>
Sent: July 29, 2023 10:40 PM
To: ceph-users(a)ceph.io; dev(a)ceph.io
Subject: [ceph-users] configure rgw
Hi,
I'm using Pacific v16.2.10 container image, deployed by cephadm.
I used to manually build config file for rgw, deploy rgw, put config file in place
and restart rgw. It works fine.
Now, I'd like to put rgw config into config db. I tried with client.rgw, but the
config
is not taken by rgw. Also "config show" doesn't work. It always says
"no config state".
```
# ceph orch ps | grep rgw
rgw.qa.ceph-1.hzfrwq ceph-1 10.250.80.100:80 running (10m) 10m ago 53m
51.4M - 16.2.10 32214388de9d 13169a213bc5
# ceph config get client.rgw | grep frontends
client.rgw basic rgw_frontends beast port=8086
*
# ceph config show rgw.qa.ceph-1.hzfrwq
Error ENOENT: no config state for daemon rgw.qa.ceph-1.hzfrwq
# ceph config show client.rgw.qa.ceph-1.hzfrwq
Error ENOENT: no config state for daemon client.rgw.qa.ceph-1.hzfrwq
# radosgw-admin --show-config -n client.rgw.qa.ceph-1.hzfrwq | grep frontends
rgw_frontends = beast port=7480
```
Any clues what I am missing here?
Thanks!
Tony
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io