Semi correct, and semi incorrect IMHO. Orchestration enables automation that's very difficult to do outside of containers. This includes stuff like safety checks that can be manually done, but difficult to always get right, 100% of the time by a person. As well as automated upgrade procedures(similar risk), best practices for setting up security(similar risk of misconfiguration) best practice monitoring, etc etc. You can do that all your self, but its a lot of effort and a lot of risk getting it wrong at least some of the time. In my experience, learning to deal with its quirks/different ways of doing things is less effort/risk then ensuring everything else is done properly, manually. Just my $0.02. Thanks, Kevin ________________________________________ From: Ranjan Ghosh <ghosh@xxxxxx> Sent: Wednesday, September 14, 2022 6:57 AM To: Eugen Block Cc: ceph-users@xxxxxxx Subject: Re: Manual deployment, documentation error? Check twice before you click! This email originated from outside PNNL. 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ceph.com%2Fen%2Fquincy%2Fcephadm%2Finstall%2F&data=05%7C01%7Ckevin.fox%40pnnl.gov%7C3841486eb57b478cc7e708da96595e55%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C0%7C637987607971914543%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=s6iuR1GoJOaB9s4sjXHWyiggeINnlzJEd3Klu7IwwEM%3D&reserved=0 > [2] > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ceph.com%2Fen%2Fquincy%2Finstall%2Fmanual-deployment%2F%23manager-daemon-configuration&data=05%7C01%7Ckevin.fox%40pnnl.gov%7C3841486eb57b478cc7e708da96595e55%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C0%7C637987607971914543%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=haSRpvpmwRTXPJas%2F39OaUGCtc4KWeD0%2BOjqK6IJrxw%3D&reserved=0 > > > Zitat von Ranjan Ghosh <ghosh@xxxxxx>: > >> Hi all, >> >> I think there's an error in the documentation: >> >> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ceph.com%2Fen%2Fquincy%2Finstall%2Fmanual-deployment%2F&data=05%7C01%7Ckevin.fox%40pnnl.gov%7C3841486eb57b478cc7e708da96595e55%7Cd6faa5f90ae240338c0130048a38deeb%7C0%7C0%7C637987607971914543%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5qCT4KhAkH2RuIAftt7NVjMEYUznzE4DHmQZQRQwbrg%3D&reserved=0 >> >> 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
 |