Hi Ranjan, I don't want to intervene but I can testify that docker doesn't make the installation for a 3-node cluster overkill. I to have a 3-node cluster (to be expanded soon to 4 nodes). Cons of using cephadm (and thus docker): - You need to learn the basics of docker Pros: + cephadm works very easy. The time you spend on learing docker will be easely compensated by the small time you need to learn cephadm + Upgrading a manual installation is very tricky! Cephadm manages upgrades of ceph automatically. You only need to give the command (done it already two times). + If you need to upgrade your OS, will the manual installation still function? With cephadm the ceph processes inside the docker containers experience minimal impact with the upgrade of the os (dind't do an OS upgrade yet, but had this issue with other applications). Greetings, Dominique. > -----Oorspronkelijk bericht----- > Van: Ranjan Ghosh <ghosh@xxxxxx> > Verzonden: woensdag 14 september 2022 15:58 > Aan: Eugen Block <eblock@xxxxxx> > CC: ceph-users@xxxxxxx > Onderwerp: Re: Manual deployment, documentation error? > > Hi Eugen, > > thanks for your answer. I don't want to use the cephadm tool because it > needs docker. I don't like it because it's total overkill for our small 3-node > cluster. I'd like to avoid the added complexity, added packages, everything. > Just another thing I have to learn in detaisl about in case things go wrong. > > The monitor service is running but the logs don't say anything :-( Okay, but at > least I know now that it should work in principle without the mgr. > > Thank you > Ranjan > > Eugen Block schrieb am 14.09.2022 um 15:26: > > Hi, > > > >> Im currently trying the manual deployment because ceph-deploy > >> unfortunately doesn't seem to exist anymore and under step 19 it says > >> you should run "sudo ceph -s". That doesn't seem to work. I guess > >> this is because the manager service isn't yet running, right? > > > > ceph-deploy was deprecated quite some time ago, if you want to use a > > deployment tool try cephadm [1]. The command 'ceph -s' is not > > depending on the mgr but the mon service. So if that doesn't work you > > need to check the mon logs and see if the mon service is up and running. > > > >> Interestingly the screenshot under step 19 says "mgr: mon- > >> node1(active)". If you follow the documentation step by step, there's > >> no mention of the manager node up until that point. > > > > Right after your mentioned screenshot there's a section for the mgr > > service [2]. > > > > Regards, > > Eugen > > > > [1] https://docs.ceph.com/en/quincy/cephadm/install/ > > [2] > > https://docs.ceph.com/en/quincy/install/manual-deployment/#manager- > dae > > mon-configuration > > > > > > Zitat von Ranjan Ghosh <ghosh@xxxxxx>: > > > >> Hi all, > >> > >> I think there's an error in the documentation: > >> > >> https://docs.ceph.com/en/quincy/install/manual-deployment/ > >> > >> Im currently trying the manual deployment because ceph-deploy > >> unfortunately doesn't seem to exist anymore and under step 19 it says > >> you should run "sudo ceph -s". That doesn't seem to work. I guess > >> this is because the manager service isn't yet running, right? > >> > >> Interestingly the screenshot under step 19 says "mgr: mon- > >> node1(active)". If you follow the documentation step by step, there's > >> no mention of the manager node up until that point. > >> > >> Thank you / BR > >> Ranjan > >> > >> _______________________________________________ > >> ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an > >> email to ceph-users-leave@xxxxxxx > > > > > > > > _______________________________________________ > > ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an > > email to ceph-users-leave@xxxxxxx > > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email > to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx