> This won't work. The load balancer has to be separate from the Gluu Servers.
This is how the Cluster Manager did it, we didn't change or enter anything manually. Following the documentation we chose the external LB which only asked for the FQDN, this was entered. It also asked for the proxy FQDN and IP which was entered, but it didn't seem to do anything with it at this stage, so not sure if it will, the documentation is not clear if there is a manual setup required from us. After entering the data and filling out the data for the primary and replica the installation went through and the hosts file in the chroot for both idp1 and idp2 was filled by the Cluster Manager as given above.
The fail to connect is also bizarre, we can login to the chroot of ipd2 and see the server (ipd1) from there. This is also why we asked which server is looking for which server here, because both can see and reach both. Double-checked the ports as well and it's enabled for both from both plus from the cluster manager. Can also be reached from within the chroot (used telnet for the there).
For the OpenDJ issue - we've performed three installations from scratch in a span of a couple of hours on Monday
> please note that use of Cluster Manager reuiqres a Gluu Support contract when used in production.
Yes, this also matches our policy of having a support contract for production systems so no issues there. We'd like to get through a successful setup first though, there were other issues during POC and review that need to be clarified from the operational point of view, but we'll open a separate ticket for those. We'd just like to get through the issues here first, after three tries it doesn't seem to be useful to do the same from scratch install again just to get the same result.