Using Sun Update Connection – Enterprise, create the profiles of your servers.
Define what is required and what is not allowed to be on each type of server. For this scenario, define a WebServerProfile profile and a TelnetServerProfile profile.
See To Create a Profile.
Create a profile that uninstalls the software of the other two profiles.
No damage is caused by setting Uninstall to components that are not there. So, make an uninstall profile called IdleServerProfile.
If there are various distributions used in the server pools and in the floating servers, align the profiles for all relevant distributions.
Create a policy that automates all actions (Yes to all actions on all Software) and call it YesToAll.
See To Create a Policy.
Create groups for each pool of servers, and a group called Idle.
For this scenario, call the server groups WebServers and TelnetServers.
See To Create a Group.
In the Idle group, assign a spare server that is your floating server and name it floating.
Write a script that takes the output of your local resource monitoring tool when the load threshold has been passed (either on overload or on idle) and runs a script similar to floatingServers.sh.