<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Do you think that people will use
cluster with 2 nodes on localhost + embedded H2 + static
loadbalancer in production? I guess not. So having our domain.xml
"pre-set" to have easy example cluster setup won't help much IMO.
Customers will be able to setup "easy" cluster in 5 minutes, but
they will be unaware of all the steps they need to set the real
"production" cluster. <br>
<br>
Also there is inconsistency with Wildfly, which may lead to some
other confusions (as you pointed in other thread for add-user
script).<br>
<br>
I think that what would be helpful is, to guide people through all
the manual steps more deeply, so after "absolve" the tutorial,
they will be able to set the domain with real production cluster
in their environment with 2 remote nodes on different machines
communicate between each other. And they will know the
possibilities for setup real loadbalancer too (HTTPD+modcluster or
Undertow+modcluster etc). But I am not sure how deep to go there,
as loadbalancer is not directly our stuff...<br>
<br>
Also maybe it would be helpful to have some guides for setup AWS
or JGroups without Multicast, but with TCP and TCPPING. I know
it's not our stuff, but you know... There were gazillion questions
regarding this in last months <span class="moz-smiley-s3"><span>
;-) </span></span><br>
<br>
Marek<br>
<br>
On 23/04/16 14:52, Bill Burke wrote:<br>
</div>
<blockquote cite="mid:571B701C.5030202@redhat.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
This helps out with documenting domain mode to have an almost
working example that I can walk through and explain. The current
distribution doesn't really help with that. There's going to be
more of this stuff. This is why I wanted to start on
documentation in January as I knew little usability things like
this would pop up. So, deal with it... <br>
<br>
Honestly, I should have just done this as I knew you were going to
be a pain in the ass...<br>
<br>
<div class="moz-cite-prefix">On 4/23/2016 1:31 AM, Stian
Thorgersen wrote:<br>
</div>
<blockquote
cite="mid:CAJgngAc9d6vs3kipgODmrBrP_iZZvVadn4wsvXW0nbuM=j9frQ@mail.gmail.com"
type="cite">
<p dir="ltr">I vote against this. It's way to late to start
making changes unless absolutely critical. At the moment we're
just doing what WildFly/EAP does out of the box and I don't
see any need for us to do different to them.</p>
<div class="gmail_quote">On 22 Apr 2016 20:43, "Bill Burke" <<a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:bburke@redhat.com"><a class="moz-txt-link-abbreviated" href="mailto:bburke@redhat.com">bburke@redhat.com</a></a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I'd like
to make the following changes to domain.xml that we
distribute<br>
so that it runs as a cluster with a load balance out of the
box on one<br>
machine:<br>
<br>
* remove the "default" profile. Users should really only be
using<br>
domain mode with a cluster<br>
* remove host.xml. Its confusing to have both a host.xml
and a<br>
host-master.xml<br>
* host-master.xml will boot only 1 server ("server-one")<br>
* host-slave.xml will boot only 1 server ("server-two")<br>
* Pre-configure a undertow load balancer [1] to loadbalance
between<br>
server one and server two<br>
* Point H2 to a shared directory under domain/servers<br>
<br>
I've checked that this setup works on my laptop. I hope to
write a<br>
Getting Started Guide around this too.<br>
<br>
[1]<br>
<a moz-do-not-send="true"
href="https://docs.jboss.org/author/display/WFLY10/Using+Wildfly+as+a+Load+Balancer"
rel="noreferrer" target="_blank">https://docs.jboss.org/author/display/WFLY10/Using+Wildfly+as+a+Load+Balancer</a><br>
<br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a moz-do-not-send="true"
href="http://bill.burkecentral.com" rel="noreferrer"
target="_blank">http://bill.burkecentral.com</a><br>
<br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/keycloak-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bill Burke
JBoss, a division of Red Hat
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://bill.burkecentral.com">http://bill.burkecentral.com</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></pre>
</blockquote>
<br>
</body>
</html>