Articles in this section

See more

Hardware and Software Specifications

Todd Kirkland
  • Updated
Follow

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 should be Windows 2016 for POCs.

**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
  • For Ubuntu (regardless to the environment type) the Disk should be 300GB

Unified Local Repositories Solution

 Base image should include 2 vCPU, 4 GB RAM, 50 GB disk, for each Repository loaded

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
  • Note -  Mount point for local repo should be /var/www
  • For Ubuntu (regardless to the environment type) the Disk should be 300GB

JetProxy

Environment Type Number of Managed Servers CPU Cores RAM Disk (OS Included*)
Small Up to 4000 2 4 250GB

 

JetPatch Manager Operating System

The JetPatch Manager can run on the following platforms: 

Platform

Architecture

Version

CentOS

64-bit

 6.X / 7.X / 8.X*

Red Hat Enterprise Linux

64-bit

6.X / 7.X / 8.X*

el7.X recommended

*el8.X supported from 4.1.2 UR2 and onwards

JetPatch Database

Supported PostgreSQL versions: 10.x and 11.x
Public Cloud PaaS: AWS RDS and Azure Database with version  10.x and 11.x
Operating System: el6.X / el7.X (el7.X recommended) 
 

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.

  1. 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
  2. Click on 'Generate'
  3. 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 Screen_Shot_2020-11-17_at_9.25.13_PM.png
  4. Restart DB

Please note: 

  1. The settings above refer to a standalone DB machine. If you have chosen the "All-In-One" option. please fill in the following
    1. PoC : Memory 8, CPU 4
    2. Small : Memory 12, CPU 8
    3. Medium : Memory 24 , 16 CPU
  2. If the configuration is not located in the default location run the following to locate it: 
sudo updatedb
locate postgresql.conf
 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.