Admin server must know all managed servers in advance to create a cluster.

[diegoliber]

Currently, in order to create a cluster of managed servers using the orawls module, I need to define a priori all resources related to machines, managed servers, channels and clusters. Also, in the moment of creation of the admin server, I must also know all the hostnames, IP addresses and ports of all my weblogic infrastructure.

This means I can't create a weblogic infrastructure using orawls in a dynamic infrastructure such as a private cloud, where the hostnames or IP addresses are defined dynamically, without using some script to update hiera or the ENC on the machine startup. This also means that any change on the cluster topology, the Puppet agent must run again on the machine which hosts the AdminServer, followed by another run on each machine who hosts a ManagedServer, in this order.

This happens because only the wls_cluster resource has the ability to inform which servers may belong to a given cluster. If the wls_server resource were able to provide the info of which cluster it would belong to instead, it would be possible to both create all cluster in the Admin Server or in each separate Managed Server dynamically.

The choice of putting this configuration in the wls_cluster was specially interesting since in WLST only a managed server may define the cluster where it belongs, never the opposite (cd("/Servers/ManagedServerXX") ; cmo.setCluster(getMBean("MyCluster")). I tested locally using a vagrant project and was able to configure a WL cluster dynamically using WLST scripts.

The questions are:

1. Was there any reason for forcing the definition of all managed servers in the admin server machine?
2. I want to know if a contribution on modifying the wls_server resource to provide cluster information would be acceptable.

[biemond]

Hi

Can you check this #200, it should at least cover some of your wanted configuration

you can do this on a wls_server

server_parameters:                     'WebCluster'

and on wls_cluster use this.

servers: 'inherited'

Should also work for wls_datasource.

For 1 is more you can do all the configuration ( more handy) over there especially with FMW add-ons, make it work and after that do a pack/unpack. Node provisioning would then be very simple.
But you can connect to the admin server from there and do the above.

2. PR are always welcome

thanks