Closed ron1 closed 3 years ago
openshift-bot
commented
4 years ago Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
openshift-bot
commented
3 years ago Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
openshift-bot
commented
3 years ago Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
openshift-ci-robot
commented
3 years ago @openshift-bot: Closing this issue.
Is this a BUG REPORT or a FEATURE REQUEST ? (choose one): FEATURE REQUEST
FEATURE REQUEST INFO
The vmware-ansible create-vm-prod-ose role main task currently hard codes disk and memory sizes for masters, infras, and apps vms. These hard-coded values should be considered minimum values and may be smaller than required by some deployments. This role would be more reusable if the following were defined as variables:
master_memory_mb: 16384 infra_memory_mb: 8192 app_memory_mb: 8192 master_disks_size_gb: [60, 40, 40, 40] infra_disks_size_gb: [60, 40, 40, 300] app_disks_size_gb: [60, 40, 40, 300]