Setting up shared volume using GlusterFS on centos 7

-
        
   I come to this solution due to one of my requirement in which i wanted to setup shared volume for my two node KVM virtual server node. I wanted to make a shared volume storage pool on both KVM node so that i can migrate VM between nodes.
           Normally this design is for ovirt HA cluster. My setup was not intended to work as HA cluster but a manual cluster to move VM from one host node to another.
           This setup is also usefull in case you need to setup any multimaster solution in which you dont want to use NFS and need data redundancy.

So here is the setup -
I have two nodes VM1  and VM2 each with a partition  /dev/vdb1 of 5GB size

I created one mount point for both VM /gb1 and mounted the partition on this mount point

# mkfs.xfs /dev/vdb1

# mount /dev/vdb1 /gb1

Above practice needs to be done on both VM node.

Next is i will install centos gluster release on both the nodes

# yum install -y centos-release-gluster5

Install gluster package now

# yum install glusterfs-server -y

start and enable gluster service

# systemctl start glusterd  &&  systemctl enable glusterd

Now setup firewall rule on both node

[root@vm2 data]# firewall-cmd --permanent --add-port=49152/tcp
success
[root@vm2 data]# firewall-cmd --permanent --add-port=24007/tcp
success
[root@vm2 data]# firewall-cmd --permanent --add-port=111/tcp
success
[root@vm1 data]# firewall-cmd --reload
success

Now probe both VM as peer for each other

[root@vm1 data]# gluster peer probe vm2

[root@vm2 data]# gluster peer probe vm1

Now will create gluster volume gfs_data. and from now i will run commands on any of one node.

[root@vm1 data]# gluster volume create gfs_data replica 2 vm1:/gb1/b1 vm2:/gb1/b1

Here b1 is will be directory which will be replicated as gluster volume. You can choose any name.

Now check the volume status

# gluster volume status gfs_data detail

If the volume is stopped, start this

# gluster volume start gfs_data

Now the gluster volume is ready to mount. I need to mount this gluster volume on /data location to both of the node.

[root@vm2] # mount -t glusterfs vm1:/gfs_data /data
[root@vm1] # mount -t glusterfs vm2:/gfs_data /data

I can check volume status any time-

[root@vm2 ~]# gluster volume status gfs_data detail
Status of volume: gfs_data
------------------------------------------------------------------------------
Brick                : Brick vm1:/gb1/b1  
TCP Port             : 49152              
RDMA Port            : 0                  
Online               : Y                  
Pid                  : 1705               
File System          : xfs                
Device               : /dev/vdb1          
Mount Options        : rw,seclabel,relatime,attr2,inode64,noquota
Inode Size           : 512                
Disk Space Free      : 5.0GB              
Total Disk Space     : 5.0GB              
Inode Count          : 2620928            
Free Inodes          : 2620874            
------------------------------------------------------------------------------
Brick                : Brick vm2:/gb1/b1  
TCP Port             : 49152              
RDMA Port            : 0                  
Online               : Y                  
Pid                  : 1772               
File System          : xfs                
Device               : /dev/vdb1          
Mount Options        : rw,seclabel,relatime,attr2,inode64,noquota
Inode Size           : 512                
Disk Space Free      : 5.0GB              
Total Disk Space     : 5.0GB              
Inode Count          : 2621440            
Free Inodes          : 2621385   


[root@vm2 ~]# gluster volume info all

Volume Name: gfs_data
Type: Replicate
Volume ID: 946fa059-68f8-4685-a041-87a9e181c41c
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: vm1:/gb1/b1
Brick2: vm2:/gb1/b1
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off


You can check the peer status  from any node

[root@vm1 gb1]# gluster peer status
Number of Peers: 1

Hostname: vm2
Uuid: afdef858-f7e3-4e82-8f23-5d109834d620
State: Peer in Cluster (Connected)











[root@vm2 ~]# gluster peer status
Number of Peers: 1

Hostname: vm1
Uuid: 8daaa23d-d3bc-489d-81c5-f70b88abaceb
State: Peer in Cluster (Connected)

Comments

Post a Comment

Popular posts from this blog

Running web ssh client on port 443 /80 with nginx as reverse proxy

-
Package used         : shellinabox , nginx Repository used        : epel-release Linux distro used    : Centos 7.6 nginx reverse proxy server ip : 192.168.1.65 shellinabox web ssh server ip : 192.168.1.111 login to web ssh server first install epel-repo # yum install epel-release -y install shellinabox package # yum -y install shellinabox start and enable shellinaboxd service # systemctl enable shellinaboxd && systemctl start shellinaboxd By default shellinaboxd service starts with ssl port 4200 for us to run this in a reverse proxy environment need to make this as insecure hence the encryption will be done by nginx to end user. edit file /etc/sysconfig/shellinabox  like bellow- USER=shellinabox GROUP=shellinabox CERTDIR=/var/lib/shellinabox PORT=4200 OPTS="--disable-ssl-menu -s /:LOGIN" OPTS="-t -s /:SSH:192.168.1.111" save file exit and restart service # systemctl restart shellinaboxd Now open firewall for listening port 4200 from nginx proxy server only #
Read more

Running cockpit behind nginx reverse proxy with nginx ssl and cockpit non ssl

-
Domain for web access to cockpit : cockpit.mylab.local cockpit server ip : 192.168.1.61 nginx server ip   : 192.168.1.65 Linux distro using is Centos 7.6 Login to cockpit server Create a file [root@repo ~]# vim /etc/cockpit/cockpit.conf content will be like [WebService] Origins = https://cockpit.mylab.local wss://cockpit.mylab.local ProtocolHeader = X-Forwarded-Proto AllowUnencrypted = true save and restart cockpit # systemctl restart cockpit now  login to your nginx webserver and install nginx # yum install nginx -y create a new file vim /etc/nginx/conf.d/cockpit.conf paste content as bellow server {     listen         80;     listen         443 ssl http2;     server_name    cockpit.mylab.local;     ssl_certificate /etc/ssl/certs/cockpit-selfsigned.crt;     ssl_certificate_key  /etc/ssl/private/cockpit-selfsigned.key;     location / {         proxy_pass http://192.168.1.61:9090;         proxy_set_header Host $host;         proxy_http_version 1.1;
Read more

Setup VOD streaming server with nginx using RTMP on Ubuntu 18.04

-
Install required packages for source code nginx build # apt-get install -y build-essential ca-certificates wget curl libpcre3 libpcre3-dev autoconf unzip automake libtool tar git libssl-dev zlib1g-dev uuid-dev lsb-release vim htop sysstat ufw fail2ban makepasswd libgd-dev libgeoip-dev -y create a directory # mkdir /usr/local/src/nginx/ # cd /usr/local/src/nginx/ download and extract nginx tar # wget -qO- http://nginx.org/download/nginx-1.14.2.tar.gz | tar zxf - clone nginx rtmp module # git clone https://github.com/arut/nginx-rtmp-module Download other modules - PCRE version 8.42 # wget https://ftp.pcre.org/pub/pcre/pcre-8.42.tar.gz && tar xzvf pcre-8.42.tar.gz - zlib version 1.2.11 # wget https://www.zlib.net/zlib-1.2.11.tar.gz && tar xzvf zlib-1.2.11.tar.gz - OpenSSL version 1.1.0h # wget https://www.openssl.org/source/openssl-1.1.0h.tar.gz && tar xzvf openssl-1.1.0h.tar.gz # cd nginx-1.14.2/ configure  nginx with modules and options # ./configure --add-modu
Read more