[ceph-users] Re: RadosGW manual deployment

[Janne Johansson]

> If there is a (planned) documentation of manual rgw bootstrapping,
> it would be nice to have also the names of required pools listed there.

It will depend on several things, like if you enable swift users, I
think they get a pool of their own, so I guess one would need to look
in the source for a full list of potential pools made by rgw.

> # verify it works
> curl http://127.0.0.1:8088
> ceph osd pool ls
> # should print at least the following pools:
> # .rgw.root
> # default.rgw.log
> # default.rgw.control
> # default.rgw.meta
> # ... and maybe also these, after some buckets are created:
> # default.rgw.buckets.index
> # default.rgw.buckets.non-ec
> # default.rgw.buckets.data
> 

My oldest cluster seems to have these ones: (some may not be relevant anymore)

.rgw.root 5  10.0KiB 0
10.8TiB   23
default.rgw.control   6   0B 0
10.8TiB8
default.rgw.data.root 7  64.7KiB 0
10.8TiB  186
default.rgw.gc8   0B 0
10.8TiB   32
default.rgw.log   9   685GiB  5.85
10.8TiB   159903
default.rgw.users.uid 10 5.32KiB 0
10.8TiB   28
default.rgw.usage 11  0B 0
10.8TiB   13
default.rgw.users.keys12459B 0
10.8TiB   14
default.rgw.meta  13  330KiB 0
10.8TiB  923
default.rgw.buckets.index 14  0B 0
10.8TiB  184
default.rgw.buckets.non-ec15  0B 0
10.8TiB  828
default.rgw.buckets.data  16 6.39TiB 13.09
42.5TiB  2777682
default.rgw.users.email   23115B 0
10.8TiB4

so .log and .usage probably need some traffic before they appear.

-- 
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-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Eugen Block]

Hi,

I was just curious what your intentions are, not meaning to critisize  
it. ;-) There are different reasons why that could be a better choice.  
And as I already mentioned previously, you only would have stray  
daemons warnings if you deployed the RGWs on hosts which already have  
cephadm managed daemons.


Thanks,
Eugen

Zitat von Jan Kasprzak :


Hello, Eugen,

Eugen Block wrote:

Janne was a bit quicker than me, so I'll skip my short instructions
how to deploy it manually. But your (cephadm managed) cluster will
complain about "stray daemons". There doesn't seem to be a way to
deploy rgw daemons manually with the cephadm tool so it wouldn't be
stray. Is there a specific reason not to use the orchestrator for
rgw deployment?


I don't want to start an opinion war here :-), but the reason is
more or less that I want to be able to see under the hood (at least
to some degree :-). So for now I want to run a plain, non-containerized
non-orchestrated setup.

Thanks all for your help, it works for me now.

-Yenya

--
| Jan "Yenya" Kasprzak  |
| https://www.fi.muni.cz/~kas/GPG: 4096R/A45477D5 |
We all agree on the necessity of compromise. We just can't agree on
when it's necessary to compromise. --Larry Wall



___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Jan Kasprzak]

Hello, Eugen,

Eugen Block wrote:
> Janne was a bit quicker than me, so I'll skip my short instructions
> how to deploy it manually. But your (cephadm managed) cluster will
> complain about "stray daemons". There doesn't seem to be a way to
> deploy rgw daemons manually with the cephadm tool so it wouldn't be
> stray. Is there a specific reason not to use the orchestrator for
> rgw deployment?

I don't want to start an opinion war here :-), but the reason is
more or less that I want to be able to see under the hood (at least
to some degree :-). So for now I want to run a plain, non-containerized
non-orchestrated setup.

Thanks all for your help, it works for me now.

-Yenya

-- 
| Jan "Yenya" Kasprzak  |
| https://www.fi.muni.cz/~kas/GPG: 4096R/A45477D5 |
We all agree on the necessity of compromise. We just can't agree on
when it's necessary to compromise. --Larry Wall
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Jan Kasprzak]

Hello, Janne,

Janne Johansson wrote:
> Den mån 29 jan. 2024 kl 08:11 skrev Jan Kasprzak :
> >
> > Is it possible to install a new radosgw instance manually?
> > If so, how can I do it?
> 
> We are doing it, and I found the same docs issue recently, so Zac
> pushed me to provide a skeleton (at least) for such a page. I have
> recently made a quincy cluster manual install with RGWs so I will
> condense what I did to something that can be used for docs later on
> (I'll leave it to Zac to format and merge).
> 
> Really short version for you:
> Install radosgw debs/rpms on the rgw box(es)
> 
> On one of the mons or a box with admin ceph auth run
>ceph auth get-or-create client.short-hostname-of-rgw mon 'allow rw'
> osd 'allow rwx'

OK, I was looking for something like ... mon 'allow profile radosgw'.
Which can be set, but does not work. This was my main problem, apparently.
mon 'allow rw' works.

> On each of the rgw box(es)
>   create a ceph-user owned dir, for instance like this
>   install -d -o ceph -g ceph /var/lib/ceph/radosgw/ceph-$(hostname -s)
>   inside this dir, put the key (or the first two lines of it) you got
> from the above ceph auth get-or-create
>   vi /var/lib/ceph/radosgw/ceph-$(hostname -s)/keyring
>   Figure out what URL rgw should answer to and all that in the config
> parts, but that would be the same
>   for manual and ceph-adm/orchestrated installs.
>   and now you should be able to start the service with
>   systemctl start ceph-radosgw@$(hostname -s).service

Works for me, thanks.

> The last part may or may not act up a bit due to two things, one is
> that it may have tried starting lots of times after the deb/rpm got
> installed, but long before you added they usable key for it, so doing
> a slight boxing match with systemd might be in order, to stop the
> service, reset-failed on the service and then restarting it. (and
> check that it is enabled, so it starts on next boot also)

No problem with that on my systems.

> Secondly, I also tend to run into this issue* where rgw (and other
> parts of ceph!) can't create pools if they don't specify PG numbers,
> which rgw doesn't do any longer, and if you get this error, you end up
> having to create all the pools manually yourself (from a mon/admin
> host or the rgw, but doing it from the rgw requires a lot more
> specifying username and keyfile locations than the default admin-key
> hosts)
> 
> *) https://tracker.ceph.com/issues/62770
>This ticket has a VERY SIMPLE method of testing if ceph versions
> has this problem or not, just
>run "ceph osd pool create some-name" and see how it fails unless
> you add a number behind
>it or not.
> 
>The help is quite clear that all other parameters are meant to be optional:
> 
> osd pool create  [] []
> [] [] []
> [] [] []
> [] [] [--bulk]
> [] [] :  create pool

Also OK on my system.

If there is a (planned) documentation of manual rgw bootstrapping,
it would be nice to have also the names of required pools listed there.

So, thanks for a heplful reply! To sum it up, the following
worked for me (on AlmaLinux 9 host with client.admin.keyring and Ceph Reef):


RGWNAME=`hostname -s`
echo "RGW name is $RGWNAME"

cat >> /etc/ceph/ceph.conf < /var/lib/ceph/radosgw/ceph-$RGWNAME/keyring
chown -R ceph:ceph /var/lib/ceph/radosgw/ceph-$RGWNAME

systemctl enable --now ceph-radosgw@$RGWNAME

# verify it works
curl http://127.0.0.1:8088
ceph osd pool ls
# should print at least the following pools:
# .rgw.root
# default.rgw.log
# default.rgw.control
# default.rgw.meta
# ... and maybe also these, after some buckets are created:
# default.rgw.buckets.index
# default.rgw.buckets.non-ec
# default.rgw.buckets.data


-Yenya

-- 
| Jan "Yenya" Kasprzak  |
| https://www.fi.muni.cz/~kas/GPG: 4096R/A45477D5 |
We all agree on the necessity of compromise. We just can't agree on
when it's necessary to compromise. --Larry Wall
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Janne Johansson]

Den mån 29 jan. 2024 kl 10:38 skrev Eugen Block :
>
> Ah, you probably have dedicated RGW servers, right?

They are VMs, but yes.

-- 
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-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Eugen Block]

Ah, you probably have dedicated RGW servers, right?

Zitat von Janne Johansson :


Den mån 29 jan. 2024 kl 09:35 skrev Eugen Block :
 But your (cephadm managed) cluster will

complain about "stray daemons". There doesn't seem to be a way to
deploy rgw daemons manually with the cephadm tool so it wouldn't be
stray. Is there a specific reason not to use the orchestrator for rgw
deployment?

@Janne: how do you deal with the stray daemons?


We don't get that problem at all. We do all installs 100% manually
(via ansible but still)
and don't see this.

--
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-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Janne Johansson]

Den mån 29 jan. 2024 kl 09:35 skrev Eugen Block :
 But your (cephadm managed) cluster will
> complain about "stray daemons". There doesn't seem to be a way to
> deploy rgw daemons manually with the cephadm tool so it wouldn't be
> stray. Is there a specific reason not to use the orchestrator for rgw
> deployment?
>
> @Janne: how do you deal with the stray daemons?

We don't get that problem at all. We do all installs 100% manually
(via ansible but still)
and don't see this.

-- 
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-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Eugen Block]

Good morning,

Janne was a bit quicker than me, so I'll skip my short instructions  
how to deploy it manually. But your (cephadm managed) cluster will  
complain about "stray daemons". There doesn't seem to be a way to  
deploy rgw daemons manually with the cephadm tool so it wouldn't be  
stray. Is there a specific reason not to use the orchestrator for rgw  
deployment?


@Janne: how do you deal with the stray daemons?

Zitat von Jan Kasprzak :


Hi all,

how can radosgw be deployed manually? For Ceph cluster deployment,
there is still (fortunately!) a documented method which works flawlessly
even in Reef:

https://docs.ceph.com/en/latest/install/manual-deployment/#monitor-bootstrapping

But as for radosgw, there is no such description, unless I am missing
something. Even going back to the oldest docs still available at
docs.ceph.com (mimic), the radosgw installation is described
only using ceph-deploy:

https://docs.ceph.com/en/mimic/install/install-ceph-gateway/

Is it possible to install a new radosgw instance manually?
If so, how can I do it?

Thanks!

-Yenya

--
| Jan "Yenya" Kasprzak  |
| https://www.fi.muni.cz/~kas/GPG: 4096R/A45477D5 |
We all agree on the necessity of compromise. We just can't agree on
when it's necessary to compromise. --Larry Wall
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io



___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: RadosGW manual deployment

[Janne Johansson]

Den mån 29 jan. 2024 kl 08:11 skrev Jan Kasprzak :
>
> Hi all,
>
> how can radosgw be deployed manually? For Ceph cluster deployment,
> there is still (fortunately!) a documented method which works flawlessly
> even in Reef:
>
> https://docs.ceph.com/en/latest/install/manual-deployment/#monitor-bootstrapping
>
> But as for radosgw, there is no such description, unless I am missing
> something. Even going back to the oldest docs still available at
> docs.ceph.com (mimic), the radosgw installation is described
> only using ceph-deploy:
>
> https://docs.ceph.com/en/mimic/install/install-ceph-gateway/
>
> Is it possible to install a new radosgw instance manually?
> If so, how can I do it?

We are doing it, and I found the same docs issue recently, so Zac
pushed me to provide a skeleton (at least) for such a page. I have
recently made a quincy cluster manual install with RGWs so I will
condense what I did to something that can be used for docs later on
(I'll leave it to Zac to format and merge).

Really short version for you:
Install radosgw debs/rpms on the rgw box(es)

On one of the mons or a box with admin ceph auth run
   ceph auth get-or-create client.short-hostname-of-rgw mon 'allow rw'
osd 'allow rwx'
On each of the rgw box(es)
  create a ceph-user owned dir, for instance like this
  install -d -o ceph -g ceph /var/lib/ceph/radosgw/ceph-$(hostname -s)
  inside this dir, put the key (or the first two lines of it) you got
from the above ceph auth get-or-create
  vi /var/lib/ceph/radosgw/ceph-$(hostname -s)/keyring
  Figure out what URL rgw should answer to and all that in the config
parts, but that would be the same
  for manual and ceph-adm/orchestrated installs.
  and now you should be able to start the service with
  systemctl start ceph-radosgw@$(hostname -s).service

The last part may or may not act up a bit due to two things, one is
that it may have tried starting lots of times after the deb/rpm got
installed, but long before you added they usable key for it, so doing
a slight boxing match with systemd might be in order, to stop the
service, reset-failed on the service and then restarting it. (and
check that it is enabled, so it starts on next boot also)

Secondly, I also tend to run into this issue* where rgw (and other
parts of ceph!) can't create pools if they don't specify PG numbers,
which rgw doesn't do any longer, and if you get this error, you end up
having to create all the pools manually yourself (from a mon/admin
host or the rgw, but doing it from the rgw requires a lot more
specifying username and keyfile locations than the default admin-key
hosts)

*) https://tracker.ceph.com/issues/62770
   This ticket has a VERY SIMPLE method of testing if ceph versions
has this problem or not, just
   run "ceph osd pool create some-name" and see how it fails unless
you add a number behind
   it or not.

   The help is quite clear that all other parameters are meant to be optional:

osd pool create  [] []
[] [] []
[] [] []
[] [] [--bulk]
[] [] :  create pool



--
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-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Eugen Block]

Hi,

I checked our environment (Nautilus) where I enabled the RGW dashboard  
integration. Please note that we don't use RGW ourselves heavily and I  
don't have access to our customer's RGWs, so this might look  
differently for an actual prod environment. Anyway, to get it up and  
running it could help. Here is the ceph.conf excerpt:



[client.rgw.rgwhost01]
host = rgwhost01.example.com
rgw_dns_name = rgwhost01.example.com
rgw_frontends = civetweb port=7480


And this is my dashboard config:

---snip---
ceph dashboard get-rgw-api-host
rgwhost01.example.com

ceph dashboard get-rgw-api-port
7480

ceph dashboard get-rgw-api-scheme
http

ceph dashboard get-rgw-api-ssl-verify
False

ceph dashboard get-rgw-api-access-key


ceph dashboard get-rgw-api-secret-key


ceph dashboard get-rgw-api-admin-resource
admin

radosgw-admin user list
[
"admin",
"eblock"
]
---snip---

Note that the admin user has the "--system" flag. Also worth noting  
that it only worked when host, rgw_dns_name and get-rgw-api-host were  
identical. I can't tell what role the rgw_dns_name plays in all that,  
though. But this is a setup that works for me.


Regards,
Eugen



Zitat von "Francesco Piraneo G." :


Hi Eugen,

1. I'm running on a test cluster manually installed under debian 10;

2. No container at all;

3. To install rados gateway I followed instructions here:  
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/installation_guide_for_red_hat_enterprise_linux/manually-installing-ceph-object-gateway


4. Following the instructions in 3. everything run fine if the  
gateway is installed on the mon1 host;


5. If i follow the same instructions in 3. to install the gateway on  
a different machine, rados gateway run, can be queried by a web  
browser (that's mean: is online and listening) but cannot be  
interfaced with dashboard;


6. rgw_dns_name! Cool question! If you follow what indicated on the  
link in 3.:


rgw dns name = .example.com
Where  is a short host name of the gateway node. To  
view the short host name, use the hostname -s command.


But if you go to  
https://docs.ceph.com/en/latest/radosgw/config-ref/#confval-rgw_dns_name:


rgw_dns_name

The DNS name of the served domain. See also the hostnames setting  
within regions.



So: I have to indicate the hostname or the DNS (name or address) for  
the domain?



I think 99% of the confusion is due to VERY POOR documentation!!


Thanks for help.

Francesco


Il 01.09.21 14:14, Eugen Block ha scritto:
That basically was my check list, it was all I had to do in my lab  
to set it up. The guide to setup a RGW manually refers to  
non-containerized environments, did you "adopt" it with cephadm or  
is it still running outside of a container?
You wrote that you switched the RGW host from MON, I think it would  
help if you shared the steps you did to create and configure the  
RGW as well as the process to move it to a different host. Is the  
"rgw_dns_name" set in the ceph.conf (if it's non-container)? Does  
it resolve properly? Without knowing the details of your setup it's  
difficult to help.




___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Francesco Piraneo G.]

Il 02.09.21 17:18, Ernesto Puerta ha scritto:


I wanted to point out the fact that you were checking docs from 3 different
Ceph releases: master, pacific and nautilus (RH Ceph 3.x), and that
probably wouldn't help to properly set up your environment.



Hi Ernesto,

I wanted to point out the fact that:

1. as part of RedHat you have access to information that we don't, so 
you can help me to understand what's happening;


2. as part of RedHat you can improve your document on both ceph and 
RedHat site;


3. If I'm mixing documents between three sources is because there is no 
an comprehensive document to perform a task: all three are fairly 
incomplete; also on the ceph dashboard if I click the link that it's 
supposed to help me, what I get is an outdated document that is not 
applicable!


Once again I'm not speaking with a bunch of passionate programmers that 
put their effort to buildup a better world, but with a company with a 
"Net income    US$434 million (2018)"


Regards.

Francesco

___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Marc]

> Once again I'm not speaking with a bunch of passionate programmers that
> put their effort to buildup a better world, but with a company with a
> "Net income    US$434 million (2018)"
> 

Yes, I also had this argument and point of view a few years ago. I can remember 
the guys from openldap sort of ridiculing redhat competences, at that time I 
just ignored their remarks. But now I have seen how 'clueless' a redhat senior 
software engineer can be, with working on this ceph-csi project. I would state 
their senior title is only related to age ;)
I guess this is sort of a sign of the times. I have also been surprised about 
how ‘badly’ adobe is developing magento 2.x, compared to the 1.9 version. It is 
almost like it is part of big organizations opensource strategy, no obligations 
on any aspect.
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Ernesto Puerta]

Hi Francesco!

I wanted to point out the fact that you were checking docs from 3 different
Ceph releases: master, pacific and nautilus (RH Ceph 3.x), and that
probably wouldn't help to properly set up your environment.

Under what kind of license would contributers make such changes? Would eg.
> this license prevent RedHat from ever putting these pages behind a login?
>

Marc, if I'm not wrong, Ceph documentation is licensed under CC-BY-SA-3.0 (
https://github.com/ceph/ceph/blob/27faeaf129b3fa1c87dfdc957d8692efd2010d5e/COPYING#L21-L23
).

Kind Regards,
Ernesto


On Wed, Sep 1, 2021 at 11:08 PM Marc  wrote:

>
>
> >
> > Il 01.09.21 18:36, Ernesto Puerta ha scritto:
> > > Hi Francesco,
> > >
> > > I think it's not helping that you're checking documentation from
> > > different sources (upstream, Red Hat) and versions (master, pacific,
> > > nautilus). I'd suggest you stick to the docs from the Ceph release
> > > you're running (e.g.: https://docs.ceph.com/en/pacific/
> > >  for Pacific/16.2.x). And if you
> > > detect any omissions or mistakes there, feel free to raise the issue
> > > (or you may also fix it yourself: since every doc page has an "Edit"
> > > link that allows you to contribute the fix).
> > >
>
> Under what kind of license would contributers make such changes? Would eg.
> this license prevent RedHat from ever putting these pages behind a login?
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Francesco Piraneo G.]

Hola Ernesto!

I need to be clear: I'm just a beginner trying to make order and develop 
a manual deployment procedures; I've not a RedHat engineer expertise to 
edit or improve official documentation; I'm going to develop mine and 
when I feel it reliable enough I'll publish on my website hoping will 
help someone, but for sure not editing the main documentation; again I'm 
not so expert to take such responsibility.


But you can help to:

a. improve official documentation based on my feedback and

b. helping me trying to figure out what's happening on my fully 
virtualized cluster (and improve documentation).


Thank you for your help!

Francesco


Il 01.09.21 18:36, Ernesto Puerta ha scritto:

Hi Francesco,

I think it's not helping that you're checking documentation from 
different sources (upstream, Red Hat) and versions (master, pacific, 
nautilus). I'd suggest you stick to the docs from the Ceph release 
you're running (e.g.: https://docs.ceph.com/en/pacific/ 
 for Pacific/16.2.x). And if you 
detect any omissions or mistakes there, feel free to raise the issue 
(or you may also fix it yourself: since every doc page has an "Edit" 
link that allows you to contribute the fix).


Kind Regards,
Ernesto
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Marc]

> 
> Il 01.09.21 18:36, Ernesto Puerta ha scritto:
> > Hi Francesco,
> >
> > I think it's not helping that you're checking documentation from
> > different sources (upstream, Red Hat) and versions (master, pacific,
> > nautilus). I'd suggest you stick to the docs from the Ceph release
> > you're running (e.g.: https://docs.ceph.com/en/pacific/
> >  for Pacific/16.2.x). And if you
> > detect any omissions or mistakes there, feel free to raise the issue
> > (or you may also fix it yourself: since every doc page has an "Edit"
> > link that allows you to contribute the fix).
> >

Under what kind of license would contributers make such changes? Would eg. this 
license prevent RedHat from ever putting these pages behind a login?
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Francesco Piraneo G.]

Hi Eugen,

1. I'm running on a test cluster manually installed under debian 10;

2. No container at all;

3. To install rados gateway I followed instructions here: 
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/installation_guide_for_red_hat_enterprise_linux/manually-installing-ceph-object-gateway


4. Following the instructions in 3. everything run fine if the gateway 
is installed on the mon1 host;


5. If i follow the same instructions in 3. to install the gateway on a 
different machine, rados gateway run, can be queried by a web browser 
(that's mean: is online and listening) but cannot be interfaced with 
dashboard;


6. rgw_dns_name! Cool question! If you follow what indicated on the link 
in 3.:


rgw dns name = .example.com
Where  is a short host name of the gateway node. To 
view the short host name, use the hostname -s command.


But if you go to 
https://docs.ceph.com/en/latest/radosgw/config-ref/#confval-rgw_dns_name:


rgw_dns_name

The DNS name of the served domain. See also the hostnames setting within 
regions.



So: I have to indicate the hostname or the DNS (name or address) for the 
domain?



I think 99% of the confusion is due to VERY POOR documentation!!


Thanks for help.

Francesco


Il 01.09.21 14:14, Eugen Block ha scritto:
That basically was my check list, it was all I had to do in my lab to 
set it up. The guide to setup a RGW manually refers to 
non-containerized environments, did you "adopt" it with cephadm or is 
it still running outside of a container?
You wrote that you switched the RGW host from MON, I think it would 
help if you shared the steps you did to create and configure the RGW 
as well as the process to move it to a different host. Is the 
"rgw_dns_name" set in the ceph.conf (if it's non-container)? Does it 
resolve properly? Without knowing the details of your setup it's 
difficult to help. 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Ernesto Puerta]

Hi Francesco,

I think it's not helping that you're checking documentation from different
sources (upstream, Red Hat) and versions (master, pacific, nautilus). I'd
suggest you stick to the docs from the Ceph release you're running (e.g.:
https://docs.ceph.com/en/pacific/ for Pacific/16.2.x). And if you detect
any omissions or mistakes there, feel free to raise the issue (or you may
also fix it yourself: since every doc page has an "Edit" link that allows
you to contribute the fix).

Kind Regards,
Ernesto


On Wed, Sep 1, 2021 at 3:56 PM Francesco Piraneo G. 
wrote:

> Hi Eugen,
>
> 1. I'm running on a test cluster manually installed under debian 10;
>
> 2. No container at all;
>
> 3. To install rados gateway I followed instructions here:
>
> https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/installation_guide_for_red_hat_enterprise_linux/manually-installing-ceph-object-gateway
>
> 4. Following the instructions in 3. everything run fine if the gateway
> is installed on the mon1 host;
>
> 5. If i follow the same instructions in 3. to install the gateway on a
> different machine, rados gateway run, can be queried by a web browser
> (that's mean: is online and listening) but cannot be interfaced with
> dashboard;
>
> 6. rgw_dns_name! Cool question! If you follow what indicated on the link
> in 3.:
>
> rgw dns name = .example.com
> Where  is a short host name of the gateway node. To
> view the short host name, use the hostname -s command.
>
> But if you go to
> https://docs.ceph.com/en/latest/radosgw/config-ref/#confval-rgw_dns_name:
>
> rgw_dns_name
>
> The DNS name of the served domain. See also the hostnames setting within
> regions.
>
>
> So: I have to indicate the hostname or the DNS (name or address) for the
> domain?
>
>
> I think 99% of the confusion is due to VERY POOR documentation!!
>
>
> Thanks for help.
>
> Francesco
>
>
> Il 01.09.21 14:14, Eugen Block ha scritto:
> > That basically was my check list, it was all I had to do in my lab to
> > set it up. The guide to setup a RGW manually refers to
> > non-containerized environments, did you "adopt" it with cephadm or is
> > it still running outside of a container?
> > You wrote that you switched the RGW host from MON, I think it would
> > help if you shared the steps you did to create and configure the RGW
> > as well as the process to move it to a different host. Is the
> > "rgw_dns_name" set in the ceph.conf (if it's non-container)? Does it
> > resolve properly? Without knowing the details of your setup it's
> > difficult to help.
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Francesco Piraneo G.]

Hi Eugen,

thank you for your answer; I think that the ceph orch apply rgw 
pacific-rgw is to deploy the rados gateway on the gateway machine, that 
I did manually.


However checking all the "set-rgw-api" values that conforms to my 
installation and applying all the radosgw-admin setup you indicated lead 
me no results: Always as the beginning


The wrong must be somewhere else...

Do you have a checklist?

Francesco


Il 31.08.21 14:53, Eugen Block ha scritto:
How exactly did you create the rgw(s), realms, users etc.? I have 
single node (pacific) where connecting the dashboard worked just fine.

Basically this is what I did:

# create realm, zonegroup, zone
radosgw-admin realm create --rgw-realm=pacific-realm --default
radosgw-admin zonegroup create --rgw-zonegroup=europe-zg --master 
--default
radosgw-admin zone create --rgw-zone=europe-zone 
--rgw-zonegroup=europe-zg --master --default

radosgw-admin period update --rgw-realm=pacific-realm --commit

# create a user (the dashboard needs one)
radosgw-admin user create --uid=admin --display-name=admin --system 
--access-key=admin --secret=admin


# apply rgw deployment
pacific:~ # ceph orch apply rgw pacific-rgw --realm=pacific-realm 
--zone=europe-zone --placement=1



Then the dashboard was configured as follows:

ceph dashboard set-rgw-api-ssl-verify false
ceph dashboard set-rgw-api-user-id admin
ceph dashboard set-rgw-api-access-key -i /tmp/rgw-api-access-key.txt
ceph dashboard set-rgw-api-secret-key -i /tmp/rgw-api-access-key.txt
ceph dashboard set-rgw-api-host my-host


I think that was it, I just can't create a bucket yet but I didn't 
check yet. 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Eugen Block]

That basically was my check list, it was all I had to do in my lab to  
set it up. The guide to setup a RGW manually refers to  
non-containerized environments, did you "adopt" it with cephadm or is  
it still running outside of a container?
You wrote that you switched the RGW host from MON, I think it would  
help if you shared the steps you did to create and configure the RGW  
as well as the process to move it to a different host. Is the  
"rgw_dns_name" set in the ceph.conf (if it's non-container)? Does it  
resolve properly? Without knowing the details of your setup it's  
difficult to help.



Zitat von "Francesco Piraneo G." :


Hi Eugen,

thank you for your answer; I think that the ceph orch apply rgw  
pacific-rgw is to deploy the rados gateway on the gateway machine,  
that I did manually.


However checking all the "set-rgw-api" values that conforms to my  
installation and applying all the radosgw-admin setup you indicated  
lead me no results: Always as the beginning


The wrong must be somewhere else...

Do you have a checklist?

Francesco


Il 31.08.21 14:53, Eugen Block ha scritto:
How exactly did you create the rgw(s), realms, users etc.? I have  
single node (pacific) where connecting the dashboard worked just  
fine.

Basically this is what I did:

# create realm, zonegroup, zone
radosgw-admin realm create --rgw-realm=pacific-realm --default
radosgw-admin zonegroup create --rgw-zonegroup=europe-zg --master --default
radosgw-admin zone create --rgw-zone=europe-zone  
--rgw-zonegroup=europe-zg --master --default

radosgw-admin period update --rgw-realm=pacific-realm --commit

# create a user (the dashboard needs one)
radosgw-admin user create --uid=admin --display-name=admin --system  
--access-key=admin --secret=admin


# apply rgw deployment
pacific:~ # ceph orch apply rgw pacific-rgw --realm=pacific-realm  
--zone=europe-zone --placement=1



Then the dashboard was configured as follows:

ceph dashboard set-rgw-api-ssl-verify false
ceph dashboard set-rgw-api-user-id admin
ceph dashboard set-rgw-api-access-key -i /tmp/rgw-api-access-key.txt
ceph dashboard set-rgw-api-secret-key -i /tmp/rgw-api-access-key.txt
ceph dashboard set-rgw-api-host my-host


I think that was it, I just can't create a bucket yet but I didn't  
check yet.




___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Eugen Block]

How exactly did you create the rgw(s), realms, users etc.? I have  
single node (pacific) where connecting the dashboard worked just fine.

Basically this is what I did:

# create realm, zonegroup, zone
radosgw-admin realm create --rgw-realm=pacific-realm --default
radosgw-admin zonegroup create --rgw-zonegroup=europe-zg --master --default
radosgw-admin zone create --rgw-zone=europe-zone  
--rgw-zonegroup=europe-zg --master --default

radosgw-admin period update --rgw-realm=pacific-realm --commit

# create a user (the dashboard needs one)
radosgw-admin user create --uid=admin --display-name=admin --system  
--access-key=admin --secret=admin


# apply rgw deployment
pacific:~ # ceph orch apply rgw pacific-rgw --realm=pacific-realm  
--zone=europe-zone --placement=1



Then the dashboard was configured as follows:

ceph dashboard set-rgw-api-ssl-verify false
ceph dashboard set-rgw-api-user-id admin
ceph dashboard set-rgw-api-access-key -i /tmp/rgw-api-access-key.txt
ceph dashboard set-rgw-api-secret-key -i /tmp/rgw-api-access-key.txt
ceph dashboard set-rgw-api-host my-host


I think that was it, I just can't create a bucket yet but I didn't check yet.


Zitat von "Francesco Piraneo G." :


Hi Eugen,

everything worked fine on my test until I decided to move the RADOS  
gateway under a different host than mon. In such case the dashboard  
is no longer able to find the RADOS gateway daemon; on my dashboard  
I have this message:


The Object Gateway Service is not configured
No RGW daemon found with user-defined host: s3.anonicloud.test, port: 80


Please consider the following:

- From monitor machine raising a curl to this url I get the s3  
welcome string:


# curl s3.anonicloud.test
xmlns="http://s3.amazonaws.com/doc/2006-03-01/;>anonymous


So this lead me to think that s3 gateway is installed, running and  
reachable from the mon machine;


$ ceph dashboard set-rgw-api-host 
$ ceph dashboard set-rgw-api-port 
$ ceph dashboard set-rgw-api-scheme 

Has been set correctly because on the error string I read where the  
dashboard can find the s3 gateway; scheme is really http (checked  
querying with get-rgw-api-scheme).


Any clue / suggestion is welcome.

Francesco



Il 24.08.21 11:22, Eugen Block ha scritto:

Hi,

I assume that the "latest" docs are already referring to quincy, if  
you check the pacific docs  
(https://docs.ceph.com/en/pacific/mgr/dashboard/) that command is  
not mentioned. So you'll probably have to use the previous method  
of configuring the credentials.


Regards,
Eugen




___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Francesco Piraneo G.]

Hi Eugen,

everything worked fine on my test until I decided to move the RADOS 
gateway under a different host than mon. In such case the dashboard is 
no longer able to find the RADOS gateway daemon; on my dashboard I have 
this message:


The Object Gateway Service is not configured
No RGW daemon found with user-defined host: s3.anonicloud.test, port: 80


Please consider the following:

- From monitor machine raising a curl to this url I get the s3 welcome 
string:


# curl s3.anonicloud.test
xmlns="http://s3.amazonaws.com/doc/2006-03-01/;>anonymous


So this lead me to think that s3 gateway is installed, running and 
reachable from the mon machine;


$ ceph dashboard set-rgw-api-host 
$ ceph dashboard set-rgw-api-port 
$ ceph dashboard set-rgw-api-scheme 

Has been set correctly because on the error string I read where the 
dashboard can find the s3 gateway; scheme is really http (checked 
querying with get-rgw-api-scheme).


Any clue / suggestion is welcome.

Francesco



Il 24.08.21 11:22, Eugen Block ha scritto:

Hi,

I assume that the "latest" docs are already referring to quincy, if 
you check the pacific docs 
(https://docs.ceph.com/en/pacific/mgr/dashboard/) that command is not 
mentioned. So you'll probably have to use the previous method of 
configuring the credentials.


Regards,
Eugen 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: radosgw manual deployment

[Eugen Block]

Hi,

I assume that the "latest" docs are already referring to quincy, if  
you check the pacific docs  
(https://docs.ceph.com/en/pacific/mgr/dashboard/) that command is not  
mentioned. So you'll probably have to use the previous method of  
configuring the credentials.


Regards,
Eugen


Zitat von "Francesco Piraneo G." :


Good morning all,

I deployed my radosgw on first monitor node on my test cluster  
following the instructions here:


https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/installation_guide_for_red_hat_enterprise_linux/manually-installing-ceph-object-gateway

However the related "Object gateway" page on ceph dashboard are  
still not accessible - as I understood because the related  
administrator profile has not been created. The related warning  
message on ceph dashboard point to this page:


https://docs.ceph.com/en/latest/mgr/dashboard/#enabling-the-object-gateway-management-frontend

So here is my question:

"When RGW is deployed with cephadm, the RGW credentials used by the  
dashboard will be automatically configured. You can also manually  
force the credentials to be set up with:


$ ceph dashboard set-rgw-credentials"

Unfortunately when I raise the indicated command to generate the  
dashboard admin credentials it seems that this command doesn't exists:


[root@mon1 ~]# ceph dashboard set-rgw-credentials
no valid command found; 10 closest matches:
dashboard set-jwt-token-ttl 
dashboard get-jwt-token-ttl
dashboard create-self-signed-cert
dashboard grafana dashboards update
dashboard get-account-lockout-attempts
dashboard set-account-lockout-attempts 
dashboard reset-account-lockout-attempts
dashboard get-alertmanager-api-host
dashboard set-alertmanager-api-host 
dashboard reset-alertmanager-api-host
Error EINVAL: invalid command

Any help is appreciated here.

Francesco




___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io