{"action":"opened","issue":{"url":"https://api.github.com/repos/ansible/ansible/issues/45474","repository_url":"https://api.github.com/repos/ansible/ansible","labels_url":"https://api.github.com/repos/ansible/ansible/issues/45474/labels{/name}","comments_url":"https://api.github.com/repos/ansible/ansible/issues/45474/comments","events_url":"https://api.github.com/repos/ansible/ansible/issues/45474/events","html_url":"https://github.com/ansible/ansible/issues/45474","id":358913817,"node_id":"MDU6SXNzdWUzNTg5MTM4MTc=","number":45474,"title":"gluster_volume brick path and arbiter nodes ","user":{"login":"zem","id":197972,"node_id":"MDQ6VXNlcjE5Nzk3Mg==","avatar_url":"https://avatars0.githubusercontent.com/u/197972?v=4","gravatar_id":"","url":"https://api.github.com/users/zem","html_url":"https://github.com/zem","followers_url":"https://api.github.com/users/zem/followers","following_url":"https://api.github.com/users/zem/following{/other_user}","gists_url":"https://api.github.com/users/zem/gists{/gist_id}","starred_url":"https://api.github.com/users/zem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zem/subscriptions","organizations_url":"https://api.github.com/users/zem/orgs","repos_url":"https://api.github.com/users/zem/repos","events_url":"https://api.github.com/users/zem/events{/privacy}","received_events_url":"https://api.github.com/users/zem/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-11T07:05:18Z","updated_at":"2018-09-11T07:05:18Z","closed_at":null,"author_association":"NONE","body":"##### SUMMARY\r\n\r\nThe system that combines the host part of the brick path  with the vfs part of the brick path only works for the special situation when every host provides the same brick path vor its vfs. \r\n\r\nWith a 2 rack 2 location setup I am using a seperate arbiter node in one of the racks to prevent splitbrain. Due to the nature of an arbiter node keeping only metadata, its discs can hold metadata for more than one brick group. The following example cant be set up with the gluster_volume module: \r\n\r\n```\r\nBrick1: rack1server1.virt.local:/data/sda/bricks/images\r\nBrick2: rack2server1.virt.local:/data/sda/bricks/images\r\nBrick3: arbiter1.virt.local:/data/sda/bricks/images_sda_server1_arbiter (arbiter)\r\nBrick4: rack1server1.virt.local:/data/sdb/bricks/images\r\nBrick5: rack2server1.virt.local:/data/sdb/bricks/images\r\nBrick6: arbiter1.virt.local:/data/sda/bricks/images_sdb_server1_arbiter (arbiter)\r\n```\r\n\r\nI would have expected just to have a list of bricks going under bricks which would perfectly reflect the setup above. It would also be good to improve the documentation because I had to look in the code to find out how it is working. \r\n\r\n\r\n##### ISSUE TYPE\r\n- Feature Idea\r\n\r\n##### COMPONENT NAME\r\n- gluster_volume\r\n"}}
{"actor":{"display_login":"zem"}}