You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
In #5082 and #4929 , we have added support for multiple bounded clusters in OpenPAI. After discussion, we may leverage it to sync user's favorite jobs or prerequisites from one cluster to another in the future. Detailed process is as follows:
The user can store his/her favorite jobs in marketplace. Also, with extend prerequisite field in job protocol #5145 , the user can create some prerequiste items in marketplace. The jobs/prerequisites can be only visible to the user himself/herself.
The user can have access to multiple clusters. He/she can register them as bounded clusters.
It is natural that the user can sync his/her favorite jobs/prerequisites to another bounded clusters. We can provide users with a Synchonize to button and let him/her transfer the data.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #5082 and #4929 , we have added support for multiple bounded clusters in OpenPAI. After discussion, we may leverage it to sync user's favorite jobs or prerequisites from one cluster to another in the future. Detailed process is as follows:
The user can store his/her favorite jobs in marketplace. Also, with extend prerequisite field in job protocol #5145 , the user can create some prerequiste items in marketplace. The jobs/prerequisites can be only visible to the user himself/herself.
The user can have access to multiple clusters. He/she can register them as bounded clusters.
It is natural that the user can sync his/her favorite jobs/prerequisites to another bounded clusters. We can provide users with a
Synchonize to
button and let him/her transfer the data.The text was updated successfully, but these errors were encountered: