COMMANDSNEWStart deploying a new cluster and write a configuration file and keyring for it. It tries to copy ssh keys from admin node to gain passwordless ssh to monitor node(s), validates host IP, creates a cluster with a new initial monitor node or nodes for monitor quorum, a ceph configuration file, a monitor secret keyring and a log file for the new cluster. It populates the newly created Ceph configuration file with fsid of cluster, hostnames and IP addresses of initial monitor members under [global] section.
Usage:
ceph-deploy new [MON][MON...]
9 n4 y G, \- U! M" ^: t2 K6 c5 z! P- y2 P
Here, [MON] is the initial monitor hostname (short hostname i.e, hostname -s).
If more than one network interface is used, public network setting has to be added under [global] section of Ceph configuration file. If the public subnet is given, new command will choose the one IP from the remote host that exists within the subnet range. Public network can also be added at runtime using
--public-network option with the command as mentioned above.
2 y) z. V- h/ @. Q- cINSTALLInstall Ceph packages on remote hosts. As a first step it installs yum-plugin-priorities in admin and other nodes using passwordless ssh and sudo so that Ceph packages from upstream repository get more priority. It then detects the platform and distribution for the hosts and installs Ceph normally by downloading distro compatible packages if adequate repo for Ceph is already added. --release flag is used to get the latest release for installation. During detection of platform and distribution before installation, if it finds the distro.init to be sysvinit (Fedora, CentOS/RHEL etc), it doesn’t allow installation with custom cluster name and uses the default name ceph for the cluster.
If the user explicitly specifies a custom repo url with
--repo-url for installation, anything detected from the configuration will be overridden and the custom repository location will be used for installation of Ceph packages. If required, valid custom repositories are also detected and installed. In case of installation from a custom repo a boolean is used to determine the logic needed to proceed with a custom repo installation. A custom repo install helper is used that goes through config checks to retrieve repos (and any extra repos defined) and installs them. cd_conf is the object built from argparse that holds the flags and information needed to determine what metadata from the configuration is to be used.
A user can also opt to install only the repository without installing Ceph and its dependencies by using
--repo option.
Usage:
ceph-deploy install [HOST][HOST...]
+ E' }/ f9 Y! L
( @/ l0 I$ Y! X* L. [2 S( I4 NHere, [HOST] is/are the host node(s) where Ceph is to be installed.
An option --release is used to install a release known as CODENAME (default: firefly).
2 v5 b Z, |: a0 j# @
MDSDeploy Ceph mds on remote hosts. A metadata server is needed to use CephFS and the mds command is used to create one on the desired host node. It uses the subcommand create to do so. create first gets the hostname and distro information of the desired mds host. It then tries to read the bootstrap-mds key for the cluster and deploy it in the desired host. The key generally has a format of {cluster}.bootstrap-mds.keyring. If it doesn’t finds a keyring, it runs gatherkeys to get the keyring. It then creates a mds on the desired host under the path /var/lib/ceph/mds/ in /var/lib/ceph/mds/{cluster}-{name} format and a bootstrap keyring under /var/lib/ceph/bootstrap-mds/ in /var/lib/ceph/bootstrap-mds/{cluster}.keyring format. It then runs appropriate commands based on distro.init to start the mds.
Usage:
ceph-deploy mds create [HOST[:DAEMON-NAME]] [HOST[:DAEMON-NAME]...]
& x5 n( ]* i& q5 u N, v2 O9 c# p( J; N0 g0 C1 P
The [DAEMON-NAME] is optional.
/ z: V' N* b! Q+ g" XMONDeploy Ceph monitor on remote hosts. mon makes use of certain subcommands to deploy Ceph monitors on other nodes.
Subcommand create-initial deploys for monitors defined in mon initial members under [global] section in Ceph configuration file, wait until they form quorum and then gatherkeys, reporting the monitor status along the process. If monitors don’t form quorum the command will eventually time out.
Usage:
ceph-deploy mon create-initial
: g/ L5 w8 }6 P( z2 m6 l, }
0 D3 ~% B. T1 ^. i2 O, v" v @Subcommand create is used to deploy Ceph monitors by explicitly specifying the hosts which are desired to be made monitors. If no hosts are specified it will default to use the mon initial members defined under [global] section of Ceph configuration file. create first detects platform and distro for desired hosts and checks if hostname is compatible for deployment. It then uses the monitor keyring initially created using new command and deploys the monitor in desired host. If multiple hosts were specified during new command i.e, if there are multiple hosts in mon initial members and multiple keyrings were created then a concatenated keyring is used for deployment of monitors. In this process a keyring parser is used which looks for [entity] sections in monitor keyrings and returns a list of those sections. A helper is then used to collect all keyrings into a single blob that will be used to inject it to monitors with
--mkfs on remote nodes. All keyring files are concatenated to be in a directory ending with .keyring. During this process the helper uses list of sections returned by keyring parser to check if an entity is already present in a keyring and if not, adds it. The concatenated keyring is used for deployment of monitors to desired multiple hosts.
Usage:
ceph-deploy mon create [HOST] [HOST...]
7 E& h) \6 _& e+ h! X( h+ q4 X! j( u x! p
Here, [HOST] is hostname of desired monitor host(s).
Subcommand add is used to add a monitor to an existing cluster. It first detects platform and distro for desired host and checks if hostname is compatible for deployment. It then uses the monitor keyring, ensures configuration for new monitor host and adds the monitor to the cluster. If the section for the monitor exists and defines a monitor address that will be used, otherwise it will fallback by resolving the hostname to an IP. If
--address is used it will override all other options. After adding the monitor to the cluster, it gives it some time to start. It then looks for any monitor errors and checks monitor status. Monitor errors arise if the monitor is not added in mon initial members, if it doesn’t exist in monmap and if neither public_addr nor public_network keys were defined for monitors. Under such conditions, monitors may not be able to form quorum. Monitor status tells if the monitor is up and running normally. The status is checked by running ceph daemon mon.hostname mon_status on remote end which provides the output and returns a boolean status of what is going on. False means a monitor that is not fine even if it is up and running, while True means the monitor is up and running correctly.
Usage:
ceph-deploy mon add [HOST]ceph-deploy mon add [HOST] --address [IP]! M) H! {( ^; N1 h
0 U, r, X# A9 ~) y) @* w h
Here, [HOST] is the hostname and [IP] is the IP address of the desired monitor node. Please note, unlike other monsubcommands, only one node can be specified at a time.
Subcommand destroy is used to completely remove monitors on remote hosts. It takes hostnames as arguments. It stops the monitor, verifies if ceph-mon daemon really stopped, creates an archive directory mon-remove under /var/lib/ceph/, archives old monitor directory in {cluster}-{hostname}-{stamp} format in it and removes the monitor from cluster by running ceph remove...command.
Usage:
ceph-deploy mon destroy [HOST] [HOST...]& z2 T0 f) M) q1 G, D X# [
+ X# x1 T, d2 ?! q5 `
Here, [HOST] is hostname of monitor that is to be removed.
* ?" J4 u2 j; R6 u( |7 i0 gGATHERKEYSGather authentication keys for provisioning new nodes. It takes hostnames as arguments. It checks for and fetches client.admin keyring, monitor keyring and bootstrap-mds/bootstrap-osd keyring from monitor host. These authentication keys are used when new monitors/OSDs/MDS are added to the cluster.
Usage:
ceph-deploy gatherkeys [HOST] [HOST...]
0 x8 y# p3 @% X5 }3 T; t
! B+ `7 E3 x+ ]4 V( U8 dHere, [HOST] is hostname of the monitor from where keys are to be pulled.
. b( s7 [ X- j8 e7 kDISKManage disks on a remote host. It actually triggers the ceph-volume utility and its subcommands to manage disks.
Subcommand list lists disk partitions and Ceph OSDs.
Usage:
ceph-deploy disk list HOST
; d6 K# s* I4 z3 b _8 J
$ P- T! G \, E( X: iSubcommand zap zaps/erases/destroys a device’s partition table and contents. It actually uses ceph-volume lvm zap remotely, alternatively allowing someone to remove the Ceph metadata from the logical volume.
) f* Z1 o! l3 X& R" a& B+ D& e* EOSDManage OSDs by preparing data disk on remote host. osd makes use of certain subcommands for managing OSDs.
Subcommand create prepares a device for Ceph OSD. It first checks against multiple OSDs getting created and warns about the possibility of more than the recommended which would cause issues with max allowed PIDs in a system. It then reads the bootstrap-osd key for the cluster or writes the bootstrap key if not found. It then uses ceph-volume utility’s lvm createsubcommand to prepare the disk, (and journal if using filestore) and deploy the OSD on the desired host. Once prepared, it gives some time to the OSD to start and checks for any possible errors and if found, reports to the user.
Bluestore Usage:
ceph-deploy osd create --data DISK HOST9 p/ ^& _3 @* a, ?8 N
# N) j& i0 F% q$ H. KFilestore Usage:
ceph-deploy osd create --data DISK --journal JOURNAL HOST
6 g% s) a! N0 N( B$ g% e& O6 u a- o" R% r \/ n
Note
For other flags available, please see the man page or the –help menu on ceph-deploy osd create
( p5 M% e! ^# n7 {! YSubcommand list lists devices associated to Ceph as part of an OSD. It uses the ceph-volume lvm list output that has a rich output, mapping OSDs to devices and other interesting information about the OSD setup.
Usage:
ceph-deploy osd list HOST! @5 y0 O0 X% R+ H' Y& s3 q
7 \, V4 O+ n9 S/ L" s, B4 p; [$ ?
ADMINPush configuration and client.admin key to a remote host. It takes the {cluster}.client.admin.keyring from admin node and writes it under /etc/ceph directory of desired node.
Usage:
ceph-deploy admin [HOST] [HOST...]
. \( E9 l1 A7 A# @+ A8 d0 k. z# { M' {, \! N# L1 ^: O6 w
Here, [HOST] is desired host to be configured for Ceph administration.
+ s! m9 @3 _# [/ G" N
CONFIGPush/pull configuration file to/from a remote host. It uses push subcommand to takes the configuration file from admin host and write it to remote host under /etc/ceph directory. It uses pull subcommand to do the opposite i.e, pull the configuration file under /etc/ceph directory of remote host to admin node.
Usage:
ceph-deploy config push [HOST] [HOST...]ceph-deploy config pull [HOST] [HOST...]
) c( [* n5 f$ u4 O4 O# T% }6 r2 k: i, p& a' p# ~
Here, [HOST] is the hostname of the node where config file will be pushed to or pulled from.
0 U. S2 {3 z) p" o
UNINSTALLRemove Ceph packages from remote hosts. It detects the platform and distro of selected host and uninstalls Ceph packages from it. However, some dependencies like librbd1 and librados2 will not be removed because they can cause issues with qemu-kvm.
Usage:
ceph-deploy uninstall [HOST] [HOST...], E! b9 c9 i9 {) _2 E" N/ U" e5 G
7 a8 A( } J1 I9 S- QHere, [HOST] is hostname of the node from where Ceph will be uninstalled.
* @+ S$ f, f* G, P0 J1 D, H9 x5 QPURGERemove Ceph packages from remote hosts and purge all data. It detects the platform and distro of selected host, uninstalls Ceph packages and purges all data. However, some dependencies like librbd1 and librados2 will not be removed because they can cause issues with qemu-kvm.
Usage:
ceph-deploy purge [HOST] [HOST...]0 ~9 N4 s1 P( f# E% M
* c M( S) h% m" `
Here, [HOST] is hostname of the node from where Ceph will be purged.
9 p" T) V! z; M4 o
PURGEDATAPurge (delete, destroy, discard, shred) any Ceph data from /var/lib/ceph. Once it detects the platform and distro of desired host, it first checks if Ceph is still installed on the selected host and if installed, it won’t purge data from it. If Ceph is already uninstalled from the host, it tries to remove the contents of /var/lib/ceph. If it fails then probably OSDs are still mounted and needs to be unmounted to continue. It unmount the OSDs and tries to remove the contents of /var/lib/ceph again and checks for errors. It also removes contents of /etc/ceph. Once all steps are successfully completed, all the Ceph data from the selected host are removed.
Usage:
ceph-deploy purgedata [HOST] [HOST...]
+ U+ k7 w# b9 S2 v* M q
4 {* h$ N; `4 S5 F- Q5 `Here, [HOST] is hostname of the node from where Ceph data will be purged.
% D4 W% P7 x S" K8 b1 M) p0 y
FORGETKEYSRemove authentication keys from the local directory. It removes all the authentication keys i.e, monitor keyring, client.admin keyring, bootstrap-osd and bootstrap-mds keyring from the node.
Usage:
ceph-deploy forgetkeys; O$ o6 Q: X% U
9 i \( h+ `; P+ l, ^" S: V4 h$ A1 k, o1 @) B
PKGManage packages on remote hosts. It is used for installing or removing packages from remote hosts. The package names for installation or removal are to be specified after the command. Two options
--install and
--remove are used for this purpose.
Usage:
ceph-deploy pkg --install [PKGs] [HOST] [HOST...]ceph-deploy pkg --remove [PKGs] [HOST] [HOST...] N" Z; s$ m& r: a0 u
8 ?0 S7 c- J' G: n$ _, K
Here, [PKGs] is comma-separated package names and [HOST] is hostname of the remote node where packages are to be installed or removed from.
' C+ e2 M B( I w: L% c) ~2 t( q
发表于 2020-12-12 20:42:57