Using wipefs free#

Get informations about one node, you can apply the command again with another node idДҐ.Get more informations about the cluster.This step from the previous procedure is optional, I am using it just to get more visibility about what is happening, and also a small reminder for whomever that uses the second procedure. Connect to a master node or any machine that have a remote and configured kubectl.Д¤. You can make sure to clear up your volume by using:ДЈ.Create and attach the volume to instance, for example: /dev/xvdc.Please note that the volume must be unmounted and empty, no partition or filesystem must be created on it, so it can be used by heketi.

These steps are inspired from IBMвЂ™s website. This method is most likely used when you cannot increase volume sizes on-the-fly, and you have to add another volume in order to expand storage capacity in your cluster. In this case, IвЂ™m going to add a new storage device to heketi topology. Add another storage device to heketi topology At last, do not forget to run the same resync command for all glusterFS nodes (node4, node6 in my case).ДЄnd now you have just increased volume capacity in your cluster.

Using wipefs free#

# Get updated informations about node5 kubectl -n kube-system exec heketi-d55cbd78c-7tj8c -n kube-system - heketi-cli - user admin - secret XXXXX node info 9ac5b33d03759ba7d9b161b879a4ea39 Node Id: 310744c2908338d7d229268a4445951b State: online Cluster Id: 65ddc905b8a32dc49db721a004a08ead Zone: 1 Management Hostname: node5 Storage Hostname: 10.0.XX.XX Devices: Id:Id:a1751200878b2bb0a64d89a15e3bc801 Name:/dev/xvdb State:online Size (GiB):64 Used (GiB):22 Free (GiB):42 Bricks:3Д§. Once the resync is done, you can check again the node to see what has changed. It looks like: вЂ™ | base64 -d # List heketi cluster Name kubectl -n kube-system exec heketi-d55cbd78c-7tj8c -n kube-system - heketi-cli - user admin - secret XXXXXX cluster list ClusterId: Id:65ddc905b8a32dc49db721a004a08ead # Get detailed informations about the cluster kubectl -n kube-system exec heketi-d55cbd78c-7tj8c -n kube-system - heketi-cli - user admin - secret XXXXX cluster info 65ddc905b8a32dc49db721a004a08ead Cluster id: 65ddc905b8a32dc49db721a004a08ead Nodes: 310744c2908338d7d229268a4445951b 9ac5b33d03759ba7d9b161b879a4ea39 e0fd9cbad89eac2989cff2b426a59288 Volumes: 29e2a3fd578bb98a7d44e9a538cc9e74 7c955fe8dff62136046fc5c794abb6a5 b22ad96e06a4bff70c16e9fe61a4ed50 Block: true File: true # Get informations about one node, you can apply the command again with another node id kubectl -n kube-system exec heketi-d55cbd78c-7tj8c -n kube-system - heketi-cli - user admin - secret XXXXX node info 9ac5b33d03759ba7d9b161b879a4ea39 Node Id: 310744c2908338d7d229268a4445951b State: online Cluster Id: 65ddc905b8a32dc49db721a004a08ead Zone: 1 Management Hostname: node5 Storage Hostname: 10.0.XX.XX Devices: Id: a1751200878b2bb0a64d89a15e3bc801 Name:/dev/xvdb State:online Size (GiB):34 Used (GiB):22 Free (GiB):12 Bricks:3 # Resync device kubectl -n kube-system exec heketi-d55cbd78c-7tj8c -n kube-system - heketi-cli - user admin - secret XXXXX device resync a1751200878b2bb0a64d89a15e3bc801 Device updatedД¦. It contains the nodesвЂ™ IP addresses and the storage devices to use in each nodeвЂќ.

Topology.json, вЂњheketi uses this configuration file to define cluster nodes topology for GlusterFS. вЂњ Heketi provides a RESTful management interface which can be used to manage the lifecycle of GlusterFS volumesвЂќ.

вЂњGluster is a scalable, distributed file system that aggregates disk storage resources from multiple servers into a single global namespaceвЂќ. In this short article I will show you two ways of doing it.Д«efore going deeper, let me introduce you the context and some terminologies that will be used throughout this article. One of the common issues when using a persistent volume solution in Kubernetes, like GlusterFS, is to start running out of storage capacity in your cluster, and you have to find a smooth way to increase volume size without losing your data.