Manual Deployment on FreeBSD

This a largely a copy of the regular Manual Deployment with FreeBSD specifics.The difference lies in two parts: The underlying diskformat, and the way to usethe tools.

All Ceph clusters require at least one monitor, and at least as many OSDs ascopies of an object stored on the cluster. Bootstrapping the initial monitor(s)is the first step in deploying a Ceph Storage Cluster. Monitor deployment alsosets important criteria for the entire cluster, such as the number of replicasfor pools, the number of placement groups per OSD, the heartbeat intervals,whether authentication is required, etc. Most of these values are set bydefault, so it’s useful to know about them when setting up your cluster forproduction.

Following the same configuration as Installation (Quick), we will set up acluster with node1 as the monitor node, and node2 and node3 forOSD nodes.

Manual Deployment on FreeBSD - 图1

Disklayout on FreeBSD

Current implementation works on ZFS pools

  • All Ceph data is created in /var/lib/ceph

  • Log files go into /var/log/ceph

  • PID files go into /var/log/run

  • One ZFS pool is allocated per OSD, like:

  1. gpart create -s GPT ada1
  2. gpart add -t freebsd-zfs -l osd.1 ada1
  3. zpool create -m /var/lib/ceph/osd/osd.1 osd.1 gpt/osd.1
  • Some cache and log (ZIL) can be attached.Please note that this is different from the Ceph journals. Cache and log aretotally transparent for Ceph, and help the file system to keep the systemconsistent and help performance.Assuming that ada2 is an SSD:
  1. gpart create -s GPT ada2
  2. gpart add -t freebsd-zfs -l osd.1-log -s 1G ada2
  3. zpool add osd.1 log gpt/osd.1-log
  4. gpart add -t freebsd-zfs -l osd.1-cache -s 10G ada2
  5. zpool add osd.1 log gpt/osd.1-cache
  • Note: UFS2 does not allow large xattribs

Configuration

As per FreeBSD default parts of extra software go into /usr/local/. Whichmeans that for /etc/ceph.conf the default location is/usr/local/etc/ceph/ceph.conf. Smartest thing to do is to create a softlinkfrom /etc/ceph to /usr/local/etc/ceph:

  1. ln -s /usr/local/etc/ceph /etc/ceph

A sample file is provided in /usr/local/share/doc/ceph/sample.ceph.confNote that /usr/local/etc/ceph/ceph.conf will be found by most tools,linking it to /etc/ceph/ceph.conf will help with any scripts that are foundin extra tools, scripts, and/or discussionlists.

Monitor Bootstrapping

Bootstrapping a monitor (a Ceph Storage Cluster, in theory) requiresa number of things:

  • Unique Identifier: The fsid is a unique identifier for the cluster,and stands for File System ID from the days when the Ceph Storage Cluster wasprincipally for the Ceph File System. Ceph now supports native interfaces,block devices, and object storage gateway interfaces too, so fsid is abit of a misnomer.

  • Cluster Name: Ceph clusters have a cluster name, which is a simple stringwithout spaces. The default cluster name is ceph, but you may specifya different cluster name. Overriding the default cluster name isespecially useful when you are working with multiple clusters and you need toclearly understand which cluster your are working with.

For example, when you run multiple clusters in a multisite configuration,the cluster name (e.g., us-west, us-east) identifies the cluster forthe current CLI session. Note: To identify the cluster name on thecommand line interface, specify the a Ceph configuration file with thecluster name (e.g., ceph.conf, us-west.conf, us-east.conf, etc.).Also see CLI usage (ceph —cluster {cluster-name}).

  • Monitor Name: Each monitor instance within a cluster has a unique name.In common practice, the Ceph Monitor name is the host name (we recommend oneCeph Monitor per host, and no commingling of Ceph OSD Daemons withCeph Monitors). You may retrieve the short hostname with hostname -s.

  • Monitor Map: Bootstrapping the initial monitor(s) requires you togenerate a monitor map. The monitor map requires the fsid, the clustername (or uses the default), and at least one host name and its IP address.

  • Monitor Keyring: Monitors communicate with each other via asecret key. You must generate a keyring with a monitor secret and provideit when bootstrapping the initial monitor(s).

  • Administrator Keyring: To use the ceph CLI tools, you must havea client.admin user. So you must generate the admin user and keyring,and you must also add the client.admin user to the monitor keyring.

The foregoing requirements do not imply the creation of a Ceph Configurationfile. However, as a best practice, we recommend creating a Ceph configurationfile and populating it with the fsid, the mon initial members and themon host settings.

You can get and set all of the monitor settings at runtime as well. However,a Ceph Configuration file may contain only those settings that override thedefault values. When you add settings to a Ceph configuration file, thesesettings override the default settings. Maintaining those settings in aCeph configuration file makes it easier to maintain your cluster.

The procedure is as follows:

  • Log in to the initial monitor node(s):
  1. ssh {hostname}

For example:

  1. ssh node1
  • Ensure you have a directory for the Ceph configuration file. By default,Ceph uses /etc/ceph. When you install ceph, the installer willcreate the /etc/ceph directory automatically.
  1. ls /etc/ceph

Note: Deployment tools may remove this directory when purging acluster (e.g., ceph-deploy purgedata {node-name}, ceph-deploy purge{node-name}).

  • Create a Ceph configuration file. By default, Ceph usesceph.conf, where ceph reflects the cluster name.
  1. sudo vim /etc/ceph/ceph.conf
  • Generate a unique ID (i.e., fsid) for your cluster.
  1. uuidgen
  • Add the unique ID to your Ceph configuration file.
  1. fsid = {UUID}

For example:

  1. fsid = a7f64266-0894-4f1e-a635-d0aeaca0e993
  • Add the initial monitor(s) to your Ceph configuration file.
  1. mon initial members = {hostname}[,{hostname}]

For example:

  1. mon initial members = node1
  • Add the IP address(es) of the initial monitor(s) to your Ceph configurationfile and save the file.
  1. mon host = {ip-address}[,{ip-address}]

For example:

  1. mon host = 192.168.0.1

Note: You may use IPv6 addresses instead of IPv4 addresses, butyou must set ms bind ipv6 to true. See Network ConfigurationReference for details about network configuration.

  • Create a keyring for your cluster and generate a monitor secret key.
  1. ceph-authtool --create-keyring /tmp/ceph.mon.keyring --gen-key -n mon. --cap mon 'allow *'
  • Generate an administrator keyring, generate a client.admin user and addthe user to the keyring.
  1. sudo ceph-authtool --create-keyring /etc/ceph/ceph.client.admin.keyring --gen-key -n client.admin --cap mon 'allow *' --cap osd 'allow *' --cap mds 'allow *' --cap mgr 'allow *'
  • Add the client.admin key to the ceph.mon.keyring.
  1. ceph-authtool /tmp/ceph.mon.keyring --import-keyring /etc/ceph/ceph.client.admin.keyring
  • Generate a monitor map using the hostname(s), host IP address(es) and the FSID.Save it as /tmp/monmap:
  1. monmaptool --create --add {hostname} {ip-address} --fsid {uuid} /tmp/monmap

For example:

  1. monmaptool --create --add node1 192.168.0.1 --fsid a7f64266-0894-4f1e-a635-d0aeaca0e993 /tmp/monmap
  • Create a default data directory (or directories) on the monitor host(s).
  1. sudo mkdir /var/lib/ceph/mon/{cluster-name}-{hostname}

For example:

  1. sudo mkdir /var/lib/ceph/mon/ceph-node1

See Monitor Config Reference - Data for details.

  • Populate the monitor daemon(s) with the monitor map and keyring.
  1. sudo -u ceph ceph-mon [--cluster {cluster-name}] --mkfs -i {hostname} --monmap /tmp/monmap --keyring /tmp/ceph.mon.keyring

For example:

  1. sudo -u ceph ceph-mon --mkfs -i node1 --monmap /tmp/monmap --keyring /tmp/ceph.mon.keyring
  • Consider settings for a Ceph configuration file. Common settings includethe following:
  1. [global]
  2. fsid = {cluster-id}
  3. mon initial members = {hostname}[, {hostname}]
  4. mon host = {ip-address}[, {ip-address}]
  5. public network = {network}[, {network}]
  6. cluster network = {network}[, {network}]
  7. auth cluster required = cephx
  8. auth service required = cephx
  9. auth client required = cephx
  10. osd journal size = {n}
  11. osd pool default size = {n}  # Write an object n times.
  12. osd pool default min size = {n} # Allow writing n copy in a degraded state.
  13. osd pool default pg num = {n}
  14. osd pool default pgp num = {n}
  15. osd crush chooseleaf type = {n}

In the foregoing example, the [global] section of the configuration mightlook like this:

  1. [global]
  2. fsid = a7f64266-0894-4f1e-a635-d0aeaca0e993
  3. mon initial members = node1
  4. mon host = 192.168.0.1
  5. public network = 192.168.0.0/24
  6. auth cluster required = cephx
  7. auth service required = cephx
  8. auth client required = cephx
  9. osd journal size = 1024
  10. osd pool default size = 3
  11. osd pool default min size = 2
  12. osd pool default pg num = 333
  13. osd pool default pgp num = 333
  14. osd crush chooseleaf type = 1
  • Touch the done file.

Mark that the monitor is created and ready to be started:

  1. sudo touch /var/lib/ceph/mon/ceph-node1/done
  • And for FreeBSD an entry for every monitor needs to be added to the configfile. (The requirement will be removed in future releases).

The entry should look like:

  1. [mon]
  2.     [mon.node1]
  3.         host = node1    # this name can be resolve
  • Start the monitor(s).

For Ubuntu, use Upstart:

  1. sudo start ceph-mon id=node1 [cluster={cluster-name}]

In this case, to allow the start of the daemon at each reboot youmust create two empty files like this:

  1. sudo touch /var/lib/ceph/mon/{cluster-name}-{hostname}/upstart

For example:

  1. sudo touch /var/lib/ceph/mon/ceph-node1/upstart

For Debian/CentOS/RHEL, use sysvinit:

  1. sudo /etc/init.d/ceph start mon.node1

For FreeBSD we use the rc.d init scripts (called bsdrc in Ceph):

  1. sudo service ceph start start mon.node1
  • For this to work /etc/rc.conf also needs the entry to enable ceph::
  • cat ‘ceph_enable=”YES”’ >> /etc/rc.conf
  • Verify that Ceph created the default pools.
  1. ceph osd lspools

You should see output like this:

  1. 0 data
  2. 1 metadata
  3. 2 rbd
  • Verify that the monitor is running.
  1. ceph -s

You should see output that the monitor you started is up and running, andyou should see a health error indicating that placement groups are stuckinactive. It should look something like this:

  1. cluster a7f64266-0894-4f1e-a635-d0aeaca0e993
  2.   health HEALTH_ERR 192 pgs stuck inactive; 192 pgs stuck unclean; no osds
  3.   monmap e1: 1 mons at {node1=192.168.0.1:6789/0}, election epoch 1, quorum 0 node1
  4.   osdmap e1: 0 osds: 0 up, 0 in
  5.   pgmap v2: 192 pgs, 3 pools, 0 bytes data, 0 objects
  6.      0 kB used, 0 kB / 0 kB avail
  7.      192 creating

Note: Once you add OSDs and start them, the placement group health errorsshould disappear. See the next section for details.

Adding OSDs

Once you have your initial monitor(s) running, you should add OSDs. Your clustercannot reach an active + clean state until you have enough OSDs to handle thenumber of copies of an object (e.g., osd pool default size = 2 requires atleast two OSDs). After bootstrapping your monitor, your cluster has a defaultCRUSH map; however, the CRUSH map doesn’t have any Ceph OSD Daemons mapped toa Ceph Node.

Long Form

Without the benefit of any helper utilities, create an OSD and add it to thecluster and CRUSH map with the following procedure. To create the first twoOSDs with the long form procedure, execute the following on node2 andnode3:

  • Connect to the OSD host.
  1. ssh {node-name}
  • Generate a UUID for the OSD.
  1. uuidgen
  • Create the OSD. If no UUID is given, it will be set automatically when theOSD starts up. The following command will output the OSD number, which youwill need for subsequent steps.
  1. ceph osd create [{uuid} [{id}]]
  • Create the default directory on your new OSD.
  1. ssh {new-osd-host}
  2. sudo mkdir /var/lib/ceph/osd/{cluster-name}-{osd-number}

Above are the ZFS instructions to do this for FreeBSD.

  • If the OSD is for a drive other than the OS drive, prepare itfor use with Ceph, and mount it to the directory you just created.

  • Initialize the OSD data directory.

  1. ssh {new-osd-host}
  2. sudo ceph-osd -i {osd-num} --mkfs --mkkey --osd-uuid [{uuid}]

The directory must be empty before you can run ceph-osd with the—mkkey option. In addition, the ceph-osd tool requires specificationof custom cluster names with the —cluster option.

  • Register the OSD authentication key. The value of ceph forceph-{osd-num} in the path is the $cluster-$id. If yourcluster name differs from ceph, use your cluster name instead.:
  1. sudo ceph auth add osd.{osd-num} osd 'allow *' mon 'allow profile osd' -i /var/lib/ceph/osd/{cluster-name}-{osd-num}/keyring
  • Add your Ceph Node to the CRUSH map.
  1. ceph [--cluster {cluster-name}] osd crush add-bucket {hostname} host

For example:

  1. ceph osd crush add-bucket node1 host
  • Place the Ceph Node under the root default.
  1. ceph osd crush move node1 root=default
  • Add the OSD to the CRUSH map so that it can begin receiving data. You mayalso decompile the CRUSH map, add the OSD to the device list, add the host as abucket (if it’s not already in the CRUSH map), add the device as an item in thehost, assign it a weight, recompile it and set it.
  1. ceph [--cluster {cluster-name}] osd crush add {id-or-name} {weight} [{bucket-type}={bucket-name} ...]

For example:

  1. ceph osd crush add osd.0 1.0 host=node1
  • After you add an OSD to Ceph, the OSD is in your configuration. However,it is not yet running. The OSD is down and in. You must startyour new OSD before it can begin receiving data.

For Ubuntu, use Upstart:

  1. sudo start ceph-osd id={osd-num} [cluster={cluster-name}]

For example:

  1. sudo start ceph-osd id=0
  2. sudo start ceph-osd id=1

For Debian/CentOS/RHEL, use sysvinit:

  1. sudo /etc/init.d/ceph start osd.{osd-num} [--cluster {cluster-name}]

For example:

  1. sudo /etc/init.d/ceph start osd.0
  2. sudo /etc/init.d/ceph start osd.1

In this case, to allow the start of the daemon at each reboot youmust create an empty file like this:

  1. sudo touch /var/lib/ceph/osd/{cluster-name}-{osd-num}/sysvinit

For example:

  1. sudo touch /var/lib/ceph/osd/ceph-0/sysvinit
  2. sudo touch /var/lib/ceph/osd/ceph-1/sysvinit

Once you start your OSD, it is up and in.

For FreeBSD using rc.d init.

After adding the OSD to ceph.conf:

  1. sudo service ceph start osd.{osd-num}

For example:

  1. sudo service ceph start osd.0
  2. sudo service ceph start osd.1

In this case, to allow the start of the daemon at each reboot youmust create an empty file like this:

  1. sudo touch /var/lib/ceph/osd/{cluster-name}-{osd-num}/bsdrc

For example:

  1. sudo touch /var/lib/ceph/osd/ceph-0/bsdrc
  2. sudo touch /var/lib/ceph/osd/ceph-1/bsdrc

Once you start your OSD, it is up and in.

Adding MDS

In the below instructions, {id} is an arbitrary name, such as the hostname of the machine.

  • Create the mds data directory.:
  1. mkdir -p /var/lib/ceph/mds/{cluster-name}-{id}
  • Create a keyring.:
  1. ceph-authtool --create-keyring /var/lib/ceph/mds/{cluster-name}-{id}/keyring --gen-key -n mds.{id}
  • Import the keyring and set caps.:
  1. ceph auth add mds.{id} osd "allow rwx" mds "allow" mon "allow profile mds" -i /var/lib/ceph/mds/{cluster}-{id}/keyring
  • Add to ceph.conf.:
  1. [mds.{id}]
  2. host = {id}
  • Start the daemon the manual way.:
  1. ceph-mds --cluster {cluster-name} -i {id} -m {mon-hostname}:{mon-port} [-f]
  • Start the daemon the right way (using ceph.conf entry).:
  1. service ceph start
  • If starting the daemon fails with this error:
  1. mds.-1.0 ERROR: failed to authenticate: (22) Invalid argument

Then make sure you do not have a keyring set in ceph.conf in the global section; move it to the client section; or add a keyring setting specific to this mds daemon. And verify that you see the same key in the mds data directory and ceph auth get mds.{id} output.

Summary

Once you have your monitor and two OSDs up and running, you can watch theplacement groups peer by executing the following:

  1. ceph -w

To view the tree, execute the following:

  1. ceph osd tree

You should see output that looks something like this:

  1. # id    weight  type name       up/down reweight
  2. -1      2       root default
  3. -2      2               host node1
  4. 0       1                       osd.0   up      1
  5. -3      1               host node2
  6. 1       1                       osd.1   up      1

To add (or remove) additional monitors, see Add/Remove Monitors.To add (or remove) additional Ceph OSD Daemons, see Add/Remove OSDs.