Hysen LabsCurvineIO/curvine：README 來源編輯指南
根據 README、倉庫資料與授權整理 CurvineIO/curvine 的安裝與核驗路徑。
專案定位
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.」。本文只整理倉庫可直接核對的內容，不把 star、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" 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「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.。