[
https://issues.redhat.com/browse/WFWIP-334?page=com.atlassian.jira.plugin...
]
Martin Choma edited comment on WFWIP-334 at 8/27/20 2:50 AM:
-------------------------------------------------------------
There is lot of environment properties in s2i which are related to configuring clustering
(~10) . [1]
{code}
OPENSHIFT_KUBE_PING_*
OPENSHIFT_DNS_PING_*
JGROUPS_*
{code}
If I understand correctly what you are suggesting here is add support for one of them
{{JGROUPS_PING_PROTOCOL}}. But that leaves us with 10 other properties where customer need
to leverage custom CLI anyway. My point is if it so helpful for user - I assume it is just
changing one value in model?
My feeling from yesterdays meeting was design purpose is to keep <cloud> logic as
small as possible.
[1]
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
was (Author: mchoma):
There is lot of environment properties in s2i which are related to configuring clustering
(~10) . [1]
If I understand correctly what you are suggesting here is add support for one of them
{{JGROUPS_PING_PROTOCOL}}. But that leaves us with 10 other properties where customer need
to leverage custom CLI anyway. My point is if it so helpful for user - I assume it is just
changing one value in model?
{code}
OPENSHIFT_KUBE_PING_*
OPENSHIFT_DNS_PING_*
JGROUPS_*
{code}
My feeling from yesterdays meeting was design purpose is to keep <cloud> logic as
small as possible.
[1]
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
Bootable JAR - Cloud - Support for dns.DNS_PING
-----------------------------------------------
Key: WFWIP-334
URL:
https://issues.redhat.com/browse/WFWIP-334
Project: WildFly WIP
Issue Type: Feature Request
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
Priority: Major
Currently kubernetes.KUBE_PING is the protocol in use when cloud is enabled.
KUBE_PING, although requiring an Openshift permission, is the simpler configuration wise
(just need KUBERNETES namespace and your are done).
DNS_PING doesn't require the extra permission but requires a new service (to expose
the port 8888 in the pod) to be created.
I propose that we keep KUBE_PING as the default protocol and extend the cloud element
with a <ping-protocol>kubernetes.KUBE_PING|dns.DNS_PING</ping-protocol>
element.
The env variable used to set the service name is the same as EAP/XP S2I builder
image: OPENSHIFT_DNS_PING_SERVICE_NAME
web-clustering example will be evolved with a profile to support DNS_PING (and also to
contain a yaml example file of the ping service).
[~luck3y], [~mchoma], [~brian.stansberry] [~fburzigo] that is the proposal to also cover
DNS_PING.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)