On Fri, 6 Dec 2019, Brad Hubbard wrote: > Tentacle? I rather like Tentacle, actually. One of the other things that has bugged me about this whole project is the ssh orchestrator name, and the combination of the two (ceph-dadmon + mgr/ssh? ssh-orch?). In reality, the two go together. Although in theory you could use most of ceph-daemon with a different orchestrator framework, in practice the bootstrap configures the ssh orch for you, and most of the rest of ceph-daemon is just an extension of mgr/ssh to run remotely. Renaming both mgr/ssh -> mgr/tentacle and /usr/bin/ceph-daemon -> /usr/bin/tentacle would solidify the idea that it's one thing, comparable to it's counterpart Rook in the kubernetes space. It would also get the 'ssh' out of the name, which is a bit misleading (and doesn't really sell its value). We use ssh to run ceph-daemon on remote nodes, but this could be swapped out for something else if the need arose. Or perhaps, in the spirit of tendrl, we should do tentacl? :) Otherwise, ceph-adm is currently in the lead. sage > > On Fri, Dec 6, 2019 at 10:25 AM Matthew Oliver <matt@xxxxxxxxxxxxx> wrote: > > > > I like ceph-manage or something like that, however that's probably too close to ceph-mgr which could get very confusing. > > > > Looking at thesaurus.com for manage, there are some other words that could be interesting (there is a bunch so I'll only name a few): > > > > - administer (so adm is a good candidate, which I know is already on the list) > > - conduct > > - govern > > - handle > > - maintain > > - operate > > - oversee > > - run > > - supervise > > - command > > - designate > > - execute > > - instruct > > - steer > > > > Matt > > > > On Fri, Dec 6, 2019 at 10:32 AM Sage Weil <sweil@xxxxxxxxxx> wrote: > >> > >> 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 > > > > _______________________________________________ > > Dev mailing list -- dev@xxxxxxx > > To unsubscribe send an email to dev-leave@xxxxxxx > > > > -- > Cheers, > Brad > > _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
