Tree
|
The resource distribution tree identifies consumers of the cluster resources, and organizes them into a manageable structure.
|
Plan (Resource plan)
|
The resource plan describes the relationship between the consumer tree and resource groups, and defines plans for how cluster resources are to be shared among consumers.
|
Consumers
|
A consumer in the tree represents any entity that can demand resources from the cluster. A consumer might be a business service, a business process that is a complex collection of business services, an individual user, or an entire line of business.
The consumers ManagementServices, SampleApplications, and ClusterServices, along with their sub-consumers, are installed by default.
ManagementServices has two sub-consumers, EGOManagementServices and SymphonyManagementServices, which run important system services on management hosts in the cluster. Services include derbydb, plc, purger, ServiceDirector, WEBGUI, RS, and WebServiceGateway. ManagementServices is configured to use the ManagementHosts resource group. Do not modify or delete this consumer.
SampleApplications has two sub-consumers, SOASamples and EclipseSamples.
The SampleApplications consumer and its sub-consumers can be modified or deleted (although you want to use the provided samples to begin using Symphony right away—this is a sample consumer with registered applications that are ready to run).
ClusterServices is configured to use the InternalResourceGroup resource group. It has two sub-consumers, EGOClusterServices and SymphonyClusterServices, which run important system services on every host in the cluster. Do not modify or delete ClusterServices, or use it to run workload units.
|
Multi-level tree
|
Company projects are generally structured with multiple layers and components. For example, a project belongs to a department, a department to a business unit and so on. A multi-level consumer tree allows you to configure consumers in a hierarchical fashion to match your business structure.
Note: As a best practice, restrict the number of tree levels to four.
|
Tree root
|
The root of the tree represents the entire cluster and all resources in it. Resources from the root are distributed through the tree to consumers.
|
Top-level consumers
|
The consumers attached directly to the root are called top-level consumers. The top-level consumer is the head of a consumer branch.
|
Leaf consumers
|
If a consumer has no descendants, it is called a leaf consumer. Services and applications can only be associated with leaf consumers.
Borrow and lend policies are set at this level.
Note: As a best practice, limit leaf consumers to fewer than 20.
|
Branches, descendants
|
If a consumer in the tree has other descendants, thereby creating a branch in a multi-level tree, it is called a branch consumer. Branch consumers exist to redistribute resources down the branch to their descendants.
Descendants of a branch consumer may also have descendants, thereby becoming branch consumers themselves. Every branch in the tree ends with a leaf consumer.
|
Parent
|
A consumer containing another consumer (a "child"). A parent can contain a child consumer, or be the child of another parent consumer.
|
Sibling
|
Two or more consumers sharing the same parent consumer.
|
Child, sub-consumer
|
A consumer nested within another consumer (a "parent"). A child (or sub-consumer) of one parent can be the parent to another nested child. A leaf consumer is always a child at the end of the branch.
|
Consumer administrator
|
For ease of management, you can create consumer administrators for top-level consumers in a multi-level tree. These users can change the plan for lower-level consumers on their branch (descendants), without requiring cluster administrator permissions. Only a cluster administrator can change the plan for top-level consumers.
|