CN112181933A - Mounting method and device - Google Patents
Mounting method and device Download PDFInfo
- Publication number
- CN112181933A CN112181933A CN202010900303.4A CN202010900303A CN112181933A CN 112181933 A CN112181933 A CN 112181933A CN 202010900303 A CN202010900303 A CN 202010900303A CN 112181933 A CN112181933 A CN 112181933A
- Authority
- CN
- China
- Prior art keywords
- instance
- client
- storage
- application
- group
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000012545 processing Methods 0.000 claims description 14
- 238000007726 management method Methods 0.000 description 13
- 238000012549 training Methods 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000007792 addition Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
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/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/1827—Management specifically adapted to NAS
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the specification provides a mounting method and a mounting device, wherein the mounting method comprises the steps of receiving a storage instance mounting request of a client, wherein the mounting request carries a network identifier of the client and an instance identifier of the storage instance; determining an application group having a binding relationship with the storage instance based on the instance identifier, and acquiring a network identifier of a group client in the application group; and mounting the client to the storage instance under the condition that the network identification of the client is matched with the network identification of the grouping client.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a mounting method. One or more embodiments of the present specification also relate to a mounting apparatus, a computing device, and a computer-readable storage medium.
Background
In a NAS (Network Attached Storage) file Storage system, file or directory operations are based on volumes, one NAS volume is called a file system instance, that is, a Storage instance, and in order to ensure user data security, a mount permission management method using an IP (Internet Protocol) as a granularity is currently provided by NAS file Storage services, that is, an IP of each client and a Storage instance are configured to implement mount and access of a client to a Storage instance.
Therefore, it is desirable to provide a mount method that can reduce operation and maintenance costs and improve efficiency and convenience of mounting storage instances on a client.
Disclosure of Invention
In view of this, the present specification provides a mounting method. One or more embodiments of the present disclosure also relate to a mounting apparatus, a computing device, and a computer-readable storage medium to solve technical problems in the prior art.
According to a first aspect of embodiments herein, there is provided a mounting method, including:
receiving a mount request of a storage instance of a client, wherein the mount request carries a network identifier of the client and an instance identifier of the storage instance;
determining an application group having a binding relationship with the storage instance based on the instance identifier, and acquiring a network identifier of a group client in the application group;
and mounting the client to the storage instance under the condition that the network identification of the client is matched with the network identification of the grouping client.
Optionally, the determining, based on the instance identifier, the application group having a binding relationship with the storage instance includes:
and determining the application group having the binding relation with the storage instance from the cache of the storage server side based on the instance identification.
Optionally, the application packet having a binding relationship with the storage instance within a preset time is cached in the cache of the storage server,
correspondingly, the determining, from the cache of the storage server, the application packet having a binding relationship with the storage instance based on the instance identifier includes:
and determining the application packet having the binding relationship with the storage instance from the cache of the storage server based on the instance identifier under the condition that the cache time of the application packet having the binding relationship with the storage instance in the cache of the storage server is less than or equal to the preset time.
Optionally, the determining, from the cache of the storage service end based on the instance identifier, the application packet having a binding relationship with the storage instance includes:
under the condition that the caching time of an application packet which has a binding relationship with the storage instance in the cache of the storage server is longer than the preset time, the storage server sends an application packet acquisition request to a packet platform, wherein the acquisition request carries the instance identifier;
and receiving the application packet which is returned by the packet platform and has the binding relationship with the instance identifier, and storing the application packet to the cache of the storage server.
Optionally, before receiving the storage instance mount request of the client, the method further includes:
the storage server receives a storage instance binding request of the packet platform;
binding the storage instance with an application group of the group platform based on the binding request and establishing a configuration relation table,
the configuration relation table comprises a binding relation, a permission relation and an association relation between the storage instance and the application group and between the application group and the group client.
Optionally, the determining, based on the instance identifier, the application group having a binding relationship with the storage instance includes:
and determining the application group having the binding relation with the storage instance from a configuration relation table of a cache of a storage server side based on the instance identification.
Optionally, before the storage server receives the storage instance binding request of the packet platform, the method further includes:
the grouping platform receives an application grouping creation request of a user, wherein the creation request carries application information of the user and a grouping client corresponding to the application information;
and creating an application group for the user based on the application information, and establishing an association relation between the application group and the group client.
Optionally, after the establishing the association relationship between the application packet and the packet client, the method further includes:
receiving an update instruction of the user for the application group, and implementing adjustment of the application group and/or a group client associated with the application group based on the update instruction.
Optionally, after the mounting the client to the storage instance, the method further includes:
receiving an access request of the client to the storage instance;
processing the access request based on the storage instance if the access request satisfies a permission relationship between the storage instance and the application group.
Optionally, after obtaining the network identifier of the packet client in the application packet, the method further includes:
and returning mounting refusing information for the client under the condition that the network identification of the client is not matched with the network identification of the grouped client.
According to a second aspect of embodiments herein, there is provided a mounting device including:
a first receiving module, configured to receive a mount request of a storage instance of a client, where the mount request carries a network identifier of the client and an instance identifier of the storage instance;
a first determining module configured to determine, based on the instance identifier, an application group having a binding relationship with the storage instance, and acquire a network identifier of a group client in the application group;
a mount module configured to mount the client to the storage instance if the network identification of the client matches the network identification of the group client.
Optionally, the first determining module is further configured to:
and determining the application group having the binding relation with the storage instance from the cache of the storage server side based on the instance identification.
Optionally, the application packet having a binding relationship with the storage instance within a preset time is cached in the cache of the storage server,
accordingly, the first determining module is further configured to:
and determining the application packet having the binding relationship with the storage instance from the cache of the storage server based on the instance identifier under the condition that the cache time of the application packet having the binding relationship with the storage instance in the cache of the storage server is less than or equal to the preset time.
Optionally, the first determining module is further configured to:
under the condition that the caching time of an application packet which has a binding relationship with the storage instance in the cache of the storage server is longer than the preset time, the storage server sends an application packet acquisition request to a packet platform, wherein the acquisition request carries the instance identifier;
and receiving the application packet which is returned by the packet platform and has the binding relationship with the instance identifier, and storing the application packet to the cache of the storage server.
Optionally, the apparatus further includes:
a second receiving module configured to receive, by the storage service end, a storage instance binding request of a packet platform;
a first binding module configured to bind the storage instance with an application package of the package platform based on the binding request and to establish a configuration relationship table,
the configuration relation table comprises a binding relation, a permission relation and an association relation between the storage instance and the application group and between the application group and the group client.
Optionally, the first determining module is further configured to:
and determining the application group having the binding relation with the storage instance from a configuration relation table of a cache of a storage server side based on the instance identification.
Optionally, the apparatus further includes:
a third receiving module, configured to receive, by the packet platform, an application packet creation request of a user, where the creation request carries application information of the user and a packet client corresponding to the application information;
a group creation module configured to create an application group for the user based on the application information and establish an association between the application group and the group client.
Optionally, the apparatus further includes:
an update module configured to receive an update instruction of the user for the application group, and to implement an adjustment of the application group and/or a group client associated with the application group based on the update instruction.
Optionally, the apparatus further includes:
a fourth receiving module configured to receive an access request of the client for the storage instance;
a processing module configured to process the access request based on the storage instance if the access request satisfies a permission relationship between the storage instance and the application group.
Optionally, the apparatus further includes:
an information returning module configured to return the mount refusing information for the client if the network identification of the client does not match the network identification of the grouped client.
According to a third aspect of embodiments herein, there is provided a computing device comprising:
a memory and a processor;
the memory is used for storing computer-executable instructions, and the processor is used for executing the computer-executable instructions, wherein the processor realizes the steps of the mounting method when executing the computer-executable instructions.
According to a fourth aspect of embodiments herein, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the mount method.
One embodiment of the present specification implements a mount method and an apparatus, where the mount method includes receiving a mount request of a storage instance of a client, where the mount request carries a network identifier of the client and an instance identifier of the storage instance; determining an application group having a binding relationship with the storage instance based on the instance identifier, and acquiring a network identifier of a group client in the application group; mounting the client to the storage instance if the network identification of the client matches the network identification of the grouped client;
the mounting method is based on the NAS storage instance mounting authentication mechanism of the application grouping granularity, the client side which sends a mounting request can be authorized to mount and access the storage instance only under the condition that the client side is matched with the grouping client side in the application grouping bound by the NAS storage instance, and when the grouping client side in the application grouping is updated, the client side which can mount and access the storage instance can be updated accordingly, so that the operation and maintenance cost is greatly reduced, and the efficiency and the convenience of the client side for mounting the storage instance are improved.
Drawings
Fig. 1 is a flowchart illustrating a specific process of a mounting method according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of a mounting method provided in one embodiment of the present specification;
fig. 3 is a schematic structural diagram of a mounting device according to an embodiment of the present disclosure;
fig. 4 is a block diagram of a computing device according to an embodiment of the present disclosure.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
First, the noun terms to which one or more embodiments of the present specification relate are explained.
NAS: network Attached Storage.
And (3) ECS: an Elastic computer Service, cloud server, ECS for short.
OPENAPI: an open API, also called an open platform, is a common Application of a service-type website, and a website service provider packages its own website service into a series of APIs (Application Programming interfaces) to open.
Mounting and authentication: the NAS server side is used for identifying whether the client side is qualified for mounting the storage instance.
Application grouping: and the computing resources comprise information such as machine IP and the like according to the logic group segmented by the application dimension.
In the present specification, a mounting method is provided. One or more embodiments of the present specification relate to a mounting apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments.
Referring to fig. 1, fig. 1 shows a specific processing flow diagram of a mount method provided according to an embodiment of the present specification, including:
step 1: the client 1, the client 2 and the client 3 respectively send storage instance mounting requests to instance mounting points of the storage server.
Each mount request carries a network identifier of a corresponding client and an instance identifier of a storage instance to be mounted, where the network identifier of the client may be an IP identifier, for example, the network identifier of the client 1 is IP1, the network identifier of the client 2 is IP3, and the network identifier of the client 3 is IP 5.
In practical application, the storage server may be understood as a NAS server, the storage instance may be understood as a NAS instance, the NAS instance may be understood as a data disk, and the client may perform data reading and writing, data storage, and the like based on the NAS instance.
Step 2: the method comprises the steps that an instance mounting point of a storage server side obtains an application group corresponding to an instance identifier of a storage instance to be mounted from a cache of the storage server side based on the instance identifier of the storage instance to be mounted, and a group client side in the application group.
For example, an instance identifier of a storage instance to be mounted of the client 1 has a binding relationship with the application packet 1, and then the application packet 1, and the packet client 1 and the packet client 2 in the application packet 1 can be obtained based on the instance identifier, where the network identifier of the packet client 1 is IP1, and the network identifier of the packet client 2 is IP 2; if the instance identifier of the storage instance to be mounted on the client 2 has a binding relationship with the application group 2, and the packet client 3 and the packet client 4 in the application group 2 can be obtained based on the instance identifier, wherein the network identifier of the packet client 3 is IP3, and the network identifier of the packet client 4 is IP 4; if there is a binding relationship between the instance identifier of the storage instance to be mounted of the client 3 and the application packet 3, the application packet 3 and the packet client 5 in the application packet 3 can be obtained based on the instance identifier, where the network identifier of the packet client 5 is an IP List.
And step 3: and respectively matching the network identifications of the respective clients of the client 1, the client 2 and the client 3 with the network identifications of the grouped clients in the application group 1, the application group 2 and the application group 3, and determining the mounting relation between the client 1 and the storage example and the mounting relation between the client 2 and the storage example.
Specifically, as can be seen from fig. 1, the network identifier of the client 1 matches the network identifier of the grouped client 1 in the application group 1, the network identifier of the client 2 matches the network identifier of the grouped client 3 in the application group 2, and the network identifier of the client 3 does not match any network identifier of any grouped client, so that it can be determined that both the client 1 and the client 2 can mount NAS instances, but the client 3 cannot mount NAS instances.
In specific implementation, before determining the mounting relationship between the client and the NAS instance, application grouping needs to be performed on the grouped clients based on specific application dimensions, for example, when a user a has 100 clients, a user uses 20 clients as model training and uses the remaining clients as graph classification, then the 100 clients can be divided into two application groups according to the two specific application dimensions, that is, the first application group includes 20 clients, the second application group includes 80 clients, and each client has a unique IP identifier.
Referring to fig. 1, the users in fig. 1 are divided into three application groups according to specific applications: the method comprises the steps of applying a group 1, applying a group 2, applying a group 3, wherein the group 1 comprises a group client 1 and a group client 2, the two group clients can realize one specific application in practical application, such as model training as described above, the group 2 comprises a group client 3 and a group client 4, the two group clients can realize the other specific application in practical application, such as graph classification as described above, the group 3 comprises a group client 5, and the group client 5 can realize other specific applications in practical application, such as query service.
In specific implementation, a NAS instance is used as a storage instance in fig. 1 to describe the mount method in detail, and it is assumed that a user has created 3 application groups on a group platform (for example, a Skyline platform): the system comprises an application group 1, an application group 2 and an application group 3, wherein the application group 1 comprises a group client 1 and a group client 2, the application group 2 comprises a group client 3 and a group client 4, and the application group 3 comprises a group client 5, and the user can perform operation and maintenance operations such as creation, update and deletion of the application group and the group client.
The User binds the application Group to be mounted and accessing the NAS instance to the instance mounting point, and configures details of the authority to access the instance through this mounting, such as retaining the authority of the native UID (User identity, representing the unique User identity)/GID (Group identity, representing the unique Group identity)/SID (System identity), and allowing read-write access.
When a plurality of clients try to mount the NAS instance, the NAS server actively acquires IP information of packet clients in the application packets through a list of bound application packets on an instance mounting point, and compares the IP information with the IP of the client requesting mounting according to the IP information, if the client belongs to one or more bound application packets, the client can successfully mount and access data in the NAS instance, such as client 1 and client 2 in fig. 1, otherwise, the client mounting request is rejected, so that the client cannot access the data in the NAS instance, such as client 3 in fig. 1; because the short cache mechanism of the NAS server actively queries the IP information of the packet client in the bound application packet when the client mount request is checked, even if the packet client in the application packet changes, that is, when the user updates the packet client in the application packet, the NAS server can sense the changes in real time, thereby implementing the normalization of instance mount access management and application packet resource management.
In practical application, a user only needs to bind one or more application packets needing to be authorized to mount and access the storage instance to the instance mounting point through a console or an OPenAPI interface, and conversely, when the right of the mount and access of a certain application packet to the storage instance is to be recovered, the user can directly delete the application packet through the OPenAPI interface.
The mounting method provided by the embodiment of the specification depends on various application groups, specific applications, application groups and NAS storage examples are associated, the management of the group clients in the application groups and the management of the NAS example clients capable of being mounted and accessed are unified, and a user only needs to manage each application group and the group clients in each application group, so that the efficiency of using NAS resources by the user is greatly improved, and meanwhile, the data security is ensured.
In practical application, each user has a plurality of clients, and each client needs to establish a binding relationship and an authority relationship with the NAS if wanting to access the NAS instance, and when a user adds a new client or deletes a certain client, the configuration update is performed by establishing the binding relationship or removing the binding relationship between the OpenAPI or the login console and the NAS, especially when the number of the clients is large and the change is frequent, the whole operation is more complicated, the subsequent maintenance burden is heavier, and the operation and maintenance management cost is greatly increased; by adopting the mounting method provided by the embodiment of the specification, a user can group the clients according to application dimensions, each application group corresponds to a batch of clients, then a binding relationship is established between each application group and the NAS instance, and mounting and accessing are realized, so that when a certain client needs to mount the NAS instance, the user only needs to add the client in the corresponding application group, and the NAS instance can be mounted on the client without installing an additional tool.
Referring to fig. 2 and fig. 2, a flowchart of a mounting method provided according to an embodiment of the present specification is shown, including the following steps:
step 202: receiving a mount request of a storage instance of a client, wherein the mount request carries a network identifier of the client and an instance identifier of the storage instance.
The client includes but is not limited to a computer, a mobile phone, and the like; the storage example includes but is not limited to a NAS example, and in practical application, the NAS example may be understood as a data disk where a user stores data; and mounting can be understood as establishing a connection relationship between the client and the storage instance.
Specifically, the number of the clients is one, two or more, the storage instances targeted by each client may be the same or different, and the setting is specifically performed according to actual requirements, for example, there are 3 clients, where a mount request of a first client is provided for the storage instance a, and a mount request of a second client and a mount request of a third client are both provided for the storage instance B; or the mount requests of the three clients are respectively made for different storage instances. For the convenience of understanding, the following examples are all described in detail by taking an example in which a client makes a mount request for one storage instance.
In specific implementation, the storage instance mount request of the client is received, that is, the storage server receives the mount request of the client for the storage instance, where the mount request carries the unique network identifier of the client and the unique instance identifier of the storage instance.
In practical applications, if the mount method is applied to a NAS file storage system, the storage server may be a NAS server.
Specifically, the network identifier of the client and the instance identifier of the storage instance may include unique identifiers generated by numbers, words, and/or special characters, and the like, each client has a unique network identifier, and each storage instance also has a unique instance identifier.
In another embodiment of this specification, before receiving the storage instance mount request of the client, the method further includes:
the storage server receives a storage instance binding request of the packet platform;
binding the storage instance with an application group of the group platform based on the binding request and establishing a configuration relation table,
the configuration relation table comprises a binding relation, a permission relation and an association relation between the storage instance and the application group and between the application group and the group client.
Specifically, the grouping platform enables application groups to be created for a user based on the application dimensions of the user, and a corresponding grouping client to be configured for each application group.
During specific implementation, a storage server establishes a TCP (Transmission Control Protocol) connection with a packet platform, and after the connection is established, the storage server receives a storage instance binding request of the packet platform, where the binding request includes an association relationship and an authority relationship between an application packet of the packet platform and a storage instance of the storage server; and the storage server binds the storage instance with the application group in the group platform based on the binding request, and establishes a configuration relation table.
For example, the packet platform includes an application packet a and an application packet B, the storage instance binding request of the packet platform indicates that the application packet a is bound to the storage instance a, and the application packet a can perform data reading and data writing on the storage instance a, the application packet B is bound to the storage instance B, and the application packet B can perform data reading and data storage on the storage instance B, and the application packet a corresponds to the packet client a1, the packet client a2, and the application packet B corresponds to the packet client B1, and the packet client B2, then after the storage instance is bound to the application packet of the packet platform based on the binding request, the configuration relationship table established is as shown in table 1:
TABLE 1
The storage instances A, B in table 1 respectively have a unique instance identifier, the application groups A, B also respectively have a unique group identifier, and the group clients a1, a2, B1, and B2 also respectively have a unique network identifier; the association relationship between the storage instance, the application group, the mount authority and the group client can be clearly seen through table 1.
In specific implementation, each storage instance of the storage server corresponds to one instance mount point, and the binding of the application packet and the storage instance can be regarded as the binding of the application packet and the instance mount point corresponding to each storage instance.
In the embodiment of the description, the application packet created by the packet platform according to the application scenario of the user is pre-bound with the storage instance of the storage server, and when the subsequent client needs to mount the storage instance, the storage server can determine whether the client is the packet client in the application packet bound to the storage instance or not until the client needs to be determined whether the client is the packet client in the application packet bound to the storage instance, so that the mounting convenience is greatly improved.
In another embodiment of this specification, before the receiving, by the storage service, a storage instance binding request of the packet platform, the method further includes:
the grouping platform receives an application grouping creation request of a user, wherein the creation request carries application information of the user and a grouping client corresponding to the application information;
and creating an application group for the user based on the application information, and establishing an association relation between the application group and the group client.
The application information includes, but is not limited to, application scenarios, such as training scenarios, data processing scenarios, graphics classification scenarios, and the like, which are specifically related to the actual related range of the user.
Specifically, a user sends an application packet creation request to a packet platform, where the creation request carries application information of the user and a packet client corresponding to each application information; and the grouping platform creates application groups for the users based on the application information after receiving the content, and then associates the grouping client corresponding to each application information with the application groups.
For example, if the application scenario actually involved by the user is a training scenario and a data processing scenario, in a specific implementation, the user allocates 20 packet clients to the training scenario for model training, and the user allocates 50 packet clients to the data processing scenario for data processing, then the packet platform creates two application packets for the user after receiving an application packet creation request of the user, where one is a training application packet and the other is a data processing application packet, then associates the 20 packet clients allocated to the training scenario with the training application packet, and associates the 50 packet clients allocated to the data processing scenario with the data processing application packet.
In the embodiment of the description, the grouping platform firstly creates a coarse-grained application group for the user based on the application dimension of the user, then establishes an association relationship between the application group and the grouping client, and the subsequent user only needs to maintain the application group and the grouping client in the application group based on the grouping platform, so that the efficiency and the convenience of using the NAS resource by the user are greatly improved.
In specific implementation, after the establishing of the association relationship between the application packet and the packet client, the method further includes:
receiving an update instruction of the user for the application group, and implementing adjustment of the application group and/or a group client associated with the application group based on the update instruction.
The updating instructions include, but are not limited to, modification, deletion, and addition instructions, that is, after the grouping platform creates the application groups for the user, the grouping platform may also modify, delete, or add the application groups or the grouping clients in the application groups after receiving the updating instructions of the user, which greatly improves the flexibility of maintenance and improves the user experience.
Step 204: and determining an application group having a binding relationship with the storage instance based on the instance identifier, and acquiring a network identifier of a group client in the application group.
Specifically, a binding relationship pre-exists between the storage instance and the application packet, and after receiving a storage instance mount request of the client, the application packet having the binding relationship with the storage instance can be found based on the instance identifier of the storage instance, and in actual application, the binding relationship between the storage instance and the application packet can be pre-stored in the cache of the storage server, so that the application packet corresponding to the instance identifier of the storage instance can be quickly found from the cache of the storage server, and the specific implementation manner is as follows:
the determining, based on the instance identification, the application group having a binding relationship with the storage instance comprises:
and determining the application group having the binding relation with the storage instance from the cache of the storage server side based on the instance identification.
In specific implementation, in order to realize that when a packet client corresponding to an application packet is updated, a client capable of mounting and accessing a storage instance is also updated, that is, a storage server can sense changes of the packet client in the application packet in real time, a mounting method according to an embodiment of the present specification employs a mechanism of short-time caching and active query to realize timely sensing of changes of the application packet bound to the storage instance, such as addition, deletion, and modification of the application packet or addition, deletion, and modification of the packet client in the application packet, and the specific implementation manner is as follows:
the application group which has binding relation with the storage instance in preset time is cached in the cache of the storage server,
correspondingly, the determining, from the cache of the storage server, the application packet having a binding relationship with the storage instance based on the instance identifier includes:
and determining the application packet having the binding relationship with the storage instance from the cache of the storage server based on the instance identifier under the condition that the cache time of the application packet having the binding relationship with the storage instance in the cache of the storage server is less than or equal to the preset time.
The preset time may be understood as a preset time length, for example, a time length of 20 seconds, 30 seconds, and the like, that is, the maximum content in the cache of the storage server may be cached for 20 seconds or 30 seconds, and the data in the cache is deleted when the preset time is exceeded.
Taking the preset time as 20 seconds as an example, the application packet which has a binding relationship with the storage instance and is in 20 seconds needs to be cached in the cache of the storage server, and then the 20 seconds can be counted by the more than one 20-second end time.
That is to say, only the application packet having the binding relationship with the storage instance in the cache of the storage server is cached in 20 seconds, and if it is determined that the application packet having the binding relationship with the storage instance cached in the cache of the storage server is still in the 20 second cache after the storage server receives the mount request of the client for the storage instance this time, it is described that the application packet having the binding relationship with the storage instance still exists in the cache, and at this time, the application packet having the binding relationship with the storage instance can be directly obtained from the cache of the storage server based on the instance identifier.
In another embodiment of this specification, the determining, from a cache of a storage server, an application packet having a binding relationship with the storage instance based on the instance identifier includes:
under the condition that the caching time of an application packet which has a binding relationship with the storage instance in the cache of the storage server is longer than the preset time, the storage server sends an application packet acquisition request to a packet platform, wherein the acquisition request carries the instance identifier;
and receiving the application packet which is returned by the packet platform and has the binding relationship with the instance identifier, and storing the application packet to the cache of the storage server.
In specific implementation, when it is determined that the caching time of an application packet having a binding relationship with a storage instance in a cache of a storage server is greater than a preset time, data in the cache of the storage server is deleted, at this time, the storage server is required to send an application packet acquisition request to a packet platform, after the packet platform receives the acquisition request, based on an instance identifier carried in the acquisition request, the application packet corresponding to the instance identifier and a packet client corresponding to the application packet are returned to the storage server, the storage server still stores the content in the cache after receiving the content, and at this time, timing is started until the content is deleted after the preset time.
In the embodiment of the present specification, the real-time performance and the accuracy of the application packet having a binding relationship with the storage instance in the cache of the storage server are ensured by a short-time cache mechanism and an active query mechanism, and since the user can update the packet client and the application packet in real time, if the storage server always uses the first bound application packet as the mount judgment, the storage server is unsafe, and thus the security of the mount method can be greatly ensured by the above method.
In practical application, in order to facilitate management and search of the application group, a configuration relationship table capable of embodying a binding relationship between the storage instance and the application group is generally stored in the cache of the storage server, and specifically, referring to table 1 above, the binding relationship between the storage instance and the application group, the authority relationship between the storage instance and the application group, and the association relationship between the application group and the corresponding group client can be quickly determined by configuring the relationship table 1.
In specific implementation, the determining, based on the instance identifier, the application group having the binding relationship with the storage instance includes:
and determining the application group having the binding relation with the storage instance from a configuration relation table of a cache of a storage server side based on the instance identification.
In practical application, the configuration relation table of the storage instance and the application packet is pre-established, so that after a storage instance mounting request of a client is received, the application packet having a binding relation with the storage instance can be quickly and accurately found from the configuration relation table based on the instance identifier of the storage instance, and the working efficiency is improved.
And when the caching time of the configuration relation table in the cache of the storage server exceeds the preset time and the storage server acquires the application group corresponding to the storage instance from the grouping platform next time, the configuration relation table is updated in time based on the acquired new data so as to ensure the accuracy of the configuration relation table.
Step 206: and mounting the client to the storage instance under the condition that the network identification of the client is matched with the network identification of the grouping client.
Specifically, the application group bound with the instance identifier is obtained through the instance identifier of the storage instance, then the group client corresponding to the application group bound with the instance identifier is obtained, and finally the network identifier of the client sending the mount request is respectively matched with the network identifiers of all the group clients corresponding to the application group bound with the client, and if the network identifiers can be matched, the client can mount the storage instance.
Optionally, after obtaining the network identifier of the packet client in the application packet, the method further includes:
and returning mounting refusing information for the client under the condition that the network identification of the client is not matched with the network identification of the grouped client.
In specific implementation, if the network identifier of the client is not matched with the network identifier of the group client corresponding to the application group bound with the client, the client cannot mount the storage instance, and at the moment, the storage server returns mounting refusal information for the client in a mail, information or pop-up screen mode and the like to prompt the client and enhance the user experience.
The mount method provided in the embodiment of the present specification eliminates operation and maintenance costs due to a fine management granularity in the prior art, unifies two types of management costs of a group client that a user originally needs to maintain an application group and a client that is an NAS storage instance to one cost for application group management, greatly improves the use efficiency of NAS resources used by the user, and ensures that only the group client in the application group that has been bound and configured can mount and access data on the NAS instance (i.e., the storage instance) by linking the client to which the mount access right is granted in a quasi-real-time manner with the change of the group client in the application group.
In another embodiment of this specification, after the mounting the client to the storage instance, the method further includes:
receiving an access request of the client to the storage instance;
processing the access request based on the storage instance if the access request satisfies a permission relationship between the storage instance and the application group.
The access request includes, but is not limited to, a read request, a write request, or a storage request of the client for the storage instance.
In specific implementation, due to the limitation of access authority between the client and the storage instance, even if the client can mount the storage instance, the data in the storage instance needs to be accessed according to the access authority; after receiving an access request of a client for a storage instance, firstly, judging whether the access request of the client can realize the access to the storage instance based on a configuration relation table in a cache of a storage service end, and if the access request of the client has no authority, accessing the storage instance based on the access request, and if the access request of the client is not realized, rejecting the access request of the client by the storage service end.
In the embodiment of the description, the access authority of the client to the storage instance is limited based on the authority relationship between the storage instance and the application group, so that the security of the storage instance is ensured.
Corresponding to the above method embodiment, the present specification further provides a mounting device embodiment, and fig. 3 shows a schematic structural diagram of a mounting device provided in an embodiment of the present specification. As shown in fig. 3, the apparatus includes:
a first receiving module 302, configured to receive a mount request of a storage instance of a client, where the mount request carries a network identifier of the client and an instance identifier of the storage instance;
a first determining module 304, configured to determine, based on the instance identifier, an application group having a binding relationship with the storage instance, and obtain a network identifier of a group client in the application group;
a mount module 306 configured to mount the client to the storage instance if the network identification of the client matches the network identification of the packet client.
Optionally, the first determining module 304 is further configured to:
and determining the application group having the binding relation with the storage instance from the cache of the storage server side based on the instance identification.
Optionally, the application packet having a binding relationship with the storage instance within a preset time is cached in the cache of the storage server,
accordingly, the first determining module 304 is further configured to:
and determining the application packet having the binding relationship with the storage instance from the cache of the storage server based on the instance identifier under the condition that the cache time of the application packet having the binding relationship with the storage instance in the cache of the storage server is less than or equal to the preset time.
Optionally, the first determining module 304 is further configured to:
under the condition that the caching time of an application packet which has a binding relationship with the storage instance in the cache of the storage server is longer than the preset time, the storage server sends an application packet acquisition request to a packet platform, wherein the acquisition request carries the instance identifier;
and receiving the application packet which is returned by the packet platform and has the binding relationship with the instance identifier, and storing the application packet to the cache of the storage server.
Optionally, the apparatus further includes:
a second receiving module configured to receive, by the storage service end, a storage instance binding request of a packet platform;
a first binding module configured to bind the storage instance with an application package of the package platform based on the binding request and to establish a configuration relationship table,
the configuration relation table comprises a binding relation, a permission relation and an association relation between the storage instance and the application group and between the application group and the group client.
Optionally, the first determining module 304 is further configured to:
and determining the application group having the binding relation with the storage instance from a configuration relation table of a cache of a storage server side based on the instance identification.
Optionally, the apparatus further includes:
a third receiving module, configured to receive, by the packet platform, an application packet creation request of a user, where the creation request carries application information of the user and a packet client corresponding to the application information;
a group creation module configured to create an application group for the user based on the application information and establish an association between the application group and the group client.
Optionally, the apparatus further includes:
an update module configured to receive an update instruction of the user for the application group, and to implement an adjustment of the application group and/or a group client associated with the application group based on the update instruction.
Optionally, the apparatus further includes:
a fourth receiving module configured to receive an access request of the client for the storage instance;
a processing module configured to process the access request based on the storage instance if the access request satisfies a permission relationship between the storage instance and the application group.
Optionally, the apparatus further includes:
an information returning module configured to return the mount refusing information for the client if the network identification of the client does not match the network identification of the grouped client.
The mount device provided in the embodiment of the present specification eliminates operation and maintenance costs due to a fine management granularity in the prior art, unifies two types of management costs of a group client that a user originally needs to maintain an application group and a client that is an NAS storage instance to one cost for application group management, greatly improves the use efficiency of NAS resources used by the user, and ensures that only the group client in the application group that has been bound and configured can mount and access data on the NAS instance (i.e., the storage instance) by linking the client to which the mount access right is granted in a quasi-real-time manner with the change of the group client in the application group.
The above is a schematic scheme of a mounting device of the present embodiment. It should be noted that the technical solution of the mounting device and the technical solution of the mounting method described above belong to the same concept, and for details that are not described in detail, reference may be made to the description of the technical solution of the mounting method described above.
FIG. 4 illustrates a block diagram of a computing device 400 provided in accordance with one embodiment of the present description. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. Processor 420 is coupled to memory 410 via bus 430 and database 450 is used to store data.
Computing device 400 also includes access device 440, access device 440 enabling computing device 400 to communicate via one or more networks 460. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 440 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 400, as well as other components not shown in FIG. 4, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 4 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 400 may also be a mobile or stationary server.
Wherein the processor 420 is configured to execute the computer-executable instructions, and the processor is configured to execute the computer-executable instructions, wherein the processor implements the steps of the mount method when executing the computer-executable instructions.
The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the mounting method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the mounting method.
An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which when executed by a processor implement the steps of the mount method.
The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the mounting method described above, and for details that are not described in detail in the technical solution of the storage medium, reference may be made to the description of the technical solution of the mounting method described above.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts, but those skilled in the art should understand that the present embodiment is not limited by the described acts, because some steps may be performed in other sequences or simultaneously according to the present embodiment. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for an embodiment of the specification.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the embodiments. The specification is limited only by the claims and their full scope and equivalents.
Claims (13)
1. A mounting method, comprising:
receiving a mount request of a storage instance of a client, wherein the mount request carries a network identifier of the client and an instance identifier of the storage instance;
determining an application group having a binding relationship with the storage instance based on the instance identifier, and acquiring a network identifier of a group client in the application group;
and mounting the client to the storage instance under the condition that the network identification of the client is matched with the network identification of the grouping client.
2. The mount method according to claim 1, wherein the determining, based on the instance identification, the application packet having the binding relationship with the storage instance comprises:
and determining the application group having the binding relation with the storage instance from the cache of the storage server side based on the instance identification.
3. The mount method according to claim 2, wherein the application packets having a binding relationship with the storage instance within a preset time are cached in the cache of the storage server,
correspondingly, the determining, from the cache of the storage server, the application packet having a binding relationship with the storage instance based on the instance identifier includes:
and determining the application packet having the binding relationship with the storage instance from the cache of the storage server based on the instance identifier under the condition that the cache time of the application packet having the binding relationship with the storage instance in the cache of the storage server is less than or equal to the preset time.
4. The mounting method according to claim 3, wherein the determining, from a cache of a storage server, the application group having a binding relationship with the storage instance based on the instance identifier comprises:
under the condition that the caching time of an application packet which has a binding relationship with the storage instance in the cache of the storage server is longer than the preset time, the storage server sends an application packet acquisition request to a packet platform, wherein the acquisition request carries the instance identifier;
and receiving the application packet which is returned by the packet platform and has the binding relationship with the instance identifier, and storing the application packet to the cache of the storage server.
5. The mount method according to claim 1, before receiving the mount request of the storage instance of the client, further comprising:
the storage server receives a storage instance binding request of the packet platform;
binding the storage instance with an application group of the group platform based on the binding request and establishing a configuration relation table,
the configuration relation table comprises a binding relation, a permission relation and an association relation between the storage instance and the application group and between the application group and the group client.
6. The mount method according to claim 5, wherein the determining, based on the instance identification, the application packet having the binding relationship with the storage instance comprises:
and determining the application group having the binding relation with the storage instance from a configuration relation table of a cache of a storage server side based on the instance identification.
7. The mount method according to claim 5, before the storage service side receives the storage instance binding request of the packet platform, further comprising:
the grouping platform receives an application grouping creation request of a user, wherein the creation request carries application information of the user and a grouping client corresponding to the application information;
and creating an application group for the user based on the application information, and establishing an association relation between the application group and the group client.
8. The mounting method according to claim 7, after establishing the association relationship between the application packet and the packet client, further comprising:
receiving an update instruction of the user for the application group, and implementing adjustment of the application group and/or a group client associated with the application group based on the update instruction.
9. The mount method according to claim 6, further comprising, after mounting the client to the storage instance:
receiving an access request of the client to the storage instance;
processing the access request based on the storage instance if the access request satisfies a permission relationship between the storage instance and the application group.
10. The mount method according to claim 1, after obtaining the network identifier of the packet client in the application packet, further comprising:
and returning mounting refusing information for the client under the condition that the network identification of the client is not matched with the network identification of the grouped client.
11. A mounting device comprising:
a first receiving module, configured to receive a mount request of a storage instance of a client, where the mount request carries a network identifier of the client and an instance identifier of the storage instance;
a first determining module configured to determine, based on the instance identifier, an application group having a binding relationship with the storage instance, and acquire a network identifier of a group client in the application group;
a mount module configured to mount the client to the storage instance if the network identification of the client matches the network identification of the group client.
12. A computing device, comprising:
a memory and a processor;
the memory is used for storing computer-executable instructions and the processor is used for executing the computer-executable instructions, wherein the steps of the mounting method of claims 1-10 are realized when the processor executes the computer-executable instructions.
13. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the mounting method of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010900303.4A CN112181933A (en) | 2020-08-31 | 2020-08-31 | Mounting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010900303.4A CN112181933A (en) | 2020-08-31 | 2020-08-31 | Mounting method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112181933A true CN112181933A (en) | 2021-01-05 |
Family
ID=73925142
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010900303.4A Pending CN112181933A (en) | 2020-08-31 | 2020-08-31 | Mounting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181933A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114237082A (en) * | 2021-11-03 | 2022-03-25 | 深圳市优必选科技股份有限公司 | Equipment management system, robot, and computer-readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172061A (en) * | 2017-06-07 | 2017-09-15 | 郑州云海信息技术有限公司 | It is a kind of to realize shared method and system |
| CN109040207A (en) * | 2018-07-20 | 2018-12-18 | 广东浪潮大数据研究有限公司 | A kind of method, device and equipment accessing User space Network File System |
-
2020
- 2020-08-31 CN CN202010900303.4A patent/CN112181933A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172061A (en) * | 2017-06-07 | 2017-09-15 | 郑州云海信息技术有限公司 | It is a kind of to realize shared method and system |
| CN109040207A (en) * | 2018-07-20 | 2018-12-18 | 广东浪潮大数据研究有限公司 | A kind of method, device and equipment accessing User space Network File System |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114237082A (en) * | 2021-11-03 | 2022-03-25 | 深圳市优必选科技股份有限公司 | Equipment management system, robot, and computer-readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2017114206A1 (en) | Method and device for processing short link, and short link server | |
| US8479265B2 (en) | Usage based authorization | |
| CN112115511A (en) | Authority verification method, device and system, and service authority configuration method and device | |
| CN111970315A (en) | Method, device and system for pushing message | |
| US9083690B2 (en) | Communication session termination rankings and protocols | |
| EP3253026A1 (en) | Cdn-based access control method and relevant device | |
| WO2017041562A1 (en) | Method and device for identifying user identity of terminal device | |
| EP2633667A2 (en) | System and method for on the fly protocol conversion in obtaining policy enforcement information | |
| CN112202750B (en) | Control method for policy execution, policy execution system and computing device | |
| WO2023056797A1 (en) | Blockchain-based data processing method, apparatus, and device, and storage medium | |
| US20130212260A1 (en) | System and method for automatic prioritization of communication sessions | |
| US11388248B1 (en) | Dynamic domain discovery and proxy configuration | |
| CN112256772A (en) | Data service method, device and readable storage medium | |
| CN105915621A (en) | Data access method and pretreatment server | |
| US10326833B1 (en) | Systems and method for processing request for network resources | |
| KR20130077433A (en) | System and method for authority management in the mobile cloud service | |
| CN106899564A (en) | A kind of login method and device | |
| CN111885177A (en) | Biological information analysis cloud computing method and system based on cloud computing technology | |
| CN106878052B (en) | User migration method and device | |
| CN108279924A (en) | Program dissemination method and device | |
| CN112181933A (en) | Mounting method and device | |
| CN113301005B (en) | Data acquisition method and device | |
| CN105184559B (en) | A kind of payment system and method | |
| CN104144170A (en) | URL filtering method, device and system | |
| US11494392B2 (en) | Tracking entity activity using computer generation of values for blockchain network entries |
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 |