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.

Sign up for GitHub

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

[OCP] Create new ppc64le flavor with larger disk #5061

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[OCP] Create new ppc64le flavor with larger disk #5061

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion components/multi-platform-controller/production-downstream/kflux-ocp-p01/host-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ data:
linux/s390x,\
linux-large/s390x,\
linux/ppc64le,\
linux-d160/ppc64le,\
linux-large/ppc64le\
"
instance-tag: rhtap-prod
Expand All @@ -65,7 +66,7 @@ data:
dynamic.linux-arm64.subnet-id: subnet-0864e71d16676bf7f
dynamic.linux-arm64.allocation-timeout: "1200"

# same as default but with 160GB disk instead of default 40GB
# same as default but with 160GB disk instead of default 40GB
dynamic.linux-d160-arm64.type: aws
dynamic.linux-d160-arm64.region: us-east-1
dynamic.linux-d160-arm64.ami: ami-03d6a5256a46c9feb
Expand Down Expand Up @@ -444,6 +445,22 @@ data:
dynamic.linux-ppc64le.max-instances: "50"
dynamic.linux-ppc64le.allocation-timeout: "1800"

# same as default but with 160GB disk instead of default 40GB
dynamic.linux-d160-ppc64le.type: ibmp
dynamic.linux-d160-ppc64le.ssh-secret: "internal-prod-ibm-ssh-key"
dynamic.linux-d160-ppc64le.secret: "internal-prod-ibm-api-key"
dynamic.linux-d160-ppc64le.key: "prod-konflux-infra"
dynamic.linux-d160-ppc64le.image: "ppc64le-rhel-94-base-27nov2024"
dynamic.linux-d160-ppc64le.crn: "crn:v1:bluemix:public:power-iaas:dal12:a/eebc7153d0c844f9915fb6f3b9850a3b:d6faf373-c0b6-4ba9-b0bc-4f7e0a74f9d5::"
dynamic.linux-d160-ppc64le.url: "https://us-south.power-iaas.cloud.ibm.com"
dynamic.linux-d160-ppc64le.network: "4d164943-b043-4c6e-bba5-d233abf66c6a"
dynamic.linux-d160-ppc64le.system: "e980"
dynamic.linux-d160-ppc64le.cores: "2"
dynamic.linux-d160-ppc64le.memory: "8"
dynamic.linux-d160-ppc64le.max-instances: "50"
dynamic.linux-d160-ppc64le.allocation-timeout: "1800"
dynamic.linux-d160-ppc64le.disk: "160"
Copy link
Contributor

Choose a reason for hiding this comment

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

I think the IBM arch do not support this parameter, I am looking to be sure and I will report back


#PPC64LE Large dynamic nodes
dynamic.linux-large-ppc64le.type: ibmp
dynamic.linux-large-ppc64le.ssh-secret: "internal-prod-ibm-ssh-key"
Expand Down
Loading