CN110392015B - Method and system for processing service request - Google Patents
Method and system for processing service request Download PDFInfo
- Publication number
- CN110392015B CN110392015B CN201810344659.7A CN201810344659A CN110392015B CN 110392015 B CN110392015 B CN 110392015B CN 201810344659 A CN201810344659 A CN 201810344659A CN 110392015 B CN110392015 B CN 110392015B
- Authority
- CN
- China
- Prior art keywords
- target
- rados
- rads
- identifier
- management server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Abstract
The invention discloses a method and a system for processing a service request, and belongs to the technical field of data storage. The method comprises the following steps: when a service request of a target user is received, a management server determines a target RADS identifier and a target RADS key according to an account identifier of the target user, wherein the target RADS key is generated by the management server based on the target RADS identifier in advance; the management server preprocesses the service request according to the target RADOS key; the management server sends a preprocessed service request to a target RADS pointed by the target RADS GW through a target RADS GW corresponding to the pre-configured target RADS identifier; and the target RADS GW acquires a RADS key corresponding to the target RADS to verify the preprocessed service request, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back. By adopting the method and the device, the service quality of the file storage service of the RADOS cluster can be ensured.
Description
Technical Field
The present invention relates to the field of data storage technologies, and in particular, to a method and a system for processing a service request.
Background
The CEPH cluster is a Distributed file system under a Linux operating system, and a RADOS (Reliable autonomous Distributed Object Store) cluster is a core part of the CEPH cluster, and may form a Distributed storage system providing a file storage service based on a plurality of RADOS.
The CEPH cluster may provide a file storage service for a cloud service provider through the RADOS GW, each RADOS GW corresponds to one RADOS, each RADOS corresponds to a plurality of RADOS GWs, and after all service requests of a user reach a management server of the cloud service provider, the management server may transmit the service requests to the corresponding RADOS through the RADOS GW. After receiving the service request sent by the user, the management server may first convert the protocol format of the service request from Amazon S3 protocol or Swift protocol to a protocol recognizable by the RADOS through the RADOS GW, and then send the service request to the RADOS, so that the RADOS executes the service request.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
when there is an error in the configuration of the RADOS GW among the RADOS as shown in fig. 1 (RADOS2-RADOS GW1 should be configured to the RADOS2, but actually configured to the RADOS1), because the RADOS2-RADOS GW1 and the RADOS2-RADOS GW2 belong to the same RADOS, once the file is uploaded to the RADOS1 through the RADOS2-RADOS GW1, if the file is downloaded through the RADOS2-RADOS GW2, the file cannot be found in the RADOS2, so that the service quality of the file storage service of the RADOS cluster will be greatly affected.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide a method and a system for processing a service request. The technical scheme is as follows:
in a first aspect, a method for processing a service request is provided, where the method includes:
when a service request of a target user is received, a management server determines a target RADS identifier and a target RADS key according to an account identifier of the target user, wherein the target RADS key is generated by the management server based on the target RADS identifier in advance;
the management server preprocesses the service request according to the target RADOS key;
the management server sends a preprocessed service request to a target RADS pointed by the target RADS GW through a target RADS GW corresponding to the pre-configured target RADS identifier;
and the target RADS GW acquires a RADS key corresponding to the target RADS to verify the preprocessed service request, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back.
Optionally, the method further includes:
when a registration request of a target user is received, the management server determines at least one RADOS and creates a basic authentication key corresponding to the target user;
for each RADOS in the at least one RADOS, the management server creates a RADOS key corresponding to the RADOS according to the RADOS identification of the RADOS and the basic authentication key;
and the management server correspondingly stores the RADOS key, the RADOS identifier of the RADOS and the account identifier of the target user, and sends the RADOS key to the RADOS for storage.
Optionally, after the target RADOS feeds back the error information, the method further includes:
and the management server reconfigures the target RADS GW so that the target RADS GW points to RADS corresponding to the target RADS identifier.
Optionally, when receiving a service request of a target user, the determining, by the management server, a target RADOS identifier and a target RADOS key according to the account identifier of the target user includes:
when a file uploading request of a target user is received, the management server determines at least one RADOS identifier corresponding to the locally stored account identifier of the target user;
the management server acquires a weight of the RADS corresponding to the at least one RADS identifier, wherein the weight is generated by calculation based on the residual storage space of the RADS;
and the management server determines that the RADOS identifier of the RADOS with the maximum weight value is a target RADOS identifier, and determines that the RADOS key corresponding to the target RADOS identifier is a target RADOS key.
Optionally, when receiving a service request of a target user, the determining, by the management server, a target RADOS identifier and a target RADOS key according to the account identifier of the target user includes:
when a file downloading request of a target file sent by a target user is received, the management server reads metadata information of the target file in a locally maintained file storage list according to an account identifier of the target user and a file identifier of the target file;
the management server determines a target RADOS according to RADOS information contained in the metadata information of the target file;
and the management server determines the RADOS identifier of the target RADOS as a target RADOS identifier, and determines the RADOS key of the target RADOS as a target RADOS key.
In a second aspect, a system for processing service requests is provided, the system comprising a management server and a plurality of RADOS, wherein:
the management server is used for determining a target RADS identifier and a target RADS key according to an account identifier of a target user when receiving a service request of the target user, wherein the target RADS key is generated by the management server based on the target RADS identifier in advance, preprocessing the service request according to the target RADS key, and sending the preprocessed service request to a target RADS pointed by a target RADS GW through a target RADS GW corresponding to the preset target RADS identifier;
and the target RADS GW is used for acquiring the RADS key of the target RADS to verify the preprocessed service request, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back.
Optionally, the management server is further configured to:
when a registration request of a target user is received, determining at least one RADOS, and creating a basic authentication key corresponding to the target user;
for each RADOS in the at least one RADOS, according to the RADOS identification of the RADOS and the basic authentication key, creating a RADOS key corresponding to the RADOS;
correspondingly storing the RADOS key, the RADOS identifier of the RADOS and the account identifier of the target user, and sending the RADOS key to the RADOS for storage.
Optionally, the management server is further configured to:
after the target RADS feeds back the error information, reconfiguring the target RADS GW so that the target RADS GW points to RADS corresponding to the target RADS identifier.
Optionally, the management server is specifically configured to:
when a file uploading request of a target user is received, determining at least one RADOS identifier corresponding to an account identifier of the target user, which is locally stored;
acquiring a weight of the RADOS corresponding to the at least one RADOS identifier, wherein the weight is generated by calculation based on the residual storage space of the RADOS;
and determining the RADOS identifier of the RADOS with the maximum weight as a target RADOS identifier, and determining the RADOS key corresponding to the target RADOS identifier as a target RADOS key.
Optionally, the management server is specifically configured to:
when a file downloading request of a target file sent by a target user is received, reading metadata information of the target file in a locally maintained file storage list according to an account identifier of the target user and a file identifier of the target file;
determining a target RADOS according to RADOS information contained in the metadata information of the target file;
and determining the RADOS identifier of the target RADOS as a target RADOS identifier, and determining the RADOS key of the target RADOS as a target RADOS key.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
in the embodiment of the invention, when a service request of a target user is received, a management server determines a target RADS identifier and a target RADS secret key according to an account identifier of the target user, wherein the target RADS secret key is generated by the management server based on the target RADS identifier in advance, the management server preprocesses the service request according to the target RADS secret key, the management server sends the preprocessed service request to a target RADS pointed by a target RADS GW through a target RADS GW corresponding to the preset target RADS identifier, the target RADS GW acquires the preprocessed service request verified by the RADS secret key corresponding to the target RADS, if the verification is successful, the service request is sent to the target RADS, and if the verification is not successful, error information is fed back. Therefore, different RADS correspond to different RADS keys, when the management server interacts with the designated RADS through the RADS GW, the RADS key of the RADS is used, and if the RADS GW configuration is wrong, the RADS GW cannot successfully verify the RADS key of the corresponding RADS, so that the RADS GW configuration error can be found in time, the problem that the file cannot be found after being uploaded due to the RADS GW configuration error can be effectively avoided, and the service quality of the file storage service of the RADS cluster can be guaranteed to a certain extent.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of an error configuration of a RADOS GW according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a network framework for processing a service request according to an embodiment of the present invention;
fig. 3 is a flowchart of a method for processing a service request according to an embodiment of the present invention;
fig. 4 is a flowchart of a method for creating a RADOS key according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The embodiment of the invention provides a method for processing a service request, which can be realized by a management server and a CEPH cluster together, wherein the management server can be a background server of a cloud service provider, the CEPH cluster can be a back-end service cluster of the cloud service provider, and a user can access the management server through a cloud service client, so that the service provided by the CEPH cluster, such as file storage service, is used. The CEPH cluster may include a RADOS cluster, the RADOS cluster may be formed by a large number of RADOS, each RADOS may independently provide a file storage service for one or more users, and a plurality of RADOS may also serve one user at the same time, specifically, a plurality of RADOS may form one RADOS group, each RADOS group serves one user, when the capacity of one RADOS group is full, a new RADOS may be added in the RADOS group, and a specific network framework may refer to fig. 2. The management server and the RADOS may each include a processor, a memory, and a transceiver, the processor may be configured to perform processing of the service request in the following process, the memory may be configured to store data required and generated in the following process, and the transceiver may be configured to receive and transmit related data in the following process.
The process flow shown in fig. 3 will be described in detail below with reference to specific embodiments, and the contents may be as follows:
And generating a target RADOS key by the management server in advance based on the target RADOS identification.
In implementation, after a user purchases a file storage service at a cloud service provider side, a cloud service client installed on a terminal may send a corresponding service request, such as a file upload request, a file download request, and the like, to a background server (i.e., a management server) of the cloud service provider, so that the management server may receive the service request sent by the user and execute the corresponding service request based on the RADOS at the back end. Specifically, taking the target user as an example, when receiving a service request of the target user, the management server may read an account identifier of the target user carried in the service request, and then may determine, according to the account identifier, a RADOS identifier (i.e., a target RADOS identifier) of the RADOS for executing the service request, and a target RADOS key generated by the management server in advance based on the target RADOS identifier.
Optionally, the file storage service provided by the management server mainly includes a file upload service and a file download service, and based on the two services, the specific processing in step 301 may be as follows:
first, a file upload service:
when a file uploading request of a target user is received, the management server determines at least one RADOS identifier corresponding to the locally stored account identifier of the target user; the management server acquires the weight of the RADS corresponding to at least one RADS identifier; and the management server determines the RADOS identifier of the RADOS with the maximum weight as a target RADOS identifier, and determines the RADOS key corresponding to the target RADOS identifier as a target RADOS key.
Wherein, the weight value is generated based on the residual storage space calculation of the RADOS.
In implementation, also taking the target user as an example, when receiving a file upload request of the target user, the management server may first obtain an account identifier of the target user based on the file upload request, and then search for at least one RADOS identifier corresponding to the account identifier of the target user from all the locally stored RADOS identifiers. Then, the management server may obtain the weight values of the RADOS corresponding to the RADOS identifiers, specifically, the management server may periodically detect the remaining storage space of each RADOS, and then calculate and generate the weight value of each RADOS based on the remaining storage space, where the larger the weight value, the more the remaining storage space of the RADOS is. Furthermore, the management server may determine, as the target RADOS identifier, the RADOS identifier of the RADOS with the largest weight in the RADOS, and determine, as the target RADOS key, the RADOS key corresponding to the target RADOS identifier. Of course, in one case, the management server may also detect, in real time, the weight values of the RADOS corresponding to the RADOS identifiers after determining at least one RADOS identifier corresponding to the account identifier of the target user.
Secondly, file downloading service:
when a file downloading request of a target file sent by a target user is received, the management server reads metadata information of the target file in a locally maintained file storage list according to an account identifier of the target user and a file identifier of the target file; the management server determines a target RADOS according to RADOS information contained in the metadata information of the target file; the management server determines the RADOS identifier of the target RADOS as the target RADOS identifier, and determines the RADOS key of the target RADOS as the target RADOS key.
The file storage list records metadata information of all files stored in the RADOS cluster.
In implementation, a file storage list of the RADOS cluster may be maintained in the management server, metadata information of all files stored in the RADOS cluster is recorded in the file storage list, and the management server may add the metadata information of the relevant file in the file storage list after sending a file upload request to one RADOS each time. Thus, when a file downloading request of a target file sent by a target user is received, the management server may first obtain an account identifier of the target user and a file identifier of the target file, which are carried in the file downloading request, then may determine the target file in a locally maintained file storage list according to the account identifier and the file identifier, and read metadata information of the target file. Next, the management server may determine, according to the RADOS information included in the metadata information of the object file, a RADOS in which the object file is located (i.e., the object RADOS), so that the management server may determine the RADOS identifier of the object RADOS as the object RADOS identifier and determine the RADOS key of the object RADOS as the object RADOS key.
In an implementation, after determining the target RADOS key, the management server may pre-process the service request according to the target RADOS key. Here, the preprocessing method may be set by a technician on the cloud service side, for example, the target RADOS key may be directly added to the service request, or the service request may be encrypted by using the target RADOS key.
In implementation, the management server may deploy, in the background, a RADOS GW for each RADOS in advance, where each RADOS GW points to a unique one RADOS, each RADOS may have multiple RADOS GWs, the management server may forward the received service request of the user to the RADOS through the RADOS GW, and meanwhile, the management server may record and store the deployment condition of the RADOS GW in a manner that the RADOS identifier corresponds to the RADOS GW. In this way, after the service request is preprocessed, the management server may determine, according to the deployment condition of the locally stored RADOS GW, a target RADOS GW corresponding to the pre-configured target RADOS identifier. Further, the management server may send the preprocessed service request to the target RADOS pointed by the target RADOS GW based on the target RADOS GW. It should be noted that the RADOS GW may be understood as a data channel for interaction between the RADOS and the outside, and the RADOS GW may be configured on any feasible device.
And step 304, the target RADS GW acquires the service request after RADS key verification preprocessing corresponding to the target RADS, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back.
In an implementation, RADOS keys may also be stored in advance in the RADOS, and the RADOS keys stored in different RADOS may be different, and each RADOS may store at least one RADOS key, and each RADOS key may be used for the authentication process of the service request of only one user. In this way, after receiving the preprocessed service request sent by the management server, the target RADOS GW may perform verification processing on the preprocessed service request based on obtaining the RADOS key corresponding to the target RADOS, and a specific verification manner may be set by a technician on the management server side based on the preprocessing manner in step 302, for example: if the preprocessing is to directly add the target RADOS key in the service request, the verification mode can be to detect whether the pre-stored RADOS key contains the target RADOS key; if the preprocessing is to encrypt the service request by using the target RADOS key, the verification method may be to determine whether the service request can be successfully decrypted by using the pre-stored RADOS key. If the authentication is successful, the target RADOS GW may transmit a service request to the target RADOS so that the target RADOS executes the corresponding service request, and if the authentication is not successful, the target RADOS GW may feed back error information to the management server.
Optionally, the management server may adjust the configuration of the RADOS GW in time based on the error information fed back by the RADOS GW, and accordingly, after step 304, the following processing may exist: and the management server reconfigures the target RADS GW so that the target RADS GW points to RADS corresponding to the target RADS identifier.
In implementation, after the management server sends the preprocessed service request to the target RADOS through the target RADOS GW, if error information fed back by the target RADOS GW is received, the target RADOS GW may configure an error and point to the wrong RADOS. Furthermore, the management server may reconfigure the target RADOS GW, so that the target RADOS GW points to the RADOS corresponding to the target RADOS identifier. Further, after receiving the error information fed back by the target RADOS, the management server may selectively feed back internal error information or countdown information and the like to the user according to the time required for reconfiguring the RADOS GW.
In the embodiment of the invention, when a service request of a target user is received, a management server determines a target RADS identifier and a target RADS secret key according to an account identifier of the target user, wherein the target RADS secret key is generated by the management server based on the target RADS identifier in advance, the management server preprocesses the service request according to the target RADS secret key, the management server sends the preprocessed service request to a target RADS pointed by a target RADS GW through a target RADS GW corresponding to the preset target RADS identifier, the target RADS GW acquires the preprocessed service request verified by the RADS secret key corresponding to the target RADS, if the verification is successful, the service request is sent to the target RADS, and if the verification is not successful, error information is fed back. Therefore, different RADS correspond to different RADS keys, when the management server interacts with the designated RADS through the RADS GW, the RADS key of the RADS is used, and if the RADS GW configuration is wrong, the RADS GW cannot successfully verify the RADS key of the corresponding RADS, so that the RADS GW configuration error can be found in time, the problem that the file cannot be found after being uploaded due to the RADS GW configuration error can be effectively avoided, and the service quality of the file storage service of the RADS cluster can be guaranteed to a certain extent.
The embodiment also discloses a method for creating a RADOS key, which specifically includes, as shown in fig. 4, the following contents:
In implementation, when a user wants to obtain a file storage service provided by a cloud service provider, the user may send a registration request to a background server (i.e., a management server) of the cloud service provider through a cloud service client installed on a terminal, so that the management server may receive the request sent by the user, and then provide the file storage service for the user based on RADOS of the backend. Taking the target user as an example, when receiving the registration request of the target user, the management server may allocate RADOS to the target user, that is, determine at least one RADOS, and simultaneously create a basic authentication key corresponding to the target user. Here, on the one hand, when allocating RADOS, the management server may determine the allocated RADOS according to the traffic size of the user and the remaining storage amount of each RADOS; on the other hand, each basic authentication key created by the management server uniquely corresponds to one user, the basic authentication keys corresponding to different users are different, and the basic authentication keys can be randomly generated or generated by combining account identifications of the users.
In implementation, after the management server determines at least one RADOS for the target user, for each RADOS, the management server may determine an RADOS identifier of the RADOS, and then create a RADOS key corresponding to the RADOS according to the RADOS identifier and the basic authentication key. It can be understood that, because the RADOS key is generated based on the basic authentication key and the RADOS identifier, and each basic authentication key uniquely corresponds to one user, the corresponding RADOS keys of the same user in different RADOS are different from each other, and the corresponding RADOS keys of different users in the same RADOS are also different from each other.
In an implementation, after the management server creates a corresponding RADOS key for each RADOS determined in step 401, the management server may store the RADOS key, the RADOS identifier of the RADOS, and the account identifier of the target user locally, and at the same time, the management server may further transmit the RADOS key to the corresponding RADOS, so that the RADOS stores the RADOS key.
Based on the same technical concept, an embodiment of the present invention further provides a system for processing a service request, where the system includes a management server and a plurality of RADOS, where:
the management server is used for determining a target RADS identifier and a target RADS key according to an account identifier of a target user when receiving a service request of the target user, wherein the target RADS key is generated by the management server based on the target RADS identifier in advance, preprocessing the service request according to the target RADS key, and sending the preprocessed service request to a target RADS pointed by a target RADS GW through a target RADS GW corresponding to the preset target RADS identifier;
and the target RADS GW is used for acquiring the RADS key of the target RADS to verify the preprocessed service request, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back.
Optionally, the management server is further configured to:
when a registration request of a target user is received, determining at least one RADOS, and creating a basic authentication key corresponding to the target user;
for each RADOS in the at least one RADOS, creating a target RADOS key corresponding to the RADOS according to the RADOS identification of the RADOS and the basic authentication key;
correspondingly storing the target RADOS key, the RADOS identifier of the RADOS and the account identifier of the target user, and sending the target RADOS key to the RADOS for storage.
Optionally, the management server is further configured to:
after the target RADS GW feeds back error information, the target RADS GW is reconfigured so that the target RADS GW points to RADS corresponding to the target RADS identifier.
Optionally, the management server is specifically configured to:
when a file uploading request of a target user is received, determining at least one RADOS identifier corresponding to an account identifier of the target user, which is locally stored;
acquiring a weight of the RADOS corresponding to the at least one RADOS identifier, wherein the weight is generated by calculation based on the residual storage space of the RADOS;
and determining the RADOS identifier of the RADOS with the maximum weight as a target RADOS identifier, and determining the RADOS key corresponding to the target RADOS identifier as a target RADOS key.
Optionally, the management server is specifically configured to:
when a file downloading request of a target file sent by a target user is received, reading metadata information of the target file in a locally maintained file storage list according to an account identifier of the target user and a file identifier of the target file;
determining a target RADOS according to RADOS information contained in the metadata information of the target file;
and determining the RADOS identifier of the target RADOS as a target RADOS identifier, and determining the RADOS key of the target RADOS as a target RADOS key.
In the embodiment of the invention, when a service request of a target user is received, a management server determines a target RADS identifier and a target RADS secret key according to an account identifier of the target user, wherein the target RADS secret key is generated by the management server based on the target RADS identifier in advance, the management server preprocesses the service request according to the target RADS secret key, the management server sends the preprocessed service request to a target RADS pointed by a target RADS GW through a target RADS GW corresponding to the preset target RADS identifier, the target RADS GW acquires the preprocessed service request verified by the RADS secret key corresponding to the target RADS, if the verification is successful, the service request is sent to the target RADS, and if the verification is not successful, error information is fed back. Therefore, different RADS correspond to different RADS keys, when the management server interacts with the designated RADS through the RADS GW, the RADS key of the RADS is used, and if the RADS GW configuration is wrong, the RADS GW cannot successfully verify the RADS key of the corresponding RADS, so that the RADS GW configuration error can be found in time, the problem that the file cannot be found after being uploaded due to the RADS GW configuration error can be effectively avoided, and the service quality of the file storage service of the RADS cluster can be guaranteed to a certain extent.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. A method of processing a service request, the method comprising:
when a service request of a target user is received, a management server determines a target RADS identifier and a target RADS key according to an account identifier of the target user, wherein the target RADS key is generated by the management server based on the target RADS identifier in advance;
the management server preprocesses the service request according to the target RADOS key;
the management server sends a preprocessed service request to a target RADS pointed by the target RADS GW through a target RADS GW corresponding to the pre-configured target RADS identifier;
and the target RADS GW acquires a RADS key corresponding to the target RADS to verify the preprocessed service request, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back.
2. The method of claim 1, further comprising:
when a registration request of a target user is received, the management server determines at least one RADOS and creates a basic authentication key corresponding to the target user;
for each RADOS in the at least one RADOS, the management server creates a RADOS key corresponding to the RADOS according to the RADOS identification of the RADOS and the basic authentication key;
and the management server correspondingly stores the RADOS key, the RADOS identifier of the RADOS and the account identifier of the target user, and sends the RADOS key to the RADOS for storage.
3. The method of claim 1, wherein after the target RADS GW feeds back the error information, the method further comprises:
and the management server reconfigures the target RADS GW so that the target RADS GW points to RADS corresponding to the target RADS identifier.
4. The method of claim 1, wherein when receiving a service request from a target user, the management server determines a target RADOS identifier and a target RADOS key according to an account identifier of the target user, and the determining comprises:
when a file uploading request of a target user is received, the management server determines at least one RADOS identifier corresponding to the locally stored account identifier of the target user;
the management server acquires a weight of the RADS corresponding to the at least one RADS identifier, wherein the weight is generated by calculation based on the residual storage space of the RADS;
and the management server determines that the RADOS identifier of the RADOS with the maximum weight value is a target RADOS identifier, and determines that the RADOS key corresponding to the target RADOS identifier is a target RADOS key.
5. The method of claim 1, wherein when receiving a service request from a target user, the management server determines a target RADOS identifier and a target RADOS key according to an account identifier of the target user, and the determining comprises:
when a file downloading request of a target file sent by a target user is received, the management server reads metadata information of the target file in a locally maintained file storage list according to an account identifier of the target user and a file identifier of the target file;
the management server determines a target RADOS according to RADOS information contained in the metadata information of the target file;
and the management server determines the RADOS identifier of the target RADOS as a target RADOS identifier, and determines the RADOS key of the target RADOS as a target RADOS key.
6. A system for processing service requests, the system comprising a management server and a plurality of RADOS, wherein:
the management server is used for determining a target RADS identifier and a target RADS key according to an account identifier of a target user when receiving a service request of the target user, wherein the target RADS key is generated by the management server based on the target RADS identifier in advance, preprocessing the service request according to the target RADS key, and sending the preprocessed service request to a target RADS pointed by a target RADS GW through a target RADS GW corresponding to the preset target RADS identifier;
and the target RADS GW is used for acquiring the RADS key of the target RADS to verify the preprocessed service request, if the verification is successful, the service request is sent to the target RADS, and otherwise, error information is fed back.
7. The system of claim 6, wherein the management server is further configured to:
when a registration request of a target user is received, determining at least one RADOS, and creating a basic authentication key corresponding to the target user;
for each RADOS in the at least one RADOS, according to the RADOS identification of the RADOS and the basic authentication key, creating a RADOS key corresponding to the RADOS;
correspondingly storing the RADOS key, the RADOS identifier of the RADOS and the account identifier of the target user, and sending the RADOS key to the RADOS for storage.
8. The system of claim 6, wherein the management server is further configured to:
after the target RADS GW feeds back error information, the target RADS GW is reconfigured so that the target RADS GW points to RADS corresponding to the target RADS identifier.
9. The system of claim 6, wherein the management server is specifically configured to:
when a file uploading request of a target user is received, determining at least one RADOS identifier corresponding to an account identifier of the target user, which is locally stored;
acquiring a weight of the RADOS corresponding to the at least one RADOS identifier, wherein the weight is generated by calculation based on the residual storage space of the RADOS;
and determining the RADOS identifier of the RADOS with the maximum weight as a target RADOS identifier, and determining the RADOS key corresponding to the target RADOS identifier as a target RADOS key.
10. The system of claim 6, wherein the management server is specifically configured to:
when a file downloading request of a target file sent by a target user is received, reading metadata information of the target file in a locally maintained file storage list according to an account identifier of the target user and a file identifier of the target file;
determining a target RADOS according to RADOS information contained in the metadata information of the target file;
and determining the RADOS identifier of the target RADOS as a target RADOS identifier, and determining the RADOS key of the target RADOS as a target RADOS key.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810344659.7A CN110392015B (en) | 2018-04-17 | 2018-04-17 | Method and system for processing service request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810344659.7A CN110392015B (en) | 2018-04-17 | 2018-04-17 | Method and system for processing service request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110392015A CN110392015A (en) | 2019-10-29 |
| CN110392015B true CN110392015B (en) | 2022-01-21 |
Family
ID=68283858
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810344659.7A Active CN110392015B (en) | 2018-04-17 | 2018-04-17 | Method and system for processing service request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110392015B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110968704B (en) * | 2019-12-24 | 2023-04-07 | 浪潮云信息技术股份公司 | Multimedia processing method of RADS Gateway |
| CN112003851A (en) * | 2020-08-19 | 2020-11-27 | 浪潮云信息技术股份公司 | Method for applying RADOS Gateway to IAM system |
| CN112257041A (en) * | 2020-10-19 | 2021-01-22 | 当家移动绿色互联网技术集团有限公司 | Item control method and device and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103905466A (en) * | 2014-04-22 | 2014-07-02 | 郭伟 | Data access control system and method for storage system |
| CN106506668A (en) * | 2016-11-23 | 2017-03-15 | 山东浪潮云服务信息科技有限公司 | A kind of method that object storage is realized based on distributed storage |
| CN107659574A (en) * | 2017-10-10 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of data access control system |
| CN107911461A (en) * | 2017-11-24 | 2018-04-13 | 网宿科技股份有限公司 | Object processing method, storage server and cloud storage system in cloud storage system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8612439B2 (en) * | 2009-06-30 | 2013-12-17 | Commvault Systems, Inc. | Performing data storage operations in a cloud storage environment, including searching, encryption and indexing |
| CN103561101A (en) * | 2013-11-06 | 2014-02-05 | 中国联合网络通信集团有限公司 | Network file system |
-
2018
- 2018-04-17 CN CN201810344659.7A patent/CN110392015B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103905466A (en) * | 2014-04-22 | 2014-07-02 | 郭伟 | Data access control system and method for storage system |
| CN106506668A (en) * | 2016-11-23 | 2017-03-15 | 山东浪潮云服务信息科技有限公司 | A kind of method that object storage is realized based on distributed storage |
| CN107659574A (en) * | 2017-10-10 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of data access control system |
| CN107911461A (en) * | 2017-11-24 | 2018-04-13 | 网宿科技股份有限公司 | Object processing method, storage server and cloud storage system in cloud storage system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110392015A (en) | 2019-10-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104506510B (en) | Method and device for equipment authentication and authentication service system | |
| CN110392015B (en) | Method and system for processing service request | |
| EP2924954B1 (en) | Device controlling methods, client and server | |
| CN107105050B (en) | Storage and downloading method and system for service objects | |
| US20100008509A1 (en) | Communication apparatus, key server, and management server | |
| US20090138714A1 (en) | Communication apparatus, key server, management server, communication server, content distribution system, communication method, and recording medium | |
| CN106301822B (en) | Method, device and system for configuring AP | |
| JP2017004220A (en) | Communication device, communication system, communication method, and program | |
| US11201928B2 (en) | Method of referencing a connection session with a wireless communication device in a local area, a system for implementing this method, a method of referencing an application user, a machine-readable medium for implementing this method, as well as a method of collecting data on the wireless communication device user, and a machine-readable medium for implementing this method | |
| CN110995656B (en) | Load balancing method, device, equipment and storage medium | |
| CN113766034A (en) | Service processing method and device based on block chain | |
| CN111431957B (en) | File processing method, device, equipment and system | |
| CN108347472A (en) | Configuration method, Cloud Server, cloud platform and the readable storage medium storing program for executing of IP address | |
| CN110750206B (en) | Data processing method, device and system | |
| CN103607449A (en) | Method, device and system for enterprise internal network physical machine to visit cloud storage virtual machine | |
| KR20230043919A (en) | service request processing | |
| JP2019161580A (en) | Data transmission device, data transmission/reception system, data reception device, data transmission method, and program | |
| CN109451497B (en) | Wireless network connection method and device, electronic equipment and storage medium | |
| CN109120738B (en) | DHCP server and method for managing network internal equipment | |
| CN105871982A (en) | Content pushing method, device and system | |
| KR102435756B1 (en) | Device group control system and method for controlling the same | |
| CN115694878A (en) | Data transmission method, equipment and storage medium | |
| US8676924B2 (en) | Server and simultaneous access control method thereof | |
| US10924575B2 (en) | Automatic network management system and methods | |
| US7836445B2 (en) | Technique for installing a station device driver |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |