Service instances
When a service is running on a host, service instances are created. Once the service is stopped, service instances no longer exist.
A service instance runs only one activity. You cannot control the activity directly, only the service instance that contains it. For example, you can migrate a service instance (and therefore the activity it contains), but you cannot migrate the activity directly. Multiple service instances can run under a single service, enabling multiple activities to run simultaneously.
By default, EGO services (including Conductor services) have a configured number of service instances to run on each slot; for example, one instance per slot.
Service instances require a host to run an activity and run using the resource group (for
example, the
ManagementHosts group or ComputeHosts group) that is
defined in the service definition files. Find the definition files at
$EGO_CONFDIR/../../eservice/esc/conf/services.Note: If you ran
egoconfig mghost, $EGO_CONFDIR is the shared directory containing the
configuration files.