Appendix A. RHMAP Ansible Playbook Pre-Requisite Checks
When you run an RHMAP Ansible Playbook, it performs the following checks.
A.1. Prerequisite Checks
For every component, the installer attempts to check for a wildcard certificate, the correct PV requirement and also checks:
| Description | Parameter Name | Default Value | Fail/warning/recommended |
|---|---|---|---|
| Outbound Internet Connection | url_to_check | fail only in strict_mode |
A.2. Checks on RHMAP Core
| Description | Parameter Name | Default Value | Fail/warning/recommended |
|---|---|---|---|
| Min number of CPUs |
| 4 | fail only in strict_mode |
| Min system memory per node (in MB) |
| 7000 | fail only in strict_mode |
| Min total free memory of all nodes (in KB) |
| 4000000 | warning |
A.3. Checks on 1 Node MBaaS
| Description | Parameter name | Default value | Fail/warning/recommended |
|---|---|---|---|
| Min number of CPUs |
| 2 | fail only in strict_mode |
| Min system memory per node (in MB) |
| 7000 | fail only in strict_mode |
| Min total free memory of all nodes (in KB) |
| 4000000 | warning |
A.4. Checks on 3 Node MBaaS
| Description | Parameter name | Default value | Fail/warning/recommended |
|---|---|---|---|
| Min number of CPUs |
| 2 | fail only in strict_mode |
| Min system memory per node (in MB) |
| 7000 | fail only in strict_mode |
| Min total free memory of all nodes (in KB) |
| 4000000 | warning |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.