Cannot set frontEndHost & frontEnd ports on a Managed server about biemond-orawls HOT 3 CLOSED

Hi Josh,

that would be very appreciated.

Thanks to @mkelderm for adding this feature last week to a cluster. You can re-use the same properties and move them from lib/puppet/type/wls_cluster to lib/puppet/type/shared

wls_cluster { 'WebCluster2':
  ensure                  => 'present',
  messagingmode           => 'unicast',
  migrationbasis          => 'consensus',
  servers                 => ['wlsServer3','wlsServer4'],
  unicastbroadcastchannel => 'channel',
  multicastaddress        => '239.192.0.0',
  multicastport           => '7001',
  frontendhost            => '10.10.10.10'
  frontendhttpport        => '1001'
  frontendhttpsport       => '1002'
}

from biemond-orawls.

Hi Edwin, I'm going to send a PR for this. As suggested above I've copied the files from the wls_cluster type into shared. I've modified the files in shared not to not include the easytype validators name. I think the wls_cluster implementation isn't idempotent. Because there isn't a way to remove the frontend host name and if you try to set it to have a blank value or '' I think the validator is then spotting this and reporting an error. What I've done I think allows for setting the initial frontendhost and with the ability to remove and also you can change. If it's not what you would like to see let me know and I can change to suit.

Thanks

Rob.

from biemond-orawls.

Closing this as my colleague Rob uploaded a PR which was merged a while ago.

Cheers,
Josh

from biemond-orawls.