<div dir="ltr">I think the external/internal address translation should be provided by the user. I'm working on a prototype here: <a href="https://github.com/slaskawi/infinispan/commit/eeeeae7b567fd84946cba90153d7abf2dd0d6641">https://github.com/slaskawi/infinispan/commit/eeeeae7b567fd84946cba90153d7abf2dd0d6641</a><div><br></div><div>I will tidy it up and send a pull request later this week.</div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, May 22, 2017 at 4:49 PM Tristan Tarrant <<a href="mailto:ttarrant@redhat.com">ttarrant@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We would need to provide a way to supply the external address at<br>
runtime, e.g. via JMX.<br>
<br>
Tristan<br>
<br>
On 5/22/17 2:50 PM, Sebastian Laskawiec wrote:<br>
> Hey Tristan!<br>
><br>
> I checked this part and it won't do the trick. The problem is that the<br>
> server does not know which address is used for exposing its services.<br>
> Moreover, this address can change with time.<br>
><br>
> Thanks,<br>
> Sebastian<br>
><br>
> On Tue, May 9, 2017 at 3:28 PM Tristan Tarrant <<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a><br>
> <mailto:<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>>> wrote:<br>
><br>
> Sebastian,<br>
> are you familiar with Hot Rod's proxyHost/proxyPort [1]. In server it is<br>
> configured using external-host / external-port attributes on the<br>
> topology-state-transfer element [2]<br>
><br>
><br>
><br>
> [1]<br>
> <a href="https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/main/java/org/infinispan/server/hotrod/configuration/HotRodServerConfigurationBuilder.java#L43" rel="noreferrer" target="_blank">https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/main/java/org/infinispan/server/hotrod/configuration/HotRodServerConfigurationBuilder.java#L43</a><br>
> [2]<br>
> <a href="https://github.com/infinispan/infinispan/blob/master/server/integration/endpoint/src/main/resources/schema/jboss-infinispan-endpoint_9_0.xsd#L203" rel="noreferrer" target="_blank">https://github.com/infinispan/infinispan/blob/master/server/integration/endpoint/src/main/resources/schema/jboss-infinispan-endpoint_9_0.xsd#L203</a><br>
><br>
><br>
> On 5/8/17 9:57 AM, Sebastian Laskawiec wrote:<br>
> > Hey guys!<br>
> ><br>
> > A while ago I started working on exposing Infinispan Cluster which is<br>
> > hosted in Kubernetes to the outside world:<br>
> ><br>
> > pasted1<br>
> ><br>
> > I'm currently struggling to get solution like this into the<br>
> platform [1]<br>
> > but in the meantime I created a very simple POC and I'm testing it<br>
> > locally [2].<br>
> ><br>
> > There are two main problems with the scenario described above:<br>
> ><br>
> > 1. Infinispan server announces internal addresses (172.17.x.x)<br>
> to the<br>
> > client. The client needs to remap them into external ones<br>
> (172.29.x.x).<br>
> > 2. A custom Consistent Hash needs to be supplied to the Hot Rod<br>
> client.<br>
> > When accessing cache, the Hot Rod Client needs to calculate<br>
> server<br>
> > id for internal address and then map it to the external one.<br>
> ><br>
> > If there will be no strong opinions regarding to this, I plan to<br>
> > implement this shortly. There will be additional method in Hot Rod<br>
> > Client configuration (ConfigurationBuilder#addServerMapping(String<br>
> > mappingClass)) which will be responsible for mapping external<br>
> addresses<br>
> > to internal and vice-versa.<br>
> ><br>
> > Thoughts?<br>
> ><br>
> > Thanks,<br>
> > Sebastian<br>
> ><br>
> > [1] <a href="https://github.com/kubernetes/community/pull/446" rel="noreferrer" target="_blank">https://github.com/kubernetes/community/pull/446</a><br>
> > [2] <a href="https://github.com/slaskawi/external-ip-proxy" rel="noreferrer" target="_blank">https://github.com/slaskawi/external-ip-proxy</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > infinispan-dev mailing list<br>
> > <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
> <mailto:<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a>><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> ><br>
><br>
> --<br>
> Tristan Tarrant<br>
> Infinispan Lead<br>
> JBoss, a division of Red Hat<br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a> <mailto:<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
> --<br>
><br>
> SEBASTIANŁASKAWIEC<br>
><br>
> INFINISPAN DEVELOPER<br>
><br>
> Red HatEMEA <<a href="https://www.redhat.com/" rel="noreferrer" target="_blank">https://www.redhat.com/</a>><br>
><br>
> <<a href="https://red.ht/sig" rel="noreferrer" target="_blank">https://red.ht/sig</a>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
<br>
--<br>
Tristan Tarrant<br>
Infinispan Lead<br>
JBoss, a division of Red Hat<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr"><p class="inbox-inbox-fullname-container" style="box-sizing:border-box;color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span class="inbox-inbox-firstname-container" style="box-sizing:border-box">SEBASTIAN</span><span class="inbox-inbox-Apple-converted-space"> </span><span class="inbox-inbox-lastname-container" style="box-sizing:border-box">ŁASKAWIEC</span></p><p class="inbox-inbox-position-container" style="box-sizing:border-box;color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span class="inbox-inbox-position" style="box-sizing:border-box">INFINISPAN DEVELOPER</span></p><p class="inbox-inbox-legal-container" style="box-sizing:border-box;font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a class="inbox-inbox-redhat-anchor" href="https://www.redhat.com/" target="_blank" style="box-sizing:border-box;color:rgb(0,136,206);margin:0px;text-decoration:none">Red Hat<span class="inbox-inbox-Apple-converted-space"> </span><span style="box-sizing:border-box">EMEA</span></a></p><table border="0" style="box-sizing:border-box;color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody style="box-sizing:border-box"><tr style="box-sizing:border-box"><td width="100px" style="box-sizing:border-box"><a href="https://red.ht/sig" style="box-sizing:border-box"><img width="90" height="auto" style="box-sizing: border-box;" src="https://www.redhat.com/files/brand/email/sig-redhat.png"></a></td></tr></tbody></table></div></div>