Skip to content
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.

Name configurable addresses to be more meaningful #221

Merged
merged 1 commit into from
Jan 18, 2017

Conversation

prashanthpai
Copy link
Contributor

The name of the configurable options should represent the services
provided or consumer of the port and not the protocol used.

  • Renamed 'rpcaddress' to 'peeraddress': Denotes the address used
    for peer to peer communication.
  • Renamed 'restaddress' to 'clientaddress': Denotes the address
    used by clients to communicate with glusterd2.

Coincidentally, these are analogous to those provided by etcd.

Signed-off-by: Prashanth Pai ppai@redhat.com

The name of the configurable options should represent the services
provided or consumer of the port and not the protocol used.

* Renamed 'rpcaddress' to 'peeraddress': Denotes the address used
  for peer to peer communication.
* Renamed 'restaddress' to 'clientaddress': Denotes the address
  used by clients to communicate with glusterd2.

Coincidentally, these are analogous to those provided by etcd.

Signed-off-by: Prashanth Pai <ppai@redhat.com>
Copy link
Member

@kshlm kshlm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In a GlusterFS context a client address would imply something a GlusterFS client would connect to. Renaming 'restaddress' to 'clientaddress' would give it the wrong meaning. I would prefer retaining 'restaddress' as it is. I'm okay with the 'peeraddress' change.

@prashanthpai
Copy link
Contributor Author

In a GlusterFS context a client address would imply something a GlusterFS client would connect to

That's exactly what this PR intends to do. Going forward, the port 24007 will be the port a GlusterFS client will connect to. Hence the name clientaddress. The same port will also serve REST requests from the clients

@kshlm kshlm merged commit 337e816 into gluster:master Jan 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants