Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
faq:prerequisites_and_system_requirements [2019/08/14 14:59] poulm typos |
faq:prerequisites_and_system_requirements [2022/04/07 09:10] stekld [Table] |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{tag>HW requirements SW}} | ||
====== Prerequisites and system requirements ====== | ====== Prerequisites and system requirements ====== | ||
+ | |||
+ | ===== Using BCV Appliance - standard way ===== | ||
+ | Typical requirement up to 7.000 users: | ||
+ | ^ Category----- | ||
+ | | Processor | ||
+ | | Memory | ||
+ | | Disk | A minimum of 250 GiB or more; The required disk space depends on the connected systems and the volume of managed data. | | ||
+ | |||
+ | |||
+ | ===== Installing IdM on prepared OS - deprecated way before BCV Appliance ===== | ||
The following requirements are valid if you are installing all components CzechIdM and databaserver on a single server. | The following requirements are valid if you are installing all components CzechIdM and databaserver on a single server. | ||
- | === Production | + | ==== Typical |
- | It depends on how many identities and role to handle on how many end systems. CzechIdM works with a system of asynchronous events that handle processors in the background. These events can efficiently be processed by CPU cores since the system is pretty parallel in its run. | + | It depends on how many identities and role to handle on how many end systems. CzechIdM works with a system of asynchronous events that handle processors in the background. These events can efficiently be processed by CPU cores since the system is pretty parallel in its run. **This configuration is mandatory on projects delivered by BCV (both testing and production use)** |
Typical requirement up to 7.000 users: | Typical requirement up to 7.000 users: | ||
Line 13: | Line 24: | ||
| Memory | | Memory | ||
| Disk | A minimum of 250 GiB or more; The required disk space depends on the connected systems and the volume of managed data. | | | Disk | A minimum of 250 GiB or more; The required disk space depends on the connected systems and the volume of managed data. | | ||
- | | OS | CentOS/ | + | | OS | CentOS/ |
| Virtualization | | Virtualization | ||
| | | | ||
- | === Minimal configuration === | + | ==== HDD partitioning for typical configuration ==== |
+ | <note important> | ||
+ | Required disk partitioning on Linux servers: | ||
+ | ^ Partition | ||
+ | | "/ | ||
+ | | "/" | ||
+ | | | ||
+ | |||
+ | ==== Minimal configuration | ||
- | This configuration is intended only for limited testing purposes. | + | This configuration is intended only for limited testing purposes |
^ Category | ^ Category | ||
Line 25: | Line 44: | ||
| Memory | | Memory | ||
| Disk | A minimum of 150 GiB or more; The required disk space depends on the connected systems and the volume of managed data. | | | Disk | A minimum of 150 GiB or more; The required disk space depends on the connected systems and the volume of managed data. | | ||
- | | OS | CentOS/ | + | | OS | CentOS/ |
| Virtualization | | Virtualization | ||
- | === HDD partitioning === | + | ==== Alternative |
- | Required disk partitioning on Linux servers: | + | |
- | ^ Partition | + | If you would like have to have more divided |
- | | "/ | + | ^ Partition |
- | | "/" | + | | "/ |
- | | | + | | "/" |
- | If you would like have to have more splitted | + | | "/ |
- | ^ Partition | + | | "/ |
- | | "/ | + | | "/ |
- | | "/" | + | | | 50+ GB of free space on LVM to distribute where it is needed* |
- | | "/ | + | | | | |
- | | "/ | + | *Warning: size of "/opt", "/data" and "/ |
- | | | + | |
- | *Warning: size of "/ | + | |