LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 187
Managing LSF on Platform EGO
EGO is only sensitive to the resource requirements of business services; EGO has no
knowledge of any run-time dynamic parameters that exist for them. This means
that EGO does not interfere with how a business service chooses to use the
resources it has been allocated.
How does Platform EGO work?
Platform products work in various ways to match business service (consumer)
demands for resources with an available supply of resources. While a specific
clustered application manager or consumer (for example, an LSF cluster) identifies
what its resource demands are, Platform EGO is responsible for supplying those
resources. Platform EGO determines the number of resources each consumer is
entitled to, takes into account a consumer’s priority and overall objectives, and then
allocates the number of required resources (for example, the number of slots,
virtual machines, or physical machines).
Once the consumer receives its allotted resources from Platform EGO, the
consumer applies its own rules and policies. How the consumer decides to balance
its workload across the fixed resources allotted to it is not the responsibility of EGO.
So how does Platform EGO know the demand? Administrators or developers use
various EGO interfaces (such as the SDK or CLI) to tell EGO what constitutes a
demand for more resources. When Platform LSF identifies that there is a demand,
it then distributes the required resources based on the resource plans given to it by
the administrator or developer.
For all of this to happen smoothly, various components are built into
Platform EGO. Each EGO component performs a specific job.
Platform EGO
components
Platform EGO comprises a collection of cluster orchestration software
components. The following figure shows overall architecture and how these
components fit within a larger system installation and interact with each other: