-
Notifications
You must be signed in to change notification settings - Fork 674
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
Support v2 MPIJob #1972
Comments
@chenxi-seu Yes, we have a plan to support MPIJob v2. Please see #1906. |
@tenzen-y Thank you for your response. Could you please confirm if my current approach is correct? |
Yes, you're right. |
Sorry, I have the same problem now, but I don't understand how you did this step. |
@mupeifeiyi This would be a good example: #1777 (comment) |
/> > > @tenzen-y Thank you for your response. Could you please confirm if my current approach is correct? I plan to first install mpi-operator and then install training-operator by configuring
Thanks, the following is useful to me:
mxjob,not mxnetjob |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
For the context here, we are planning to implement support for MPIJob V2 as part of Kubeflow Training V2 proposal: https://bit.ly/3WzjTlw |
We noticed that the MPIJob used in the Kubeflow community documentation is v2beta1 version (https://www.kubeflow.org/docs/components/training/mpi/), but it seems that the training-operator only supports the v1 version of MPIJob. Does the training-operator community have plans to support v2?
![image](https://private-user-images.githubusercontent.com/78208999/292863783-e67a8c8d-ae9d-4c42-a4e5-d8dc832c45d6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ1NzMyODcsIm5iZiI6MTcyNDU3Mjk4NywicGF0aCI6Ii83ODIwODk5OS8yOTI4NjM3ODMtZTY3YThjOGQtYWU5ZC00YzQyLWE0ZTUtZDhkYzgzMmM0NWQ2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI1VDA4MDMwN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiOTVlZThjZDQzMjY1NjVhZDAyMjZjNzlhNTYzNmJkZDE1OTdhNmMyYTdlODc4YzVhNWZhOGY5ZGU4OTAxNTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.IKqxAkWijzXClWWmYiqET11tr0QTiZkTWvB_3DwVmi0)
Currently, if users need to use both MPIJob and PytorchJob together, they need to install mpi-operator to support v2beta1 MPIJob first, and then install training-operator to use the v1 PytorchJob.
The text was updated successfully, but these errors were encountered: