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

Setting Intel MPI architectures separately #548

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

alculquicondor
Copy link
Collaborator

Intel MPI only seems to support linux/amd64 at the moment

@alculquicondor
Copy link
Collaborator Author

/approve

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor

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

Copy link
Member

@tenzen-y tenzen-y left a comment

Choose a reason for hiding this comment

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

/lgtm

Can you create an issue to keep tracking this?
Intel MPI experts may be able to help.

@alculquicondor
Copy link
Collaborator Author

I think that is beyond the scope of this repo

@tenzen-y
Copy link
Member

tenzen-y commented Apr 5, 2023

I think that is beyond the scope of this repo

Oh, yes. That doesn't seem to have anything to do with the mpi-operator.

1 package can be upgraded. Run 'apt list --upgradable' to see it.
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://apt.repos.intel.com/oneapi all InRelease' doesn't support architecture 'arm64'

@google-oss-prow google-oss-prow bot merged commit c77dfcf into kubeflow:master Apr 5, 2023
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.

2 participants