Skip to content

Add IBM Power VS: types#5609

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
clnperez:new-upstream-types
Feb 28, 2022
Merged

Add IBM Power VS: types#5609
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
clnperez:new-upstream-types

Conversation

@clnperez
Copy link
Copy Markdown
Contributor

@clnperez clnperez commented Feb 4, 2022

For more background on IPI on Power VS, refer to the enhancement
proposal here: openshift/enhancements#736

Older discussions on some of the code here can be found in
#5224.
An older unreviewed version of this PR can be found here:
#5292

Signed-off-by: Christy Norman christy@linux.vnet.ibm.com

@openshift-ci openshift-ci Bot requested review from jhixson74 and kirankt February 4, 2022 22:53
@openshift-ci openshift-ci Bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 4, 2022
@clnperez
Copy link
Copy Markdown
Contributor Author

clnperez commented Feb 4, 2022

@rna-afk can you advise on how we should add the right reviewers and owners to some of these files? Back in October the answer was to add what the checks are complaining about, so sounds like we need to be educated on the new best practices there.

@clnperez clnperez changed the title Add IBM Power VS: types only Add IBM Power VS: types Feb 4, 2022
Comment thread pkg/types/powervs/machinepools.go Outdated
Comment thread pkg/types/powervs/platform.go Outdated
Comment thread pkg/types/powervs/platform.go Outdated
Comment thread pkg/types/powervs/platform.go Outdated
Comment thread pkg/types/powervs/platform.go Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The text here implies to me that you can have a successful install without specifying the VPC, in which case your cluster will not use VPC Load Balancers. Is that accurate? Or is the optional aspect of this like it is for other platforms where omitting the VPC tells the installer to create a VPC for you?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

ah -- i blanked on explaining that a few things here are temporary. we've had to pause on including the vpc creation, so for now there are manual steps for dev that we need to take to create a vpc and the networks in both ibmcloud and power vs. after that, vpc will be created by the installer. it's not going to be optional when we've got networking a fix into prod.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Let's still clean up the text in the description to represent the current behavior.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

i did clean some things up a couple of weeks ago, but, sounds like youre asking for something additional. can you elaborate on where you want current behavior documented?

Comment thread pkg/types/powervs/validation/machinepool.go Outdated
Comment thread pkg/types/powervs/validation/machinepool.go Outdated
Comment thread pkg/types/powervs/machinepools.go Outdated
Comment thread pkg/types/powervs/validation/platform.go Outdated
Comment thread pkg/types/powervs/platform.go Outdated
@staebler
Copy link
Copy Markdown
Contributor

staebler commented Feb 5, 2022

@rna-afk can you advise on how we should add the right reviewers and owners to some of these files? Back in October the answer was to add what the checks are complaining about, so sounds like we need to be educated on the new best practices there.

Add the following to all your installer PRs. Aditya will be the point for doing reviews.
/cc @rna-afk

@openshift-ci openshift-ci Bot requested a review from rna-afk February 5, 2022 01:31
@rna-afk
Copy link
Copy Markdown
Contributor

rna-afk commented Feb 7, 2022

For the owners file, this looks right but you should add the alias (multiarch-reviewers/approvers) in this file. Also you need to add the former in almost every powervs folder you create in the installer. I can guide you on which folders.

@openshift-ci openshift-ci Bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 9, 2022
@kirankt
Copy link
Copy Markdown
Contributor

kirankt commented Feb 9, 2022

For the owners file, this looks right but you should add the alias (multiarch-reviewers/approvers) in this file. Also you need to add the former in almost every powervs folder you create in the installer. I can guide you on which folders.

Question. Why multiarch-{reviewers,approvers} as opposed to powervs-{reviewers,approvers}? Looks like the file follows platform-{reviewers,approvers} format.

@rna-afk
Copy link
Copy Markdown
Contributor

rna-afk commented Feb 9, 2022

Question. Why multiarch-{reviewers,approvers} as opposed to powervs-{reviewers,approvers}? Looks like the file follows platform-{reviewers,approvers} format.

Not sure if there's a preference on the naming and well now I think powervs would be better. Thanks!

@clnperez
Copy link
Copy Markdown
Contributor Author

clnperez commented Feb 9, 2022

multiarch-reviewers comes from the name of the team I work closely with inside Red Hat. @Prashanth684 is the dev I work the most with. Thoughts, Prashanth?

@clnperez
Copy link
Copy Markdown
Contributor Author

clnperez commented Feb 9, 2022

I think I've addressed all @staebler's comments and fixed the two checks that were failing. The only outstanding questions may be around some of our temporary dev networking requirements that we should be able to remove in a week or so. Hopefully everyone is okay with a followup PR for those.

Comment thread data/data/install.openshift.io_installconfigs.yaml Outdated
@Prashanth684
Copy link
Copy Markdown
Contributor

multiarch-reviewers comes from the name of the team I work closely with inside Red Hat. @Prashanth684 is the dev I work the most with. Thoughts, Prashanth?

i would add myself, @r4f4 and @AnnaZivkovic as they work on the installer side of things.and maybe some folks from IBM as well who worked on this

Copy link
Copy Markdown
Contributor

@rna-afk rna-afk left a comment

Choose a reason for hiding this comment

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

Looks good. Just a few nits/questions

Comment thread pkg/types/powervs/validation/platform.go Outdated
Comment thread pkg/types/powervs/validation/machinepool.go Outdated
Comment thread pkg/types/powervs/validation/machinepool.go Outdated
Comment thread pkg/types/powervs/validation/machinepool.go Outdated
Comment thread pkg/types/powervs/validation/machinepool.go Outdated
@clnperez
Copy link
Copy Markdown
Contributor Author

clnperez commented Feb 9, 2022

after a quick chat with @Prashanth684 we decided to switch to powervs-[reviewers|approvers] vs multiarch, and not add the other two IDs he listed.

hopefully good to go now. i've looked through failing tests on each run (with a special focus on the ibmcloud ones, since we share some things -- though nothing in this PR so just being extra careful) and nothing looks related.

Comment thread pkg/types/powervs/validation/machinepool_test.go Outdated
@clnperez
Copy link
Copy Markdown
Contributor Author

clnperez commented Feb 9, 2022

/retest ci/prow/unit
/retest ci/prow/okd-unit

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 9, 2022

@clnperez: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws
  • /test e2e-aws-upgrade
  • /test e2e-gcp-upgrade
  • /test e2e-metal-ipi-ovn-ipv6-required
  • /test gofmt
  • /test golint
  • /test govet
  • /test images
  • /test okd-images
  • /test okd-unit
  • /test okd-verify-codegen
  • /test openstack-manifests
  • /test shellcheck
  • /test tf-lint
  • /test unit
  • /test verify-codegen
  • /test verify-vendor
  • /test yaml-lint

The following commands are available to trigger optional jobs:

  • /test e2e-alibaba
  • /test e2e-aws-disruptive
  • /test e2e-aws-fips
  • /test e2e-aws-proxy
  • /test e2e-aws-rhel8
  • /test e2e-aws-shared-vpc
  • /test e2e-aws-single-node
  • /test e2e-aws-upi
  • /test e2e-aws-upi-proxy
  • /test e2e-aws-workers-rhel8
  • /test e2e-azure
  • /test e2e-azure-resourcegroup
  • /test e2e-azure-shared-vpc
  • /test e2e-azure-upi
  • /test e2e-azurestack
  • /test e2e-azurestack-upi
  • /test e2e-crc
  • /test e2e-gcp
  • /test e2e-gcp-shared-vpc
  • /test e2e-gcp-upi
  • /test e2e-gcp-upi-xpn
  • /test e2e-ibmcloud
  • /test e2e-libvirt
  • /test e2e-metal
  • /test e2e-metal-assisted
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-metal-ipi-swapped-hosts
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-metal-single-node-live-iso
  • /test e2e-openstack
  • /test e2e-openstack-kuryr
  • /test e2e-openstack-parallel
  • /test e2e-openstack-proxy
  • /test e2e-openstack-upi
  • /test e2e-ovirt
  • /test e2e-vsphere
  • /test e2e-vsphere-upi
  • /test okd-e2e-aws
  • /test okd-e2e-aws-upgrade
  • /test okd-e2e-gcp
  • /test okd-e2e-gcp-upgrade
  • /test okd-e2e-vsphere
  • /test tf-fmt

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-installer-master-e2e-aws
  • pull-ci-openshift-installer-master-e2e-aws-fips
  • pull-ci-openshift-installer-master-e2e-aws-single-node
  • pull-ci-openshift-installer-master-e2e-aws-upgrade
  • pull-ci-openshift-installer-master-e2e-aws-workers-rhel8
  • pull-ci-openshift-installer-master-e2e-azure-upi
  • pull-ci-openshift-installer-master-e2e-crc
  • pull-ci-openshift-installer-master-e2e-ibmcloud
  • pull-ci-openshift-installer-master-e2e-libvirt
  • pull-ci-openshift-installer-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-installer-master-e2e-metal-single-node-live-iso
  • pull-ci-openshift-installer-master-e2e-openstack
  • pull-ci-openshift-installer-master-e2e-openstack-kuryr
  • pull-ci-openshift-installer-master-e2e-ovirt
  • pull-ci-openshift-installer-master-gofmt
  • pull-ci-openshift-installer-master-golint
  • pull-ci-openshift-installer-master-govet
  • pull-ci-openshift-installer-master-images
  • pull-ci-openshift-installer-master-okd-e2e-aws
  • pull-ci-openshift-installer-master-okd-e2e-aws-upgrade
  • pull-ci-openshift-installer-master-okd-images
  • pull-ci-openshift-installer-master-okd-unit
  • pull-ci-openshift-installer-master-okd-verify-codegen
  • pull-ci-openshift-installer-master-openstack-manifests
  • pull-ci-openshift-installer-master-shellcheck
  • pull-ci-openshift-installer-master-tf-fmt
  • pull-ci-openshift-installer-master-tf-lint
  • pull-ci-openshift-installer-master-unit
  • pull-ci-openshift-installer-master-verify-codegen
  • pull-ci-openshift-installer-master-verify-vendor
  • pull-ci-openshift-installer-master-yaml-lint
Details

In response to this:

/retest ci/prow/unit
/retest ci/prow/okd-unit

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@clnperez
Copy link
Copy Markdown
Contributor Author

clnperez commented Feb 9, 2022

/test unit
/test okd-unit

Comment thread pkg/types/powervs/powervs_regions.go Outdated
Comment thread data/data/install.openshift.io_installconfigs.yaml Outdated
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

8 similar comments
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@staebler
Copy link
Copy Markdown
Contributor

/lgtm cancel
The unit and verify-codegen pre-submit checks are failing.

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2022
For more background on IPI on Power VS, refer to the enhancement
proposal here: openshift/enhancements#736

Older discussions on some of the code here can be found in
openshift#5224.
An older unreviewed version of this PR can be found here:
openshift#5292

Signed-off-by: Christy Norman <christy@linux.vnet.ibm.com>
@clnperez
Copy link
Copy Markdown
Contributor Author

sorry missed a typo. fixed and those are passing now. PTAL @staebler

@rna-afk
Copy link
Copy Markdown
Contributor

rna-afk commented Feb 28, 2022

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 28, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

6 similar comments
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 28, 2022

@clnperez: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-libvirt 1604905 link false /test e2e-libvirt
ci/prow/okd-e2e-aws 1604905 link false /test okd-e2e-aws
ci/prow/e2e-azure-upi 1604905 link false /test e2e-azure-upi
ci/prow/okd-e2e-aws-upgrade 1604905 link false /test okd-e2e-aws-upgrade
ci/prow/e2e-openstack 1604905 link false /test e2e-openstack
ci/prow/e2e-metal-single-node-live-iso 1604905 link false /test e2e-metal-single-node-live-iso
ci/prow/e2e-ibmcloud 1604905 link false /test e2e-ibmcloud
ci/prow/e2e-crc 1604905 link false /test e2e-crc
ci/prow/e2e-aws-workers-rhel8 1604905 link false /test e2e-aws-workers-rhel8

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@clnperez
Copy link
Copy Markdown
Contributor Author

/test e2e-aws
this one's being weird. timeouts and image pull issues. @rna-afk any idea if something's up with ci?

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@rna-afk
Copy link
Copy Markdown
Contributor

rna-afk commented Feb 28, 2022

Not aware of any problems in CI right now. The e2e-aws test is failing since this morning. Probably some kind of performance issue with AWS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants