mirror of
https://github.com/gluster/gluster-block.git
synced 2026-02-05 12:45:33 +01:00
471401c48a
* gluster-blockd: support volfile server setting through Env This patch is majorly for GCS and kube use-case, where the discovery service, whos name look like FQDN will resolve the backend volfile servers path, for each and every block hosting volume from all the associated pods/nodes in the cluster. As of today gluster-blockd and tcmu-runner use localhost as volfile server address to communicate with block hosting volumes, with this patch series we will provide a way to set volfile server address (discovery service) of a remote/separate gluster cluster, where the block hosting volume is running out- side the gluster-block (daemon running) nodes. This way, we achieve the isolation between the glusterd and gluster-blockd daemons, and hence they both can now run in different nodes/pods. Thanks to Amar Tumballi <amarts@redhat.com> for all the discussions around this subject. Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com> * replace: support volfile server setting through Env Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com> * genconfig: support volfile server setting through Env Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com> * config: support volfile server setting through config file Just uncommnet below line at /etc/sysconfig/gluster-blockd and change the value to fit discovery service name, Ex: > #GB_BHV_VOLSERVER="localhost" GB_BHV_VOLSERVER="dhcpXX-YYY.lab.github.com" followed by restart of gluster-blockd.service to take changes into effect. Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com> Reviewed & Tested-by: Xiubo Li <xiubli@redhat.com> Reviewed-by: Amar Tumballi <amarts@redhat.com>