CurvineIO/curvine：README 来源编辑指南

CurvineIO/curvine 的 README 将项目描述为"AI-Native & Cloud-Native FS: A high-performance file semantic layer for cloud object storage, integrated with high-speed cache. CNCF Sandbox Project."。本文只整理仓库能直接核验的内容，不把星标、Fork 或宣传语当成质量证明。README 在"README"下的说明是：> Curvine: AI-Native & Cloud-Native File System , A high-performance POSIX file semantic layer built on top of cloud object storage, with an integrated multi-tier distributed cache, designed from the ground up for large-scale AI workloads。这给出的首先是项目边界，而不是已经完成的生产验证。

从 README 的"🎯 Why Curvine"和相关条目看，读者可以先判断它是否解决自己的具体问题：Each Agent Pod gets an isolated file system view via the native CSI driver, with the same logical isolation as block storage but without the per-node attach-count ceiling.。如果你的目标与这段说明不一致，就不应仅凭项目热度采用它。这里保留原项目名、命令和组件名，方便回到一手来源核对。 README 还列出了另一条可核对的信息：Provisioning a PVC is just mkdir on a distributed file system , millisecond-level, no cloud control-plane API calls, no rate limits.。这类原文条目可以帮助读者设计试运行步骤，但不能代替自己的环境测试。

README 把工作方式分散写在"📚 Documentation Resources"等段落中。可确认的线索包括：For more detailed information, please refer to:。这篇整理没有把未写出的架构、性能或安全边界补成结论；真正的运行链仍应结合仓库目录、配置文件和版本标签检查。

第一次安装应从 README 给出的入口开始。当前可复核的命令是： # Build all modules make all # Build core modules only: server client cli make build ARGS="-p core" # Build fuse and core modules make build ARGS="-p core -p fuse" # Build server-native SPDK/RDMA support. Client-side artifacts such as # curvine-cli and curvine-fuse are built in isolated client-safe profiles. make build ARGS="-p core -p fuse --spdk-rdma --spdk-dir /opt/spdk" 如果仓库没有提供命令，本文不会替它编造安装步骤，而是建议先打开 README 的"Roadmap 2026"部分，确认系统依赖、默认端口和首次初始化动作。

日常使用的细节取决于项目实际文档。README 的"🎯 Why Curvine"段落提到：The AI infrastructure landscape is undergoing a fundamental architectural shift: from a centralized model where a single large model instance serves all requests, to a distributed model where tens of thousands of Agent instances run。对于配置文件、环境变量、权限和数据目录，当前稿只记录来源明确的部分；未写明的默认值必须在测试环境中验证，并保留可回滚的配置副本。 同一部分还提到：Pods can be scheduled across nodes and AZs freely; data stays reachable because it lives in the shared Curvine namespace, not a node-bound volume.。