Project

General

Profile

Documentation #57596

MON Service

Added by Alex Karl 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/services
Target version:
-
% Done:

0%

Tags:
cephadm,mon
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Recently service specification using yaml has been introduced and the documentation has been added under https://docs.ceph.com/en/quincy/cephadm/services/?highlight=param_N%3A%20val_N#service-specification
But the documentation of the mon service has not been updated.
I am ,for example, a bit confused if the networks dictionary inside the service specification for the mon service would be the same as public_network config [[https://docs.ceph.com/en/latest/cephadm/services/mon/#designating-a-particular-subnet-for-monitors]]

History

#1 Updated by Ilya Dryomov about 2 months ago

  • Target version deleted (v17.2.4)

#2 Updated by Adam King about 2 months ago

the "networks" parameter inside the service spec is a separate thing from the public/cluster network. The public_network is mostly untouched by cephadm and is only used by cephadm when filtering hosts to place mon daemons on. The "networks" parameter in the spec is for which network we should bind to for services that need to bind to some network:port. From a code comment on the networks spec parameter

#: A list of network identities instructing the daemons to only bind
#: on the particular networks in that list. In case the cluster is distributed
#: across multiple networks, you can add multiple networks. See
#: :ref:`cephadm-monitoring-networks-ports`,
#: :ref:`cephadm-rgw-networks` and :ref:`cephadm-mgr-networks`.

Also available in: Atom PDF