returns (DeallocateSpaceResponse); } 空间分配器接口 空间分配器相关接口及部分数据结构定义如下： #include #include <vector> enum class AllocateType { NONE = 0, SMALL = 1, BIG = 2 }; struct AllocateHint { = 0; }; struct Extent { uint64_t offset = 0; uint32_t len = 0; }; using Extents = std::vector; class Allocator { public: Allocator(...) {} virtual ~Allocator() = default;© XXX

of snapshots l Support asynchronous and incremental snapshot l Support lazy (pre-allocated space) and non-lazy (allocated space on needs) clones from snapshots/mirrors l Support rollback from snapshot scattered all over the storage nodes. ChunkServer provides 4KB random read/write capability to support 4KB aligned read/write on block devices.CurveBS file structure of virtual block device As mentioned unit of a consistent replication group, contains Consensus Module and Log Module. 2. The State Machine corresponds to the chunk in the CurveBS, and it applies the operations on the chunk (write, delete

rebootupload the file that store in disk to s3. */ int UploadAllCacheWriteFile(); std::vector wait_for_upload; bthread::Mutex mtx_; void AsyncUploadFunc(); /**

offset); ●ssize_t pfs_pwritev(int fd, const struct iovec *iov, int iovcnt, off_t offset); ●IO vector的接口主要是为了与brpc的iobuf对接，iobuf由若干地址不连 续的block组成，一次IO提交可以提高效率。10/17/22 8 PFS+SPDK 的部分读写的实现 ●某些盘只支持4

code : curve/src/mds/copyset/ bool GenCopyset(const ClusterInfo& cluster, int numCopysets, std::vector* out); 例如要在(zone1 zone2 zone3 zone4)中创建8个copyset: result: cs1 [copyset-1, copyset-7] cs2

, , :: < > ) CopysetManager GenCopyset const ClusterInfo& cluster int numCopysets std vector Copyset * out 6.6、topology topology参考curve的topology的实现，由于curve的physical pool和logic pool在curvef

Restore data on a disk within 5 minutes Data availability of 6 nines can be achievedCloud native Support Currently we offer CSI Driver for block storage to provide PV/PVC resources on KubernetesAgenda data copy ● RDMA Cloud NativeCluster topology The physical pool is used to physically isolate machine resources Zone is the basic unit of fault isolation Server Indicates a physical server Chunkserver api Manage multiple types of storage (object storage, HDFS storage, Elastic block storage) Support both on-premise and public cloudsAgenda Why develop storage Design objectives Achievements in

LIFECYCLE Plan to Support app lifecycle, storage lifecycle(backup, failure, recovery) DEEP INSIGHTS Plan to Support metrics, alerts, log processing and workload analysis AUTO PILOT Plan to Support horizontal/vertical metadata backup and recovery • MDS / ChunkServer should respect failure domains of Kubernetes • Support for public cloud environments • Dashboard-driven configuration after minimal Curve installFeature alternative to host path • Support automatically detect new nodes, adding / removing nodes and disk drives • Support dynamic volume resizing • chunkserver on PVC support for different data and metadata(HDD

magnification for file new write • Cooperate with Alibaba to support high-performance polardb for postgresql using CurveBS • Cloud-native support for CurveBS • CurveBS clusters and related monitoring services FlowCurveFS Roadmap • CurveFS based on CurveBS • Cache support on CurveFS • NFS support on CurveFS • Cloud tiering support • Cloud-native support for CurveFS • CurveFS clusters and related monitoring

container service (in Plan) • Config CurveBS by (Cluster and Pool CRDs) in Kubernetes (in Plan) • Support Operator capability level 5 (in Plan) • horizontal / vertical scaling, auto config tuning, abnormal CurveFS by (cluster and storage pools) CRDs in Kubernetes (in Plan) • Support Operator capability level 5 (in Plan) • now support helmCurrent Status • Release 2 major version on CurveBS • v1.2 supporting on CurveBS • POSIX-compatible and mountable • Cache support on CurveFS • CurveFS cloud native support • csi plugin for CurveFS • support operator capability level 2: automated application provisioning