Add new script to start the GossipRouter

[pruivo]

In k8s, we can use the same image to start the infinispan server (default entrypoint)
or the gossip router server

The gossip router server will be used to provide cross-site replication
between k8s clusters (a.k.a. Gossip Router Tunnel).

Tested locally and it will be consumed by infinispan/infinispan-operator#1201

$ podman run --entrypoint /opt/gossiprouter/bin/launch.sh infinispan/server -port 8080

GossipRouter started in 95 ms listening on 0.0.0.0:8080

[ryanemerson]

Ideally this should be a native binary that is contained within it's own minimal image based upon ub8-micro. Upstream the JGroups project could use a GH action to create the binary and package it in a container. Downstream might be trickier though, WDYT?

[pruivo]

AFAIK, we don't support native images downstream; I think using the JGroups jar inside our image is the best way:

• It uses the productized JGroups inside our image
• The infinispan server image is built for multiple platforms

Using an image with the Gossip Router (there is an old one here: https://registry.hub.docker.com/r/jboss/jgroups-gossip) it would require changing the operator code for upstream and downstream

• upstream would use the gossip router image
• downstream the infinispan server image

is it worth the trouble?

IMO, I think Tristan's idea will be simpler: https://infinispan.zulipchat.com/#narrow/stream/118645-infinispan/topic/meeting-20210726/near/247210074

[ryanemerson]

IMO, I think Tristan's idea will be simpler: https://infinispan.zulipchat.com/#narrow/stream/118645-infinispan/topic/meeting-20210726/near/247210074

Isn't that the same as mine? Or do you just mean a native binary stored within our existing image?

is it worth the trouble?

Probably not 😃

If we can't have native binaries downstream then I'm happy to go with this approach for now and we can refactor later as required.

[pruivo]

I mean storing the GossipRouter binary in our infinispan-server native image.

[ryanemerson]

Thanks @pruivo