Does LSF 9 on EGO support a grace period when reclamation is configured in the resource plan?
No. Resources are immediately reclaimed even if you set a resource reclaim grace period.
Does LSF 9 on EGO support upgrade of the master host only?
Yes
Under EGO Service Controller daemon management mode on Windows, does PEM start sbatchd and res directly or does it ask Windows to start sbatchd and res as Windows Services?
On Windows, LSF still installs sbatchd and res as Windows services. If EGO Service Controller daemon control is selected during installation, the Windows service will be set up as Manual. PEM will start up the sbatchd and res directly, not as Windows Services.
What's the benefit of LSF daemon management through the EGO Service Controller?
EGO Service Controller provides High Availability services to sbatchd and res, and faster cluster startup than startup with lsadmin and badmin.
How does the hostsetup script work in LSF 9?
LSF 9 hostsetup script functions essentially the same as previous versions. It sets up a host to use the LSF cluster and configures LSF daemons to start automatically. In LSF 9, running hostsetup --top=/path --boot="y" will check the EGO service defination files sbatchd.xml and res.xml. If res and sbatchd startup is set to "Automatic", the host rc setting will only start lim. If set to "Manual", the host rc setting will start lim, sbatchd, and res as in previous versions.
Is non-shared mixed cluster installation supported, for example, adding UNIX hosts to a Windows cluster, or adding Windows hosts to a UNIX cluster?
In LSF 9, non-shared installation is supported. For example, to add a UNIX host to a Windows cluster, set up the Windows cluster first, then run lsfinstall -s -f slave.config. In slave.config, put the Windows hosts in LSF_MASTER_LIST. After startup, the UNIX host will become an LSF host. Adding a Windows host is even simpler. Run the Windows installer, enter the current UNIX master host name. After installation, all daemons will automatically start and the host will join the cluster.
As EGO and LSF share base configuration files, how are other resources handled in EGO in addition to hosts and slots?
Same as previous releases. LSF 9 mbatchd still communicates with LIM to get available resources. By default, LSF can schedule jobs to make use of all resources started in cluster. If EGO-enabled SLA scheduling is configured, LSF only schedules jobs to use resources on hosts allocated by EGO.
How about compatibility for external scripts and resources like elim, melim, esub and others?
LSF 9 supports full compatibility for these external executables. elim.xxx is started under LSF_SERVERDIR as usual. By default, LIM is located under LSF_SERVERDIR.
Can Platform LSF MultiCluster share one EGO base?
No, each LSF cluster must run on top of one EGO cluster.
Can EGO consumer policies replace MultiCluster lease mode?
Conceptually, both define resource borrowing and lending policies. However, current EGO consumer policies can only work with slot resources within one EGO cluster. MultiCluster lease mode supports other load indices and external resources between multiple clusters. If you are using MultiCluster lease mode to share only slot resources between clusters, and you are able to merge those clusters into a single cluster, you should be able to use EGO consumer policy and submit jobs to EGO-enabled SLA scheduling to achieve the same goal.