Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify list of hosts in separate inventory file #422

Open
mbukatov opened this issue Aug 11, 2017 · 1 comment
Open

Specify list of hosts in separate inventory file #422

mbukatov opened this issue Aug 11, 2017 · 1 comment

Comments

@mbukatov
Copy link
Contributor

mbukatov commented Aug 11, 2017

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

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:

$ gdeploy -c example.conf

Desired state

I'm able to keep the list of servers in a separate file:

$ cat glusterservers.hosts
10.70.43.127
10.70.42.190
10.70.42.232
10.70.43.67

so that the gluster config file would be just:

# 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
@mbukatov
Copy link
Contributor Author

Does this feature make sense or do I miss something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant