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

Reform Bohrium executor with virtual Kubelet or Argo executor plugin #222

Open
zjgemi opened this issue Jan 24, 2023 · 1 comment
Open

Comments

@zjgemi
Copy link
Collaborator

zjgemi commented Jan 24, 2023

Current Bohrium executor runs an actual Pod with a go process or a DPDispatcher script running in the container to poll the job status. When massive steps with Bohrium executor are running simultaneously, the resource usage is considerable.

To reduce the cost, we can use virtual Kubelet to submit Bohrium job and poll the job status in the framework of https://github.com/dptech-corp/virtual-kubelet. A prerequisite of this project is a unified artifact storage (e.g. OSS) as the interface of Argo Workflows and Bohrium.

@zjgemi
Copy link
Collaborator Author

zjgemi commented Jun 13, 2023

Another possible solution is using executor plugins of Argo to write an executor for Bohrium tasks. It is needed to develop a server which implements APIs to submit Bohrium jobs and to acquire job statuses.

@zjgemi zjgemi changed the title Reform Bohrium executor with virtual Kubelet Reform Bohrium executor with virtual Kubelet or Argo executor plugin Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant