CN112714166B - Multi-cluster management method and device for distributed storage system - Google Patents

Multi-cluster management method and device for distributed storage system Download PDF

Info

Publication number
CN112714166B
CN112714166B CN202011531025.6A CN202011531025A CN112714166B CN 112714166 B CN112714166 B CN 112714166B CN 202011531025 A CN202011531025 A CN 202011531025A CN 112714166 B CN112714166 B CN 112714166B
Authority
CN
China
Prior art keywords
cluster
account information
login
login account
manageable
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
Application number
CN202011531025.6A
Other languages
Chinese (zh)
Other versions
CN112714166A (en
Inventor
邓美瑶
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Big Data Technologies Co Ltd
Original Assignee
New H3C Big Data Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Big Data Technologies Co Ltd filed Critical New H3C Big Data Technologies Co Ltd
Priority to CN202011531025.6A priority Critical patent/CN112714166B/en
Publication of CN112714166A publication Critical patent/CN112714166A/en
Application granted granted Critical
Publication of CN112714166B publication Critical patent/CN112714166B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Abstract

The application provides a multi-cluster management method and a device of a distributed storage system, the method is applied to a management node included in a first cluster, the management node logs in the first cluster in a local browser, and the local browser displays a plurality of clusters to be jumped, and the method comprises the following steps: receiving a cluster switching instruction input by a user, wherein the cluster switching instruction comprises an identifier of a second cluster selected by the user from a plurality of clusters to be jumped; acquiring first login account information of a second cluster from the manageable cluster list according to the identifier of the second cluster; sending a login request to a second cluster, wherein the login request comprises first login account information; receiving a login response sent by the second cluster after the first login account information is verified, wherein the login response comprises a login token; and jumping to the second cluster according to the login token, and displaying a management page of the second cluster in the local browser.

Description

Multi-cluster management method and device for distributed storage system
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for multi-cluster management of a distributed storage system.
Background
The distributed storage system is a data storage technology and consists of a plurality of hosts, wherein each host is called a node; a node is a program entity which can independently complete a set of logics according to a distributed protocol, and data is stored by writing the data into a local storage device.
The distributed storage system software is software defined storage implemented by adopting a distributed cluster technology. The software is a unit constructed on the basis of storage servers, and a large number of scattered storage servers form an organic unified storage cluster. The software carries out unified management on the local hard disks of the storage servers, forms the local hard disks into a virtual storage pool and provides massive, undifferentiated and unified distributed storage service.
As shown in fig. 1, fig. 1 is a schematic diagram of a distributed storage system networking. In fig. 1, the distributed storage system includes four types of networks, namely, a service network, a management network, a storage front-end network, and a storage back-end network. The service network refers to the application server accessing the system through the service network and using the storage resources and services provided by the system. The management network refers to that an administrator accesses a management node in the system through the management network to operate and manage the system. The storage front-end network refers to a data link between a gateway and a system in the system and is used for sending the IO request to the OSD. The storage back-end network is an internal network of the system and is used for finishing heartbeat and data balance among OSD.
The distributed storage system comprises the following three node types, namely a management node, a storage node and a monitoring node. The management node refers to a host installed with distributed storage system software and used for deploying and managing the distributed storage system. The user can access the IP address of the management node through the browser, and then log in a Web management page of the system. A storage node refers to a host within a system for storing data. The monitoring node refers to a host used for monitoring the system cluster in the system.
At present, when a plurality of systems are managed, a user operation terminal opens a plurality of browser windows, respectively inputs management IPs of the systems, and inputs a user name and a password in a login page for a plurality of times; meanwhile, if the system is not operated within the preset time after logging in the system, the system needs to be logged in again when the system is operated again. Thus, when a user manages a plurality of systems, a plurality of repeated and time-consuming operations need to be executed, and user experience is reduced.
Disclosure of Invention
In view of this, the present application provides a multi-cluster management method and apparatus for a distributed storage system, so as to solve the problem that in the prior art, when a user manages multiple systems, multiple repeated and time-consuming operations need to be performed, which reduces user experience.
In a first aspect, the present application provides a multi-cluster management method for a distributed storage system, where the method is applied to a management node included in a first cluster, and a plurality of clusters to be jumped are displayed in a local browser, and the method includes:
receiving a cluster switching instruction input by a user, wherein the cluster switching instruction comprises an identifier of a second cluster selected by the user from a plurality of clusters to be jumped;
acquiring first login account information of the second cluster from a manageable cluster list according to the identifier of the second cluster;
sending a login request to the second cluster, wherein the login request comprises the first login account information;
receiving a login response sent by the second cluster after the first login account information is verified, wherein the login response comprises a login token;
and jumping to the second cluster according to the login token, and displaying a management page of the second cluster in the local browser.
In a second aspect, the present application provides a multi-cluster management apparatus for a distributed storage system, where the apparatus is applied to a management node included in a first cluster, the management node has logged in the first cluster in a local browser, and the local browser displays a plurality of clusters to be jumped, and the apparatus includes:
a receiving unit, configured to receive a cluster switching instruction input by a user, where the cluster switching instruction includes an identifier of a second cluster selected by the user from multiple clusters to be jumped;
an obtaining unit, configured to obtain, according to the identifier of the second cluster, first login account information of the second cluster from a manageable cluster list;
a sending unit, configured to send a login request to the second cluster, where the login request includes the first login account information;
the receiving unit is further configured to receive a login response sent by the second cluster after the first login account information is verified, where the login response includes a login token;
and the jumping display unit is used for jumping to the second cluster according to the login token and displaying the management page of the second cluster in the local browser.
In a third aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.
Therefore, by applying the multi-cluster management method and the device for the distributed storage system provided by the application, the management node receives a cluster switching instruction input by a user, wherein the cluster switching instruction comprises an identifier of a second cluster selected by the user from a plurality of clusters to be jumped. And according to the identifier of the second cluster, the management node acquires the first login account information of the second cluster from the manageable cluster list. And the management node sends a login request to the second cluster, wherein the login request comprises the first login account information. And the management node receives a login response sent by the second cluster after the first login account information is verified, wherein the login response comprises a login token. And according to the login token, the management node jumps to the second cluster and displays a management page of the second cluster in the local browser.
Therefore, the problem that in the prior art, when a user manages a plurality of systems, a plurality of repeated and time-consuming operations need to be executed, and user experience is reduced is solved. The method and the device realize the operation of a plurality of clusters only by logging in one cluster, reduce the process of inputting the user name and the password for a plurality of times, and simultaneously reduce the process of re-inputting the user name and the password caused by no operation on other clusters for a long time.
Drawings
FIG. 1 is a schematic diagram of a distributed storage system networking;
fig. 2 is a flowchart of a multi-cluster management method of a distributed storage system according to an embodiment of the present application;
fig. 3 is a schematic management page of a first cluster according to an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a configuration of a manageable cluster list in a management page according to an embodiment of the present application;
fig. 5 is a schematic diagram of a cluster jump page provided in an embodiment of the present application;
fig. 6 is a schematic view illustrating synchronization of login account information among multiple clusters according to an embodiment of the present disclosure;
fig. 7 is a diagram illustrating a multi-cluster management apparatus of a distributed storage system according to an embodiment of the present application;
fig. 8 is a hardware structure diagram of a network device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application 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 herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The following describes in detail a multi-cluster management method of a distributed storage system according to an embodiment of the present application. Referring to fig. 2, fig. 2 is a flowchart of a multi-cluster management method of a distributed storage system according to an embodiment of the present application. The method is applied to a management node included in a first cluster, and the multi-cluster management method of the distributed storage system provided by the embodiment of the application may include the following steps.
Step 210, receiving a cluster switching instruction input by a user, where the cluster switching instruction includes an identifier of a second cluster selected by the user from multiple clusters to be jumped.
Specifically, a management node (e.g., a first management node) of a first cluster receives a double-click instruction input by a user, and the double-click instruction is used for opening a browser in the first management node. And according to the double-click instruction, the first management node opens the browser.
And the first management node receives the address information of the first cluster input by the user in an address bar of the browser and jumps to a management page of the first cluster. As shown in fig. 3, fig. 3 is a schematic view of a management page of a first cluster according to an embodiment of the present application. And the user can operate the first cluster through the management page of the first cluster. For example, clicking to view the system log of the first cluster, clicking to process alarm information within the first cluster, and so forth.
At this time, if the user wants to operate other clusters, the user selects a cluster to be jumped from the multi-cluster management drop-down list above the management page of the first cluster. It will be appreciated that in the multi-cluster management drop-down list, the identity of multiple clusters is configured. The identification may specifically include an IP address of the cluster, a name of the cluster, or a combination of the IP address of the cluster, the name of the cluster, and so on. The user can select the cluster to be jumped through the identification of the cluster displayed in the multi-cluster management drop-down list.
After the user selects the cluster to be jumped, a cluster switching instruction is input into the multi-cluster management drop-down list. The cluster switch instruction includes an identification of a second cluster selected by the user from the plurality of clusters to be jumped.
Further, before executing this step, the first management node also executes a process of creating second login account information of the target cluster and storing the second login account information of the target cluster into the manageable cluster list.
The first management node creates second login account information jumping to the target cluster, wherein the second login account information comprises a cluster IP address, a user name and a password of the target cluster. For example, the cluster IP address of the target cluster is 196.16.20.33; the user name is admin; the password is 123456. It is understood that the second login account information may also include a cluster name, e.g., 180, 123 _.
The first management node generates an authentication request that includes a cluster IP address, a username, and a password for the target cluster. The first management node sends the verification request to the target cluster. In an embodiment of the present application, the first management node includes a Leader process. The process that the first management node sends the verification request to the target cluster is specifically that a first Leader process included in the first management node sends the verification request to a second Leader process included in a second management node in the target cluster.
And the second Leader process calls a restful interface of the login to verify the cluster IP address, the user name and the password included in the verification request. The second Leader process verifies the cluster IP address, username, and password without error (i.e., passes). The second management node generates an authentication response (e.g., a first authentication response) indicating that the second login account information included in the authentication request is authenticated.
It can be understood that, in the authentication process of the cluster IP address, the user name, and the password, if any information is authenticated incorrectly (i.e., fails), the second management node still generates an authentication response (e.g., a second authentication response) indicating that the second login account information included in the authentication request is not authenticated.
Each verification response comprises a verification identifier, and the verification identifier is used for indicating whether the second login account information verification is passed or not.
The second management node sends a first verification response to the first management node. And after receiving the first verification response, the first management node determines that the second login account information passes the verification of the target cluster according to the verification identifier. The first management node stores the cluster IP address, the user name and the password of the target cluster into a manageable cluster list.
Further, in this embodiment of the present application, the first management node further stores the third login account information of the first cluster in the manageable cluster list.
In this embodiment of the present application, the manageable cluster list may be configured in the management page. Fig. 4 is a schematic diagram illustrating a configuration manageable cluster list in a management page provided in the embodiment of the present application, as shown in fig. 4. In fig. 4, the manageable cluster list includes the second login account information of a plurality of target clusters, and the second login account information of each target cluster passes the authentication of the target cluster.
Also included on top of the manageable cluster list are a number of function buttons, e.g., create, refresh, more buttons. The user may click on the create button to enter the second login account information for the target cluster. And after receiving the second login account information input by the user, the management node sends a verification request to the target cluster. The user can click a refresh button, and the first management node updates the manageable cluster list after receiving a refresh instruction input by the user. Or, after adding the second login account information of a new target cluster to the manageable cluster list or deleting the second login account information of an existing target cluster, the first management node can display the updated manageable cluster list by itself.
Step 220, according to the identifier of the second cluster, obtaining the first login account information of the second cluster from the manageable cluster list.
Specifically, according to the description in step 210, after the first management node obtains the identifier of the second cluster from the cluster switching instruction, the first management node obtains the first login account information of the second cluster from the manageable cluster list. I.e. the cluster IP address, username and password of the second cluster are obtained.
Step 230, sending a login request to the second cluster, where the login request includes the first login account information.
Specifically, according to the description in step 220, after the first management node obtains the cluster IP address, the user name, and the password of the second cluster, the first management node generates a login request, where the login request includes the cluster IP address, the user name, and the password of the second cluster.
The first management node sends a login request to the second cluster. It is to be understood that a first Leader process comprised by a first management node sends a login request to a second Leader process comprised by a second management node in a second cluster.
And the second Leader process calls a restful interface of the login to verify the cluster IP address, the user name and the password of the second cluster included in the login request.
Step 240, receiving a login response sent by the second cluster after the first login account information is verified, where the login response includes a login token.
Specifically, the second Leader process verifies (i.e., passes) the cluster IP address, username, and password of the second cluster as described in step 230. The second management node generates a login Token (Token), which is a string of characters.
The second management node sends a login response (e.g., a first login response) to the first management node, the first login response including a login token. And after receiving the first login response, the first management node acquires a login token from the first login response, and determines that the cluster IP address, the user name and the password of the second cluster pass the verification of the second cluster.
It can be understood that, in the verification process of the cluster IP address, the user name, and the password of the second cluster by the second Leader process, if any information is verified incorrectly (i.e., failed), the second management node still generates a login response (e.g., a second login response), where the second login response is used to indicate that the first login account information of the second cluster included in the login request is not verified. The second login response does not include a login token.
And the second management node sends a second login response to the first management node. And after receiving the second login response, the first management node does not obtain the login token from the second login response. The first management node determines that the cluster IP address, the username, and the password of the second cluster fail authentication by the second cluster.
In the embodiment of the application, after the first management node does not acquire the login token, the first management node may generate a prompt message. The first management node displays the prompt message. The prompt message is used for informing the user of the jump failure.
It should be noted that the foregoing login token specifically refers to a credential for facilitating a client to request data from a server multiple times. That is, after the client successfully logs in for the first time, the server generates a login token and returns the login token to the client, and subsequently, the client can request data from the server by carrying the login token in the request without carrying the user name and the password again.
And 250, jumping to the second cluster according to the login token, and displaying a management page of the second cluster in the local browser.
Specifically, according to the description of step 240, after the first management node obtains the login token, a skip prompt message is generated first. The first management node displays the skip prompting information, as shown in fig. 5, fig. 5 is a schematic diagram of a cluster skip page provided in the embodiment of the present application. In fig. 5, the skip prompting message is "determine to skip to the second cluster IP as 196.16.20.33 management page".
And if the user wants to access the second cluster, the user clicks the confirmation button, and the first management node directly jumps to the management page of the second cluster after receiving a jump confirmation instruction input by the user. And if the user does not wish to access the second cluster, the user clicks a cancel button, and the first management node does not execute the operation of jumping the cluster after receiving a jump cancel instruction input by the user.
Further, after receiving a jump confirmation instruction input by a user, the first management node generates an access request for accessing the second cluster, where the access request includes a login token. The first management node sends an access request to the second management node. And after receiving the access request, the second management node acquires the login token from the access request, and generates an access response which comprises the URL of the management page of the second cluster. The second management node sends an access response to the first management node.
And after receiving the access response, the first management node acquires the URL of the management page of the second cluster. And skipping is realized through the URL of the management page of the second cluster.
Therefore, by applying the multi-cluster management method of the distributed storage system provided by the application, the management node receives a cluster switching instruction input by a user, wherein the cluster switching instruction comprises an identifier of a second cluster selected by the user from a plurality of clusters to be jumped. And according to the identifier of the second cluster, the management node acquires the first login account information of the second cluster from the manageable cluster list. And the management node sends a login request to the second cluster, wherein the login request comprises the first login account information. And the management node receives a login response sent by the second cluster after the first login account information is verified, wherein the login response comprises a login token. And according to the login token, the management node jumps to the second cluster and displays a management page of the second cluster in the local browser.
Therefore, the problem that in the prior art, when a user manages a plurality of systems, a plurality of repeated and time-consuming operations need to be executed, and user experience is reduced is solved. The method and the device realize the operation of a plurality of clusters only by logging in one cluster, reduce the process of inputting the user name and the password for a plurality of times, and simultaneously reduce the process of re-inputting the user name and the password caused by no operation on other clusters for a long time.
Optionally, in this embodiment of the present application, a process of synchronizing login account information among multiple clusters is further included.
Specifically, the first management node obtains fourth login account information of the first type of cluster and fifth login account information of the second type of cluster in the manageable cluster list. The first type cluster may be a cluster newly stored in the manageable cluster list, and the second type cluster may be another cluster except the cluster newly stored in the manageable cluster list.
And the first management node sends fourth login account information to the second type cluster so that the second type cluster verifies the fourth login account information, and stores the fourth login account information in a manageable cluster list of the first management node after the fourth login account information passes verification.
And the first management node sends the fifth login account information to the first type cluster so that the first type cluster verifies the fifth login account information, and stores the fifth login account information in a manageable cluster list of the first type cluster after the verification is passed.
It can be understood that, if the fifth/fourth login account information already exists in the first/second type cluster, the existing login account information is updated according to the newly received login account information. Therefore, mutual synchronous login account information among multiple clusters is realized, and further mutual skipping among the clusters is realized.
In an example, as shown in fig. 6, fig. 6 is a schematic diagram illustrating synchronization of login account information among multiple clusters according to an embodiment of the present disclosure. Initially, none of the clusters A, B, C, D are configured with login account information for other clusters, i.e., the manageable cluster list for each cluster is empty.
In order to realize the jump between the cluster A and the cluster B, the cluster A stores the login account information of the cluster A and the login account information of the cluster B in a manageable cluster list. In this manner, clusters A, B may implement a jump to each other. At this time, the login account information of the cluster C is added to the manageable cluster list of the cluster a, and after the cluster C verifies the login account information without error, the cluster a stores the login account information of the cluster C into the manageable cluster list of the cluster a. Meanwhile, the cluster A sends the login account information of the cluster C to the cluster B, and the cluster B stores the login account information of the cluster C into a manageable cluster list of the cluster B. Cluster a also sends login account information of cluster B in the manageable cluster list to cluster C. If the manageable cluster list of the cluster C stores the login account information of the cluster B, the cluster C updates the manageable cluster list of the cluster C according to the received login account information of the cluster B. In this way, the clusters A, B, C jump to each other.
Similarly, after the login account information of the cluster D is added to the manageable cluster list of the cluster a, the login account information of the cluster D is synchronized into the cluster B, C, and the login account information of the cluster A, B, C is synchronized into the cluster D. Therefore, the clusters A, B, C, D jump to each other;
it can be understood that, in combination with the actual situation, in order to prevent resource occupation caused by synchronization of login account information due to too many clusters, the management node may support addition of login account information of 16 clusters at most.
Based on the same inventive concept, the embodiment of the application also provides a multi-cluster management device of the distributed storage system corresponding to the multi-cluster management method of the distributed storage system. Referring to fig. 7, fig. 7 is a structural diagram of a multi-cluster management apparatus of a distributed storage system according to an embodiment of the present application, where the apparatus is applied to a management node included in a first cluster, the management node has logged in the first cluster in a local browser, and the local browser displays multiple clusters to be jumped to, and the apparatus includes:
a receiving unit 710, configured to receive a cluster switching instruction input by a user, where the cluster switching instruction includes an identifier of a second cluster selected by the user from multiple clusters to be jumped;
an obtaining unit 720, configured to obtain, according to the identifier of the second cluster, first login account information of the second cluster from the manageable cluster list;
a sending unit 730, configured to send a login request to the second cluster, where the login request includes the first login account information;
the receiving unit 710 is further configured to receive a login response sent by the second cluster after the first login account information is verified, where the login response includes a login token;
and a jump display unit 740, configured to jump to the second cluster according to the login token, and display a management page of the second cluster in the local browser.
Optionally, the apparatus further comprises: a creating unit (not shown in the figure) configured to create second login account information for jumping to a target cluster, where the second login account information includes a cluster IP address, a user name, and a password of the target cluster;
the sending unit 730 is further configured to send an authentication request to the target cluster, where the authentication request includes a cluster IP address, a user name, and a password of the target cluster;
the receiving unit 710 is further configured to receive an authentication response sent by the target cluster after the cluster IP address, the user name, and the password of the target cluster are authenticated;
the device further comprises: and a storage unit (not shown in the figure) for storing the cluster IP address, the user name and the password of the target cluster into the manageable cluster list according to the verification response.
Optionally, the storage unit (not shown in the figure) is further configured to store third login account information of the first cluster into the manageable cluster list.
Optionally, the apparatus further comprises: an obtaining unit (not shown in the figure), configured to obtain fourth login account information of the first type of cluster and fifth login account information of the second type of cluster in the manageable cluster list;
the sending unit 730 is further configured to send the fourth login account information to the second type cluster, so that the second type cluster verifies the fourth login account information, and after the fourth login account information passes the verification, the fourth login account information is stored in a manageable cluster list of the second type cluster;
the sending unit 730 is further configured to send the fifth login account information to the first type cluster, so that the first type cluster verifies the fifth login account information, and after the verification passes, the fifth login account information is stored in a manageable cluster list of the first type cluster.
Optionally, the jump display unit 740 is specifically configured to display jump prompt information;
and when a jump confirmation instruction input by a user is received, jumping to the second cluster.
Therefore, by applying the multi-cluster management device of the distributed storage system provided by the application, the device receives a cluster switching instruction input by a user, wherein the cluster switching instruction comprises an identifier of a second cluster selected by the user from a plurality of clusters to be jumped. And according to the identifier of the second cluster, the device acquires the first login account information of the second cluster from the manageable cluster list. The device sends a login request to the second cluster, wherein the login request comprises the first login account information. The device receives a login response sent by the second cluster after the first login account information is verified, wherein the login response comprises a login token. According to the login token, the device jumps to the second cluster and displays a management page of the second cluster in the local browser.
Therefore, the problem that in the prior art, when a user manages a plurality of systems, a plurality of repeated and time-consuming operations need to be executed, and user experience is reduced is solved. The method and the device realize the operation of a plurality of clusters only by logging in one cluster, reduce the process of inputting the user name and the password for a plurality of times, and simultaneously reduce the process of re-inputting the user name and the password caused by no operation on other clusters for a long time.
Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 8, including a processor 810, a transceiver 820 and a machine-readable storage medium 830, where the machine-readable storage medium 830 stores machine-executable instructions capable of being executed by the processor 810, and the processor 810 is caused by the machine-executable instructions to perform the multi-cluster management method of the distributed storage system provided by the embodiment of the present application. The aforementioned multi-cluster management apparatus of the distributed storage system shown in fig. 7 can be implemented by using a hardware structure of a network device as shown in fig. 8.
The computer-readable storage medium 830 may include a Random Access Memory (RAM) and a Non-volatile Memory (NVM), such as at least one disk Memory. Alternatively, the computer-readable storage medium 830 may be at least one memory device located remotely from the processor 810.
The Processor 810 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In the embodiment of the present application, the processor 810 is caused by machine executable instructions by reading the machine executable instructions stored in the machine readable storage medium 830, so as to enable the processor 810 itself and the call transceiver 820 to execute the multi-cluster management method of the distributed storage system described in the foregoing embodiment of the present application.
Additionally, embodiments of the present application provide a machine-readable storage medium 830, the machine-readable storage medium 830 storing machine-executable instructions, which when invoked and executed by the processor 810, cause the processor 810 itself and the invoking transceiver 820 to perform the aforementioned multi-cluster management method of the distributed storage system described in embodiments of the present application.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
For the multi-cluster management apparatus and machine-readable storage medium embodiment of the distributed storage system, since the contents of the related method are substantially similar to those of the foregoing method embodiment, the description is relatively simple, and the relevant points can be referred to the partial description of the method embodiment.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (10)

1. A multi-cluster management method of a distributed storage system is applied to a management node included in a first cluster, the management node logs in the first cluster in a local browser, and the local browser displays a plurality of clusters to be jumped, and the method comprises the following steps:
receiving a cluster switching instruction input by a user, wherein the cluster switching instruction comprises an identifier of a second cluster selected by the user from a plurality of clusters to be jumped;
acquiring first login account information of the second cluster from a manageable cluster list according to the identifier of the second cluster;
sending a login request to the second cluster, wherein the login request comprises the first login account information;
receiving a login response sent by the second cluster after the first login account information is verified, wherein the login response comprises a login token;
and jumping to the second cluster according to the login token, and displaying a management page of the second cluster in the local browser.
2. The method of claim 1, wherein prior to receiving the user-entered cluster switch instruction, the method further comprises:
creating second login account information jumping to a target cluster, wherein the second login account information comprises a cluster IP address, a user name and a password of the target cluster;
sending a verification request to the target cluster, wherein the verification request comprises a cluster IP address, a user name and a password of the target cluster;
receiving an authentication response sent by the target cluster after the cluster IP address, the user name and the password of the target cluster are authenticated;
and storing the cluster IP address, the user name and the password of the target cluster into the manageable cluster list according to the verification response.
3. The method of claim 2, further comprising:
and storing the third login account information of the first cluster into the manageable cluster list.
4. The method of claim 3, further comprising:
acquiring fourth login account information of the first type of cluster and fifth login account information of the second type of cluster in the manageable cluster list;
sending the fourth login account information to the second type cluster so that the second type cluster verifies the fourth login account information, and storing the fourth login account information in a manageable cluster list of the second type cluster after the fourth login account information passes the verification;
and sending the fifth login account information to the first type cluster so that the first type cluster verifies the fifth login account information, and storing the fifth login account information in a self manageable cluster list after the verification is passed.
5. The method according to claim 1, wherein the jumping to the second cluster specifically comprises:
displaying skip prompt information;
and when a jump confirmation instruction input by a user is received, jumping to the second cluster.
6. A multi-cluster management apparatus of a distributed storage system, the apparatus being applied to a management node included in a first cluster, the management node having logged in the first cluster in a local browser, and the local browser displaying a plurality of clusters to be jumped to, the apparatus comprising:
a receiving unit, configured to receive a cluster switching instruction input by a user, where the cluster switching instruction includes an identifier of a second cluster selected by the user from multiple clusters to be jumped;
an obtaining unit, configured to obtain, according to the identifier of the second cluster, first login account information of the second cluster from a manageable cluster list;
a sending unit, configured to send a login request to the second cluster, where the login request includes the first login account information;
the receiving unit is further configured to receive a login response sent by the second cluster after the first login account information is verified, where the login response includes a login token;
and the jumping display unit is used for jumping to the second cluster according to the login token and displaying the management page of the second cluster in the local browser.
7. The apparatus of claim 6, further comprising:
the system comprises a creating unit, a sending unit and a processing unit, wherein the creating unit is used for creating second login account information jumping to a target cluster, and the second login account information comprises a cluster IP address, a user name and a password of the target cluster;
the sending unit is further configured to send an authentication request to the target cluster, where the authentication request includes a cluster IP address, a user name, and a password of the target cluster;
the receiving unit is further configured to receive an authentication response sent by the target cluster after the cluster IP address, the user name, and the password of the target cluster are authenticated;
the device further comprises: and the storage unit is used for storing the cluster IP address, the user name and the password of the target cluster into the manageable cluster list according to the verification response.
8. The apparatus of claim 7, wherein the storage unit is further configured to store third login account information of the first cluster in the manageable cluster list.
9. The apparatus of claim 8, further comprising:
the acquiring unit is used for acquiring fourth login account information of the first type cluster and fifth login account information of the second type cluster in the manageable cluster list;
the sending unit is further configured to send the fourth login account information to the second type cluster, so that the second type cluster verifies the fourth login account information, and after the fourth login account information passes the verification, the fourth login account information is stored in a manageable cluster list of the second type cluster;
the sending unit is further configured to send the fifth login account information to the first type cluster, so that the first type cluster verifies the fifth login account information, and after the verification is passed, the fifth login account information is stored in a manageable cluster list of the first type cluster.
10. The device according to claim 6, wherein the jump display unit is specifically configured to display a jump prompt message;
and when a jump confirmation instruction input by a user is received, jumping to the second cluster.
CN202011531025.6A 2020-12-22 2020-12-22 Multi-cluster management method and device for distributed storage system Active CN112714166B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011531025.6A CN112714166B (en) 2020-12-22 2020-12-22 Multi-cluster management method and device for distributed storage system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011531025.6A CN112714166B (en) 2020-12-22 2020-12-22 Multi-cluster management method and device for distributed storage system

Publications (2)

Publication Number Publication Date
CN112714166A CN112714166A (en) 2021-04-27
CN112714166B true CN112714166B (en) 2022-03-29

Family

ID=75545233

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011531025.6A Active CN112714166B (en) 2020-12-22 2020-12-22 Multi-cluster management method and device for distributed storage system

Country Status (1)

Country Link
CN (1) CN112714166B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114513530B (en) * 2022-04-19 2022-08-19 山东省计算中心(国家超级计算济南中心) Cross-domain storage space bidirectional supply method and system
CN115051838A (en) * 2022-05-24 2022-09-13 广州市迪士普音响科技有限公司 Central control host cluster control method, device, equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006323526A (en) * 2005-05-17 2006-11-30 Fujitsu Ltd Cluster management program, recording medium with its program recorded, cluster management method, node and cluster
CN109936565A (en) * 2019-01-28 2019-06-25 平安科技(深圳)有限公司 Log in the method, apparatus, computer equipment and storage medium of multiple service clusters
CN110958256A (en) * 2019-12-06 2020-04-03 无锡华云数据技术服务有限公司 Cluster management method and management system
CN111314100A (en) * 2018-12-11 2020-06-19 中国移动通信集团山东有限公司 Web cluster switching method and system
CN111865632A (en) * 2019-04-28 2020-10-30 阿里巴巴集团控股有限公司 Switching method of distributed data storage cluster and switching instruction sending method and device
CN111917846A (en) * 2020-07-19 2020-11-10 中信银行股份有限公司 Kafka cluster switching method, device and system, electronic equipment and readable storage medium
CN111988275A (en) * 2020-07-15 2020-11-24 宏图智能物流股份有限公司 Single sign-on method, single sign-on server cluster and electronic equipment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006323526A (en) * 2005-05-17 2006-11-30 Fujitsu Ltd Cluster management program, recording medium with its program recorded, cluster management method, node and cluster
CN111314100A (en) * 2018-12-11 2020-06-19 中国移动通信集团山东有限公司 Web cluster switching method and system
CN109936565A (en) * 2019-01-28 2019-06-25 平安科技(深圳)有限公司 Log in the method, apparatus, computer equipment and storage medium of multiple service clusters
CN111865632A (en) * 2019-04-28 2020-10-30 阿里巴巴集团控股有限公司 Switching method of distributed data storage cluster and switching instruction sending method and device
CN110958256A (en) * 2019-12-06 2020-04-03 无锡华云数据技术服务有限公司 Cluster management method and management system
CN111988275A (en) * 2020-07-15 2020-11-24 宏图智能物流股份有限公司 Single sign-on method, single sign-on server cluster and electronic equipment
CN111917846A (en) * 2020-07-19 2020-11-10 中信银行股份有限公司 Kafka cluster switching method, device and system, electronic equipment and readable storage medium

Also Published As

Publication number Publication date
CN112714166A (en) 2021-04-27

Similar Documents

Publication Publication Date Title
US11088903B2 (en) Hybrid cloud network configuration management
US10827008B2 (en) Integrated user interface for consuming services across different distributed networks
US11307967B2 (en) Test orchestration platform
US20210203731A1 (en) Discovery of cloud-based infrastructure and resources
US20210209007A1 (en) Methods for improved web application testing using remote headless browsers and devices thereof
US8924592B2 (en) Synchronization of server-side cookies with client-side cookies
EP2989543B1 (en) Method and device for updating client
US20130346619A1 (en) Apparatus and methods for auto-discovery and migration of virtual cloud infrastructure
US11233863B2 (en) Proxy application supporting multiple collaboration channels
US10719611B2 (en) Static security scanner for applications in a remote network management platform
US10817267B2 (en) State machine representation of a development environment deployment process
US10783060B2 (en) Post-upgrade debugging in a remote network management platform
US8694993B1 (en) Virtualization platform for secured communications between a user device and an application server
CN112714166B (en) Multi-cluster management method and device for distributed storage system
US20220050699A1 (en) Workspace resiliency with multi-feed status resource caching
EP3685265A1 (en) Geographic location based computing asset provisioning in distributed computing systems
US11356455B2 (en) Behavior-based authentication
US20200249975A1 (en) Virtual machine management
US10382588B2 (en) Resource access driven distributed transaction coordination system
Toshev Learning RabbitMQ
US11381665B2 (en) Tracking client sessions in publish and subscribe systems using a shared repository
US10785096B2 (en) Graphical user interfaces for device discovery and scheduling thereof
US11509527B1 (en) Assisted and context-driven network changes
JP5734421B2 (en) Management information generation method, management information generation program, and management information generation apparatus
US20220038444A1 (en) Cloud device, application processing method, electronic device and storage medium

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