Versions Compared

Old Version 133

changes.mady.by.user Shachar Greenberg

Saved on

compared with

New Version Current

changes.mady.by.user Amit Munwes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Supported Hypervisors

DPOD can be installed on either a virtual environment (hypervisors) or physical servers (Intel(C) based CPUs), depending on the required performance.For a production environment suitable for hypervisor (virtual environment), the virtual appliance is supported on the following VMware hypervisorsinfrastructure (hypervisor). The following hypervisors are supported for running a DPOD production installation:

  • VMWare ESX - v6.0, v6.5, v6.7, v7.0

  • VMWare Workstation/Player - v14, v15, v16

  • VMware Fusion - v11.0, v11.5, v12.0, v12.1x

  • PureApp (only on Intel Processors) - no pattern yet available, can be provided only as an imported OVA.

Hyper-V

DPOD is NOT currently tested on Hyper-V, and there are currently no plans to add such testing in the future. Therefore it cannot be guaranteed that the installation of DPOD on Hyper-V works, nor can the performance of such an installation be guaranteed.

...

If a customer decides to install DPOD on Hyper-V:

  1. The support will be limited to application bugs and issues that affect other hypervisors as well (issues that are not specific to Hyper-V).

  2. The customer might be asked to install DPOD on a supported infrastructure (such as VMware or physical servers) to prove that the issue is not specific to Hyper-V, in order to get support.

Note: DPOD can also be installed on physical servers (it might even be required for high loads), which can provide an alternative for customers that only own Hyper-V for virtualization. More information is available below.

Supported Physical Hardware

DPOD can be installed on physical servers (with Intel(C) based CPUs), especially when the load is high and the performance requires so. See the resources requirements listed below for more information.

Physical hardware should be purchased according to specifications provided by support L3 team in a short sizing process.

Resources Requirements

DPOD offers 6 basic load configuration setups deployment profiles:

  • One load configuration architecture for A development deployment profile (exists only in the Developer Edition ISO file).
    The Developer Edition ISO file name is DPOD-Developer-CentOS-<version>.iso, and can be downloaded from Fix Central.

  • Five load configuration architectures for the Standard EditionFive Standard Edition deployment profiles, available as: 

    • Appliance Mode (ISO file) - DPOD_CentOS_<version>.iso - can be downloaded from PPA.

    • Non-Appliance Mode (Compressed Executable file) - DPOD_RedHat_<version>.cef - can be downloaded from PPA.

  • It is not possible to change the load configuration architecture deployment profile after DPOD is installed. In order to change from one architecture deployment profile to another, a new installation of DPOD is required, discarding the old data collected so far.

Please consider the following rules of thumb for sizing:

  • Customers that expect a load of up to 120 TPS (across all devices, including future growth) may choose one of the options from the table below.

  • Customers that expect a load of over 120 TPS (across all devices, including future growth) are required to complete a sizing process by opening a support ticket with IBM Support.

  • Currently a single installation of DPOD cell environment with 7 physical cell members can process up to ~20,000 TPS (assuming ~35 Syslog records per transaction on average). Customers with higher load than that may create several installations, each can handle up to ~20,000 TPS.

Available in Edition

Load Configuration ArchitectureDeployment Profile

Goal

TPS Limit(74)

Supports Virtual Environment

Cores

RAM

Storage

Developer

Development

Developers only. In rare cases can be used for functional POCs. Under restricted license.

2-3 TPS

Can be virtual (5)

2 cores (1)

4 GB (3)

Single disk: 30GB

Standard

Minimal

POCs and evaluation.
Limited history period to reduce memory requirements.

5 TPS

Can be virtual (5)

4 cores (1)

18 GB (3)OS: 40

GB
Install: 40 GB
Data(2): 100-300 Single disk: 200-400 GB

Standard

Low

Environment with low load levels

40 TPS

Can be virtual (5)

6 cores (1)

32 GB (3)

OS: 40 GB
Install: 40 GB
Data(2): 100-1000 GB

Standard

Medium

Environment with moderate load

80 TPS

Can be virtual (5)

8 cores (1)

64 GB (3)

OS: 40 GB
Install: 40 GB
Data(2): 300-2,000 GB

Standard

High

Environment with moderate load

120 TPS

Can be virtual, but not recommended (5)

16 cores (1)

128-256 GB (3)

OS: 40 GB
Install: 40 GB
Data(2): 1-8 TB

Standard

High_20dv

Environment with medium to very high load

200-1500 TPS (6)

Must be installed on a physical server

Needs sizing (6)

Needs sizing (6)

Needs sizing (6)

Standard

High_20dv

Environment with very high load

2750 TPS (6)

Must be installed on a physical server

Needs sizing (6)

Needs sizing (6)

Needs sizing (6)

Standard

Federated Architecture

Environment with very high load that requires several DPOD servers

>2750 TPS - TBD TPS (6)

Must be installed on physical servers

Needs sizing (6)

Needs sizing (6)

Needs sizing (6)

...

(4) The TPS is the maximum total transaction transactions load across all devices/domains connected to DPOD.

(5) Virtual deployments performance cannot be guaranteed. Virtual deployments performance depends on the server hosting the VM (ESX), its configuration, the overall load it is experiencing at any given time from any of its VMs, and especially the performance of the remote storage.

(6) Customers will be provided with specifications after a sizing process with L3.

(7) If If the TPS is too high and DPOD is unable to process all the incoming messages, some will be dropped, causing DPOD to show unreliable data (some transactions might not appear, some errors might not be displayed, some data such as latency might be missing from some of the transactions, etc.). When messages are dropped, an internal alert is generated and displayed in DPOD Web Console (under DPOD Health → Internal Alerts).

(5) Virtual deployments performance cannot be guaranteed. Virtual deployments performance depends on the server hosting the VM (ESX), its configuration, the overall load it is experiencing at any given time from any of its VMs, and especially the performance of the remote storage.

(6) Customers will be provided with specifications after a short sizing process with support L3 team.

Storage Requirements

  • DPOD is I/O intensive, as it needs to persist all logs and information at very high rates. Therefore, for most of the installations, it needs to be configured with very fast disks, and with at least 3 separate disks (OS, app/logs, data).

  • Some configurations, such as the Cell environment, require additional data disks.

  • Usage of slow disks will impact the maximum TPS that DPOD can process, the performance of queries and the amount of time between the creation of transaction logs and the availability of the data on DPOD's dashboards.

  • For each 1 TB of data 64 GB of RAM is recommended for responsive queries (dashboards and filters).

  • NFS is not supported for the data disk, as the Store relies on file system behavior that NFS does not supply. Data corruption and other problems can occur.

  • Software RAID (such as CentOS built-in RAID) is not supported.

  • The data disk retention is automatically managed by DPOD. For each type of data (transactional, resources, payload, etc.), once its quota is full, old data will be discarded to make room for new data of the same type. A bigger disk size will hold a longer history.

...

  • CentOS 7.7-7.9 - x86-64 bit only on supported HW or Hypervisor as stated above.

  • RHEL 7.7-7.9, 8.3-8.5 - x86-64 bit only on supported HW or Hypervisor as stated above.

  • Server The OS must be a fresh install, without any other installed products.

  • In Non-Appliance mode the The OS support is not covered, but recommendations will be provided.

  • Third-party software such as antivirus, cybersecurity, monitoring, APM, endpoint protection, backup, etc. might significantly decrease the performance of DPOD and impact its functionality. During the resolution of issues, DPOD support will ask the customer to disable any 3rd party software in order to isolate the issues and verify their source. Support cannot be provided if the 3rd party tools are not disabled.

...