# US 12,007,942 B2 · Methods and systems for seamlessly provisioning client application nodes in a distributed system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,007,942 B2 - Document ID: US12007942B2 - Status: Granted - Kind: B2 - Application number: 17/512,204 - Filed: 2021-10-27 - Published: 2023-04-27 - Granted: 2024-06-11 - Earliest claimed: 2021-10-27 - Assignees: EMC IP Holding Company LLC - Applicants: EMC IP Holding Company LLC - Inventors: Jean-Pierre Bono; Thomas Fridtjof Dahl - Web page: https://patentgrep.com/patent/US12007942B2 ## CPC - G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)} - G06F 16/182: Distributed file systems - G06F 3/0607: {by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device} - G06F 3/0631: {by allocating resources to storage systems} - G06F 3/0638: {Organizing or formatting or addressing of data} - G06F 3/0665: {at area level, e.g. provisioning of virtual or logical volumes} - G06F 3/0689: {Disk arrays, e.g. RAID, JBOD} - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In general, embodiment relate to a method for provisioning a plurality of client application nodes in a distributed system using a management node, the method comprising: creating a file system in a namespace; associating the file system with a scale out volume; mounting the file system on a metadata node in the distributed system, wherein mounting the file system comprises storing a scale out volume record of the scale out volume; storing file system information for the file system in a second file system on the management node, wherein the file system information specifies the file system and the metadata node on which the file system is mounted; wherein storing the file system information triggers distribution of the file system information to at least a portion of a plurality of client application nodes. ## Claims ### Claim 1 A method for provisioning a plurality of client application nodes in a distributed system using a management node, the method comprising: creating a file system in a namespace; associating the file system with a scale out volume (SOV), wherein: the SOV is associated with storage devices, the SOV provides a layer of abstraction between a sparse virtual space associated with the file system and the storage devices, and the storage devices are scalable in size without impacting interaction between the sparse virtual space and the plurality of client application nodes; mounting the file system on a metadata node in the distributed system, wherein mounting the file system comprises storing a scale out volume record of the SOV, wherein mounting the file system on the metadata node further comprises storing a set of mapped Redundant Array of Independent Disks (RAID) groups (MRGs) records corresponding to a set of MRGs; storing file system information for the file system in a second file system on the management node, wherein the file system information specifies the file system, the metadata node on which the file system is mounted, a first export rule, and a second export rule; wherein the first export rule specifies that only at least a portion of a plurality of client application nodes is able to access the file system information; wherein the second export rule specifies that only a portion of the file system information is accessible to at least a sub-portion of the portion of the plurality of client application nodes; and wherein storing the file system information triggers distribution of the file system information to the at least a portion of the plurality of client application nodes based on the first export rule and the second export rule. ### Claim 2 (depends on 1) The method of claim 1, wherein associating the file system with a scale out volume comprises generating the scale out volume record, wherein the scale out volume record specifies a size of the file system and the set of MRGs associated with the SOV. ### Claim 3 (depends on 2) The method of claim 2, each MRG in the set of MRGs corresponds to a set of the storage devices, wherein data and metadata associated with the file system is stored across the set of the storage device. ### Claim 4 (depends on 2) The method of claim 2, wherein a MRG record in the set of MRG records specifies at least a plurality of the storage devices that are members of the MRG, a type of media of the plurality of the storage devices, and a size of the MRG. ### Claim 5 (depends on 4) The method of claim 4, wherein the type of media is persistent memory (PMEM). ### Claim 6 (depends on 1) The method of claim 1, wherein the namespace is maintained on a second metadata node in the distributed system, wherein namespace information for the namespace is stored in the second file system and specifies the second metadata node on which the namespace is maintained. ### Claim 7 A non-transitory computer readable medium comprising instructions which, when executed by a processor, enables the processor to perform a method, the method comprising: creating a file system in a namespace; associating the file system with a scale out volume (SOV), wherein: the SOV is associated with storage devices, the SOV provides a layer of abstraction between a sparse virtual space associated with the file system and the storage devices, and the storage devices are scalable in size without impacting interaction between the sparse virtual space and a plurality of client application nodes; mounting the file system on a metadata node in a distributed system, wherein mounting the file system comprises storing a scale out volume record of the SOV, wherein mounting the file system on the metadata node further comprises storing a set of mapped Redundant Array of Independent Disks (RAID) groups (MRGs) records corresponding to a set of MRGs; storing file system information for the file system in a second file system on a management node, wherein the file system information specifies the file system, the metadata node on which the file system is mounted, a first export rule, and a second export rule; wherein the first export rule specifies that only at least a portion of a plurality of client application nodes is able to access the file system information; wherein the second export rule specifies that only a portion of the file system information is accessible to at least a sub-portion of the portion of the plurality of client application nodes; and wherein storing the file system information triggers distribution of the file system information to the at least a portion of the plurality of client application nodes based on the first export rule and the second export rule. ### Claim 8 (depends on 7) The non-transitory computer readable medium of claim 7, wherein associating the file system with a scale out volume comprises generating the scale out volume record, wherein the scale out volume record specifies a size of the file system and the set of MRGs associated with the SOV. ### Claim 9 (depends on 8) The non-transitory computer readable medium of claim 8, wherein each MRG in the set of MRGs corresponds to a set of the storage devices, wherein data and metadata associated with the file system is stored across the set of the storage device. ### Claim 10 (depends on 8) The non-transitory computer readable medium of claim 8, wherein a MRG record in the set of MRG records specifies at least a plurality of the storage devices that are members of the MRG, a type of media of the plurality of the storage devices, and a size of the MRG. ### Claim 11 (depends on 10) The non-transitory computer readable medium of claim 10, wherein the type of media is persistent memory (PMEM). ### Claim 12 (depends on 7) The non-transitory computer readable medium of claim 7, wherein the namespace is maintained on a second metadata node in the distributed system, wherein namespace information for the namespace is stored in the second file system and specifies the second metadata node on which the namespace is maintained. ### Claim 13 A node, comprising: memory comprising instructions; a processor configured to execute the instructions, wherein when the instructions are executed the node performs a method, the method comprising: creating a file system in a namespace; associating the file system with a scale out volume (SOV), wherein: the SOV is associated with storage devices, the SOV provides a layer of abstraction between a sparse virtual space associated with the file system and the storage devices, and the storage devices are scalable in size without impacting interaction between the sparse virtual space SOV and a plurality of client application nodes; mounting the file system on a metadata node in a distributed system, wherein mounting the file system comprises storing a scale out volume record of the SOV, wherein mounting the file system on the metadata node further comprises storing a set of mapped Redundant Array of Independent Disks (RAID) groups (MRGs) records corresponding to a set of MRGs; storing file system information for the file system in a second file system on the node, wherein the file system information specifies the file system, the metadata node on which the file system is mounted, a first export rule, and a second export rule; wherein the first export rule specifies that only at least a portion of plurality of client application nodes is able to access the file system information; wherein the second export rule specifies that only a portion of the file system information is accessible to at least a sub-portion of the portion of the plurality of client application nodes; and wherein storing the file system information triggers distribution of the file system information to the at least a portion of a plurality of client application nodes based on the first export rule and the second export rule. ### Claim 14 (depends on 13) The node of claim 13, wherein associating the file system with a scale out volume comprises generating the scale out volume record, wherein the scale out volume record specifies a size of the file system and the set of MRGs associated with the SOV, wherein a MRG record in the set of MRG records specifies at least a plurality of the storage devices that are members of the MRG, a type of media of the plurality of the storage devices, and a size of the MRG.