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 <kas@xxxxxxxxxx>:
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 <kas at {fi.muni.cz - work | yenya.net - private}> |
| 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@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
