Skip to content

Decommission open-gpu-server#174

Merged
jaimergp merged 1 commit into
mainfrom
remove-open-gpu-server
Mar 13, 2026
Merged

Decommission open-gpu-server#174
jaimergp merged 1 commit into
mainfrom
remove-open-gpu-server

Conversation

@jaimergp
Copy link
Copy Markdown
Member

IMPORTANT:

We've been informed that the server hosted by Quansight (open-gpu-server) will be decommissioned next week. In order to prevent mid-job cancelations that can affect package uploads, we'll remove access by merging this PR on Monday, March 16th, no later than 11AM UTC.

We are working on getting access to alternative services for long-running jobs, but it might take a bit, so expect some disruption while we figure this out.

cc @conda-forge/core, @conda-forge/astra-toolbox, @conda-forge/cutlass, @conda-forge/flash-attn, @conda-forge/jaxlib, @conda-forge/libmagma, @conda-forge/mongodb, @conda-forge/muscat-split, @conda-forge/nodejs, @conda-forge/onnxruntime, @conda-forge/pytorch-cpu, @conda-forge/pytorch_scatter, @conda-forge/qt-webengine, @conda-forge/ray-packages, @conda-forge/tensorflow, @conda-forge/tinygrad, @conda-forge/torchao, @conda-forge/viskores, @conda-forge/vllm, @conda-forge/vtk-m, @conda-forge/webkit2gtk4-1 , @conda-forge/xformers.

@jaimergp
Copy link
Copy Markdown
Member Author

jaimergp commented Mar 12, 2026

Based on the .cirun access list, the following feedstocks need CPU runners:

  • conda-forge/cf-autotick-bot-test-package-feedstock
  • conda-forge/cutlass-feedstock
  • conda-forge/flash-attn-feedstock
  • conda-forge/jaxlib-feedstock
  • conda-forge/mongodb-feedstock
  • conda-forge/nodejs-feedstock
  • conda-forge/onnxruntime-feedstock
  • conda-forge/pytorch-cpu-feedstock
  • conda-forge/pytorch-scatter-feedstock
  • conda-forge/qt-webengine-feedstock
  • conda-forge/ray-packages-feedstock
  • conda-forge/tensorflow-feedstock
  • conda-forge/tinygrad-feedstock
  • conda-forge/torchao-feedstock
  • conda-forge/viskores-feedstock
  • conda-forge/vllm-feedstock
  • conda-forge/vtk-m-feedstock
  • conda-forge/webkit2gtk4.1-feedstock
  • conda-forge/xformers-feedstock

These need GPU runners:

  • conda-forge/astra-toolbox-feedstock
  • conda-forge/cf-autotick-bot-test-package-feedstock
  • conda-forge/conda-forge-ci-setup-feedstock
  • conda-forge/conda-smithy-feedstock
  • conda-forge/flash-attn-feedstock
  • conda-forge/libmagma-feedstock
  • conda-forge/muscat-split-feedstock
  • conda-forge/pytorch-cpu-feedstock-gpu
  • conda-forge/tensorflow-feedstock
  • conda-forge/tinygrad-feedstock
  • conda-forge/torchao-feedstock
  • conda-forge/viskores-feedstock
  • conda-forge/vllm-feedstock

Perhaps more interestingly is to see it together. Note I've removed test feedstocks for clarity.

These need both types of runners:

  • conda-forge/flash-attn-feedstock
  • conda-forge/pytorch-cpu-feedstock
  • conda-forge/tensorflow-feedstock
  • conda-forge/tinygrad-feedstock
  • conda-forge/torchao-feedstock
  • conda-forge/viskores-feedstock
  • conda-forge/vllm-feedstock

These ONLY need CPU:

  • conda-forge/cutlass-feedstock
  • conda-forge/jaxlib-feedstock
  • conda-forge/mongodb-feedstock
  • conda-forge/nodejs-feedstock
  • conda-forge/onnxruntime-feedstock
  • conda-forge/pytorch-scatter-feedstock
  • conda-forge/qt-webengine-feedstock
  • conda-forge/ray-packages-feedstock
  • conda-forge/vtk-m-feedstock
  • conda-forge/webkit2gtk4.1-feedstock
  • conda-forge/xformers-feedstock

These ONLY need GPU:

  • conda-forge/astra-toolbox-feedstock
  • conda-forge/libmagma-feedstock
  • conda-forge/muscat-split-feedstock

@RaulPPelaez
Copy link
Copy Markdown

IIRC the cutlass feedstock does not need this runner anymore conda-forge/cutlass-feedstock#22

@fbordeu
Copy link
Copy Markdown

fbordeu commented Mar 12, 2026

@jaimergp Thanks for your time. We use this machine for the cuda support not for the long-running jobs.

conda-forge/muscat-split-feedstock can live without cuda support.
For the moment it not very clear to me how to build artefacts for all the nvidia cards architectures.
We use kokkos, and kokkos-kernels for the gpu support and we need to set, at compilation time, the target GPU architecture.

So what do I have to do to keep things working?. After this PR is merge can I continue building linux packages using the "classic" conda-forge runners?

Thanks again, conda-forge rules

@jaimergp
Copy link
Copy Markdown
Member Author

It may vary from project to project, but it should be possible to compile things with GPU support even without a GPU present. Testing the outputs is the main problem. We are working on finding a replacement for both use cases of the GPU server, but it's likely that the long running CPU support will land before GPU runners.

@jaimergp
Copy link
Copy Markdown
Member Author

Ok, we were just informed that the server will be disconnected today at 4PM ET so I'm going to remove the integrations now to avoid any killed jobs. Sorry about the sudden change! We can continue the discussions in a follow-up issue.

@jaimergp jaimergp merged commit 883cc82 into main Mar 13, 2026
1 check failed
jviehhauser added a commit to jviehhauser/onnxruntime-feedstock that referenced this pull request Apr 7, 2026
The Quansight Open GPU Server (OpenStack) was decommissioned on
2026-03-13 (conda-forge/.cirun#174), so cirun-openstack-cpu-4xlarge
runners no longer exist. All Linux GHA jobs were timing out after 24h
waiting for runners that will never come.

Cirrus runners access was granted via conda-forge/admin-requests#1982.
This switches Linux builds to ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-lg
(16 CPUs, 48GB RAM). Windows builds remain on cirun-azure-windows-4xlarge.

Re-rendered with conda-smithy 3.59.0.
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

Successfully merging this pull request may close these issues.

3 participants