DRAFT - Document creation in progress
UMS Design and Best Practices¶
In this document, we will cover some basic sizing, and configuration best practices for configuring an IGEL UMS cluster to manage IGEL devices accross multiple types of environments.
Sizing Guidelines¶
Universal Management Suite (UMS)¶
A note on sizing
The size guidelines below are just that. You may need to expand your UMS cluster if you have a complex environment, or are using multiple UMS Jobs.
It is not recomended to deploy more than 4 CPU's and 16 GB of RAM for any single server, and you should never have more than 6 UMS servers in a single cluster.
| Environment | Total IGEL Devices | UMS Server Count | CPU Cores | RAM | Storage* | Database Type | Minimum License Type |
|---|---|---|---|---|---|---|---|
| Lab | < 100 | 1 | 4 | 9 GB | 120 GB | Embedded | Essential |
| Essential | < 5,000 | 1 | 4 | 12 GB | 120 GB | Embedded | Essential |
| Small | < 25,000 | 1+ | 4 | 16 GB | 120 GB | External | Standard |
| Medium | < 50,000 | 2+ | 4 | 16 GB | 120 GB | External | Standard |
| Large | < 100,000 | 4+ | 4 | 16 GB | 120 GB | External | Enterprise |
| Enterprise | > 100,000 | 6 | 4 | 16 GB | 120 GB | External | Enterprise |
Storage Size
Storage may need to be expanded if you are using UMS servers as distribution servers for apps / large files.
IGEL Cloud Gateway (ICG)¶
The IGEL Cloud Gateway acts as a reverse-proxy for external IGEL devices to connect back to UMS. This connection is only used for management of the IGEL devices, and does not act as a VPN or allow external traffic back into your network.
It is recomended to have a minimum of two ICG servers for your UMS cluster for redundancy.
Recomended Specs¶
- CPU Cores: 2
- RAM: 4 GB
- Disk Space: 2 GB Free Space
Storage Size
You may need more storage space if you are delivering larger files, as ICG will cache the file locally to deliver it externally.