Sebastian,
are you familiar with Hot Rod's proxyHost/proxyPort [1]. In server it is
configured using external-host / external-port attributes on the
topology-state-transfer element [2]
[1]
https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/ma...
[2]
https://github.com/infinispan/infinispan/blob/master/server/integration/e...
On 5/8/17 9:57 AM, Sebastian Laskawiec wrote:
Hey guys!
A while ago I started working on exposing Infinispan Cluster which is
hosted in Kubernetes to the outside world:
pasted1
I'm currently struggling to get solution like this into the platform [1]
but in the meantime I created a very simple POC and I'm testing it
locally [2].
There are two main problems with the scenario described above:
1. Infinispan server announces internal addresses (172.17.x.x) to the
client. The client needs to remap them into external ones (172.29.x.x).
2. A custom Consistent Hash needs to be supplied to the Hot Rod client.
When accessing cache, the Hot Rod Client needs to calculate server
id for internal address and then map it to the external one.
If there will be no strong opinions regarding to this, I plan to
implement this shortly. There will be additional method in Hot Rod
Client configuration (ConfigurationBuilder#addServerMapping(String
mappingClass)) which will be responsible for mapping external addresses
to internal and vice-versa.
Thoughts?
Thanks,
Sebastian
[1]
https://github.com/kubernetes/community/pull/446
[2]
https://github.com/slaskawi/external-ip-proxy
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat