Difference between revisions of "Ceph Server"
|Line 78:||Line 78:|
# from /etc/network/interfaces
# from /etc/network/interfaces
iface inet static
Revision as of 13:27, 4 July 2017
Ceph is a distributed object store and file system designed to provide excellent performance, reliability and scalability - See more at: http://ceph.com.
Proxmox VE supports Ceph’s RADOS Block Device to be used for VM and container disks. The Ceph storage services are usually hosted on external, dedicated storage nodes. Such storage clusters can sum up to several hundreds of nodes, providing petabytes of storage capacity.
For smaller deployments, it is also possible to run Ceph services directly on your Proxmox VE nodes. Recent hardware has plenty of CPU power and RAM, so running storage services and VM/CTs on same node is possible.
This articles describes how to setup and run Ceph storage services directly on Proxmox VE nodes. If you want to install and configure an external Ceph storage read the Ceph documentation. To configure an external Ceph storage works as described in section Ceph Client accordingly.
- Easy setup and management with CLI and GUI support on Proxmox VE
- Thin provisioning
- Snapshots support
- Self healing
- No single point of failure
- Scalable to the exabyte level
- Setup pools with different performance and redundancy characteristics
- Data is replicated, making it fault tolerant
- Runs on economical commodity hardware
- No need for hardware RAID controllers
- Easy management
- Open source
You need at least three identical servers for the redundant setup. Here is the specifications of one of our test lab clusters with Proxmox VE and Ceph (three nodes):
- Dual Xeon E5-2620v2, 64 GB RAM, Intel S2600CP mainboard, Intel RMM, Chenbro 2U chassis with eight 3.5” hot-swap drive bays, 2 fixed 2.5" SSD bays
- 10 GBit network for Ceph traffic (one Dual 10 Gbit Intel X540-T2 in each server, one 10Gb switch - Cisco SG350XG-2F1)
- Single enterprise class SSD for the Proxmox VE installation (because we run Ceph monitors there and quite a lot of logs), we use one Samsung SM863 240 GB per host.
- Use at least two SSD as OSD drives. You need high quality and enterprise class SSDs here, never use consumer or "PRO" consumer SSDs. In our testsetup, we have 4 Intel SSD DC S3520 1.2TB, 2.5" SATA SSD per host for storing the data (OSD, no extra journal) - This setup delivers about 14 TB storage. By using the redundancy of 3, you can store up to 4,7 TB (100%). But to be prepared for failed disks and hosts, you should never fill up your storage with 100 %.
- As a general rule, the more OSD the better, fast CPU (high GHZ) is also recommended. NVMe express cards are also possible, e.g. mix of slow SATA disks with SSD/NVMe journal devices.
Again, if you expect good performance, always use enterprise class SSD only, we have good results in our testlabs with:
- SATA SSDs:
- Intel SSD DC S3520
- Intel SSD DC S3610
- Intel SSD DC S3700/S3710
- Samsung SSD SM863
- NVMe PCIe 3.0 x4 as journal:
- Intel SSD DC P3700
By adding more OSD SSD/disks into the free drive bays, the storage can be expanded. Of course, you can add more servers too as soon as your business is growing, without service interruption and with minimal configuration changes.
If you do not want to run virtual machines and Ceph on the same host, you can just add more Proxmox VE nodes and use these for running the guests and the others just for the storage.
Installation of Proxmox VE
Before you start with Ceph, you need a working Proxmox VE cluster with 3 nodes (or more). We install Proxmox VE on a fast and reliable enterprise class SSD, so we can use all bays for OSD (Object Storage Devices) data. Just follow the well known instructions on Installation and Proxmox VE 2.0 Cluster.
Use ext4 if you install on SSD (at the boot prompt of the installation ISO you can specify parameters, e.g. "linux ext4 swapsize=4").
Network for Ceph
All nodes need access to a separate 10Gb network interface, exclusively used for Ceph. We use network 10.10.10.0/24 for this tutorial.
It is highly recommended to use 10Gb for that network to avoid performance problems. Bonding can be used to increase availability.
If you do not have fast network switches, you can also setup a Full Mesh Network for Ceph Server.
The network setup (ceph private network) from our first node contains:
# from /etc/network/interfaces auto eno2 iface eno2 inet static address 10.10.10.1 netmask 255.255.255.0
The network setup (ceph private network) from our second node contains:
# from /etc/network/interfaces auto eno2 iface eno2 inet static address 10.10.10.2 netmask 255.255.255.0
The network setup (ceph private network) from our third node contains:
# from /etc/network/interfaces auto eth2 iface eth2 inet static address 10.10.10.3 netmask 255.255.255.0
Installation of Ceph packages
You now need to select 3 nodes and install the Ceph software packages there. We wrote a small command line utility called 'pveceph' which helps you performing this tasks, you can also choose the version of Ceph. Login to all your nodes and execute the following on all:
node1# pveceph install -version jewel
node2# pveceph install -version jewel
node3# pveceph install -version jewel
This sets up an 'apt' package repository in /etc/apt/sources.list.d/ceph.list and installs the required software.
Create initial Ceph configuration
After installation of packages, you need to create an initial Ceph configuration on just one node, based on your private network:
node1# pveceph init --network 10.10.10.0/24
This creates an initial config at /etc/pve/ceph.conf. That file is automatically distributed to all Proxmox VE nodes by using pmxcfs. The command also creates a symbolic link from /etc/ceph/ceph.conf pointing to that file. So you can simply run Ceph commands without the need to specify a configuration file.
Creating Ceph Monitors
After that you can create the first Ceph monitor service using:
node1# pveceph createmon
Continue with CLI or GUI
As soon as you have created the first monitor, you can start using the Proxmox GUI (see the video tutorial on Managing Ceph Server) to manage and view your Ceph configuration.
Of course, you can continue to use the command line tools (CLI). We continue with the CLI in this wiki article, but you should achieve the same results no matter which way you finish the remaining steps.
Creating more Ceph Monitors
You should run 3 monitors, one on each node. Create them via GUI or via CLI. So please login to the next node and run:
node2# pveceph createmon
And execute the same steps on the third node:
node3# pveceph createmon
If you add a node where you do not want to run a Ceph monitor, e.g. another node for OSDs, you need to install the Ceph packages with 'pveceph install' and you need to initialize Ceph with 'pveceph init'
PS: per thread https://forum.proxmox.com/threads/ceph-nodes-alternate-red-green-on-pve-screen.32670/ as of 2017-02-06 a node will seem to have issues [ really not ] on pve screen. red/green alternating . so as of this writing you must do this for any node that is not a ceph mon:
Creating Ceph OSDs
First, please be careful when you initialize your OSD disks, because it basically removes all existing data from those disks. So it is important to select the correct device names. The Proxmox VE GUI displays a list of all disk, together with device names, usage information and serial numbers.
Creating OSDs can be done via GUI - self explaining - or via CLI, explained here:
Having that said, initializing an OSD can be done with:
# pveceph createosd /dev/sd[X]
If you want to use a dedicated SSD journal disk:
# pveceph createosd /dev/sd[X] -journal_dev /dev/sd[X]
Example: /dev/sdf as data disk (4TB) and /dev/sdb is the dedicated SSD journal disk
# pveceph createosd /dev/sdf -journal_dev /dev/sdb
This partitions the disk (data and journal partition), creates filesystems, starts the OSD and add it to the existing crush map. So afterward the OSD is running and fully functional. Please create at least 12 OSDs, distributed among your nodes (4 on each node).
It should be noted that this command refuses to initialize disk when it detects existing data. So if you want to overwrite a disk you should remove existing data first. You can do that using:
# ceph-disk zap /dev/sd[X]
- In some cases disks that used to be part of a 3ware raid need the following in addition to zap.
#To remove partition table and boot sector the following should be sufficient: dd if=/dev/zero of=/dev/$DISK bs=1024 count=1
DISK=$1 if [ "$1" = "" ]; then echo "Need to supply a dev name like sdg . exiting" exit 1 fi echo " make sure this is the correct disk " echo $DISK echo " you will end up with NO partition table when this procedes . example: Disk /dev/$1 doesn't contain a valid partition table Press enter to procede , or ctl-c to exit " read x dd if=/dev/zero of=/dev/$DISK bs=512 count=50000
You can create OSDs containing both journal and data partitions or you can place the journal on a dedicated SSD. Using a SSD journal disk is highly recommended if you expect good performance.
In order to use a dedicated journal disk (SSD), the disk needs to have a GPT partition table. You can create this with 'gdisk /dev/sd(x)'. If there is no GPT, you cannot select the disk as journal. Currently the journal size is fixed to 5 GB.
The standard installation creates some default pools, so you can either use the standard 'rbd' pool, or create your own pools using the GUI.
In order to calculate your the number of placement groups for your pools, you can use:
Ceph PGs per Pool Calculator
pool size notes
TBD: verify that this is a suggested setting for preserving data:
- suggested settings:
- pool size:3
- min. size:2
- from pve mail list:
Hi Daniel, i would Not use Size of 2! At least you should use Size 3 and min Size of 2.
Otherwise you will be in Trouble in Case of a serious ceph error.
You can find a lot of discussion in the ceph Mailing List Related to this.
You can then configure Proxmox VE to use such pools to store VM images, just use the GUI ("Add Storage": RBD). A typical entry in the Proxmox VE storage configuration looks like:
# from /etc/pve/storage.cfg rbd: my-ceph-storage monhost 10.10.10.1;10.10.10.2;10.10.10.3 pool rbd content images username admin krbd 0
You also need to copy the keyring to a predefined location.
- Note that the file name needs to be storage id + .keyring . storage id is the expression after 'rbd:' in /etc/pve/storage.cfg which is my-ceph-storage in the current example.
# mkdir /etc/pve/priv/ceph # cp /etc/ceph/ceph.client.admin.keyring /etc/pve/priv/ceph/my-ceph-storage.keyring
If you want to store containers on Ceph, you need to create an extra pool using KRBD.
# from /etc/pve/storage.cfg rbd: my-ceph-storage-for-lxc monhost 10.10.10.1;10.10.10.2;10.10.10.3 pool rbd-lxc content images username admin krbd 1
Set the Ceph OSD tunables
ceph osd crush tunables hammer
If you set the tunable and your ceph cluster is used you should do this when the cluster has the least load. Also try to use the backfill option to do this process slower.
Important Do not set tunable to optimal because then krbd will not work. Set it to hammer.
Why do we need a new command line tool (pveceph)?
For the use in the specific Proxmox VE architecture we use pveceph. Proxmox VE provides a distributed file system (pmxcfs) to store configuration files.
We use this to store the Ceph configuration. The advantage is that all nodes see the same file, and there is no need to copy configuration data around using ssh/scp. The tool can also use additional information from your Proxmox VE setup.
Tools like ceph-deploy cannot take advantage of that architecture.
Note for users of HP SmartArray controllers
Proxmox will struggle to add an OSD on a SmartArray conroller via the GUI. This is due to an '!' being inserted into the device path, where a '/' should be instead. An example would be that "/dev/cciss!c0d0" is shown instead of "/dev/cciss/c0d0".
This is, however, very easy to fix with a small file edit.
Connect to the terminal via SSH.
Open the following file in your editor of choice (Vi, Emacs, Nano, etc):
Find the line that says:
$devname =~ s|/dev/||;
Add the following string on a new line, immediately after the line mentioned above:
$devname =~ s|cciss/|cciss!|;
Finally, save the file.
Unfortunately, this will still not allow the disk to be added via the GUI, but you can now use the instructions above to add the OSD via the CLI, and then carry on as you otherwise would with creation of pools, etc.
Upgrading existing Ceph Server from Hammer to Jewel
Proxmox YouTube channel
You can subscribe to our Proxmox VE Channel on YouTube to get updates about new videos.
Further readings about Ceph
- https://www.sebastien-han.fr/blog/2014/10/10/ceph-how-to-test-if-your-ssd-is-suitable-as-a-journal-device/, Journal SSD Recommendations
these are just some notes of things learned from setting up a ceph cluster in early 2017. unofficial advice.
it is best to use the same suggested model drive for all osd's.
make one change at a time
after ceph is set up and running make only one change at a time.
adding and osd, changing pool settings - check log and make sure health is normal before the next change. too many changes at the same time can result in slow systems - bad for cli.
to check that change has completed check logs. at pve>ceph>log
- or from cli
using a disk that was part of a zfs pool
as of now
ceph-disk zap /dev/sd?
else it does not show up on pve > ceph > osd > Create OSD
restore lxc from zfs to ceph
if lxc is on zfs with compression the actual disk usage can be far greater then expected. see https://forum.proxmox.com/threads/lxc-restore-fail-to-ceph.32419/#post-161287
One way to know actual disk usage:
- restore backup to a ext4 directory and run du -sh , then do restore manually specifying target disk size.
make sure that you use virtio-scsi controller (not LSI), see VM options. I remember some panic when using LSI recently but I did not debug it further as modern OS should use virtio-scsi anyways. https://forum.proxmox.com/threads/restarted-a-node-some-kvms-on-other-nodes-panic.32806
kvm hard disk cache
use write-through [ from forum 2/2017 ]
"Periodically, you may need to perform maintenance on a subset of your cluster, or resolve a problem that affects a failure domain (e.g., a rack). If you do not want CRUSH to automatically rebalance the cluster as you stop OSDs for maintenance, set the cluster to noout first:"
ceph osd set noout
that can be done from pve at ceph>osd . very important.
research this 1ST . check forum , ceph mail list and http://docs.ceph.com/docs/master/rados/configuration/auth-config-ref/ :" The cephx protocol is enabled by default. Cryptographic authentication has some computational costs, though they should generally be quite low. If the network environment connecting your client and server hosts is very safe and you cannot afford authentication, you can turn it off. This is not generally recommended."
Our ceph network is isolated, and I am looking to speed up ceph performance so did this.
1- turn off all VM's which use ceph
2- /etc/pve/ceph.conf set:
auth cluster required = none auth service required = none auth client required = none
3- stop ceph daemons per http://docs.ceph.com/docs/master/rados/operations/operating/ To stop all daemons on a Ceph Node (irrespective of type), execute the following:
- Do on all mon nodes **
sudo systemctl stop ceph\*.service ceph\*.target
4- you need also to remove the client key in /etc/pve/priv/ceph/
cd /etc/pve/priv # do not do this line, else this file will be recreated by /usr/share/perl5/PVE/API2/Ceph.pm and using old keys later will not work. #-#mv ceph.client.admin.keyring ceph.client.admin.keyring-old mkdir /etc/pve/priv/ceph/old mv /etc/pve/priv/ceph/ceph* /etc/pve/priv/ceph/old/
5- start ceph To start all daemons on a Ceph Node (irrespective of type), execute the following:
- On all mon nodes **
systemctl start ceph.target
6- start vm's