[
https://issues.apache.org/jira/browse/CURATOR-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706983#comment-15706983
]
ASF GitHub Bot commented on CURATOR-360:
----------------------------------------
GitHub user IMS94 opened a pull request:
https://github.com/apache/curator/pull/175
[CURATOR-360] Allow TestingCluster to listen on other network interfaces
Currently, when we create a TestingCluster, all the TestingServers will be
bound to the local interface (127.0.0.1). This becomes a constraint if we want
to run a TestingCluster which can be used for testing over a network (say LAN).
To provide more flexibility over network interfaces, I have added the
concept of **hostname** into the **InstanceSpec** class in this PR.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/IMS94/curator CURATOR-360
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/175.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #175
----
commit 0a0a1e7d8beac27cd07dd0f445e55e9c6646e10c
Author: Imesha <[email protected]>
Date: 2016-11-29T23:55:24Z
CURATOR-360 - Allow Zookeeper servers in TestingCluster to listen on
network interfaces other than localhost
----
> Allow Zookeeper servers in TestingCluster to listen on network interfaces
> other than localhost
> ----------------------------------------------------------------------------------------------
>
> Key: CURATOR-360
> URL: https://issues.apache.org/jira/browse/CURATOR-360
> Project: Apache Curator
> Issue Type: Improvement
> Components: Tests
> Reporter: Imesha Sudasingha
> Priority: Minor
> Labels: test-framework
>
> Currently, when we create a TestingCluster, all the TestingServers will be
> bound to the local interface (127.0.0.1). This becomes a constraint if we
> want to run a TestingCluster which can be used for testing over a network
> (say LAN).
> In order to address that we can add a hostname to be provided optionally in
> the InstanceSpec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)