Hi Sage,
On 12/06/2013 11:57 PM, Sage Weil wrote:
On Wed, 20 Nov 2013, mark.doffman@xxxxxxxxxxxxxxx wrote:
From: Rob Taylor <rob.taylor@xxxxxxxxxxxxxxx>
Document using the cephfs as a root device, its purpose,
functionality and use.
Signed-off-by: Mark Doffman <mark.doffman@xxxxxxxxxxxxxxx>
Signed-off-by: Rob Taylor <rob.taylor@xxxxxxxxxxxxxxx>
Reviewed-by: Ian Molton <ian.molton@xxxxxxxxxxxxxxx>
---
Documentation/filesystems/{ => ceph}/ceph.txt | 0
Documentation/filesystems/ceph/cephroot.txt | 81 +++++++++++++++++++++++++++
2 files changed, 81 insertions(+)
rename Documentation/filesystems/{ => ceph}/ceph.txt (100%)
create mode 100644 Documentation/filesystems/ceph/cephroot.txt
diff --git a/Documentation/filesystems/ceph.txt b/Documentation/filesystems/ceph/ceph.txt
similarity index 100%
rename from Documentation/filesystems/ceph.txt
rename to Documentation/filesystems/ceph/ceph.txt
diff --git a/Documentation/filesystems/ceph/cephroot.txt b/Documentation/filesystems/ceph/cephroot.txt
new file mode 100644
index 0000000..ae0f5bb
--- /dev/null
+++ b/Documentation/filesystems/ceph/cephroot.txt
@@ -0,0 +1,81 @@
+Mounting the root filesystem via Ceph (cephroot)
+===============================================
+
+Written 2013 by Rob Taylor <rob.taylor@xxxxxxxxxxxxxxx>
+
+derived from nfsroot.txt:
+
+Written 1996 by Gero Kuhlmann <gero@xxxxxxxxxxxxxx>
+Updated 1997 by Martin Mares <mj@xxxxxxxxxxxxxxxxxxxxxxxx>
+Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@xxxxxxxxxxxxxxx>
+Updated 2006 by Horms <horms@xxxxxxxxxxxx>
+
+
+
+In order to use a diskless system, such as an X-terminal or printer server
+for example, it is necessary for the root filesystem to be present on a
+non-disk device. This may be an initramfs (see Documentation/filesystems/
+ramfs-rootfs-initramfs.txt), a ramdisk (see Documentation/initrd.txt), a
+filesystem mounted via NFS or a filesystem mounted via Ceph. The following
+text describes on how to use Ceph for the root filesystem.
+
+For the rest of this text 'client' means the diskless system, and 'server'
+means the Ceph server.
+
+
+1.) Enabling cephroot capabilities
+ -----------------------------
+
+In order to use cephroot, CEPH_FS needs to be selected as
+built-in during configuration. Once this has been selected, the cephroot
+option will become available, which should also be selected.
+
+In the networking options, kernel level autoconfiguration can be selected,
+along with the types of autoconfiguration to support. Selecting all of
+DHCP, BOOTP and RARP is safe.
+
+
+2.) Kernel command line
+ -------------------
+
+When the kernel has been loaded by a boot loader (see below) it needs to be
+told what root fs device to use. And in the case of cephroot, where to find
+both the server and the name of the directory on the server to mount as root.
+This can be established using the following kernel command line parameters:
+
+root=/dev/ceph
+
+This is necessary to enable the pseudo-Ceph-device. Note that it's not a
+real device but just a synonym to tell the kernel to use Ceph instead of
+a real device.
+
+cephroot=<monaddr>:/[<subdir>],<ceph-opts>
+
+ <monaddr> Monitor address. Each takes the form host[:port]. If the port
+ is not specified, the Ceph default of 6789 is assumed.
+
+ <subdir> A subdirectory subdir may be specified if a subset of the file
+ system is to be mounted
+
+ <ceph-opts> Standard Ceph options. All options are separated by commas.
+ See Documentation/filesystems/ceph/ceph.txt for options and
+ their defaults.
Maybe there is an existing convention here, but: it seems like it would be
simpler to do something like
cephroot=<ip[:<port>][,...]>:/[<subdir>]
i.e., the existing syntax used by mount, that (among other things) can
also include a port, or be a list of mon ips, so that the parsing code
can be re-used. Then,
cephopts=<ceph-opts>
Hopefully this would avoid the parsing in root.c and make things behave
more consistently with respect to how mount(8) is used?
This would make things more consistent with mount, and easier! The
reason to keep it the way it is is for consistency with NFS and DHCP
option 17.
NFS concatenates the options in DHCP root-path (option 17) with the ones
placed on the kernel command line. We could separate out the device and
path strings from the options, but they would still be merged together
in the DHCP string. Some parsing would still be required to split the
DHCP string and merge with command line options. I'd prefer to keep them
together on the command line also, just to have things stay similar to NFS.
Thanks
Mark
sage
+
+4.) References
+ ----------
+
+
+5.) Credits
+ -------
+
+ cephroot was derived from nfsroot by Rob Taylor <rob.taylor@xxxxxxxxxxxxxxx>
+ and Mark Doffman <mark.doffman@xxxxxxxxxxxxxxx>
+
+ The nfsroot code in the kernel and the RARP support have been written
+ by Gero Kuhlmann <gero@xxxxxxxxxxxxxx>.
+
+ The rest of the IP layer autoconfiguration code has been written
+ by Martin Mares <mj@xxxxxxxxxxxxxxxxxxxxxxxx>.
+
+ In order to write the initial version of nfsroot I would like to thank
+ Jens-Uwe Mager <jum@xxxxxxxxxxxxx> for his help.
--
1.8.4
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
