During CDM on Wednesday I suggested that ceph-daemon should probably be renamed before octopus (and before the name sticks). In speech "ceph daemon" is confusing, and the name doesn't really reflect what it is: a user-facing tool - to bootstrap a new cluster, - launch a (containerized) shell, - enter an existing daemon container, - tail a daemon's log, or - adopt a daemon deployed with a legacy tool (ceph-deploy, ceph-ansible, etc) into a ceph-daemon style container - remove all trace of a cluster from the localhost, and an internal tool used by ssh-orch to - deploy or remove a container running a ceph daemon - start, stop, or update an existing container - run ceph-volume (to gather device inventory, create osds, zap, etc.) - gather a host inventory of services (containers) The original tool was more like "ceph daemon tool" but it was shortened to ceph-daemon at the start. We voted on some alternatives here: https://pad.ceph.com/p/ceph-daemon-tool but the winner is currently 'cephctl' with is IMO a non-starteer. Usually 'ctl' utilities are for interacting with running systems/daemons via some runtime API--that's basically what the 'ceph' CLI utility is. ceph-daemon is more akin to kubeadm or ceph-deploy or something like that. So... I shortened/pruned the list again. Please weigh in. And if you have a bright idea for a better name, feel free to add it. Thanks! sage _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
