Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Server groups enforce placement policies that determine how a set of instances is distributed across physical compute hosts. Use server groups to guarantee high availability through host separation, improve performance through co-location, or meet compliance requirements for workload isolation.
Prerequisites
  • An active Xloud project
  • At least two compute hosts available (required for anti-affinity enforcement)
  • Sufficient server group quota

​
Placement Policies

PolicyBehaviorFailure Mode
affinityAll instances placed on the same physical hostLaunch fails if the target host cannot accommodate the instance
anti-affinityEach instance placed on a different physical hostLaunch fails if insufficient distinct hosts are available
soft-affinityPrefer the same host; allow different hosts if requiredLaunch succeeds even when co-location is not possible
soft-anti-affinityPrefer different hosts; allow same host if no alternative existsLaunch succeeds even when distinct hosts are unavailable
Use anti-affinity for production replicated services (web tiers, application clusters, database replicas) where a single host failure must not take down all instances simultaneously. Use soft-anti-affinity when you want best-effort separation without hard placement failures.

​
Create a Server Group

1

Navigate to Server Groups

Navigate to Compute > Server Groups in the sidebar. Click Create Server Group.
2

Configure the server group

FieldTypeRequiredDescription
NameText inputYesHuman-readable name for the group
PolicyDropdownYesPlacement policy — see the table above
The dropdown options are:
  • affinity — instances on same physical machine (mandatory)
  • anti-affinity — instances on different machines (mandatory)
  • soft-affinity — same machine preferred (best effort)
  • soft-anti-affinity — different machines preferred (best effort)
The dialog also displays your current Server Groups quota usage (used / limit). If your quota is exhausted, the submit button is disabled.
3

Create the group

Click Confirm. The server group appears in the list.
Server group appears in the list with the selected policy.

​
View Server Groups

Navigate to Compute > Server Groups. The list shows:
ColumnDescription
ID/NameGroup identifier (clickable to view details)
Member CountNumber of instances in the group
PolicyPlacement policy
Filter by Name or Policy using the search/filter bar.Click a group name to view the detail page, which shows the Members tab listing all instances assigned to this server group.

​
Launch Instances in a Server Group

When creating an instance, expand the Advanced Options section in Step 3 (System Config) of the wizard. Select your server group from the Server Group table.Alternatively, from the server group detail page, click the Create Instance action in the More dropdown. The server group is pre-selected in the wizard.

​
Delete a Server Group

Navigate to Compute > Server Groups. Click the Delete action (the first row action) on the group row. Confirm the deletion in the dialog.
Deleting a server group removes the placement constraint. Existing instances are not affected, but new launches will no longer enforce the policy.

​
Next Steps

Launch an Instance

Create instances with server group placement in the 4-step wizard

Availability Zones

Understand fault domains and zone-level placement

Live Migration

Move instances between hosts while respecting group policies

Troubleshooting

Resolve placement failures and group member limit issues