-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error using Helm connector with MPI example #82
Comments
Prior to this commit, the MPI example was not working for these reasons: - When scheduling a job on multiple locations the STREAMFLOW_HOSTS variable was not correctly populated; - Helm connector had some issues with file transfers and tar streaming; - DockerCompose connector had issues with parsing available locations. All these issues are solved by this fix, which also fixes #82.
Prior to this commit, the MPI example was not working for these reasons: - When scheduling a job on multiple locations the STREAMFLOW_HOSTS variable was not correctly populated; - Helm connector had some issues with file transfers and tar streaming; - DockerCompose connector had issues with parsing available locations. All these issues are solved by this fix, which also fixes #82.
Prior to this commit, the MPI example was not working for these reasons: - When scheduling a job on multiple locations the STREAMFLOW_HOSTS variable was not correctly populated; - Helm connector had some issues with file transfers and tar streaming; - DockerCompose connector had issues with parsing available locations. All these issues are solved by this fix, which also fixes #82.
Prior to this commit, the MPI example was not working for these reasons: - When scheduling a job on multiple locations the STREAMFLOW_HOSTS variable was not correctly populated; - Helm connector had some issues with file transfers and tar streaming; - DockerCompose connector had issues with parsing available locations. All these issues are solved by this fix, which also fixes #82.
Dear @zhangzhenhuajack, |
when I git pull update , still has error. @GlassOfWhiskey
|
Hi @zhangzhenhuajack, streamflow run --debug streamflow_jk.yml In this way, I can get a bit more information to reproduce it. |
I think copy file is error, helm not support copy file to k8s's pod,maybe need to used I have other question is : Whether PVC needs to be configured to solve location file communication problems with k8s |
this pod is running,but pod can not interact with location's file. @GlassOfWhiskey |
if streamflow can directly support |
Hi @zhangzhenhuajack, |
Oh BTW StreamFlow 0.2.0.dev4 also as a new Kubernetes connector, which doesn't require Helm charts but only a list of Kubernetes |
The text was updated successfully, but these errors were encountered: