[V0 deprecation] Deprecate V0 Neuron backend

[WoosukKwon]

In vLLM V1, Neuron will be supported as a plugin.

See #21082

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Code Review

This pull request cleanly deprecates and removes the V0 Neuron backend. The changes are comprehensive, covering not only the core implementation files but also associated tests, examples, CI/CD pipeline configurations, and dependency management files. The removal appears to be thorough, with no obvious leftover code or broken references. I found no issues of high or critical severity. The changes align well with the stated objective of moving Neuron support to a plugin for vLLM V1.

[WoosukKwon]

@aarondou Could you please take a look? I'm actually not sure which part will still be needed for your proposal #21082

[aarondou]

Thank you for putting up the changes @WoosukKwon . Will review.

[aarondou]

We will pull the changes down to integrate with our V1 internal implementation to test the changes. The changes to support Neuron on vLLM V1 will be published as PRs at the same time.

[mrinalks]

@WoosukKwon #21082 proposes Neuron as an in-tree implementation (not plugin) on V1 Engine. Please see Change 1 and Change 2 (various options) there. @aarondou let us review the files here and ensure nothing required is actually deleted.

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @WoosukKwon.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[elaineyz]

Certain files (for example vllm/platforms/neuron.py) would need to remain in place if Neuron V1 follows in-tree implementation. We have a separate discussion scheduled for 8/6 to discuss in-tree vs. plugin. Let's hold off on merging this PR until after we get clarity on 8/6.

[simon-mo]

In the spirit of #21690, we plan to move aggressively deleting V0 code. The functionality of V1 can be added back later and a gap in support should be fine for now. Even if we keep Neuron code, with the deletion of scheduler and others, it won't be runnable.