[HEALTH]: Vineyard

[kevin-wangzefeng]

Project name

Vineyard

Archiving Checklist

• TOC vote to archive passed

PRs

• Move project (logo) to archived in the artwork repo Move Vyneyard to Archive artwork#671
• Move project to archived on landscape Update Vineyard project status from sandbox to archived landscape#4918
• Remove maintainer list from project-maintainers.csv Remove Vineyard project from project-maintainers.csv foundation#1455
• Archive DevStats data (open issue in devstats repo) Remove archived project Vineyard from DevStats devstats#145
• Remove from CLOMonitor data Remove archived Vineyard project from CNCF clomonitor#1919

Mailing lists

• Remove from staff list of maintainer emails list
• Archive (lock) maintainers mailing list (groups.io)
• Remove mailing list from maintainers@cncf.io (google groups) mailing group

Send emails

• Remove project (logo) from all slide decks (contact pr@cncf.io)
• Remove project (logo) from event sites (contact events@cncf.io)
• Remove from CNCF store (reach out to staff or email store@cncf.io)
• Archive project in LFX Insights (move to archive in PCC - Email Formation team)

Other:

• Remove from maintainers & project from service desk
• Check with LF IT for any CI/CD or other infrastructure the needs to be removed
• Revoke maintainer access to Copilot - check if the maintainers are listed on other projects for Copilot access

Project Issue Link

TBA

Concern

Project Link: v6d-ioi/v6d

Vineyard has had no real activity since December of last year.

Additional information can be seen on their LFX Insights dashboard

Prior engagement

No response

Additional Information

No response

[lukaszgryglicki]

Recent activity.

[dashanji]

Hi @kevin-wangzefeng @lukaszgryglicki @angellk @chira001.

We would like to acknowledge the recent inactivity in the Vineyard (v6d) project. The main reason is that we have been focusing on internal development, where a series of significant enhancements and optimizations have been carried out. These improvements aim to strengthen v6d’s capabilities as a foundational infrastructure component for large-scale data processing and AI workloads — especially in the field of Large Language Models (LLMs).

While this has temporarily slowed down our open-source updates, we are now actively working on gradually open-sourcing key components and features. We firmly believe that Vineyard (v6d) holds great potential in the open-source ecosystem — especially as a core building block for next-generation AI infrastructure, such as in projects like AIBrix(https://github.com/vllm-project/aibrix) and beyond.

Our on-going efforts that will be shared with the community include:

1. Enhanced remote data accessing that leverages the advanced technologies of RDMA for high-performance data transfer.
2. Specialized metadata service design that are optimized for KVCache sharing LLM workloads.
3. End-to-end integration with vLLM and SGLang that provides a mechanism for unified KVCache management for both distributed KVCache and P/D disaggregated inference pipelines.

Future Plans:

Focus on AI Infrastructure:
We will continue optimizing the existing codebase to better support AI and machine learning workflows, with a special emphasis on LLM-related integrations. One of the key use cases we’re exploring is using Vineyard as a high-performance backend storage for KVCache Connector, enabling efficient management and sharing of attention key-value caches across distributed inference pipelines.

Strengthen Community Collaboration:
We aim to actively engage with the community by collecting user feedback and encouraging more developers to contribute and collaborate, AIBrix is a great example of how we can work together to build a more robust and versatile AI infrastructure.

Thank you for your understanding and continued support. We are committed to making Vineyard (v6d) more active, valuable, and impactful moving forward, and we look forward to sharing our progress with you in the near future.

[chira001]

@dashanji could you provide an update on the status of the project please?

[dashanji]

Hi, @chira001. Thanks for your attention! We’re excited to share that we’ve recently open-sourced several internal features—including Enhanced Remote Data Access and End-to-End Integration with vLLM. For full details, please refer to the PR(v6d-io/v6d#2063). This is just the first step; we plan to release many more AI infrastructure–related features as open source in the near future.

If you have any further questions, please feel free to let me know!