Hi all, > My feeling is that there should be multiple "tracks" of documentation. > One cephadm track and one for all manual operations clearly separated. I would like to second that. I argued as well for this some time ago in the thread about containerised deployments. Documentation on ceph and documentation on cephadm need to be clearly and cleanly separated. A lot of clusters run bare metal or non-cephadm and if more and more cephadm commands creep into the ceph documentation, it will become a pain for many to read and decode it into actual ceph commands. Application ceph and orchestration cephadm are different things, so please keep them separate. They should, in fact, each have their own documentation project. Best regards, ================= Frank Schilder AIT Risø Campus Bygning 109, rum S14 ________________________________________ From: Robert Sander <r.sander@xxxxxxxxxxxxxxxxxxx> Sent: 24 August 2022 09:16:38 To: ceph-users@xxxxxxx Subject: Re: Ceph User Survey 2022 - Comments on the Documentation Am 23.08.22 um 18:40 schrieb John Zachary Dover: > "correct documentation, not the mix of out-dated and correct descriptions > and examples" This is also my biggest issue with the documentation. There is a nice chapter on how to deploy the cluster with cephadm and do some operations on it. But when you look at the other chapters for more information it seems like cephadm was never invented. My feeling is that there should be multiple "tracks" of documentation. One cephadm track and one for all manual operations clearly separated. Regards -- Robert Sander Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 220009 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin _______________________________________________ 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
 |