Bug 763739 (GLUSTER-2007) - [FEAT] Need glusterd to listen or communicate thru a specific network
Summary: [FEAT] Need glusterd to listen or communicate thru a specific network
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-2007
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.1.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-25 11:17 UTC by Timothy Asir
Modified: 2012-12-21 11:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-21 11:12:40 UTC
Regression: ---
Mount Type: ---
Documentation: DNR
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Timothy Asir 2010-10-25 11:17:12 UTC 
An option is required in gluster(d) to listen or communicate thru a given private network. This is a required feature for platform HA implementation.
Comment 1 Anand Avati 2010-10-29 01:12:13 UTC 
Why is this feature required? Please explain the necessity.
Comment 2 Amar Tumballi 2011-04-25 09:00:43 UTC 
Not sure if this is required for Platform HA or not. Overall, its nice to provide an option to bind glusterd to one particular IP (which can be done by 'option bind-address' now in glusterd.vol file). But surely it would be good to keep an option in CLI to make bricks bind to one particular IP. As of today its INADDR_ANY
Comment 3 Amar Tumballi 2012-12-21 11:12:40 UTC 
workaround for this is to add an option 'bind-address' in glusterd.vol file. Closing as WORKSFORME as bind-address is present for the exact same reason.
Note You need to log in before you can comment on or make changes to this bug.