Question: does this change how Glusterfs can be utilized in a virtualized context, including with VMware? My understanding was that the virtual IP handling in VMware had previously presented problems. -------- Original Message -------- Subject: Change in glusterfs[master]: nlm: use virtual ip of server to connect to client From: "Rajesh Amaravathi (Code Review)" <root@xxxxxxxxxxxxxxx> To: CC: Rajesh Amaravathi has uploaded a new change for review. Change subject: nlm: use virtual ip of server to connect to client ...................................................................... nlm: use virtual ip of server to connect to client In cases where the servers use virtual ip's, this commit makes sure we use them and not the physical ip. This change also refactors code around nlm4_establish_callback by sending granted msg only after a connection establishment. Change-Id: I087362c547a25aa52ef7fc6653845a3863466ee6 BUG: 888283 Signed-off-by: Rajesh Amaravathi <rajesh@xxxxxxxxxx> --- M rpc/rpc-transport/socket/src/socket.c M xlators/nfs/server/src/nlm4.c M xlators/nfs/server/src/nlm4.h 3 files changed, 83 insertions(+), 69 deletions(-) git pull ssh://git.gluster.org/glusterfs refs/changes/26/4326/1 -- To view, visit http://review.gluster.org/4326 To unsubscribe, visit http://review.gluster.org/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I087362c547a25aa52ef7fc6653845a3863466ee6 Gerrit-PatchSet: 1 Gerrit-Project: glusterfs Gerrit-Branch: master Gerrit-Owner: Rajesh Amaravathi <rajesh@xxxxxxxxxx>
