Object storage service processing method and device, equipment and medium

Abstract

The invention relates to the field of cloud storage, in particular to an object storage service processing method and device, equipment and a medium. According to the method, the object storage request sent by the cloud platform is received, and the storage configuration information and the object storage demand are obtained from the object storage request, so that dependence on Swift related components and services is avoided, and resource consumption and maintenance range of the cloud platform are reduced. And secondly, the mode of acquiring the target interface service module from the plurality of interface service modules is more flexible, and customized selection can be performed according to different storage configuration information and object storage requirements. The limitation that Swift API maintenance depends on open source communities and release of storage manufacturers is eliminated, and customization requirements can be better met. And furthermore, the target interface service module is directly called to send the object storage demand to the corresponding storage system, so that the intermediate link that the API request passes through a Swift component and then is issued to a storage platform is reduced, the resource consumption is reduced, and the response time is shortened.

Description

Technical Field

[0001] The present invention relates to the field of cloud storage, and in particular to a method, device, equipment and medium for processing object storage services. Background Art

[0002] In cloud storage, object storage is an important technology that stores data and metadata in objects. Each object has a unique identifier, which can be stored persistently, accessed and shared at any time. With low cost, high scalability and high reliability, it has become an effective solution for big data storage and is widely used in multiple industries. The cloud storage market is flourishing, and the connection and management of heterogeneous object storage systems launched by various cloud vendors by IaaS cloud platforms have become an important aspect of evaluating their resource management capabilities. As an open source cloud platform project, Open Stack has been widely supported. Cloud vendors can launch cloud platforms based on it. Connection and efficient management of heterogeneous object storage systems allow users to manage with a unified management interface without having to understand the underlying architecture and consider data security and reliability. It provides flexible and convenient operation methods, provides possibilities for third-party application development, and lays the foundation for enterprises to build private cloud storage platforms. The Swift component of OpenStack is an object storage service that supports standard Swift APIs and provides a RESTful interface to manage object storage services. Heterogeneous object storage systems can be connected to these APIs so that they can be accessed and managed by Open Stack.

[0003] However, this approach has some problems, such as the need to install, enable, and configure Swift-related components and services, which increases the resource consumption and maintenance scope of the cloud platform; the object storage management functions supported by the cloud platform are limited to the Swift API, and its maintenance depends on the release of the open source community and storage vendors, which is not friendly to customized demand support; API requests need to be sent to the storage platform through Swift components, which increases resource consumption, response time, and system maintenance difficulty. Summary of the invention

[0004] In view of this, an embodiment of the present invention provides a method, device, equipment and medium for processing object storage business to solve the problems that the object storage management function of the cloud platform is limited by the Swift API and its maintenance relies on the open source community and storage manufacturers to release, which is not friendly to customized requirements, and the API request is sent to the storage platform through the Swift component, which increases resource consumption, response time and system maintenance difficulty.

[0005] In a first aspect, an embodiment of the present invention provides a method for processing an object storage service, the method being applied to an object storage service distribution terminal, the object storage service distribution terminal being connected to a cloud platform, the method comprising:

[0006] Receiving an object storage request sent by the cloud platform, wherein the object storage request includes storage configuration information and object storage requirements;

[0007] Acquire multiple interface service modules associated with the object storage service distribution terminal, and acquire a target interface service module corresponding to the storage configuration information from the multiple interface service modules;

[0008] Sending the object storage requirement to the target interface service module;

[0009] The target interface business module is called to send the object storage demand to the corresponding storage system, and receive the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

[0010] Further, acquiring a target interface service module corresponding to the storage configuration information from a plurality of interface service modules includes:

[0011] Extracting storage attribute information and function classification information from the storage configuration information, wherein the storage attribute information includes a target storage vendor identifier and a target storage protocol;

[0012] Obtaining an analysis strategy corresponding to the target storage vendor identifier;

[0013] The function classification information and the target storage protocol are analyzed according to the analysis strategy to obtain the target interface service module.

[0014] Further, the function classification information and the target storage protocol are analyzed according to the analysis strategy to obtain the target interface service module, including:

[0015] If the function classification information is a business type, obtaining a protocol matching condition associated with the business type;

[0016] The target storage protocol is matched with the protocol matching condition to obtain the target protocol matching condition hit by the target storage protocol, and the standard interface business module corresponding to the target protocol matching condition is used as the target interface business module.

[0017] Further, the function classification information and the target storage protocol are analyzed according to the analysis strategy to obtain the target interface service module, including:

[0018] If the function classification information is a management type, the management interface service module corresponding to the target storage vendor identifier is used as the target interface service module.

[0019] Further, calling the target interface business module to send the object storage demand to a corresponding storage system and receiving a processing result fed back by the storage system includes:

[0020] If the target interface business module is a standard interface business module corresponding to the target storage protocol, the standard interface business module is called to send the object storage demand to the first storage system corresponding to the target storage vendor identifier, wherein the first storage system is a storage system associated with the standard interface business module, the first storage system parses the object storage demand to obtain an operation task and a resource demand, allocates corresponding resources to the operation task according to the resource demand, and performs corresponding object storage processing operations according to the operation task to obtain a processing result;

[0021] The processing result fed back by the first storage system is received through the standard interface service module.

[0022] Further, calling the target interface business module to send the object storage demand to a corresponding storage system and receiving a processing result fed back by the storage system includes:

[0023] If the target interface business module is a management interface business module corresponding to the target storage vendor identifier, the management interface business module is called to parse the object storage requirement to obtain the target management function, and a management layer interface corresponding to the target management function is obtained from a second storage system corresponding to the target storage vendor identifier, wherein the second storage system is a storage system associated with the management interface business module;

[0024] Calling the management interface business module to send a call request to the management layer interface of the second storage system, wherein the management layer interface is used to obtain target data matching the target management function from the second storage system and feed the target data back to the management interface business module;

[0025] The management interface service module is called to encapsulate the target data to obtain the encapsulated target data.

[0026] Furthermore, the method further comprises:

[0027] Obtaining a module configuration request, wherein the module configuration request includes a storage manufacturer identifier and module configuration information;

[0028] Constructing an original management interface service module in the object storage service distribution terminal according to the storage vendor identifier;

[0029] Using the module configuration information, adjusting parameters and setting functions of the original management interface service module to obtain a management interface service module corresponding to the storage vendor identifier;

[0030] A connection relationship between the management interface business module and each management layer interface in the storage system corresponding to the storage vendor identifier is established, and the connection relationship is stored in the management interface business module corresponding to the storage vendor identifier.

[0031] In a second aspect, an embodiment of the present invention provides a device for processing an object storage service, the device comprising:

[0032] A receiving module, configured to receive an object storage request sent by the cloud platform, wherein the object storage request includes storage configuration information and object storage requirements;

[0033] An acquisition module, used to acquire multiple interface business modules associated with the object storage business distribution terminal, and acquire a target interface business module matching the storage configuration information from the multiple interface business modules;

[0034] A sending module, used for sending the object storage requirement to the target interface service module;

[0035] A calling module is used to call the target interface business module to send the object storage demand to the corresponding storage system, and receive the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

[0036] In a third aspect, an embodiment of the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0037] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method of the first aspect or any corresponding embodiment thereof.

[0038] This application first receives the object storage request sent by the cloud platform and obtains the storage configuration information and object storage requirements from it, thus avoiding the dependence on Swift-related components and services, and reducing the resource consumption and maintenance scope of the cloud platform. Secondly, the method of obtaining the target interface business module from multiple interface business modules is more flexible, and customized selection can be made according to different storage configuration information and object storage requirements. It gets rid of the restrictions on the maintenance of SwiftAPI that depends on the open source community and storage manufacturers, and can better meet customized needs. Furthermore, directly calling the target interface business module to send the object storage requirements to the corresponding storage system reduces the intermediate links of API requests passing through the Swift component and then being sent to the storage platform, thereby reducing resource consumption, shortening response time, and reducing the difficulty of system maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 is a flowchart of a method for processing an object storage service according to some embodiments of the present invention;

[0041] Figure 2 is a schematic diagram of a framework of an object storage service system according to some embodiments of the present invention;

[0042] Figure 3 is a flowchart of determining a target interface service module according to some embodiments of the present invention;

[0043] Figure 4 is a flowchart of a method for processing an object storage service according to some embodiments of the present invention;

[0044] Figure 5 is a flowchart of determining a target interface service module according to some embodiments of the present invention;

[0045] Figure 6 is a flowchart of a method for processing an object storage service according to some embodiments of the present invention;

[0046] Figure 7 is a structural block diagram of a device for processing an object storage service according to an embodiment of the present invention;

[0047] Figure 8 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0049] According to an embodiment of the present invention, a method, apparatus, device and medium for processing an object storage service are provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0050] In this embodiment, a method for processing an object storage service is provided. The method is applied to an object storage service distribution terminal. The object storage service distribution terminal is connected to a cloud platform. Figure 1 is a flow chart of a method for processing an object storage service according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0051] Step S101: receiving an object storage request sent by a cloud platform, wherein the object storage request includes storage configuration information and object storage requirements.

[0052] In the embodiments of the present application, Figure 2 As shown, the object storage service distribution terminal, as a key node connecting the cloud platform and the storage system, receives object storage requests sent from the cloud platform. The object storage request includes: storage configuration information and object storage requirements. The storage configuration information includes: storage attribute information and function classification information. The storage attribute information includes the target storage vendor identifier and the target storage protocol. The target storage vendor identifier determines the specific storage vendor to which the request is directed, such as storage vendor A or storage vendor B. Different storage vendors may differ in storage technology, service quality, interface specifications, etc., so this identifier is crucial for accurately distributing requests to the corresponding processing modules. The target storage protocol specifies the communication method of object storage, such as the S3 protocol. Different protocols differ in function, performance, and compatibility, which determines the interface and operation method used in the subsequent processing process.

[0053] In addition, the request also includes functional classification information, which is divided into business and management categories. Object storage requests for business categories are usually initiated by applications on the cloud platform. These applications provide services directly to users, and their purpose is to meet the business needs of users in the process of using the applications. It mainly involves operations on data in the storage system. For example, creating a bucket to store pictures uploaded by users may also include operations such as reading, updating, and deleting buckets or objects. Taking the creation of a bucket as an example, the application needs to ensure that the bucket can be created correctly and meets specific storage requirements, such as storage vendors, object storage protocols, etc.

[0054] The object storage request for management is initiated by the cloud platform administrator. The administrator is responsible for managing and monitoring the storage resources on the cloud platform to ensure the stable operation and efficient use of the storage system. Specific content: Mainly management operations on the storage system. For example, obtaining the usage statistics of the storage system may also include configuring storage policies, managing user permissions, monitoring the operating status of the storage system, etc. Taking obtaining the usage statistics of the storage system as an example, the administrator needs to understand the usage of the storage system in order to plan and optimize resources.

[0055] Step S102: acquiring multiple interface service modules associated with the object storage service distribution terminal, and acquiring a target interface service module corresponding to the storage configuration information from the multiple interface service modules.

[0056] In an embodiment of the present application, obtaining a target interface service module corresponding to storage configuration information from a plurality of interface service modules includes the following steps A1-A3:

[0057] Step A1, extracting storage attribute information and function classification information from storage configuration information, wherein the storage attribute information includes a target storage vendor identifier and a target storage protocol.

[0058] Specifically, key storage attribute information and functional classification information are extracted from the storage configuration information. The target storage vendor identifier in the storage attribute information specifies the specific storage vendor to which the request is directed, such as storage vendor A. This identifier is crucial for determining the subsequent processing path, as different storage vendors may have different storage system characteristics and interface requirements. The target storage protocol (such as S3) specifies the communication protocol followed by object storage requests. Different storage protocols may differ in function and operation, which determines how requests are processed in the storage system. Functional classification information divides requests into business and management categories, which provides an important basis for subsequent processing flows.

[0059] Step A2: Obtain the analysis strategy corresponding to the target storage vendor identifier.

[0060] Specifically, obtain the analysis strategy corresponding to the target storage vendor ID. Different storage vendors have different processing methods and requirements, so it is necessary to determine the corresponding analysis strategy based on the specific storage vendor ID. This analysis strategy will be used for subsequent analysis of the functional classification information and the target storage protocol to determine the target interface business module.

[0061] Step A3: Analyze the function classification information and the target storage protocol according to the analysis strategy to obtain the target interface service module.

[0062] Specifically, the function classification information and the target storage protocol are analyzed according to the analysis strategy to obtain the target interface business module, including: if the function classification information is a business type, obtaining the protocol matching condition associated with the business type; using the target storage protocol to match the protocol matching condition to obtain the target protocol matching condition hit by the target storage protocol, and using the standard interface business module corresponding to the target protocol matching condition as the target interface business module.

[0063] First, obtain the protocol matching conditions associated with the service type. The protocol matching conditions are pre-set for service class requests and are used to determine the interface service module that matches a specific storage protocol. Then use the target storage protocol to match the protocol matching conditions. If the target storage protocol hits a target protocol matching condition, the standard interface service module corresponding to the target protocol matching condition is used as the target interface service module. For example, Figure 3 As shown, if the target storage protocol is S3, and the service class request meets the matching condition of the S3 protocol, then the "standard interface service module (S3)" is determined as the target interface service module.

[0064] As an example, assume that in the storage configuration information, the storage attribute information includes the target storage vendor identifier as "X storage vendor" and the target storage protocol as "Y protocol". The functional classification information is "Business Type A". The analysis policy corresponding to "X storage vendor" is obtained. Because the functional classification information is the business type, the protocol matching conditions associated with "Business Type A" are obtained. Assume that the protocol matching conditions are: Condition 1 corresponds to standard interface business module 1, and the condition requires that the storage protocol is Z protocol; Condition 2 corresponds to standard interface business module 2, and the condition requires that the storage protocol is Y protocol and W protocol; Condition 3 corresponds to standard interface business module 3, and the condition requires that the storage protocol is T protocol. The target storage protocol "Y protocol" is used to match these protocol matching conditions, and it is found that the target storage protocol hits condition 2. Therefore, the standard interface business module 2 corresponding to condition 2 is used as the target interface business module.

[0065] It should be noted that when the functional classification information is a business type, by obtaining the protocol matching conditions associated with the business type, the appropriate interface business module can be determined in a targeted manner according to different business needs. By matching the target storage protocol with these protocol matching conditions, the target protocol matching conditions hit by the target storage protocol can be accurately found, and then the corresponding standard interface business module can be used as the target interface business module. On the one hand, this can ensure that the interface business module is highly adapted to the specific business type and storage protocol, thereby improving the pertinence and effectiveness of the system; on the other hand, it can achieve flexible selection of interfaces according to different business scenarios and storage protocols, improve the flexibility and scalability of the system, enable the storage system to better meet various complex business needs, and improve the overall performance and efficiency of the storage system.

[0066] Step S103: sending the object storage requirement to the target interface service module.

[0067] In the embodiment of the present application, taking a business class object storage request as an example, when the application needs to create a storage bucket in the object storage of storage vendor A to store pictures uploaded by users. The object storage service distribution platform sends this specific storage requirement to the target interface service module. If the conditions that the storage vendor is A, the business class request and the object storage protocol is S3 are met, the target interface service module is the "standard interface service module (S3)". By sending the object storage requirement, the subsequent processing flow is started, and the request is passed to the module that can actually interact with the storage system.

[0068] Step S104, calling the target interface business module to send the object storage demand to the corresponding storage system, and receiving the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

[0069] In an embodiment of the present application, a target interface business module is called to send the object storage demand to a corresponding storage system, and a processing result fed back by the storage system is received, including: if the target interface business module is a standard interface business module corresponding to the target storage protocol, the standard interface business module is called to send the object storage demand to a first storage system corresponding to the target storage vendor identifier, wherein the first storage system is a storage system associated with the standard interface business module, the first storage system parses the object storage demand to obtain operation tasks and resource requirements, allocates corresponding resources to the operation tasks according to the resource requirements, and performs corresponding object storage processing operations according to the operation tasks to obtain processing results; and receives the processing results fed back by the first storage system through the standard interface business module.

[0070] As an example, when the target interface business module is the "standard interface business module (S3)", it sends the object storage demand to the first storage system corresponding to the target storage vendor identifier (storage vendor A). The first storage system here is built based on Ceph object storage. After receiving the object storage demand, the first storage system will parse it. The parsing process includes extracting operation tasks and resource requirements. For example, for the demand to create a storage bucket with read-only permissions, the operation tasks may include creating a bucket and setting bucket permissions, and the resource requirements may include a certain storage space, etc. The storage system will allocate storage space that meets the demand from its available resources to the operation task of creating a storage bucket. Then, the corresponding object storage processing operation is performed according to the operation task. For the demand to create a read-only storage bucket, first call the API for creating a bucket to create the bucket, and then call the API for setting the bucket permission to read-only to set the permission. By performing these operations, the first storage system obtains the processing result. The processing result may include information such as whether the storage bucket is successfully created and whether the permissions are correctly set. Then, the first storage system feeds back the processing result to the "standard interface business module (S3)". This feedback is performed according to the original route to ensure the accurate transmission of information. The "standard interface service module (S3)" receives the processing result fed back by the first storage system, and prepares to return it to the object storage service distribution platform.

[0071] This application first receives the object storage request sent by the cloud platform and obtains the storage configuration information and object storage requirements from it, thus avoiding the dependence on Swift-related components and services, and reducing the resource consumption and maintenance scope of the cloud platform. Secondly, the method of obtaining the target interface business module from multiple interface business modules is more flexible, and customized selection can be made according to different storage configuration information and object storage requirements. It gets rid of the restrictions on the maintenance of SwiftAPI that depends on the open source community and storage manufacturers, and can better meet customized needs. Furthermore, directly calling the target interface business module to send the object storage requirements to the corresponding storage system reduces the intermediate links of API requests passing through the Swift component and then being sent to the storage platform, thereby reducing resource consumption, shortening response time, and reducing the difficulty of system maintenance.

[0072] Figure 4 is a flow chart of a method for processing an object storage service according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0073] Step S201: Receive an object storage request sent by a cloud platform, wherein the object storage request includes storage configuration information and object storage requirements. For details, please refer to step S101 in the above embodiment, which will not be described again.

[0074] Step S202: Acquire multiple interface service modules associated with the object storage service distribution terminal, and acquire a target interface service module corresponding to the storage configuration information from the multiple interface service modules.

[0075] In an embodiment of the present application, obtaining a target interface service module corresponding to storage configuration information from a plurality of interface service modules includes the following steps B1-B3:

[0076] Step B1, extracting storage attribute information and function classification information from storage configuration information, wherein the storage attribute information includes a target storage vendor identifier and a target storage protocol.

[0077] Specifically, when the cloud platform administrator initiates an object storage request through the management interface, the request contains rich information. In this step, key storage attribute information and function classification information are extracted from the storage configuration information. Among them, the target storage vendor identifier specifies the specific storage vendor to which the request is directed. In this scenario, it is assumed that the storage vendor is determined to be B. Different storage vendors may have differences in storage system architecture, management methods, and provided functions, so this identifier is crucial for accurately processing requests. Function classification information indicates that the request is a management request. Management requests are different from business requests. They mainly involve management operations on the storage system, such as obtaining usage statistics of the storage system, configuring storage policies, managing user permissions, etc.

[0078] Step B2: Obtain the analysis strategy corresponding to the target storage vendor identifier.

[0079] Specifically, different storage vendors have different processing methods and requirements, so it is necessary to determine the corresponding analysis strategy based on the specific storage vendor identification. This analysis strategy will be used for subsequent analysis of functional classification information and target storage protocols to determine the appropriate interface business module to process management requests.

[0080] Step B3: Analyze the function classification information and the target storage protocol according to the analysis strategy to obtain the target interface service module.

[0081] Specifically, the function classification information and the target storage protocol are analyzed according to the analysis strategy to obtain the target interface business module, including: if the function classification information is a management type, the management interface business module corresponding to the target storage vendor identifier is used as the target interface business module.

[0082] If the function classification information is management type, the management interface business module corresponding to the target storage vendor identifier is directly used as the target interface business module. Figure 5As shown, when the storage vendor is determined to be B and the request is of management type (such as obtaining usage statistics of the storage system), the "management interface business module (storage vendor B)" becomes the target interface business module.

[0083] Because management requests usually involve management operations on the storage system, they need to interact with the management system of a specific storage vendor. Each storage vendor's management system may have different interfaces and implementation methods, so a dedicated management interface business module is required to handle these requests. The management interface business module can call the management layer API provided by the storage vendor to the south to implement specific management requirements, such as obtaining usage statistics. In this process, it is necessary to interact with the management system of storage vendor B to obtain relevant data and organize and format it, and then provide an API call interface for the "object storage business distribution platform" to return the processing results to the distribution platform. Finally, the distribution platform returns the response to the management interface of the cloud platform for the administrator to view.

[0084] Suppose there is a storage system, and the storage attribute information and function classification information are extracted from its storage configuration information. In the storage attribute information, the target storage vendor is identified as "ABC storage vendor" and the target storage protocol is "XYZ storage protocol". The function classification information is "management type". Since the function classification information is "management type", according to the rules, the management interface business module corresponding to "ABC storage vendor" is determined as the target interface business module. Suppose "ABC storage vendor" provides a special management interface business module M for the storage system, then in this case, the target interface business module is M. This module M includes various functions for managing the storage system, such as storage capacity monitoring, storage device status query, storage policy configuration and other functions to meet the needs of managing the storage system.

[0085] It should be noted that when the function classification information is of management type, directly using the management interface business module corresponding to the target storage vendor identifier as the target interface business module can achieve a high degree of pertinence and professionalism. Different storage vendors often have their own unique storage architecture and management requirements. This method can ensure that the management interface business module is closely integrated with the storage system of a specific vendor, making full use of the specific management functions and features provided by the vendor. This can improve the efficiency and accuracy of management, making the management of the storage system more convenient and efficient. At the same time, this design also has good maintainability and scalability. When the storage system involves equipment from different vendors, the corresponding management interface can be quickly determined based on the vendor identifier, which facilitates system upgrades and maintenance, and also provides a convenient access method for possible storage system expansion in the future.

[0086] Step S203: Send the object storage requirement to the target interface service module. For details, please refer to step S103 in the above embodiment, which will not be described again.

[0087] Step S204, calling the target interface business module to send the object storage demand to the corresponding storage system, and receiving the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

[0088] In the embodiment of the present application, calling the target interface business module to send the object storage demand to the corresponding storage system and receiving the processing result fed back by the storage system includes the following steps C1-C3:

[0089] Step C1, if the target interface business module is the management interface business module corresponding to the target storage vendor identifier, then call the management interface business module to parse the object storage requirements to obtain the target management function, and obtain the management layer interface corresponding to the target management function from the second storage system corresponding to the target storage vendor identifier, wherein the second storage system is the storage system associated with the management interface business module.

[0090] Specifically, when the target interface business module is determined to be the management interface business module corresponding to the target storage vendor identifier, such as the management interface business module of storage vendor B. First, the management interface business module is called to parse the object storage demand. In this scenario, the object storage demand is to obtain usage statistics of the storage system. After parsing this demand, the management interface business module determines that the target management function is to obtain usage statistics.

[0091] Next, the management layer interface corresponding to the target management function is obtained from the second storage system corresponding to the target storage manufacturer identifier (storage manufacturer B). Different storage manufacturers may have different management layer interface systems, and the management interface business module needs to accurately find the interface corresponding to the target management function (obtaining usage statistics) for subsequent calls.

[0092] Step C2, calling the management interface business module to send a call request to the management layer interface of the second storage system, wherein the management layer interface is used to obtain target data matching the target management function from the second storage system and feed the target data back to the management interface business module.

[0093] Specifically, the management interface service module is called to send a call request to the management layer interface of the second storage system. The purpose of this request is to obtain target data that matches the target management function from the second storage system. After receiving the request, the management layer interface will perform corresponding operations in the second storage system, that is, the management layer interface will extract relevant data from the storage system, such as storage capacity usage, data access frequency and other information. Then, the target data is fed back to the management interface service module.

[0094] Step C3, calling the management interface service module to encapsulate the target data to obtain the encapsulated target data.

[0095] Specifically, after the management interface business module receives the target data, it needs to encapsulate it. The purpose of encapsulation is to organize the data obtained from the second storage system into a unified format so that it can be smoothly fed back to the object storage business distribution platform. The encapsulated target data may include operations such as organization and format conversion of the original data to make it more in line with the display requirements of the cloud platform management interface or to facilitate subsequent data processing. Finally, the management interface business module prepares to return the encapsulated target data to the object storage business distribution platform along the original route, and the distribution platform then returns the response to the cloud platform's management interface for the administrator to view.

[0096] The embodiment of the present application firstly receives the object storage request sent by the cloud platform and obtains the storage configuration information and object storage requirements therefrom, thereby avoiding the dependence on Swift-related components and services, and reducing the resource consumption and maintenance scope of the cloud platform. Because it is no longer simply dependent on the Swift component, but selects the target interface business module from multiple interface business modules according to specific needs, there is no need to install, enable and configure specific Swift-related content. Secondly, the method of obtaining the target interface business module from multiple interface business modules is more flexible, and customized selection can be made according to different storage configuration information and object storage requirements, rather than being restricted by the Swift API. In this way, it gets rid of the limitation that the maintenance of the Swift API depends on the open source community and storage manufacturers, and can better meet customized needs. Furthermore, the target interface business module is directly called to send the object storage requirements to the corresponding storage system, reducing the intermediate link of the API request passing through the Swift component and then being sent to the storage platform, thereby reducing resource consumption, shortening the response time, and reducing the difficulty of system maintenance.

[0097] Finally, for open source distributed object storage systems such as Ceph, this solution can flexibly select the target interface business module and potentially find a more appropriate way to connect to the storage platform management layer, rather than having no feasible solution like the Swift API.

[0098] In the embodiments of the present application, Figure 6 As shown, the method also includes:

[0099] Step S301: Obtain a module configuration request, wherein the module configuration request includes a storage manufacturer identifier and module configuration information.

[0100] In an embodiment of the present application, the object storage service distribution terminal receives a module configuration request through an interactive interface with the cloud platform. This interface can be a specific API endpoint or a communication channel such as a message queue. When the cloud platform needs to configure a management interface business module for a specific storage vendor, it will send a request containing the storage vendor identifier and module configuration information to this interface. The storage vendor identifier can be a unique code or name used to identify a specific storage vendor, such as "storage vendor B". The module configuration information can be transmitted in a structured data format (such as JSON or XML), which includes various configuration parameters and requirement descriptions, such as specific management functions that need to be called, data format requirements, permission settings, etc.

[0101] Step S302: construct an original management interface service module in the object storage service distribution terminal according to the storage manufacturer identifier.

[0102] In an embodiment of the present application, the object storage service distribution terminal determines the type of management interface service module to be constructed based on the received storage vendor identifier. A module construction framework can be designed in advance, and when a specific storage vendor identifier is identified, an initial management interface service module is created based on this framework. For example, if the storage vendor identifier is "storage vendor B", the terminal can select a template suitable for storage vendor B from the existing module template library, and create an original management interface service module based on this. This module may contain some basic structures and functions, but has not yet been customized according to specific configuration information.

[0103] Step S303: Use the module configuration information to adjust parameters and set functions of the original management interface service module to obtain the management interface service module corresponding to the storage manufacturer identifier.

[0104] In an embodiment of the present application, first, the module configuration information is parsed to extract specific parameters and functional requirements. For example, if the configuration information specifies that a specific type of storage system usage statistics need to be obtained, then the specific management function that needs to be called is determined. Then, the original management interface business module is adjusted according to these requirements. For parameter adjustment, the corresponding variable value in the module can be modified directly. For example, if the configuration information specifies the format requirements for data return, the data processing part in the module is adjusted so that it can output data in the specified format. For function settings, specific functions can be implemented by adding or modifying functions or methods in the module. For example, if additional calculations or analysis of the acquired data is required, the corresponding calculation functions are added to the module.

[0105] Step S304: construct a connection relationship between the management interface business module and each management layer interface in the storage system corresponding to the storage vendor identifier, and store the connection relationship in the management interface business module corresponding to the storage vendor identifier.

[0106] First, determine the management layer interface information of the storage system corresponding to the storage vendor identifier. This can be obtained by consulting the documents provided by the storage vendor or by interacting with the storage system. For example, storage vendor B may provide a set of specific APIs for management operations. The addresses and authentication methods of these APIs are the management layer interface information. Then, establish connections with these management layer interfaces in the management interface business module. You can use appropriate communication protocols and libraries to implement the connection, such as using the HTTP protocol to interact with the RESTful API. In the process of establishing the connection, authentication and authorization operations may be required to ensure that the management interface business module has the authority to access the management layer interface of the storage system. Finally, store the established connection relationship in the management interface business module so that the storage system can be quickly accessed in subsequent operations. Data structures (such as dictionaries, lists, etc.) can be used to store connection information, such as the address of the storage API, authentication tokens, etc. In this way, when it is necessary to call the management function of the storage system, the management interface business module can directly use these connection information for communication.

[0107] In this embodiment, a processing device for object storage service is also provided, which is used to implement the above embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0108] This embodiment provides a device for processing object storage services, such as Figure 7 As shown, including:

[0109] The receiving module 701 is used to receive an object storage request sent by the cloud platform, wherein the object storage request includes storage configuration information and object storage requirements;

[0110] An acquisition module 702 is used to acquire multiple interface service modules associated with the object storage service distribution terminal, and acquire a target interface service module that matches the storage configuration information from the multiple interface service modules;

[0111] The sending module 703 is used to send the object storage requirement to the target interface business module;

[0112] The calling module 704 is used to call the target interface business module to send the object storage demand to the corresponding storage system, and receive the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

[0113] In an embodiment of the present application, the acquisition module 702 is used to extract storage attribute information and functional classification information from the storage configuration information, wherein the storage attribute information includes the target storage vendor identifier and the target storage protocol; obtain the analysis strategy corresponding to the target storage vendor identifier; analyze the functional classification information and the target storage protocol according to the analysis strategy to obtain the target interface business module.

[0114] In an embodiment of the present application, the acquisition module 702 is used to obtain the protocol matching conditions associated with the business type if the functional classification information is a business type; use the target storage protocol to match the protocol matching conditions to obtain the target protocol matching conditions that hit the target storage protocol, and use the standard interface business module corresponding to the target protocol matching conditions as the target interface business module.

[0115] In the embodiment of the present application, the acquisition module 702 is used to use the management interface business module corresponding to the target storage vendor identifier as the target interface business module if the function classification information is a management type.

[0116] In an embodiment of the present application, the calling module 704 is used to call the standard interface business module to send the object storage demand to the first storage system corresponding to the target storage vendor identifier if the target interface business module is a standard interface business module corresponding to the target storage protocol, wherein the first storage system parses the object storage demand to obtain the operation task and resource demand, allocates the corresponding resources to the operation task according to the resource demand, and performs the corresponding object storage processing operation according to the operation task to obtain the processing result; and receives the processing result fed back by the first storage system through the standard interface business module.

[0117] In an embodiment of the present application, the calling module 704 is used to call the management interface business module to parse the object storage requirements to obtain the target management function if the target interface business module is the management interface business module corresponding to the target storage vendor identifier, and obtain the management layer interface corresponding to the target management function from the second storage system corresponding to the target storage vendor identifier; call the management interface business module to send a call request to the management layer interface of the second storage system, wherein the management layer interface is used to obtain target data matching the target management function from the second storage system, and feed the target data back to the management interface business module; call the management interface business module to encapsulate the target data to obtain the encapsulated target data.

[0118] In an embodiment of the present application, the device also includes: a configuration module, which is used to obtain a module configuration request, wherein the module configuration request includes a storage vendor identifier and module configuration information; construct an original management interface business module in an object storage service distribution terminal according to the storage vendor identifier; use the module configuration information to adjust parameters and set functions of the original management interface business module to obtain a management interface business module corresponding to the storage vendor identifier; construct a connection relationship between the management interface business module and each management layer interface in the storage system corresponding to the storage vendor identifier, and store the connection relationship in the management interface business module corresponding to the storage vendor identifier.

[0119] See also Figure 8 , Figure 8 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 8 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 8 A processor 10 is taken as an example.

[0120] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0121] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0122] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the use of a computer device based on the presentation of a small program landing page, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0123] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0124] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0125] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0126] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for processing an object storage service, characterized in that: The method is applied to an object storage service distribution terminal, the object storage service distribution terminal is connected to a cloud platform, and the method includes: Receiving an object storage request sent by the cloud platform, wherein the object storage request includes storage configuration information and object storage requirements; Acquire multiple interface service modules associated with the object storage service distribution terminal, and acquire a target interface service module corresponding to the storage configuration information from the multiple interface service modules; Sending the object storage requirement to the target interface service module; The target interface business module is called to send the object storage demand to the corresponding storage system, and receive the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

2. The method according to claim 1, characterized in that The acquiring a target interface service module corresponding to the storage configuration information from a plurality of interface service modules comprises: Extracting storage attribute information and function classification information from the storage configuration information, wherein the storage attribute information includes a target storage vendor identifier and a target storage protocol; Obtaining an analysis strategy corresponding to the target storage vendor identifier; The function classification information and the target storage protocol are analyzed according to the analysis strategy to obtain the target interface service module.

3. The method according to claim 2, characterized in that The step of analyzing the function classification information and the target storage protocol according to the analysis strategy to obtain the target interface service module includes: If the function classification information is a business type, obtaining a protocol matching condition associated with the business type; The target storage protocol is matched with the protocol matching condition to obtain the target protocol matching condition hit by the target storage protocol, and the standard interface business module corresponding to the target protocol matching condition is used as the target interface business module.

4. The method according to claim 2, characterized in that: The step of analyzing the function classification information and the target storage protocol according to the analysis strategy to obtain the target interface service module includes: If the function classification information is a management type, the management interface service module corresponding to the target storage vendor identifier is used as the target interface service module.

5. The method according to claim 2, characterized in that: The calling of the target interface business module to send the object storage demand to the corresponding storage system and receiving the processing result fed back by the storage system includes: If the target interface business module is a standard interface business module corresponding to the target storage protocol, the standard interface business module is called to send the object storage demand to the first storage system corresponding to the target storage vendor identifier, wherein the first storage system is a storage system associated with the standard interface business module, the first storage system parses the object storage demand to obtain an operation task and a resource demand, allocates corresponding resources to the operation task according to the resource demand, and performs corresponding object storage processing operations according to the operation task to obtain a processing result; The processing result fed back by the first storage system is received through the standard interface service module.

6. The method according to claim 2, characterized in that The calling of the target interface business module to send the object storage demand to the corresponding storage system and receiving the processing result fed back by the storage system includes: If the target interface business module is a management interface business module corresponding to the target storage vendor identifier, the management interface business module is called to parse the object storage requirement to obtain the target management function, and a management layer interface corresponding to the target management function is obtained from a second storage system corresponding to the target storage vendor identifier, wherein the second storage system is a storage system associated with the management interface business module; Calling the management interface business module to send a call request to the management layer interface of the second storage system, wherein the management layer interface is used to obtain target data matching the target management function from the second storage system and feed the target data back to the management interface business module; The management interface service module is called to encapsulate the target data to obtain the encapsulated target data.

7. The method according to claim 1, characterized in that The method further comprises: Obtaining a module configuration request, wherein the module configuration request includes a storage manufacturer identifier and module configuration information; Constructing an original management interface service module in the object storage service distribution terminal according to the storage vendor identifier; Using the module configuration information, adjusting parameters and setting functions of the original management interface service module to obtain a management interface service module corresponding to the storage vendor identifier; A connection relationship between the management interface business module and each management layer interface in the storage system corresponding to the storage vendor identifier is established, and the connection relationship is stored in the management interface business module corresponding to the storage vendor identifier.

8. A device for processing object storage services, characterized in that: The device comprises: A receiving module, configured to receive an object storage request sent by a cloud platform, wherein the object storage request includes storage configuration information and object storage requirements; An acquisition module, used to acquire multiple interface business modules associated with the object storage business distribution terminal, and acquire a target interface business module matching the storage configuration information from the multiple interface business modules; A sending module, used for sending the object storage requirement to the target interface service module; A calling module is used to call the target interface business module to send the object storage demand to the corresponding storage system, and receive the processing result fed back by the storage system, wherein the processing result is obtained by the storage system performing the corresponding object storage processing operation according to the object storage demand.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 7.

Images