CN110958256A

CN110958256A - Cluster management method and management system

Info

Publication number: CN110958256A
Application number: CN201911243130.7A
Authority: CN
Inventors: 郭栋; 仇大玉; 潘风云
Original assignee: Wuxi Huayun Data Technology Service Co Ltd
Current assignee: Wuxi Huayun Data Technology Service Co Ltd
Priority date: 2019-12-06
Filing date: 2019-12-06
Publication date: 2020-04-03
Anticipated expiration: 2039-12-06
Also published as: CN110958256B

Abstract

The embodiment of the application provides a cluster management method and a management system, wherein the cluster management method is applied to a cluster management system, and the cluster management system comprises a container gateway and a cluster information database; the container gateway is connected with a plurality of cluster data, and is provided with a unique entrance address; the method comprises the following steps: receiving a first operation instruction sent by a user after logging in the container gateway together with the unique entry address, wherein the first operation instruction comprises identification information of a target cluster; searching target cluster login data matched with the identification information in the cluster information database; controlling the container gateway to log in to the target cluster using the target cluster login data. Because the embodiment of the application adopts the unique entry address to realize the access to the plurality of clusters, the related information of the plurality of clusters does not need to be maintained.

Description

Cluster management method and management system

Technical Field

The present application relates to the field of cloud computing, and in particular, to a cluster management method and a management system.

Background

kubernets, K8s for short, is an open source, is used to manage containerized distributed system platforms on multiple hosts in a cloud platform, and can implement management of a cluster.

To facilitate management of clusters, kubernets official community provides kubernets Dashboard, which is two parts: a front end and a back end. The front end is a UI interface seen by a user, the rear end is a part used for communicating with the Kubernets API Server, and the front end encapsulates a request sent by the front end and forwards the request to the Kubernets API Server to realize the management of the cluster. In this way, the user can manage the cluster through the visual interface.

However, in the prior art, referring to fig. 1 and fig. 1, as a structural schematic diagram of a cluster management system in the prior art, it can be seen that clusters created by a user each correspond to a respective Dashboard, and each Dashboard corresponds to a respective access address, user name and password, and therefore, when there are many clusters, the user needs to maintain relevant information of each cluster, including the Dashboard address, the user name and the password, or Token.

Disclosure of Invention

In view of this, the present application provides a cluster management method and a management system, so as to implement management of multiple clusters without maintaining information of each cluster.

In order to achieve the above object, the following solutions are proposed:

a cluster management method is applied to a cluster management system, and the cluster management system comprises a container gateway and a cluster information database; the container gateway is connected with a plurality of cluster data, and is provided with a unique entrance address; the method comprises the following steps:

receiving a first operation instruction sent by a user after logging in the container gateway together with the unique entry address, wherein the first operation instruction comprises identification information of a target cluster;

searching target cluster login data matched with the identification information in the cluster information database;

controlling the container gateway to log in to the target cluster using the target cluster login data.

Preferably, each cluster is provided with a respective back end;

said controlling said container gateway to log onto said target cluster using said target cluster login data comprises:

determining a target cluster back-end address and back-end login information in the target cluster login data;

controlling the container gateway to access the target cluster back-end address by using the back-end login information;

and displaying the target cluster information corresponding to the rear end of the target cluster by using the graphical interface of the container gateway.

Preferably, the gateway container integrates the back end of each cluster into an internal component;

and controlling the container gateway to be connected with the front end of the target cluster by using the back end login information.

Preferably, the system further comprises a back end intermediate layer device, wherein the back end intermediate layer device integrates the back end of each cluster into an internal component;

controlling the container gateway to send the target cluster login data to the middle layer device;

and the intermediate layer device returns the target cluster information corresponding to the rear end of the target cluster to the container gateway and establishes connection with the front end of the target cluster according to the target login data.

Preferably, the method further comprises the following steps:

the target cluster is a third party cluster;

and the cluster information database receives the related information of the third party cluster input by the user in advance through a third party interface.

Preferably, the method further comprises the following steps:

receiving a second operation instruction which is sent by a user and is used for operating the target cluster;

and performing corresponding operation on the target group entry according to the second operation instruction.

Another aspect of the present invention further provides a cluster management system, including:

the system comprises a system processing device, a container gateway and a cluster information database;

the container gateway is connected with a plurality of cluster data, and is provided with a unique entrance address;

the system processing means is for:

Preferably, each cluster is provided with a respective back end;

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

FIG. 1 is a schematic diagram of a cluster management system in the prior art;

fig. 2 is a schematic flowchart of a cluster management method according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a cluster management system in a cluster management method according to an embodiment of the present invention;

fig. 4 is another schematic structural diagram of a cluster management system in a cluster management method disclosed in the embodiment of the present invention;

fig. 5 is a schematic structural diagram of a cluster management system in a cluster management method disclosed in the embodiment of the present invention;

fig. 6 is a schematic structural diagram of a cluster management system according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides a cluster management method and a cluster management system. The cluster management is mainly realized.

The Dashboard of the cluster comprises two parts: the front end can be a graphical interface seen by a user, the back end is a part used for communicating with the K8s API Server, a request sent by the front end is packaged and then forwarded to the K8s API Server for execution, and a subsequent result is packaged and then returned to the user.

The following describes embodiments of the present invention in detail.

Referring to fig. 2 and fig. 3, fig. 2 is a schematic flowchart of a cluster management method according to an embodiment of the present invention, and fig. 3 is a schematic structural diagram of a cluster management system in the cluster management method according to the embodiment of the present invention.

The embodiment of the invention discloses a cluster management method applied to a cluster management system.

The cluster management system comprises a container gateway and a cluster information database; the container gateway is connected with a plurality of cluster data, and is provided with a unique entrance address; the method comprises the following steps:

s100, receiving a first operation instruction sent by a user after logging in the container gateway together with the unique entry address, wherein the first operation instruction comprises identification information of a target cluster;

s200, searching target cluster login data matched with the identification information in the cluster information database;

s300, controlling the container gateway to log in the target cluster by using the target cluster login data.

In the embodiment of the present invention, the container gateway may be specifically a project for forwarding a user request, and forwards the user request to a backend specific cluster, and the creation process may be deployed on a server as a Linux server, and may be run as a Systemd service or in a container instance.

In the embodiment of the present invention, when each cluster is created, cluster information of the cluster is stored in the cluster information database, for example, a Dashboard address, a username password, or Token of each cluster.

In the embodiment of the invention, the container gateway is provided with the only entrance, and when a user needs to manage a certain cluster, the container gateway can be used for realizing the management.

In the embodiment of the invention, the container gateway is provided with the user interface component, and a user can log in the unique entry address to access the user interface. Of course, the user interface may be configured to log in a manner that the user needs to enter an account password, or may automatically recognize the login according to the identity information of the user when logging in. In any case, the user can log into the container gateway through the unique portal address.

At this time, the graphical interface displays the related information of the managed clusters, and the user may issue a first operation instruction to a certain cluster, where the first operation instruction includes the identification information of the target cluster.

And then matching target cluster login data corresponding to the identification information in a cluster information database. The container gateway is then controlled to access the target cluster.

The control container gateway may access the target cluster in at least three ways, which will be described in detail later.

It may be understood that, in the embodiment of the present invention, the cluster information database may be implemented in various ways, for example: mariadb, or the like, or Etcd, or the like.

Because the embodiment of the application adopts the unique entry address to realize the access to the plurality of clusters, the related information of the plurality of clusters does not need to be maintained.

As can be seen from the foregoing embodiments, the embodiments of the present invention may include at least three ways to achieve access to a target cluster.

The first case may be that each cluster is provided with its own backend.

In the embodiment of the invention, each cluster is provided with a respective back end;

In the embodiment of the invention, each cluster is provided with a respective back end, and a user can access a target cluster through a container gateway.

In practice, the inside of the container gateway can be divided into a user interface component and a request forwarding component. And when the user logs in the container gateway, displaying a graphical interface for the user to operate by utilizing the user interface component.

The user selects the target cluster to be accessed through the graphical interface, and the container gateway realizes the rear-end login of the target cluster according to the rear-end login information and the rear-end login information which are correspondingly stored in the cluster information database by the target cluster.

In actual use, the user interface component transmits the operation-related instruction to the request forwarding component, and the request forwarding component realizes the login with the target cluster backend.

And after the login is successful, displaying the target cluster information corresponding to the rear end of the target cluster in the graphical interface to realize various operations on the target cluster.

The drawback of this approach is that each cluster needs to be deployed with a backend, which causes resource waste, and if there is a target cluster, such as a third party cluster, that is not installed with a backend, the docking cannot be achieved.

Based on this, in the embodiment of the present invention, the gateway container integrates the back ends of the clusters into an internal component; referring to fig. 4, fig. 4 is another schematic structural diagram of a cluster management system in a cluster management method disclosed in the embodiment of the present invention;

In the embodiment of the invention, the gateway container integrates the back ends of the clusters into the internal component, so that each cluster is not required to be separately provided with the back end.

It should be noted that the internal component can implement connection with the backend, and only the relevant information of the backend needs to be known. Such as the address of the back-end K8s API Server and the corresponding username password or Token.

In the embodiment of the invention, the internal component can be called to initiate an access request to the corresponding target cluster back end.

It is understood that the information that the graphical interface of the internal component can display includes object information in a certain cluster at the back end, such as common kubernets objects like Pod, delivery, and Service.

It should be noted that the back end in this embodiment of the present invention may be in a one-to-many manner, that is, one back end may correspond to multiple front ends, and the back end may also dynamically create a corresponding relationship, and when corresponding back end information and front end information are newly added in the cluster information database, the corresponding relationship between the back end and the front end is dynamically created.

In the embodiment of the invention, more resources can be saved compared with the previous embodiment.

For this way, the architecture is too cumbersome, and therefore, further optimization is possible.

Fig. 5 is a schematic structural diagram of a cluster management system in the cluster management method disclosed in the embodiment of the present invention; in the embodiment of the invention, the device also comprises a rear end intermediate layer device, wherein the rear end intermediate layer device integrates the rear end of each cluster into an internal component;

In the embodiment of the invention, the system also comprises an intermediate layer device which is an intermediate layer of the independent container gateway, so that the architecture is simpler and more concise, and the coupling degree is reduced.

In the embodiment of the invention, the container gateway does not need to communicate with the cluster information database, and the request of the user is directly forwarded to the middle layer device at the back end.

The back end obtains the target login data, connects with the front end by using the target login data, and forwards the request to the corresponding cluster.

Thus, the improved architecture and method reduces the degree of coupling.

In the embodiment of the invention, the access to the third party cluster can also be realized. The third party cluster refers to a cluster which is not built by a user, and the clusters may exist in a public cloud or other environments, so that information of the third party cluster needs to be input in advance if a target cluster is the third party cluster. Thus. The embodiment of the invention also comprises the following steps:

the target cluster is a third party cluster;

In the embodiment of the present invention, a third party interface is provided, where the third party interface must meet the kubernets specification of the community standard, that is, the third party cluster needs to be a standard kubernets cluster.

The user inputs the related information of the third party cluster through the third party interface, wherein the related information comprises the information such as the address of Kubernetes APIServer, a user name password or Token and the like, so that the access to the third party cluster is realized.

When the related information of the third party cluster is entered, the container gateway or the middle layer device in the above embodiment automatically establishes the corresponding relationship between the back end and the front end to realize the access to the third party cluster.

After establishing the data connection with the target cluster, the embodiment of the present invention further includes:

In the embodiment of the invention, a second operation instruction sent by a user is also received.

And then sending the second operation instruction to the target cluster to implement corresponding operations, such as data processing operations, store-and-forward operations, and the like.

Therefore, the embodiment of the invention can realize the management of multiple clusters, does not need to maintain the information of each cluster, has multiple architectures and corresponding data processing methods, and can realize the management of the multiple clusters under various environments.

Corresponding to the foregoing method embodiment, the present invention further provides a cluster management system, and referring to fig. 6, fig. 6 is a schematic structural diagram of a cluster management system provided in the embodiment of the present invention.

The cluster management system of the present invention includes:

a system processing device 1, a container gateway 2 and a cluster information database 3;

the system processing means is for:

Preferably, each cluster is provided with a respective back end;

It can be understood that, for each step implemented by the processing device of the cluster management system provided by the present invention, reference may be made to each step in the cluster management method in the foregoing embodiment, and the reference may be made to each step, which is not described herein again.

The embodiment of the application provides a cluster management system, which adopts a unique entry address to realize access to a plurality of clusters, so that the related information of the plurality of clusters does not need to be maintained.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A cluster management method is applied to a cluster management system, wherein the cluster management system comprises a container gateway and a cluster information database; the container gateway is connected with a plurality of cluster data, and is provided with a unique entrance address; the method comprises the following steps:

2. The method of claim 1, wherein each cluster is provided with a respective backend;

3. The method of claim 1, wherein the gateway container integrates back-ends of each cluster into internal components;

and controlling the container gateway to be connected with the rear end of the target cluster by using the rear end login information.

4. The method of claim 1, further comprising a back-end middle-tier device that integrates the back-end of each cluster into an internal component;

5. The method of claim 3 or 4, further comprising:

the target cluster is a third party cluster;

6. The method of any one of claims 1 to 4, further comprising:

7. A cluster management system, comprising:

the system processing means is for:

8. The system of claim 7, wherein each cluster is provided with a respective backend;

9. The system of claim 7, wherein the gateway container integrates back-ends of each cluster into internal components;

10. The system of claim 7, further comprising a back-end middle-tier device that integrates the back-end of each cluster into an internal component;