There are 3 optional deployment sizings (with an additional sizing for PoC environments) that are recommended which are based on the Environment size and the number of running agents.
All-In-One
The following information is valid for environments that the JetPatch Application Server (JetPatch Manager) and the DB are located on the same machine
JetPatch Machine
| Environment Type | Number of Managed Servers | CPU Cores | RAM | Disk (OS Included*) |
| Micro | Up to 200 | 8 | 16GB | 250GB |
| Small | Up to 4K | 16 | 32GB | 400GB |
| Medium | Up to 8K | 32 | 64GB | 650GB |
*OS requires about 30GB
Separate Machines
The following information is valid for environments that the JetPatch Application Server (JetPatch Manager) and the DB are located on different machines
JetPatch Machine
| Environment Type | Number of Managed Servers | CPU Cores | RAM | Disk (OS Included*) |
| Small | Up to 4K | 8 | 16GB | 250GB |
| Medium | Up to 8K | 16 | 32GB | 250GB |
| Large | 8K and above | 20 | 64GB | 250GB |
*OS requires about 30GB
Database Machine
| Environment Type | Number of Managed Servers | CPU Cores | RAM | Disk (OS Included*) |
| Small | Up to 4K | 8 | 16 | 250GB |
| Medium | Up to 8K | 12 | 24 | 350GB |
| Large | 8K and above | 16 | 48 | 350GB |
*OS requires about 30GB
Repositories
WSUS Machine
| Environment Type | Number of Managed Servers | CPU Cores | RAM | Disk (OS Included**) |
| Micro | Up to 200 | 4 | 8GB | 300GB |
| Small | Up to 4K | 4 | 12GB | 400GB |
| Medium | Up to 8K | 8 | 16GB | 800GB |
| Large | 8K and above | 16 | 32GB | 1.5TB |
**Windows OS requires about 35GB
Local Repository Machine
For each managed Linux flavor in the environment
| Environment Type | Number of Managed Servers | CPU Cores | RAM | Disk (OS Included*) |
| Micro | Up to 200 | 4 | 8 | 150GB |
| Small | Up to 4K | 4 | 12 | 150GB |
| Medium | Up to 8K | 8 | 16 | 150GB |
| Large | 8K and above | 8 | 16 | 150GB |
- *OS requires about 30GB
- Note - mount point for local repo should be /var/www
JetProxy
| Environment Type | Number of Managed Servers | CPU Cores | RAM | Disk (OS Included*) |
| Small | Up to 4000 | 2 | 4 | 250GB |
JetPatch Manager Operating System
|
Platform |
Architecture |
Version |
|
CentOS |
64-bit |
6.X / 7.X |
|
Red Hat Enterprise Linux |
64-bit |
6.X / 7.X |
el7.X recommended
JetPatch Database
Supported PostgreSQL versions: 10.x and 11.xPublic Cloud PaaS: AWS RDS and Azure Database with version 10.x and 11.x
Client Servers Requirements:
- JetPatch Connector:
- For Linux and Windows OS: ~570 MB free space (70MB for software installation and 500MB logs)
- For Solaris: ~700 MB free space (200MB for software installation and 500MB logs
- Note: The Connector has minimal impact on resource consumption (on average less than 1% CPU and less than 30 MB RAM)
- Patches installation: More than 10% free space
- Agents installation: 1-2 GB free space (also depends on the amount of agents and their size)
How to tune your Database
We highly recommend tuning the database configuration based on the following article before starting using JetPatch.
- Open the link and fill in all parameters based on your machine settings you've configured in.
- DB Version : 9 / 10 / 11
- OS Type : Linux
- DB Type : Web Application
- Total Memory Size : Insert memory size based on the JetPatch Machine you chose.
- Number CPU : Insert memory size based on the JetPatch Machine you chose.
- Storage : HDD Storage
- Click on 'Generate'
- Modify the 'Postgres.conf' configuration file based onthe recommendations given in the PGTune link. The configuration file path is /var/lib/pgsql/data/postgresql.conf
- Restart DB
Please note:
- The settings above refer to a standalone DB machine. If you have chosen the "All-In-One" option. please fill in the following
- PoC : Memory 8, CPU 4
- Small : Memory 12, CPU 8
- Medium : Memory 24 , 16 CPU
- If the configuration is not located in the default location run the following to locate it:
sudo updatedblocate postgresql.conf
Comments
0 comments
Please sign in to leave a comment.