Bobcares

For every $500 you spend, we will provide you with a $500 credit on your account*

BLACK FRIDAY SPECIAL

*Get up to $4000, Offer valid till November 30th, 2024

For every $500 you spend, we will provide you with a $500 credit on your account*

BLACK FRIDAY SPECIAL

*Get up to $4000, Offer valid till November 30th, 2024

Automatically Deploys Ceph Monitors | How To?

by | Nov 30, 2022

Let’s see how Ceph automatically deploys monitors in this article. At Bobcares, with our Server Management Services, we can handle your server-related issues.

How Ceph automatically deploys monitors?

As the cluster expands, Ceph automatically deploys monitor daemons, and as the cluster contracts, Ceph automatically reduces them. The effective setting of the subnet is necessary for the seamless operation of this automated expansion and shrinking.

automatically deploys ceph monitors

When we add additional hosts to the cluster, Cephadm automatically installs up to five monitor daemons if the nodes or the entire cluster is situated on a single subnet. On the new hosts, it set up the monitor automatically. The additional hosts are located on the same subnet as the storage cluster’s bootstrapped host.

Cephadm can also grow and deploy monitors to adapt to changes in the storage cluster’s size.

Pre-requisites: Active Red Hat Ceph Storage cluster, Hosts added to the cluster.

Deployment methods

We can use the placement specification in the CLI for the setup process. We need to specify a different number to run a different number of monitors. The Ceph Orchestrator will choose hosts at random and deploy the monitor to them if we do not indicate the hosts to which the monitor should be deployed.

Firstly, we need to log into the Cephadm shell. Then we can use any of the below methods for the process.

1. We use the placement to deploy monitors on hosts. The syntax is as follows:

ceph orch apply mon --placement="HOST_NAME_1 HOST_NAME_2 HOST_NAME_3"

2. We use the placement to deploy a specific number of monitors on specific hosts with labels. Firstly, we must add the labels to the hosts using the below code:

ceph orch host label add HOSTNAME_1 LABEL

Then deploy daemons using the following code:

ceph orch apply mon --placement="HOST_NAME_1:mon HOST_NAME_2:mon HOST_NAME_3:mon"

3. Using placement, we deploy a specific number of monitors on specific hosts. The syntax is as follows:

ceph orch apply mon --placement="NUMBER_OF_DAEMONS HOST_NAME_1 HOST_NAME_2 HOST_NAME_3"

4. We can deploy monitor daemons randomly on the hosts in the storage cluster using the below code:

ceph orch apply mon NUMBER_OF_DAEMONS

Verification

1. We can list the service. For e.g.,

[ceph: root@host01 /]# ceph orch ls

2. We can also list the hosts, daemons, and processes using the below code:

ceph orch ps command line interface--daemon_type=DAEMON_NAME

[Looking for a solution to another query? We’re available 24/7.]

Conclusion

The article sums up the methods to create an automatic deployment of Ceph monitors using the command line interface.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF