vSAN 7平台组件架构解析.pptx

;;The main vSAN architecture components are:;vSAN Architecture Analogy: Building a House;The CLOM process runs on every vSAN node:;ide;Each object has a DOM owner, a DOM client, and a DOM component manager. DOM Client: Processes the I/O generated by a VM Runs on every node that contains VMs Forwards I/O to the DOM Owner DOM Owner: Receives I/O requests from the DOM Client Determines object accessibility Replicates I/O based on the objects RAID layout and determines in which components the data block resides Forwards the I/O to the DOM Component Manager where the components reside DOM Component Manager: Interacts with the LSOM locally to commit the I/O to disk;The LSOM performs the following functions: Creates the local components as instructed by the DOM Provides read and write buffering Performs the encryption process for the vSAN datastore Reports unhealthy storage and network devices Performs I/O retries on failing devices Interacts directly with the solid-state and magnetic devices Performs solid-state drive log recovery when the vSAN node boots;ices;RDT is a network protocol for the transmission of vSAN traffic.;When it receives a request to create an object, the CLOM determines whether the object can be created with the selected VM storage policy. If the object can be created, the CLOM instructs the DOM to create the components.;During component creation, the DOM, CLOM, and LSOM have the following interactions: The DOM decides what components are created locally. The DOM instructs the LSOM to create the local components. The LSOM interacts at the drive layer and provides persistent storage. The DOM interacts with the LSOM across the local hosts. If components are required on other nodes, the DOM interacts with the DOM instance on the remote node.;The DOM and the CLOM consult the CMMDS: To get information about available resources in the cluster To learn about the topology and the object configuration;Step-by-Step VM Creation (1) The process of creating a V