You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not possible to keep list of gluster servers and gluster configurations separate.
Version
gdeploy-2.0.2-7.noarch (from sac-gdeploy copr)
Current state
List of gluster machines is placed in a [hosts] section in gdeploy config file like this:
# This is a mandatory section, and hostnames/ip-address are listed one per line.
[hosts]
10.70.43.127
10.70.42.190
10.70.42.232
10.70.43.67
# Backend setup for all the hosts listed inside [hosts] section
[backend-setup]
devices=/dev/vdb
mountpoints=/gluster/brick1
brick_dirs=/gluster/brick1/one
# Backend setup for all the hosts listed inside [hosts] section
[backend-setup]
devices=/dev/vdb
mountpoints=/gluster/brick1
brick_dirs=/gluster/brick1/one
and I would execute gdeploy like this:
$ gdeploy -i glusterservers.hosts -c example.conf
The text was updated successfully, but these errors were encountered:
It's not possible to keep list of gluster servers and gluster configurations separate.
Version
gdeploy-2.0.2-7.noarch (from sac-gdeploy copr)
Current state
List of gluster machines is placed in a
[hosts]
section in gdeploy config file like this:Example comes from Write a config file to do the backend setup
So that everything is specified in a single file, which is passed to gdeploy like this:
Desired state
I'm able to keep the list of servers in a separate file:
so that the gluster config file would be just:
and I would execute gdeploy like this:
The text was updated successfully, but these errors were encountered: