gluster / gluster-ansible-cluster Goto Github PK

the var gluster_cluster_add_bricks is not mentioned anywhere in the docs and im thinking this was just a typo

I should be able to add a brick to the existing cluster

Acceptance criteria

• * Document the role variables.
• * Verify that the bricks are added and volume is started.
• * Verify that rebalance/self-heal is started
• * Add examples to demonstrate the role

Hi, I try to deploy glusterfs in raw machines but I got:

TASK [gluster.cluster/roles/gluster_volume : Start glusterd on the nodes if not already started] *************************************************************************************************************************************************************
failed: [devops-env1-glusterfs-zone1-01 -> 10.11.1.150] (item=devops-env1-glusterfs-zone1-01) => {"changed": false, "item": "devops-env1-glusterfs-zone1-01", "msg": "Could not find the requested service glusterd: host"}

Do I need to create manually ansible task to install it?

The variable 'gluster_cluster_options' is present in the file 'README.md' and in 'gluster-ansible-cluster/roles/gluster_volume/tasks', but in this last file the line is commented. The variable 'gluster_cluster_options' is presented but not usable.

How to set an option like 'gluster volume set myvol1 cluster.quorum-type auto' ?

Hi Contributors,

I am experimenting with this and the infra roles and i have successfully setup a cluster with 3 nodes, 2 bricks, replica set to 2 and arbiter count set to 1. I am not fully aware of many intricacies around Gluster but it looks like the Arbiter brick size used is the same as the normal bricks. Does this make sense? My understanding was that the arbiter doesn't need the same space as the normal bricks.

Thank you in advance.

README.md is empty. Should contain documentation to all the variables this role provides.

Currently, the code makes the assumption that the host from which gluster-ansible is run to set up the gluster cluster is connected to the gluster nodes with the same network that is used for gluster communication. This can be seen here: https://github.com/gluster/gluster-ansible-cluster/blob/master/roles/gluster_volume/tasks/main.yml#L7 and here : https://github.com/gluster/gluster-ansible/blob/master/playbooks/gluster-cluster/cluster-vars.yml#L65 .

It would be convenient to allow for those two networks to be separate. I stumbled across this while setting up automation for gluster-samba integration tests in gluster/samba-integration#16. In that scenario I tried to run the gluster-ansible playbook from a setup VM that would only be on the vagrant-libvirt network and not on the cluster network that is created for gluster. I am trying to work around that by adding the setup vm to the cluster network, but it should not be necessary.

I think the tying of the ansible connection to the cluster network is artifical and could be lifted.

Hello
i try install gluster on centos 7.6
Get error: Could not find the requested service glusterd: host

cat ansible.cfg 
[defaults]
inventory = hosts
remote_user = centos
host_key_checking = False
stdout_callback=debug

cat hosts
[gluster_servers]
gluster1 ansible_ssh_host=172.26.9.65
gluster2 ansible_ssh_host=172.26.9.67
gluster3 ansible_ssh_host=172.26.9.66

cat playbook.yml 
---
- name: Create Gluster cluster
  hosts: gluster_servers
  remote_user: centos
  gather_facts: false

  vars:
    # gluster volume
    gluster_cluster_hosts:
      - 172.26.9.65
      - 172.26.9.67
      - 172.26.9.66
    gluster_cluster_volume: testvol
    gluster_cluster_transport: 'tcp'
    gluster_cluster_force: 'yes'
    gluster_cluster_bricks: '/mnt/brick1/store,/mnt/brick2/store'

    # variables to create specific type of the volume
    gluster_cluster_replica_count: 3

    # variables to set specific volume options
    gluster_cluster_options: 'performance.cache-size:256MB'

  roles:
    - gluster.cluster

TASK [gluster.cluster/roles/gluster_volume : Start glusterd on the nodes if not already started] *************************************************************************************************************
failed: [gluster1 -> 172.26.9.65] (item=172.26.9.65) => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    }, 
    "ansible_loop_var": "item", 
    "changed": false, 
    "item": "172.26.9.65"
}

MSG:

Could not find the requested service glusterd: host

failed: [gluster1 -> 172.26.9.67] (item=172.26.9.67) => {
    "ansible_loop_var": "item", 
    "changed": false, 
    "item": "172.26.9.67"
}

MSG:

Could not find the requested service glusterd: host

failed: [gluster1 -> 172.26.9.66] (item=172.26.9.66) => {
    "ansible_loop_var": "item", 
    "changed": false, 
    "item": "172.26.9.66"
}

MSG:

Could not find the requested service glusterd: host

Hi,
In the example yml file the below line give error

roles:
  - gluster.volume

When I change this line to

roles:
  - gluster_volume

It works, becasue, I assume, the name of the role directory is "gluster_volume".
Thanks.