summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorSage Weil <sage@newdream.net>2011-05-06 14:21:53 -0700
committerSage Weil <sage@newdream.net>2011-05-06 14:21:53 -0700
commitd74ecc2630e8dceb4a4e15a4367e77d25e069276 (patch)
tree961a7f733f6fe14e81eed3755670660ca89bf2d7 /man
parentfb84e6b26b916592c4f4ee0ccc9ba70ec4dd004a (diff)
downloadceph-d74ecc2630e8dceb4a4e15a4367e77d25e069276.tar.gz
mkcephfs.man: update man page
Not beautiful, but at least it's accurate. Signed-off-by: Sage Weil <sage@newdream.net>
Diffstat (limited to 'man')
-rw-r--r--man/mkcephfs.880
1 files changed, 67 insertions, 13 deletions
diff --git a/man/mkcephfs.8 b/man/mkcephfs.8
index f0d435f5fab..1a7d101ad24 100644
--- a/man/mkcephfs.8
+++ b/man/mkcephfs.8
@@ -3,18 +3,55 @@
mkcephfs \- create a ceph file system
.SH SYNOPSIS
.B mkcephfs
-[ \fB\-a\fP ]
[ \fB\-c\fP\fI ceph.conf\fP ]
-[ \fB\-k\fI /path/to/keyring.bin\fP ]
-[ \fB\-\-clobber_old_data\fP ]
+[ \fB\-k\fI /path/to/admin.keyring\fP ]
[ \fB\-\-mkbtrfs\fP ]
+[ \fB\-a\fR, \fB\-\-all-hosts\fP ]
.SH DESCRIPTION
.B mkcephfs
-is used to create an empty Ceph file system, possibly spanning multiple
-hosts. The \fIceph.conf\fP file describes the composition of the
-Ceph cluster, including which hosts are participating, which daemons
-run where, and which paths are used to store file system data or
-metadata.
+is used to create an empty Ceph file system, possibly spanning
+multiple hosts. The \fIceph.conf\fP file describes the composition of
+the entire Ceph cluster, including which hosts are participating,
+which daemons run where, and which paths are used to store file system
+data or metadata.
+.P
+The
+.B mkcephfs
+tool can be used in two ways. If \fB\-a\fR is used, it will use ssh
+and scp to connect to remote hosts on your behalf and do the setup of
+the entire cluster. This is the easiest solution, but can also be
+inconvenient (if you don't have ssh to connect without prompting for
+passwords) or slow (if you have a large cluster).
+.P
+Alternatively, you can run each setup phase manually. First, you need to prepare
+a monmap that will be shared by each node:
+.IP
+.nf
+# prepare
+master# mkdir /tmp/foo
+master# mkcephfs -c /etc/ceph/ceph.conf \\
+ --prepare-monmap -d /tmp/foo
+.fi
+.P
+Share the /tmp/foo directory with other nodes in whatever way is convenient for you. On each
+OSD and MDS node,
+.IP
+.nf
+osdnode# mkcephfs --init-local-daemons osd -d /tmp/foo
+mdsnode# mkcephfs --init-local-daemons mds -d /tmp/foo
+.fi
+.P
+Collect the contents of the /tmp/foo directories back onto a single node, and then
+.IP
+.nf
+master# mkcephfs --prepare-mon -d /tmp/foo
+.fi
+.P
+Finally, distribute /tmp/foo to all monitor nodes and, on each of those nodes,
+.IP
+.nf
+monnode# mkcephfs --init-local-daemons mon -d /tmp/foo
+.fi
.SH OPTIONS
.TP
\fB\-a\fR, \fB\-\-allhosts\fR
@@ -24,17 +61,34 @@ executing commands via SSH.
\fB\-c\fI ceph.conf\fR, \fB\-\-conf=\fIceph.conf\fR
Use the given conf file instead of the default \fI/etc/ceph/ceph.conf\fP.
.TP
-\fB\-k\fI /path/to/keyring.bin\fR
-Location to write the client.admin keyring, which is used to administer the cluster. The default is \fI/etc/ceph/keyring.bin\fP, but must still be specified explicitly.
-.TP
-\fB\-\-clobber_old_data\fR
-Overwrite any existing data found in monitor or osd paths.
+\fB\-k\fI /path/to/keyring\fR
+Location to write the client.admin keyring, which is used to administer the cluster. The default is \fI/etc/ceph/keyring\fP.
.TP
\fB\-\-mkbtrfs\fR
Create and mount the any btrfs file systems specified in the
\fBceph.conf\fP for OSD data storage using \fBmkfs.btrfs\fP. The
"btrfs devs" and (if it differs from
"osd data") "btrfs path" options must be defined.
+
+.SH SUBCOMMANDS
+The sub-commands performed during cluster setup can be run individually with
+.TP
+ \fB\-\-prepare\-monmap\fR \fB\-d \fIdir\fB
+Create an initial monmap with a random fsid/uuid and store it in
+\fIdir\fR.
+.TP
+ \fB\-\-init\-local\-daemons\fR \fItype\fR \fB\-d \fIdir\fB Initialize
+any daemons of type \fItype\fR on the local host using the monmap in
+\fIdir\fR. For types \fIosd\fR and \fImds\fR, the resulting
+authentication keys will be placed in \fIdir\fR. For type \fImon\fR,
+the initial data files generated by \fB\-\-prepare\-mon\fR (below) are
+expected in \fIdir\fR.
+.TP
+ \fB\-\-prepare\-mon\fR \fB\-d \fIdir\fB
+Prepare the initial monitor data based on the monmap, OSD, and MDS
+authentication keys collected in \fIdir\fR, and put the result in
+\fIdir\fR.
+
.SH AVAILABILITY
.B mkcephfs
is part of the Ceph distributed file system. Please refer to the Ceph wiki at