You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@geode.apache.org by GitBox <gi...@apache.org> on 2020/11/20 09:47:27 UTC

[GitHub] [geode] albertogpz opened a new pull request #5766: GEODE-8738: Updated documentation about WAN deployments with sites wi…

albertogpz opened a new pull request #5766:
URL: https://github.com/apache/geode/pull/5766


   …th the same IP address and port for all gateway receivers
   
   Thank you for submitting a contribution to Apache Geode.
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
   
   - [ ] Has your PR been rebased against the latest commit within the target branch (typically `develop`)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [ ] Does `gradlew build` run cleanly?
   
   - [ ] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Note:
   Please ensure that once the PR is submitted, check Concourse for build issues and
   submit an update to your PR as soon as possible. If you need help, please send an
   email to dev@geode.apache.org.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] davebarnes97 merged pull request #5766: GEODE-8738: Updated documentation about WAN deployments with sites wi…

Posted by GitBox <gi...@apache.org>.
davebarnes97 merged pull request #5766:
URL: https://github.com/apache/geode/pull/5766


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] davebarnes97 commented on pull request #5766: GEODE-8738: Updated documentation about WAN deployments with sites wi…

Posted by GitBox <gi...@apache.org>.
davebarnes97 commented on pull request #5766:
URL: https://github.com/apache/geode/pull/5766#issuecomment-731438229


   @albertogpz Thank you for your contribution.
   I have edited your text for format and style, but I am unable to push my changes to your fork. I attach the file here so you can incorporate my changes from your side. Please let me know if you'd like to receive these changes in another way.
   Best regards, and thanks!
   [GEODE-8738-edit.zip](https://github.com/apache/geode/files/5576363/GEODE-8738-edit.zip)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] albertogpz commented on a change in pull request #5766: GEODE-8738: Updated documentation about WAN deployments with sites wi…

Posted by GitBox <gi...@apache.org>.
albertogpz commented on a change in pull request #5766:
URL: https://github.com/apache/geode/pull/5766#discussion_r533197364



##########
File path: geode-docs/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html.md.erb
##########
@@ -387,3 +387,51 @@ boglesbymac(ny-3:88715)<v4>:36808 | 5371 | 5            |["boglesbymac(ln-1:8865
 boglesbymac(ny-4:88724)<v5>:52993 | 5247 | 6            |["boglesbymac(ln-1:88651)<v2>:48277","boglesbymac(ln-4:88681)<v5>:42784","boglesbymac(ln-2:88662)<v3>:12796","boglesbymac(ln-3:88672)<v4>:43675"]
 ```
 
+### <a id="setting_up_a_multisite_system__section_E3A44F85359046C7ADD12861D261637C" class="no-quick-link"></a>Configuring just one IP address and port to access all gateway receivers in a site
+
+There could be WAN deployments in which we do not want to expose the IP address and port of every gateway receiver to the other site but instead expose just one IP address and port for all gateway receivers. This way, the internal topology of the site is hidden to the other site. This case is quite common in cloud deployments, in which a reverse proxy/load balancer distributes incoming requests to the site (in our case, replication requests) among the available servers (in our case, gateway receivers).
+
+<%=vars.product_name%> supports this configuration by means of a particular use of the hostname-for-senders, start-port and end-port parameters of the gateway receiver.
+
+In order to configure a WAN deployment that hides the gateway receivers behind the same IP address and port, all the gateway receivers must have the same value for the hostname-for-senders parameter (the hostname or IP address to be used by clients to access them) and the same value in the start-port and end-port parameters (the port to be used by clients to access them).
+
+As an example, a deployment in which all gateway receivers of a site are accessed via the "gateway1.mycompany.com" hostname and port "1971", every gateway receiver in that site must be configured as follows:
+
+``` pre
+gfsh> create gateway-receiver --hostname-for-senders="gateway1.mycompany.com" --start-port=1971 --end-port=1971
+```
+
+The following output shows how the receiver side would look like after this configuration if 4 gateway recievers were configured:

Review comment:
       Good catch, Alberto! Thanks.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] alb3rtobr commented on a change in pull request #5766: GEODE-8738: Updated documentation about WAN deployments with sites wi…

Posted by GitBox <gi...@apache.org>.
alb3rtobr commented on a change in pull request #5766:
URL: https://github.com/apache/geode/pull/5766#discussion_r532989605



##########
File path: geode-docs/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html.md.erb
##########
@@ -387,3 +387,51 @@ boglesbymac(ny-3:88715)<v4>:36808 | 5371 | 5            |["boglesbymac(ln-1:8865
 boglesbymac(ny-4:88724)<v5>:52993 | 5247 | 6            |["boglesbymac(ln-1:88651)<v2>:48277","boglesbymac(ln-4:88681)<v5>:42784","boglesbymac(ln-2:88662)<v3>:12796","boglesbymac(ln-3:88672)<v4>:43675"]
 ```
 
+### <a id="setting_up_a_multisite_system__section_E3A44F85359046C7ADD12861D261637C" class="no-quick-link"></a>Configuring just one IP address and port to access all gateway receivers in a site
+
+There could be WAN deployments in which we do not want to expose the IP address and port of every gateway receiver to the other site but instead expose just one IP address and port for all gateway receivers. This way, the internal topology of the site is hidden to the other site. This case is quite common in cloud deployments, in which a reverse proxy/load balancer distributes incoming requests to the site (in our case, replication requests) among the available servers (in our case, gateway receivers).
+
+<%=vars.product_name%> supports this configuration by means of a particular use of the hostname-for-senders, start-port and end-port parameters of the gateway receiver.
+
+In order to configure a WAN deployment that hides the gateway receivers behind the same IP address and port, all the gateway receivers must have the same value for the hostname-for-senders parameter (the hostname or IP address to be used by clients to access them) and the same value in the start-port and end-port parameters (the port to be used by clients to access them).
+
+As an example, a deployment in which all gateway receivers of a site are accessed via the "gateway1.mycompany.com" hostname and port "1971", every gateway receiver in that site must be configured as follows:
+
+``` pre
+gfsh> create gateway-receiver --hostname-for-senders="gateway1.mycompany.com" --start-port=1971 --end-port=1971
+```
+
+The following output shows how the receiver side would look like after this configuration if 4 gateway recievers were configured:

Review comment:
       There is a typo: "recievers"




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [geode] albertogpz commented on pull request #5766: GEODE-8738: Updated documentation about WAN deployments with sites wi…

Posted by GitBox <gi...@apache.org>.
albertogpz commented on pull request #5766:
URL: https://github.com/apache/geode/pull/5766#issuecomment-731541699


   > @albertogpz Thank you for your contribution.
   > I have edited your text for format and style, but I am unable to push my changes to your fork. I attach the file here so you can incorporate my changes from your side. Please let me know if you'd like to receive these changes in another way.
   > Best regards, and thanks!
   > [GEODE-8738-edit.zip](https://github.com/apache/geode/files/5576363/GEODE-8738-edit.zip)
   
   @davebarnes97 , thanks for the review and the appropriate corrections. I agree to all of them.
   Might be good that @boglesby or @bschuchardt take a look at the text too.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org