Ceph » Orchestrator

https://docs.ceph.com/docs/master/mgr/orchestrator/#orchestrator-cli ??

Sebastian Wagner wrote:

https://docs.ceph.com/docs/master/mgr/orchestrator/#orchestrator-cli ??

That's a good find, but at the minimum we can make this text clearer:

A logical service, Typically comprised of multiple service instances on multiple hosts for HA

fs_name for mds type

rgw_zone for rgw type

ganesha_cluster_id for nfs type

and

A single instance of a service. Usually a daemon, but maybe not (e.g., might be a kernel service like LIO or knfsd or whatever)

This identifier should uniquely identify the instance

Let's define things for cephadm a bit more in detail:

• a service_type is something like mon, mgr, alertmanager etc.
• a service_id is the name of the service. Some services don't have names.
• a service_name is <service_type>.<service_id>
• a daemon_type is the same as the service_type
• a daemon_id is typically <service_id>.<hostname>.<random-string>. (Not the case for e.g. OSDs. OSDs are always called OSD.N)
• a daemon_name is <daemon_type>.<daemon_id>

While the previous comment has a technical definition of various terms, it doesn't make clear the difference between a "service" and a "daemon". This distinction is easy to understand, though:

A service (e.g. "osd service", "mon service", etc.) is a cluster-wide term meaning all daemons of a given type (e.g. "osd", "mon", etc.), no matter where they happen to be in the cluster.

A daemon (e.g. "osd daemon") is just that: an individual daemon supposed to be running on a cluster node.