Add "Build OKD for ppc64le" proposal

[mjturek]

Add proposal to build and publish ppc64le payloads alongside x86_64 builds.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign pmorie after the PR has been reviewed.
You can assign the PR to them by writing /assign @pmorie in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

Hi @mjturek. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[mjturek]

I know this is a bit bare bones at the moment but I'd like to start a conversation about how we can start building and publishing for ppc64le. If there's something that you think should be detailed or discussed, please bring it up here!

[vrutkovs]

/cc @LorbusChris @smarterclayton

[vrutkovs]

/ok-to-test

[squeed]

/uncc

[LorbusChris]

Thanks for working on this @mjturek!

I'd suggest we approach Fedora and/or CentOS infra folks to discuss the resource requirements with them.

Some additional details on how the builds will be done would be great, too.
For OKD on x86, FCOS is built on an external Jenkins cluster, while container builds are done on Prow (the majority of OKD containers are mirrored/promoted OCP CI builds, the rest are also built on Prow and directly tagged into the origin namespace.)

How do you envision the process be for ppc64le (i.e. is the intention to setup a ppc64le build cluster on Fedora/CentOS infra and onboard it to Prow?)

[openshift-bot]

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]

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

[clnperez]

/remove-lifecycle stale

We've been working on a prow cluster on Power inside of Power VS (part of IBM Cloud). Once we have that working we can extend what we've learned there to OKD. It's just taking a bit longer as there are no upstream images for prow on Power (yet).

[clnperez]

/remove-lifecycle rotten

[openshift-bot]

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle stale.
Stale proposals rot after an additional 30d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle stale

[LorbusChris]

We might still want to do this eventually. We're working on ARM64 CI and OKD builds now, which should serve as a blueprint for further archs.

/remove-lifecycle stale

[openshift-bot]

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle stale.
Stale proposals rot after an additional 7d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle stale

[clnperez]

/remove-lifecycle stale
we've got upstream prow images for ppc64le. making some progress.

any news on the ARM front @LorbusChris ?

[clnperez]

/remove-lifecycle stale

[clnperez]

@LorbusChris we're getting a bit more interest from customers. You'd mentioned getting with the Fedora and/or CentOS infra folks. Is there a process there? Do you know who to ping?

[LorbusChris]

Hi @clnperez,
I think that specific comment is now obsolete.
OKD is built on OpenShift's multi-cluster Prow CI system, so there'd have to be at least one ppc64le build farm cluster set up and added to Prow.
I think work for that is already on its way, but I'm not involved in that effort. Once that's set up though, and there are per-component CI builds and CI release payloads, it'll be possible to also create OKD release payloads for that arch.

[clnperez]

Yep, that's underway (and I've been keeping informed). Sounds like what we do need is fcos builds first -- and that's a conversation that's happening (kind of) here: coreos/fedora-coreos-tracker#987 & coreos/coreos-assembler#2473

[openshift-bot]

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle stale.
Stale proposals rot after an additional 7d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale enhancement proposals rot after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Rotten proposals close after an additional 7d of inactivity.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten enhancement proposals close after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Reopen the proposal by commenting /reopen.
Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Exclude this proposal from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten enhancement proposals close after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Reopen the proposal by commenting /reopen.
Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Exclude this proposal from closing again by commenting /lifecycle frozen.

/close

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.