This explains the Orchestration mid server selection procedure.
Orchestration mid server selection happens based on multiple factors like application, IP ranges, capabilities, operational state, validated or not. Below are the steps to determine mid server selection for orchestration activities. At each stage, mid servers that won't satisfy the condition would be filtered out. At the end, a random mid server or a default mid server would be selected.
- Validated Mid Servers --> This process start with all the mid servers that are validated.
- Orchestration application --> This list would be further filter down based on "Orchestration" application or ALL application.
- IP Ranges --> Then IP ranges be checked to for this destination IP.
- Capability --> Based on the orchestration activity capability ( SSH, PowerShell, WMI, etc..), all the mid servers would be filtered further.
- At this stage, there may be multiple mid servers or none. If we have multiple, this list would be further filtered based on the below priority order.
- Up, Degraded, down. Each priority order be checked for all the mid servers. If any priority order finds a mid server, further priority oder check would be skipped.
- To this mid server list, default mid server would also be added to check the operation status. As soon as we find mid servers, a random mid server will be selected for further activities.
- If no mid server is identified, orchestration uses the default mid server.