search

wildfly / wildfly-glow

Galleon Layers Output from War: Automatic discover of WildFly provisioning information from an application.
Apache License 2.0
7 stars 5 forks source link

High Availability Option #79

Closed fabrii closed 1 week ago

fabrii commented 2 weeks ago

When using "--ha" option, the produced standalone.xml does not change. I was expecting some additional subsystems as distributable-web or infinispan. Is this a bug or am I misunderstanding?

Thanks

fabrii commented 2 weeks ago

Adding <distributable/> to web.xml made it work

fabrii commented 2 weeks ago

Another related question:

Is --ha working together with --cloud ?

I read in some blogs, that for HA to work in Kubernetes/OpenShift, we need a discovery protocol called KUBE_PING, but I dont see references to this in the standalone when using both options (ha and cloud)

jfdenise commented 1 week ago

Hi @fabrii , yes DNS_PING will be automatically enabled when you deploy to the cloud. So --ha and --cloud are good together. You can give it a try by using the --provision=openshift --ha (you need to be connected to an openshift cluster such as the sandbox: https://developers.redhat.com/developer-sandbox The DNS_PING will be enabled in the deployment, a ping headless service will get started and, at startup time, the protocol will get added to the server configuration. BTW, we are working at a kind of dry-run of the openshift provisioning to "just" generate the openshift resources and Docker files allowing you to do that in offline mode.

fabrii commented 1 week ago

Thank you!