> 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
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
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
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
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
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
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
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
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:
>
>
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
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
> 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
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.
>
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
>
> 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
> >
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:
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
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
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
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
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
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
22 matches
Mail list logo
