Center Client Requirements
...
Five load configuration architecture setups that exist for the Standard Edition are available in:
Appliance Mode (ISO file) - IBM_DataPower_OpDashboard_<version>.iso
Non-Appliance Mode (Compressed Executable file) : IBM_DataPower_OpDashboard_RH_<version>.cef
The following table lists the typical usage characteristics of each edition, and the physical or virtual resources it requires.
Availability in Edition | Load Configuration Architecture Setup | Goal | TPS Limits recommended(4) | Supports Virtual Env | Cores (1) | Memory (3) | Storage (GB) |
|---|---|---|---|---|---|---|---|
| Developer | Development | Developers only. In rare cases can be used for functional POCs. restricted license | 2-3 | Yes | 2 | 3 GB | All: 20GB |
Standard | Minimal | POCs and Evaluation. Limited history period to reduce memory requirements | 5 | Yes | 4 | 18 GB | OS: 40 |
| Standard | Low | Environment with low load levels | 40 | Yes | 6 | 32 GB | OS: 40 |
| Standard | Medium | Environment with Moderate load | 80 | Yes | 8 | 64GB | OS: 40 |
| Standard | High | Environment with High load | 120 | Yes, but not recommend | 12 | 128GB | OS: 40 |
| Standard | High_20dv | Environment with Medium load | 200 Can be increased to 1500 TPS(5) | No. required to be install on a physical server | 16 (Physical) | 200GB | OS: 40 |
| Standard | High_20dv | Environment with High load | 1500 TPS(5) | 20 (Physical)(5) | 256GB | OS: 40 |
Customer with more than 1500 TPS will be required to have multiple nodes.
For example: a customer wants to attach to DPOD pool of appliances that generates a peak a peak around 10,000 TPS.
This customer will need to have 7 physical servers , Intel based , with cpu hyperthreadedcpu hyperthreaded, each with 256 GB memory , 20 physical cores and storage specification as described below.
1 Node = 1500 TPS
7 Nodes = 10,500 TPS.
Customers that plan to use more than one node are expected to submit sizing questionnaire.
(1) These could be cores on an 80% utilized ESXi
...
(5) To reach 1500 TPS customer requires to have 256GB memory + 20 Physical cores (each is HyperThreaded thus brings to total of 40) + Local storage with RAID0 with 4-8 SSD Disks (SAS 6GBs) each support at least 80K Random Write IOPS 4KiB and write avg latency of less than 35 uSec.
Storage Recommendation
- DPOD serves DPOD serves as a database and should therefore be configured to use very fast disks. Therefore, DPOD installation requires 3 DISKS for OS , Install, Data.
- Usage of slow disks is not recommended and will impact the amount of time between creation of transaction logs and the availability of the data on DPOD's dashboards.
- For Physical hardware installation that can utilize HW RAID services we recommend the following:
- RAID5 - 40GB - for OS disk
- RAID5 - 40GB - for App disk
- RAID0 - Depends on volume - for Data disk.
| Warning | ||
|---|---|---|
| ||
DPODs does not support CentOS built in RAID (Software Raid) . The only RAID that we can support is the one handled by controller |
Network Requirements
Operating System Requirements - Only applicable to Non Appliance mode
- CentOS 7.2.0 - x86-64 bit or RHEL 7.2.0 - x86-64 bit only .
- Server OS must be a fresh install without any other installed products .
- In non Appliance mode the OS support is not covered but recommendation will be provided.
- The existence of other 3rd party SW products for backups, security and monitoring can be accepted but because of the diversity we can not know their impact.
- When an unwanted situation occurs with DPOD, Support will be provided if customer agreed to disable this 3rd party tools effects so we can know this is only the DPOD issue.
Utility Software for for Administrators
An SSH client to connect to DPOD appliance once installed.
An FTP Client software to upload/edit files in the appliance when required .
...