Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase memory and CPU so OPP products will install #472

Conversation

gparvin
Copy link
Member

@gparvin gparvin commented Apr 26, 2024

The attempt to install OPP failed because more CPU and Memory was needed. Increasing resources to match what AWS uses.

Running a test with this PR to see if it resolves the resource issue.

mprahl
mprahl previously approved these changes Apr 26, 2024
@openshift-ci openshift-ci bot added the lgtm label Apr 26, 2024
@openshift-ci openshift-ci bot removed the lgtm label Apr 30, 2024
@gparvin gparvin force-pushed the vmware-resources branch from e2b3539 to 93a2460 Compare May 1, 2024 12:36
@gparvin gparvin changed the title [WIP] Increase memory and CPU so OPP products will install Increase memory and CPU so OPP products will install May 1, 2024
@gparvin
Copy link
Member Author

gparvin commented May 1, 2024

I moved the values to the configmap for aws and vmware. This is ready for another look.
The configmap changes resulted in this bug on aws: https://issues.redhat.com/browse/OCPQE-21328 which this commit resolves.

@gparvin gparvin requested review from mprahl, dhaiducek and JustinKuli May 8, 2024 12:41
Copy link
Member

@dhaiducek dhaiducek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Some minor comments to consider.

@@ -1,10 +1,14 @@
# This manifest creates 3 OpenShift MachineSets that are intended for installing OpenShift Cluster Storage on AWS.
# This manifest creates storage nodes necessary for installing OPP on an AWS or VMWare OpenShift cluster.
# - AWS creates 2 replices in each of 3 zones.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# - AWS creates 2 replices in each of 3 zones.
# - AWS creates 2 replicas in each of 3 zones.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fixed!

Comment on lines 2 to 28
data:
vmwareReplicas: "6"
vmwareCPU: "8"
vmwareMemory: "32768"
awsReplicas: "2"
awsInstanceType: m6a.2xlarge
us-east-1-4.10: ami-0c72f473496a7b1c2
us-east-1-4.11: ami-0722eb0819717090f
us-east-1-4.12: ami-0fe05b1aa8dacfa90
us-east-1-4.13: ami-0624891c612b5eaa0
us-east-1-4.14: ami-0b56cb92505dea7ed
us-east-1-4.15: ami-0b56cb92505dea7ed
us-east-1-4.16: ami-057df4d0cb8cbae0d
us-east-2-4.10: ami-09e637fc5885c13cc
us-east-2-4.11: ami-026e5701f495c94a2
us-east-2-4.12: ami-0ff64f495c7e977cf
us-east-2-4.13: ami-0dc6c4d1bd5161f13
us-east-2-4.14: ami-0dc6c4d1bd5161f13
us-east-2-4.15: ami-0b577c67f5371f6d1
us-east-2-4.16: ami-0f736c64d5751d7d3
zone1: a
zone2: b
zone3: c
kind: ConfigMap
metadata:
name: opp-settings
namespace: policies
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Moved the metadata to the top. I find the alphabetical field ordering unconventional.

Suggested change
data:
vmwareReplicas: "6"
vmwareCPU: "8"
vmwareMemory: "32768"
awsReplicas: "2"
awsInstanceType: m6a.2xlarge
us-east-1-4.10: ami-0c72f473496a7b1c2
us-east-1-4.11: ami-0722eb0819717090f
us-east-1-4.12: ami-0fe05b1aa8dacfa90
us-east-1-4.13: ami-0624891c612b5eaa0
us-east-1-4.14: ami-0b56cb92505dea7ed
us-east-1-4.15: ami-0b56cb92505dea7ed
us-east-1-4.16: ami-057df4d0cb8cbae0d
us-east-2-4.10: ami-09e637fc5885c13cc
us-east-2-4.11: ami-026e5701f495c94a2
us-east-2-4.12: ami-0ff64f495c7e977cf
us-east-2-4.13: ami-0dc6c4d1bd5161f13
us-east-2-4.14: ami-0dc6c4d1bd5161f13
us-east-2-4.15: ami-0b577c67f5371f6d1
us-east-2-4.16: ami-0f736c64d5751d7d3
zone1: a
zone2: b
zone3: c
kind: ConfigMap
metadata:
name: opp-settings
namespace: policies
kind: ConfigMap
metadata:
name: opp-settings
namespace: policies
data:
vmwareReplicas: "6"
vmwareCPU: "8"
vmwareMemory: "32768"
awsReplicas: "2"
awsInstanceType: m6a.2xlarge
us-east-1-4.10: ami-0c72f473496a7b1c2
us-east-1-4.11: ami-0722eb0819717090f
us-east-1-4.12: ami-0fe05b1aa8dacfa90
us-east-1-4.13: ami-0624891c612b5eaa0
us-east-1-4.14: ami-0b56cb92505dea7ed
us-east-1-4.15: ami-0b56cb92505dea7ed
us-east-1-4.16: ami-057df4d0cb8cbae0d
us-east-2-4.10: ami-09e637fc5885c13cc
us-east-2-4.11: ami-026e5701f495c94a2
us-east-2-4.12: ami-0ff64f495c7e977cf
us-east-2-4.13: ami-0dc6c4d1bd5161f13
us-east-2-4.14: ami-0dc6c4d1bd5161f13
us-east-2-4.15: ami-0b577c67f5371f6d1
us-east-2-4.16: ami-0f736c64d5751d7d3
zone1: a
zone2: b
zone3: c

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, i fixed that too. Thanks!

The attempt to install OPP failed because more CPU and Memory was needed.
Increasing vmware resources to match what AWS uses. The adjustments to
the configmap usage had to be re-organized too, since the configmap needs
to exist ahead of time to resolve the template values.

Referenced bug:
- https://issues.redhat.com/browse/OCPQE-21328

Signed-off-by: Gus Parvin <[email protected]>
@gparvin gparvin force-pushed the vmware-resources branch from 93a2460 to 82ecffc Compare May 9, 2024 14:55
@gparvin gparvin requested a review from dhaiducek May 9, 2024 14:56
Copy link
Member

@dhaiducek dhaiducek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! You can also leverage the new object-templates-raw feature in the generator in the future so that you don't have to specify the ConfigurationPolicy stuff around it. 😉

Copy link

openshift-ci bot commented May 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhaiducek, gparvin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit f59e3b5 into open-cluster-management-io:main May 9, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants