Metadata federal management system and method under unified namespace

Abstract

The invention provides a metadata federation management system and method under a unified namespace. The system comprises a data storage unit, a data directory unit, a metadata federation unit and a data gateway unit. The data storage unit comprises a plurality of heterogeneous storage systems, and the types of the heterogeneous storage systems are different. The data directory unit is used for managing business metadata of each heterogeneous storage system; the business metadata is used for describing the data content, the data source and the data association relationship. The metadata federation unit is used for managing technical metadata of each heterogeneous storage system, and the technical metadata is used for describing logic-to-physical mapping information, access protocol and endpoint information and authentication and authorization information of data. The data gateway unit is used for providing protocol conversion and is responsible for data routing to read and cache data. Through unified management of the metadata by the metadata federation unit, the problem of data islands in a heterogeneous storage environment can be avoided.

Description

Technical Field

[0001] This application relates to the field of information storage technology, and in particular to a metadata federated management system and method under a unified namespace. Background Technology

[0002] Large-scale model applications, such as enterprises or organizations training large-scale multimodal models, mainly obtain their data through massive multi-source heterogeneous data collection (such as publicly available Internet text, professional corpora, and synthetic data) and enhanced generation with cross-modal alignment (such as text-image synthesis based on semantic association). Throughout the data lifecycle, the storage system needs to provide functions such as PB (Petabytes) or even EB (Exabytes) level high-concurrency throughput, cross-modal data consistency guarantee, and long-term fault tolerance and recovery.

[0003] For organizations with massive data management needs, storage resources can be used to create an automated and scalable global data environment, providing their users with a local access experience for data across various storage types from different vendors, potentially residing in one or more locations. However, managing various types of storage systems typically requires moving massive amounts of metadata to a separate metadata server (or metadata cluster). Metadata migration is very time-consuming, especially for petabyte-scale or even exabyte-scale storage systems, increasing the time overhead of system management. Furthermore, during the migration, the managed storage system can only provide performance-limited storage access. Summary of the Invention

[0004] In view of this, this application provides a metadata federated management system and method under a unified namespace, so as to at least solve the technical problems existing in the related technologies.

[0005] According to a first aspect of this application, a unified namespace-based metadata federated management system is provided, the system comprising: The data storage unit includes multiple heterogeneous storage systems of different types. A data catalog unit is used to manage the business metadata of each of the heterogeneous storage systems; the business metadata is used to describe data content, data source, and data association relationships. The metadata federation unit, connected to the data directory unit, is used to manage the technical metadata of each heterogeneous storage system. The technical metadata is used to describe the logical-to-physical mapping information of the data, access protocol and endpoint information, and authentication and authorization information. Specifically, for heterogeneous storage systems with independent metadata servers, the metadata federation unit manages their corresponding technical metadata by registering the information of the independent metadata servers. The data gateway unit, connected to the metadata federation unit, is used to provide protocol conversion and is responsible for data routing to read and cache data.

[0006] In one alternative implementation, the data federation unit manages the multiple heterogeneous storage systems according to different integration strategies based on the types of the multiple heterogeneous storage systems.

[0007] In one alternative implementation, for a heterogeneous storage system of network-attached storage type, the metadata federation unit obtains its corresponding technical metadata information by crawling the full directory tree.

[0008] In one alternative implementation, the data catalog unit is also used to provide a globally unified index.

[0009] In one alternative implementation, the data gateway unit may be dynamically expanded according to the load; and / or, the data gateway unit is controlled by the metadata federation unit.

[0010] In one optional implementation, the plurality of heterogeneous storage systems include two types: those using the standard NFS protocol and those using non-standard NFS protocols. For heterogeneous storage systems using the standard NFS protocol, the access path is direct access. For heterogeneous storage systems using non-standard NFS protocols, the access path is determined based on whether the heterogeneous storage system has an independent metadata server.

[0011] In one optional implementation, for a heterogeneous storage system that uses a non-standard NFS protocol and has no independent metadata server, the access path is accessed via the data gateway unit; for a heterogeneous storage system that uses a non-standard NFS protocol and has an independent metadata server, the access path is accessed via the private protocol of the target operating environment.

[0012] According to a second aspect of this application, a metadata federation management method under a unified namespace is provided, applied to the management system in any embodiment of the first aspect; the method includes: The data catalog unit responds to a user's business query request by obtaining the target business metadata of the target data and returning the target business metadata to the user; the target business metadata is used to describe the data content, data source, and data association of the target data. In response to a user data query command, the metadata federation unit determines the target technical metadata that matches the target business metadata; the target technical metadata is used to describe the logical-to-physical mapping information, access protocol and endpoint information, and authentication and authorization information of the target data; The metadata federation unit returns the target technology metadata to the user; the target technology metadata is used to determine the data layout of the target heterogeneous storage system and the storage access protocol type of the target heterogeneous storage system; The target heterogeneous storage system accepts access operations performed by users according to the storage access protocol type.

[0013] In an optional implementation, the method further includes: When the target heterogeneous storage system uses the standard NFS protocol, the target access path is determined to be direct access; When the target heterogeneous storage system uses a non-standard NFS protocol, the corresponding access method is determined based on whether the target heterogeneous storage system has an independent metadata server.

[0014] In one optional implementation, when the target heterogeneous storage system uses a non-standard NFS protocol, determining the corresponding access method based on whether the target heterogeneous storage system has an independent metadata server includes: For heterogeneous storage systems that use non-standard NFS protocols and do not have independent metadata servers, the access path is through the data gateway unit. For heterogeneous storage systems that use non-standard NFS protocols and have independent metadata servers, the access path is accessed via the target operating environment's private protocol.

[0015] The metadata federated management system and method under a unified namespace provided in this application include a data storage unit 10, a data directory unit 20, a metadata federated unit 30, and a data gateway unit 40. The metadata federated unit 30 manages the technical metadata of heterogeneous storage systems of different types. For heterogeneous storage systems with independent metadata servers, the metadata federated unit manages their corresponding technical metadata by registering the information of the independent metadata servers. In this way, data in the data storage unit 10 can be incorporated into the unified namespace without migration. The metadata federated unit 30 achieves a separation design between metadata and data, enabling the management of storage systems from different vendors, regions, and access protocols. It also provides parallel data access under a unified namespace, allowing for global management without modifying existing storage, thus solving the data silo problem in heterogeneous storage environments.

[0016] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram illustrating the structure of a metadata federated management system under a unified namespace, as shown in an exemplary embodiment of this application. Figure 2 This is a schematic diagram illustrating the access process of a metadata federated management system under a unified namespace, as shown in an exemplary embodiment of this application. Figure 3 This is a flowchart illustrating an exemplary embodiment of the present application of a metadata federation management method under a unified namespace; Figure 4 This is a flowchart illustrating an exemplary embodiment of the present application of a method for determining storage access based on protocol type; Figure 5 This is a schematic diagram illustrating a method for metadata federation management under a unified namespace, as shown in an exemplary embodiment of this application. Detailed Implementation

[0019] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0020] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0021] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0022] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0023] All user-related data involved in the technical solution of this application are obtained with the user's authorization, such as through pop-up windows or by inviting individuals to upload their own data.

[0024] Research has revealed that organizations with massive data management needs can leverage their existing storage resources to create an automated and scalable global data environment, providing their users with local access to data across various storage types from different vendors, potentially residing in one or more locations. However, managing data across different vendors, storage platforms, and geographical locations presents significant challenges. This is particularly true for storage systems using non-standard protocols like NFSv4.2 / pNFS (Parallel NFS) that manage files or objects, such as Lustre, GPFS (General Parallel File System), and BeeGFS. Current methods for managing these systems require moving massive amounts of metadata to a dedicated metadata server (or metadata cluster). Since metadata migration is extremely time-consuming, especially for petabyte-scale or even exabyte-scale storage systems, this increases the time overhead of system management. Furthermore, during the migration, the managed storage system can only provide limited storage access.

[0025] In addition, existing metadata management solutions only handle the efficient storage and accurate querying of structured attributes (such as permissions, paths, modification times, etc.). For multimodal application scenarios, such as the need to perform semantic-level retrieval and analysis of unstructured data (such as file content, image features, text descriptions, etc.) (e.g., "find all files with similar topics to a certain document"), existing metadata management solutions are unable to efficiently handle complex queries.

[0026] Based on the above research, this application provides a metadata federated management system and method under a unified namespace. This system enables parallel data access under a unified namespace for multiple independent storage systems using non-standard protocols. Data in the managed storage systems does not need to be moved, nor does the metadata of storage systems with independent metadata servers. This avoids data silos caused by storing data in incompatible storage types. Furthermore, the management system provides efficient data access and data content retrieval. In other words, this management system can solve the data silo problem in multi-source heterogeneous storage environments, providing a unified data view and high-performance parallel data access capabilities without requiring data migration (storage systems with independent metadata servers do not require metadata migration).

[0027] The metadata server can be a single server or a server cluster consisting of multiple servers; there is no specific limitation.

[0028] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0029] See Figure 1 As shown, Figure 1 A schematic diagram of a metadata federated management system under a unified namespace is shown. This namespace-based metadata federated management system 100 includes a data storage unit 10, a data directory unit 20, a metadata federation unit 30, and a data gateway unit 40. The data storage unit 10 includes multiple heterogeneous storage systems. The data directory unit 20 manages the business metadata of each heterogeneous storage system. The business metadata describes data content, data source, and data relationships. The metadata federation unit manages the technical metadata of each heterogeneous storage system. The technical metadata describes the logical-to-physical mapping information of the data, access protocols and endpoint information, and authentication and authorization information. The data gateway unit 40 provides protocol conversion and is responsible for specific data routing, reading and caching data.

[0030] The logical-to-physical mapping information refers to the mapping relationship between logical libraries and physical libraries, mapping logical concepts to actual storage locations. The access protocol indicates the type of storage access protocol used by the heterogeneous storage system, and endpoint information refers to the set of target service addresses and protocol entry points required to access storage units. Authentication and authorization information includes user authentication information and data access permissions (such as read, write, and view permissions), where user authentication information indicates that the authenticated user has the authority to access the data.

[0031] This application provides a metadata federated management system 100 under a unified namespace, comprising a data storage unit 10, a data directory unit 20, a metadata federated unit 30, and a data gateway unit 40. The metadata federated unit 30 manages the technical metadata of different types of heterogeneous storage systems. For heterogeneous storage systems with independent metadata servers, the metadata federated unit manages their corresponding technical metadata by registering the information of the independent metadata servers. In this way, data in the data storage unit 10 can be incorporated into the unified namespace without migration. The metadata federated unit 30 achieves a separation of metadata and data, enabling the management of storage systems from different vendors, regions, and access protocols, and providing parallel data access under a unified namespace. It allows for global management without modifying existing storage, solving the data silo problem in heterogeneous storage environments.

[0032] In this context, the separation of metadata and data paths means that metadata is placed in metadata federation unit 30, while data is placed in data storage unit 10. In large-scale storage scenarios, each of these units is stored on a separate server. In this way, metadata and data are stored independently and separately.

[0033] It should be noted that the above-mentioned units can be interconnected (including direct or indirect connections) to communicate with each other. For example, data flow and control flow can interact through clearly defined interfaces.

[0034] Specifically, data storage unit 10 includes all managed heterogeneous storage systems. These heterogeneous storage systems are of different types and can be divided into standard NFS and non-standard NFS categories based on their protocol support. In this embodiment, for heterogeneous storage systems using the standard NFS protocol, the access path is direct access; for heterogeneous storage systems using the non-standard NFS protocol, the access path is determined based on whether the heterogeneous storage system has an independent metadata server.

[0035] For example, for heterogeneous storage systems using non-standard NFS protocols and without independent metadata servers, the access path is through the data gateway unit 40 (indirect access); for heterogeneous storage systems using non-standard NFS protocols and with independent metadata servers, the access path is through the private (native) protocol of the target operating environment, i.e., through the private protocol of the heterogeneous storage system. For example, storage in heterogeneous storage systems supporting standard NFS / pNFS protocols can be accessed directly; for heterogeneous storage systems using non-standard NFS protocols such as SMB, S3, or NAS using non-standard NFS, which do not have independent metadata servers (clusters), the access path is through the data gateway unit 40; while for heterogeneous storage systems such as Lustre with independent metadata servers, access is through the Lustre private protocol. For example, by deploying Lustre clients in the form of Serverless Runtime or Stateless Containers, access is achieved through their private protocol, thereby ensuring performance while realizing parallel data access under a unified namespace.

[0036] The data catalog unit 20 provides a globally unified index, offering users a unified data view and semantic query capabilities. For example, the data catalog unit 20 can be used to build a globally unified business metadata (also known as semantic metadata) index library. Utilizing technologies such as vector databases, it organizes information such as data business tags, owners, lineage relationships, and access frequency, enabling users to quickly query data through advanced semantic attributes, thereby understanding the business context of the data without traversing the underlying storage units. Lineage relationships reflect the upstream and downstream relationships between data.

[0037] The metadata federation unit 30 is used to realize the federated management of technical metadata. Specifically, it can manage the multiple heterogeneous storage systems according to different integration strategies based on their types. That is, it can adopt differentiated integration strategies based on the types of the managed heterogeneous storage systems.

[0038] For example, for heterogeneous storage systems of the network-attached storage type, the metadata federation unit 30 obtains its corresponding metadata information through full directory tree crawling. That is, for network-attached storage systems, a crawler can obtain their complete directory tree structure metadata. For storage systems with independent metadata servers (clusters), their metadata servers (clusters) are registered in the data directory unit 20, forming a metadata federation management with the metadata federation unit 30. The data directory unit 20 records the information of newly added metadata servers (clusters). That is, for storage systems with independent metadata servers (clusters), only their metadata server information needs to be federated. For example, the metadata information in the independent metadata server can be directly registered in the data directory unit 20 without migrating (copying) the metadata. In this way, the technical metadata of various heterogeneous storage systems can be uniformly managed, providing a consistent technical view for the upper layer, and saving physical storage space used for storing metadata.

[0039] The data gateway unit 40, acting as a protocol adaptation layer, provides multi-protocol access capabilities and can perform protocol conversion. Furthermore, it can execute specific data paths and linearly increase data throughput bandwidth through horizontal scaling. In some embodiments, the data gateway unit 40 can dynamically expand according to the load; if the number of users served by the data gateway unit 40 reaches a certain threshold or the storage space used for caching reaches a set threshold, a new data gateway needs to be added. In other embodiments, the data gateway unit 40 is also controlled by the metadata federation unit 30, working collaboratively with it, receiving instructions from the metadata federation unit 30, and directly exchanging data with various heterogeneous storage systems in the data storage unit 10.

[0040] See Figure 2 As shown, Figure 2 This diagram illustrates the access process of a metadata federated management system under a unified namespace. Various units can interact with each other via interfaces for data and control flow. The access process begins with a user querying business metadata, then retrieves technical metadata, and finally routes to the appropriate path based on the protocol type indicated by the technical metadata.

[0041] Specifically, the application interaction side, acting as the system's access starting point, can generate user query requests based on user output. These requests first reach the data directory unit 20. The data directory unit 20 manages global business metadata and can return corresponding business metadata. Then, the user can input a data query command based on the business metadata returned by the data directory unit 20. This command is passed to the metadata federation unit 30, which searches for the corresponding technical metadata and determines the corresponding access path based on the protocol type indicated by the technical metadata. If the determined access path is indirect, the access can be routed to the data gateway unit 40, which then directs it to the underlying data storage unit 10. This system, through its metadata and data path separation architecture, achieves logically unified management and parallel access to physically distributed storage resources, effectively solving the data silo problem in multi-source heterogeneous storage environments.

[0042] It should be noted that the system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without any inventive effort.

[0043] For example, each of the above units can be a server, such as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud storage, big data and artificial intelligence platforms.

[0044] See Figure 3 The diagram shows a flowchart of a metadata federation management method under a unified namespace provided in an embodiment of this application. This method is applied to the metadata federation management system 100 under a unified namespace in any of the foregoing embodiments. The method includes the following steps S101-S104: S101, the data catalog unit responds to the user's business query request, obtains the target business metadata of the target data, and returns the target business metadata to the user; the target business metadata is used to describe the data content, data source and data association of the target data.

[0045] S102, the metadata federation unit responds to the user data query instruction and determines the target technical metadata that matches the target business metadata; the target technical metadata is used to describe the logical-to-physical mapping information, access protocol and endpoint information, and authentication and authorization information of the target data.

[0046] S103, the metadata federation unit returns the target technology metadata to the user; the target technology metadata is used to determine the data layout of the target heterogeneous storage system and the storage access protocol type of the target heterogeneous storage system.

[0047] S104, the target heterogeneous storage system accepts access operations performed by the user according to the storage access protocol type.

[0048] This access operation includes read and write operations. For example, the metadata federation unit returns technical metadata of the user's target data; the user can determine the protocol type used by the target heterogeneous storage system based on this technical metadata, and determine the corresponding target access path based on the protocol type. The user can then perform access operations on the target heterogeneous storage system based on other information provided by the technical metadata. Alternatively, the metadata federation unit can perform the above operations based on the technical metadata and return the target access path to the user.

[0049] In some embodiments, see Figure 4 As shown, the method may further include the following steps S1031~S1032: S1031, if the target heterogeneous storage system adopts the standard NFS protocol, the target access path is determined to be direct access.

[0050] S1032, when the target heterogeneous storage system adopts a non-standard NFS protocol, the corresponding access method is determined based on whether the target heterogeneous storage system has an independent metadata server.

[0051] In some embodiments, when the target heterogeneous storage system uses a non-standard NFS protocol, determining the corresponding access method based on whether the target heterogeneous storage system has an independent metadata server includes: For heterogeneous storage systems that use non-standard NFS protocols and do not have independent metadata servers, the access path is through the data gateway unit. For heterogeneous storage systems that use non-standard NFS protocols and have independent metadata servers, the access path is accessed via the target operating environment's private protocol.

[0052] Specifically, see Figure 5 As shown, Figure 5This diagram illustrates a process for a unified namespace-based metadata federation management approach. The process begins with a user querying data catalog unit 20 to obtain the business metadata of the target data. This step enables the user to understand the data content, source, and relationships at the business semantic level. Subsequently, guided by the business metadata, the user accesses metadata federation unit 30 to obtain detailed technical metadata, thereby clarifying the underlying information such as the data's physical storage location, organizational structure, and access interfaces.

[0053] Furthermore, the method can also determine the access protocol. For example, the protocol type supported by the storage unit (target heterogeneous storage system) can be identified based on the acquired technical metadata. If the storage unit supports the standard NFS / pNFS protocol, the user can directly access the storage unit to achieve efficient data read and write operations. If the storage unit uses a non-standard NFS / pNFS protocol, the access path is further subdivided. For storage resources without an independent metadata server, such as those using SMB, S3, or non-standard NFS NAS protocols, the access request will be converted via the data gateway unit 40 before accessing the storage unit. For storage cluster systems with an independent metadata server, such as Lustre, GPFS, or other types of storage cluster systems, a private access protocol is embedded in the form of Serverless Runtime or Stateless Containers, and the native protocol of the cluster is used to directly access the storage unit.

[0054] This application achieves seamless, parallel access to heterogeneous storage resources within a unified namespace through a multi-layered metadata collaboration and protocol adaptive routing mechanism. The entire process demonstrates the architectural advantages of separating metadata from data paths, ensuring effective isolation between the simplicity of the user access interface and the complexity of the backend storage protocol, ultimately providing users with a transparent and efficient data access experience.

[0055] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0056] Furthermore, embodiments of the subject matter and functional operation described in this specification can be implemented in the following ways: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. Alternatively or additionally, program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information and transmit it to a suitable receiving device for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or combinations thereof.

[0057] The processing and logic flow described in this specification can be executed by one or more programmable computers that execute one or more computer programs to perform corresponding functions by operating on input data and generating output. The processing and logic flow can also be executed by dedicated logic circuitry—such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the device can also be implemented as dedicated logic circuitry.

[0058] Suitable computers for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of central processing unit. Typically, the central processing unit receives instructions and data from read-only memory and / or random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as disks, magneto-optical disks, or optical disks, or the computer will be operatively coupled to such mass storage devices to receive data from or transfer data to them, or both. However, a computer is not required to have such devices. Furthermore, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0059] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, such as semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0060] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0061] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0062] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0063] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A metadata federation management system under a uniform namespace, characterized in that, The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof.

2. The system of claim 1, wherein, The application relates to a metadata federation management system under a unified namespace, and a method thereof.

3. The system of claim 2, wherein, The application relates to a metadata federation management system under a unified namespace, and a method thereof.

4. The system of claim 1, wherein, The application relates to a metadata federation management system under a unified namespace, and a method thereof.

5. The system of claim 1, wherein, The application relates to a metadata federation management system under a unified namespace, and a method thereof.

6. The system of claim 1, wherein, The application relates to a metadata federation management system under a unified namespace, and a method thereof.

7. The system of claim 6, wherein, The application relates to a metadata federation management system under a unified namespace, and a method thereof.

8. A metadata federation management method under a uniform namespace, characterized by, The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and a method thereof. The application relates to a metadata federation management system under a unified namespace, and 9. The method of claim 8, wherein, The method further comprises: in the case that the target heterogeneous storage system adopts a standard NFS protocol, determining the target access path as direct access; in the case that the target heterogeneous storage system adopts a non-standard NFS protocol, determining the corresponding access mode according to whether the target heterogeneous storage system has an independent metadata server.

10. The method of claim 9, wherein, The method further comprises: for a heterogeneous storage system adopting a non-standard NFS protocol and having no independent metadata server, the access path is accessed via the data gateway unit; for a heterogeneous storage system adopting a non-standard NFS protocol and having an independent metadata server, the access path is accessed via a private protocol of the target running environment.

Images