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
I started under the assumption that the test runner and the Deluge nodes would be able to share a filesystem (that was the initial plan with Wings), but:
this creates performance artifacts, particularly if we're mounting the same persistent for everyone;
Hetzner doesn't support ReadWriteMany.
We therefore need to change approach. While I could generate data locally at the clients, this would mean modifying the client images for an experiment, which I don't want to do. I'm therefore going to try to use the Kubernetes Python client and implement a different uploader.
I'll also adjust the PVCs so they use local storage. This should eliminate performance artifacts.
The text was updated successfully, but these errors were encountered:
I started under the assumption that the test runner and the Deluge nodes would be able to share a filesystem (that was the initial plan with Wings), but:
We therefore need to change approach. While I could generate data locally at the clients, this would mean modifying the client images for an experiment, which I don't want to do. I'm therefore going to try to use the Kubernetes Python client and implement a different uploader.
I'll also adjust the PVCs so they use local storage. This should eliminate performance artifacts.
The text was updated successfully, but these errors were encountered: