projects / ceph.git / blame
| Commit | Line | Data |
|---|---|---|
| a4b75251 TL |
1 | .. _mgr-cephadm-mgr: |
| 2 | ||
| 3 | =========== | |
| 4 | MGR Service | |
| 5 | =========== | |
| 6 | ||
| 7 | The cephadm MGR service is hosting different modules, like the :ref:`mgr-dashboard` | |
| 8 | and the cephadm manager module. | |
| 9 | ||
| 10 | .. _cephadm-mgr-networks: | |
| 11 | ||
| 12 | Specifying Networks | |
| 13 | ------------------- | |
| 14 | ||
| 15 | The MGR service supports binding only to a specific IP within a network. | |
| 16 | ||
| 17 | example spec file (leveraging a default placement): | |
| 18 | ||
| 19 | .. code-block:: yaml | |
| 20 | ||
| 21 | service_type: mgr | |
| 22 | networks: | |
| 23 | - 192.169.142.0/24 | |
| 24 | ||
| 20effc67 TL |
25 | .. _cephadm_mgr_co_location: |
| 26 | ||
| a4b75251 TL |
27 | Allow co-location of MGR daemons |
| 28 | ================================ | |
| 29 | ||
| 30 | In deployment scenarios with just a single host, cephadm still needs | |
| 20effc67 TL |
31 | to deploy at least two MGR daemons in order to allow an automated |
| 32 | upgrade of the cluster. See ``mgr_standby_modules`` in | |
| a4b75251 TL |
33 | the :ref:`mgr-administrator-guide` for further details. |
| 34 | ||
| 20effc67 TL |
35 | See also: :ref:`cephadm_co_location`. |
| 36 | ||
| 37 | ||
| a4b75251 TL |
38 | Further Reading |
| 39 | =============== | |
| 40 | ||
| 41 | * :ref:`ceph-manager-daemon` | |
| 42 | * :ref:`cephadm-manually-deploy-mgr` | |
| 43 |