This scenario takes you through the steps of getting your cluster prepared for registering four new services, modifying your service profile, and registering your service. You have already created a basic tree that follows your business structure and you have either modified the default resource group ComputeHosts or you have decided to leave that resource group as-is (with all your compute hosts).
Suppose we have two different lines of business under a consumer branch called Research: Data Flow and Storage.
Adding services requires creating consumers and changing the resource plan to ensure the new consumers have the necessary resources.
The checklists below provide guidance for the types of information that you need when actually creating a new service in the software.
There must be one consumer per service.
The consumer must be a leaf consumer—it cannot have any descendants.
Free CPU slots on management hosts
There must be one CPU slot free for each service on management hosts.
Free CPU slots on compute hosts
Are there enough CPU slots available on compute hosts to be allocated to the new services?
The compute host resource group must have enough CPU slots available. Otherwise, you may need to add more hosts or shift resources around existing consumers.
Workload unit submission user accounts
In order to submit workload units to the cluster, there must be user accounts defined in EGO that can connect and submit workload units. These accounts only exist in the EGO user database.
Each consumer must be associated with an operating system user account (workload execution user account). A consumer’s workload units run under this account.
The user account must exist on all the hosts in the cluster, including management hosts. On Windows, it is recommended that these user accounts be domain accounts. Also, the password must be the same on all hosts.
When you create a consumer, you are required to specify an OS user account—this is the OS account under which workload units run. Ensure this account exists on all hosts in the cluster.
If you specify a Windows user account, and the user has not already been configured, you have to run egosh ego execpasswd to register the user account password with EGO before the execution user can run an activity without exiting.
Create consumers and the consumer structure that you have planned out.
Note that the consumers that are to be attached to services must specify hosts from both a resource group that contains compute hosts (ComputeHosts by default) and the ManagementHosts resource group.
Use your plan summary to enter the required information for the consumer.