CN114257505A

CN114257505A - Server node configuration method, device, equipment and storage medium

Info

Publication number: CN114257505A
Application number: CN202111566956.4A
Authority: CN
Inventors: 胡永强; 冯波; 殷源; 周波
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2021-12-20
Filing date: 2021-12-20
Publication date: 2022-03-29
Anticipated expiration: 2041-12-20
Also published as: CN114257505B

Abstract

The application provides a server node configuration method, a server node configuration device, equipment and a storage medium, relates to the technical field of Internet of things, and is used for improving the availability of resources of server nodes and the balance of resource consumption while dynamically configuring the server nodes for tenants. The method comprises the following steps: receiving query operation of a user on a management page; responding to the query operation, determining an available server list of a tenant corresponding to the user, and returning the available server list to the management page; receiving a configuration operation of the user on any server node in the available server list on the management page; and responding to the configuration operation, and performing node configuration on any server node.

Description

Server node configuration method, device, equipment and storage medium

Technical Field

The application relates to the technical field of Internet of things, and provides a server node configuration method, device, equipment and storage medium.

Background

With the development of science and technology, cloud technology is gradually proposed, and computing and storage in a cloud environment can enable users to store and process own data in a third-party data center. Users of the cloud may be generally referred to as "tenants", and the "tenant" structure may be applied to the cloud service platform. For example, in tenant design of a cloud computing service platform, relatively independent resource management capabilities are provided for different tenants in a resource isolation manner, and then, a tenant system can involve measures such as configuration of each tenant on a corresponding server node in an application process.

At present, in the existing server node configuration technology, the following two configuration methods are often adopted, the first method is to directly allocate fixed server nodes for tenants, but different users may use respective server nodes differently, so that uneven node energy consumption of each tenant is easily caused, energy consumption of part of tenant nodes is too fast, and thus response time of each device and application under the corresponding tenant is affected, and even risks such as downtime are caused. The second method is to deploy tenants to a cluster, and then perform elastic flexible configuration on server nodes accessed by the tenants in a cluster manner, but this method cannot limit resource usage quotas of each tenant, and since a share of users accessing the cluster is deployed on each server node of the cluster, each tenant needs to be started when the cluster is started, and process consumption of the corresponding server node is increased.

Disclosure of Invention

The embodiment of the application provides a server node configuration method, a server node configuration device, equipment and a storage medium, which are used for improving the availability of resources of a server node and the balance of resource consumption while dynamically configuring the server node for a tenant.

In one aspect, a server node configuration method is provided, and is applied to an internet of things platform, and the method includes:

receiving query operation of a user on a management page;

responding to the query operation, determining an available server list of a tenant corresponding to the user, and returning the available server list to the management page;

receiving a configuration operation of the user on any server node in the available server list on the management page;

and responding to the configuration operation, and performing node configuration on any server node.

In the embodiment of the application, the tenant-based query is performed on the available server list, and then the server node is selected from the available server list for configuration, that is, the server node can be dynamically configured based on the tenant, so that the tenant can select the server node for configuration according to the resource requirement of the tenant, and the resource availability and the resource consumption balance of the server node are greatly improved.

In a possible embodiment, the determining, in response to the query operation, an available server list of a tenant corresponding to the user includes:

responding to the query operation, and acquiring the resource utilization rates of all server nodes in the current database cluster;

determining a target server node with the resource utilization rate not greater than a preset resource utilization rate threshold value according to the resource utilization rates of all the server nodes;

and determining an available server list of the tenant corresponding to the user according to the target server node.

In a possible implementation manner, the performing node configuration on the any server node in response to the configuration operation includes:

responding to the configuration operation, and acquiring all cluster information in the current database cluster; the cluster information comprises information related to each server node;

receiving node selection operation of the user on a management page;

responding to the node selection operation, and determining whether the server node selected by the user exists or not according to all the cluster information;

and if the server node exists, carrying out node configuration on the server node selected by the user.

In one possible embodiment, after node configuration of the server node selected by the user, the method further includes:

receiving tenant starting operation of the user on a management page;

responding to the tenant starting operation, and acquiring all cluster information of the current database cluster;

determining a server node corresponding to a designated tenant according to all cluster information of the current database cluster; the designated tenant is a tenant to be started by a user;

and sending the tenant starting task to the server node corresponding to the designated tenant.

In a possible implementation manner, after sending the tenant start task to the server node corresponding to the specified tenant, the method further includes:

determining whether the specified tenant boots;

if the designated tenant is determined to be started, returning a first user execution result to the management page; wherein the first user execution result is used to indicate that the specified tenant has started; alternatively, the first and second electrodes may be,

if the designated tenant is determined not to be started, starting a tenant component, updating the running state of the designated tenant, and returning a second user execution result to the management page; wherein the second user execution result is used to indicate that the specified tenant has been launched.

receiving tenant stopping operation of the user on a management page;

responding to the tenant stopping operation, and acquiring all cluster information of the current database cluster;

determining a server node corresponding to a designated tenant according to all cluster information of the current database cluster;

and sending a tenant stopping task to the server node corresponding to the specified tenant.

In a possible implementation manner, after sending the stop tenant task to the server node corresponding to the specified tenant, the method further includes:

determining whether the specified tenant is stopped;

if the specified tenant is determined to be stopped, returning a third user execution result to the management page; wherein the third user execution result is used to indicate that the specified tenant has stopped; alternatively, the first and second electrodes may be,

if the specified tenant is determined not to stop, stopping the tenant component, updating the running state of the specified tenant, and returning a fourth user execution result to the management page; wherein the fourth user execution result is used to indicate that the specified tenant has been stopped.

receiving tenant restarting operation performed by the user on a management page;

responding to the operation of the tenant restart, and acquiring all cluster information of the current database cluster;

and sending the tenant restarting task to the server node corresponding to the designated tenant.

In a possible implementation manner, after sending the tenant restart task to the server node corresponding to the specified tenant, the method further includes:

determining whether the designated tenant reboots;

if the designated tenant is determined to be restarted, returning a fifth user execution result to the management page; wherein the fifth user execution result is used to indicate that the specified tenant has restarted; alternatively, the first and second electrodes may be,

if the designated tenant is determined not to be restarted, restarting the tenant component, updating the running state of the designated tenant, and returning a sixth user execution result to the management page; wherein the sixth user execution result is used for indicating that the designated tenant is restarted.

In one aspect, a server node configuration method is provided, which is applied to a user terminal, and the method includes:

responding to a query operation performed by a user, and sending the query operation to an Internet of things platform so that the Internet of things platform determines an available server list of a tenant corresponding to the user;

receiving the available server list returned by the Internet of things platform;

responding to configuration operation of the user on any server node in the available server list, and sending the configuration operation to the Internet of things platform so that the Internet of things platform performs node configuration on any server node.

In one aspect, a server node configuration method is provided, and the method includes:

acquiring query operation performed by a user;

determining an available server list of a tenant corresponding to the user according to the query operation;

acquiring configuration operation of the user on any server node in the available server list;

and carrying out node configuration on any server node according to the configuration operation.

On one hand, a server node configuration device is provided, and is applied to an internet of things platform, and the method and the device are as follows:

the first receiving unit is used for receiving query operation of a user on a management page;

a first determining unit, configured to determine, in response to the query operation, an available server list of a tenant corresponding to the user, and return the available server list to the management page;

the first receiving unit is further configured to receive a configuration operation performed by the user on any server node in the available server list on the management page;

and the first configuration unit is used for responding to the configuration operation and carrying out node configuration on any server node.

In a possible implementation manner, the first determining unit is specifically configured to:

In a possible implementation manner, the first configuration unit is specifically configured to:

receiving node selection operation of the user on a management page;

In a possible implementation manner, the apparatus further includes a first sending unit, where the first sending unit is configured to:

receiving tenant starting operation of the user on a management page;

In a possible implementation, the apparatus further includes a tenant starting unit, where the tenant starting unit is configured to:

after sending the tenant start task to the server node corresponding to the designated tenant, the method further includes:

determining whether the specified tenant boots;

In a possible implementation, the first sending unit is further configured to:

receiving tenant stopping operation of the user on a management page;

In a possible implementation, the apparatus further includes a tenant stopping unit, where the tenant stopping unit is configured to:

determining whether the specified tenant is stopped;

In a possible implementation, the first sending unit is further configured to:

In a possible implementation, the apparatus further includes a tenant restart unit, where the tenant restart unit is configured to:

determining whether the designated tenant reboots;

In one aspect, a server node configuration apparatus is provided, which is applied in a user terminal, and the method apparatus:

a second sending unit, configured to send, in response to a query operation performed by a user, the query operation to an internet of things platform, so that the internet of things platform determines an available server list of a tenant corresponding to the user;

the second receiving unit is used for receiving the available server list returned by the Internet of things platform;

the second sending unit is further configured to send, in response to a configuration operation performed by the user on any server node in the available server list, the configuration operation to the internet of things platform, so that the internet of things platform performs node configuration on any server node.

In one aspect, an apparatus for configuring a server node is provided, where the method includes:

the acquisition unit is used for acquiring query operation performed by a user;

a second determining unit, configured to determine, according to the query operation, an available server list of a tenant corresponding to the user;

the obtaining unit is further configured to obtain a configuration operation performed by the user on any server node in the available server list;

and the second configuration unit is used for carrying out node configuration on any server node according to the configuration operation.

In one aspect, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of the above aspect when executing the computer program.

In one aspect, a computer storage medium is provided having computer program instructions stored thereon that, when executed by a processor, implement the steps of the method of the above aspect.

In one aspect, a computer program product is provided, having computer program code stored thereon, for performing the steps of the method of the above aspect when the computer program code runs on a computer.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or related technologies, the drawings needed to be used in the description of the embodiments or related technologies are briefly introduced below, it is obvious that the drawings in the following description are only the 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 view of an application scenario provided in an embodiment of the present application;

fig. 2 is a schematic flowchart of a server node configuration method according to an embodiment of the present application;

FIG. 3 is a schematic view of a management page provided by an embodiment of the present application;

fig. 4 is a schematic flowchart of determining a list of available servers according to an embodiment of the present application;

fig. 5 is a schematic flowchart of node configuration according to an embodiment of the present application;

fig. 6 is a schematic flowchart of initiating a tenant according to an embodiment of the present application;

FIG. 7 is another schematic diagram of a management page provided by an embodiment of the present application;

fig. 8 is another schematic flowchart of initiating a tenant according to an embodiment of the present application;

fig. 9 is a schematic flowchart of stopping tenants according to an embodiment of the present application;

fig. 10 is another schematic flowchart of stopping tenants according to an embodiment of the present application;

fig. 11 is a schematic flowchart of restarting a tenant according to an embodiment of the present application;

fig. 12 is another schematic flowchart of restarting a tenant according to an embodiment of the present application;

fig. 13 is another schematic flowchart of restarting a tenant according to an embodiment of the present application;

fig. 14 is a schematic flowchart of a process of starting an internet of things platform according to an embodiment of the present application;

fig. 15 is another schematic flowchart of a server node configuration method according to an embodiment of the present application;

fig. 16 is another schematic flowchart of a server node configuration method according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of a server node configuration apparatus according to an embodiment of the present application;

fig. 18 is a schematic structural diagram of a server node configuration apparatus according to an embodiment of the present application;

fig. 19 is a schematic structural diagram of a server node configuration apparatus according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying 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. In the present application, the embodiments and features of the embodiments may be arbitrarily combined with each other without conflict. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here. In addition, in the technical scheme of the application, the data acquisition, transmission, use and the like all meet the requirements of relevant national laws and regulations.

First, some terms in the present application will be explained.

(1) Tenant, refers to an organization that uses the system, e.g., vendor, enterprise department, etc. The user and the tenant are a universal concept applicable to multiple industries. A user of an environment/system is a subscriber to the environment/system. The system allows its user to enter the system through a login procedure and obtain access rights to the system and its resources. The users are divided into several groups at the management granularity, and each group becomes a tenant.

(2) The database cluster is a highly extensible data distribution and cluster platform and can be used for realizing distributed data storage and data caching.

Based on this, in the embodiment of the application, a server node configuration method applicable to a platform of the internet of things is designed, in the method, query operation performed by a user on a management page can be received, and further, by responding to the query operation, an available server list of a tenant corresponding to the user can be determined, and the available server list is returned to the management page; further, a configuration operation performed by a user on any server node in the available server list on the management page may be received, and then, a node configuration may be performed on any server node by responding to the configuration operation. Therefore, in the embodiment of the application, the tenant-based query is performed on the available server list, and then the server node is selected from the available server list for configuration, that is, the server node can be dynamically configured based on the tenant, so that the tenant can select the server node for configuration according to the resource requirement of the tenant, and the resource availability and the resource consumption balance of the server node are greatly improved.

The technical scheme of the embodiment of the application can be applied to any possible server node configuration scene. Fig. 1 is a schematic view of an application scenario provided in the embodiment of the present application. The application scenario of the server node configuration may include the user terminal 10 and the server node configuration device 11.

The user terminal 10 may be a device capable of receiving an operation such as a configuration related to a server node by a user, and may be, for example, a mobile phone, a Personal Computer (PC), a notebook computer, or the like.

The server node configuration device 11 may be a server that provides data storage and data computation for a server node configuration process, may be an independent physical server, may also be a database cluster or a distributed system formed by a plurality of physical servers, and may also be a cloud server that provides basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and big data and artificial intelligence platform, but is not limited thereto. The server node configuration device 11 may include one or more processors 101, memory 102, and I/O interfaces 103 to interact with other devices, etc. In addition, the server node configuring device 11 may further configure a database 104, and the database 104 may be configured to store data corresponding to information of each server node involved in the scheme provided in the embodiment of the present application. The memory 102 of the server node configuration device 11 may store program instructions of the server node configuration method provided in the embodiment of the present application, and when the program instructions are executed by the processor 101, the steps of the server node configuration method provided in the embodiment of the present application can be implemented to improve the availability of resources of the server node and the balance of resource consumption while dynamically configuring the server node for the tenant.

In a possible embodiment, when the server node configuring device 11 detects a query operation performed by a user on the user terminal 10 through the I/O interface 103, the processor 101 of the server node configuring device 11 executes the program instructions of the server node configuring method stored in the memory 102, queries a list of available servers of tenants corresponding to the user from the database cluster, and returns the list of available servers to the management page of the user terminal 10, and further, when the server node configuring device 11 detects a configuration operation performed by the user on any server node on the user terminal 10 through the I/O interface 103 again, the server node configuring device 11 performs node configuration on any server node based on the configuration operation, thereby improving the balance of resource consumption and availability of resources of the server nodes while performing dynamic configuration on the tenants, and the configuration information of any server node, etc. corresponding to the program instructions, is stored in the database 104 during execution.

Of course, the method provided in the embodiment of the present application is not limited to be used in the application scenario shown in fig. 1, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. The functions that can be implemented by each device in the application scenario shown in fig. 1 will be described in the following method embodiments, and will not be described in detail herein. Hereinafter, the method of the embodiment of the present application will be described with reference to the drawings.

As shown in fig. 2, a schematic flow chart of the server node configuration method provided in the embodiment of the present application is provided, where the method may be executed by an internet of things platform in the server node configuration device 11 in fig. 1, and the embodiment of the present application is not limited to this, and the flow of the method is described as follows.

Step 201: and receiving the query operation of the user on the management page.

In the embodiment of the present application, when the node resource rate of the server node currently used by the tenant corresponding to the user is not sufficient to store data, or when the tenant corresponding to the user does not use any server node for data storage, a server node needs to be added for the tenant corresponding to the user to perform data storage correspondingly. When a server node is newly added, as shown in fig. 3, for a schematic diagram of a management page provided in the embodiment of the present application, a description of a server that a user needs to search for may be filled in a "host description" column, and then an available server list of a tenant corresponding to the user is queried through a query operation, for example, clicking a "search" button. Or, the IP address of the server that the user needs to find may be directly filled in the column of the "IP address", and then the server node corresponding to the IP address may be directly queried through a query operation of clicking a "search" button.

Step 202: and responding to the query operation, determining an available server list of the tenant corresponding to the user, and returning the available server list to the management page.

In the embodiment of the application, after receiving a query operation performed by a user on a management page, the platform of the internet of things performs a corresponding server node query process for the query operation, for example, a query process is performed according to the resource utilization rate of a server node, and then, according to the server node query process, a list of available servers of tenants corresponding to the user can be queried. Further, in order to enable the user to view the available server list, the internet of things platform returns the available server list to the management page for the user to view and operate, as shown in fig. 3, the host name, the node number, the host description, the node status, the IP address, and the like of each available server can be viewed in the available server list. One user in the embodiment of the application can correspond to one or more tenants.

Step 203: and receiving the configuration operation of the user on any server node in the available server list on the management page.

In actual application, after the management page receives and displays the available server list, the user may determine the server node to be configured according to the preference of the user or according to the node resource rate of each server node in the available server list. Furthermore, after the server node to be configured is selected, a corresponding node configuration operation may be performed on the selected server node, for example, configuring tenant information corresponding to a user to the selected server node, that is, binding the tenant and the selected server node together.

Step 204: and responding to the configuration operation, and performing node configuration on any server node.

In actual application, after receiving a configuration operation performed by a user on a management page, the internet of things platform may bind a tenant and a selected server node together for the configuration operation.

In a possible implementation manner, since under a normal condition, when the resource usage rate of the server node reaches a certain resource usage rate threshold, if the tenant still uses the server node to process the task, the response time of each device and application program applied by the tenant will be affected very easily, and even a downtime condition occurs. Therefore, in the embodiment of the present application, when determining the available server list of the tenant corresponding to the user, the determination may be performed according to the resource utilization rate of each server node. Fig. 4 is a schematic flow chart of determining a list of available servers according to an embodiment of the present application, and a specific flow is described as follows.

Step 401: and responding to the query operation, and acquiring the resource utilization rates of all server nodes in the current database cluster.

In actual application, after receiving query operation performed by a user on a management page, the platform of the internet of things can obtain resource utilization rates of all server nodes in a current database cluster according to the query operation.

Step 402: and determining a target server node with the resource utilization rate not greater than a preset resource utilization rate threshold value according to the resource utilization rates of all the server nodes.

In practical application, after the resource utilization rates of all server nodes in the current database cluster are obtained, the server node of which the resource utilization rate is not greater than the preset resource utilization rate threshold value among all the server nodes can be used as the target server node. For example, the preset resource usage threshold may be set to 60%, and if the resource usage of the server node is greater than 60%, the server node may be filtered as an unavailable server node when performing server node filtering, and further, the server node may not be fed back in the available server list. Certainly, the preset resource utilization rate threshold may not be 60%, and the preset resource utilization rate threshold may be configured by a super administrator of the internet of things platform according to the requirement.

Step 403: and determining an available server list of the tenant corresponding to the user according to the target server node.

In actual application, after the target server nodes are determined according to the resource utilization rate, the determined target server nodes can be added into the available server list, and therefore the available server list of the tenant corresponding to the user is determined. Of course, in order to enable the user to select a server node from the available server list for configuration more easily and quickly, the server node configured by the tenant may not be displayed in the available server list.

In addition, when determining the available server list of the tenant, the resource utilization rate of the server node currently configured by the tenant may be determined first, and if the resource utilization rate of the server node currently configured by the tenant is not greater than 30%, it is indicated that more node resources are left in the server node currently configured by the tenant, and further, in order to improve the resource availability of the server node, the available server list of the tenant corresponding to the user may be directly determined as an "empty" table, that is, it is prompted that the node resource utilization rate of the server node currently configured by the user is too low, and expansion is not allowed. At this time, if the user must perform capacity expansion (must select a server node for configuration), the user needs to apply for the super administrator of the platform of the internet of things, and after the application is approved, the user can select and configure the corresponding server node.

In a possible implementation manner, as shown in fig. 5, a flowchart of node configuration provided in an embodiment of the present application is described as follows.

Step 501: and responding to the configuration operation to acquire all cluster information in the current database cluster.

In this embodiment, the cluster information may include information related to each server node. For example, the host name, node number, host description, node status, and IP address of each server node, etc.

Step 502: and receiving the node selection operation performed on the management page by the user.

After the internet of things platform responds to configuration operation performed by a user to acquire all cluster information in the current database cluster, the internet of things platform can also receive node selection operation performed by the user on a management page, namely, the user selects a server node required to be configured.

Step 503: and responding to the node selection operation, and determining whether the server node selected by the user exists or not according to all the cluster information.

In the embodiment of the application, after the internet of things platform receives a node selection operation performed by a user on a management page, the internet of things platform responds to the node selection operation, and then determines whether a server node selected by the user exists in an available server list according to all acquired cluster information in a current database cluster.

Step 504: and if the server node exists, carrying out node configuration on the server node selected by the user.

In the embodiment of the application, if the server node selected by the user is in the available server list, the node configuration is performed on the server node selected by the user, that is, the tenant corresponding to the user and the server node are bound together, and the configuration information of the tenant corresponding to the user and the server node is written into the database cluster, so that the user can query the server node.

In a possible implementation manner, after the user configures the selected server node, in order to determine whether the server node selected by the user is successfully configured, in this embodiment of the present application, the determination may be performed by starting a tenant corresponding to the selected server node. As shown in fig. 6, a schematic flowchart of a process for starting a tenant provided in the embodiment of the present application is described as follows.

Step 601: and receiving tenant starting operation performed on the management page by the user.

In the embodiment of the present application, as shown in fig. 7, based on fig. 7, when a user wants to start a tenant, a tenant starting operation may be performed on the management page shown in fig. 7, for example, a "start" button in an operation bar is clicked, and then, the internet of things platform receives the tenant starting operation, so as to start a corresponding tenant component.

Step 602: and responding to the tenant starting operation, and acquiring all cluster information of the current database cluster.

In the embodiment of the application, after the platform of the internet of things receives tenant starting operation performed on a management page by a user, the tenant starting operation is responded, so that all cluster information of the current database cluster is acquired.

Step 603: and determining a server node corresponding to the designated tenant according to all cluster information of the current database cluster.

In the embodiment of the present application, the designated tenant may be a tenant to be started by the user. When node configuration is carried out, configuration information of the tenants and the server nodes is written into the database cluster, so that the server nodes corresponding to the designated tenants can be determined from all cluster information of the current database cluster.

Step 604: and sending the tenant starting task to the server node corresponding to the designated tenant.

In the embodiment of the application, after the server node corresponding to the designated tenant is determined, the tenant starting task can be sent to the server node, so that the designated tenant is started. That is, the solution of the present application supports running tenants through a designated server node.

In one possible implementation manner, in order to facilitate the user to know the starting condition of the specified tenant, after the tenant starting task is completed, the execution result of the tenant starting task may be fed back to the management page for the user to view. As shown in fig. 8, another schematic flow diagram for starting a tenant provided in the embodiment of the present application is provided, and a specific flow is introduced as follows.

Step 801: it is determined whether the specified tenant boots.

Step 802: and if the designated tenant is determined to be started, returning a first user execution result to the management page.

In an embodiment of the present application, the first user execution result may be used to indicate that the specified tenant has started.

Step 803: and if the specified tenant is determined not to be started, starting the tenant component, updating the running state of the specified tenant, and returning a second user execution result to the management page.

In the embodiment of the present application, the second user execution result may be used to indicate that the specified tenant has been started.

In a possible implementation manner, as shown in fig. 9, a schematic flow chart of stopping tenants provided in the embodiment of the present application is provided, and a specific flow is described as follows.

Step 901: and receiving a tenant stopping operation performed on the management page by the user.

In the embodiment of the present application, when a user wants to stop a tenant, a tenant stopping operation may be performed on the management page shown in fig. 7, for example, a "stop" button in an operation bar is clicked, and then, the internet of things platform receives the tenant stopping operation, so as to stop a corresponding tenant component.

Step 902: and responding to the stopping of the tenant operation, and acquiring all cluster information of the current database cluster.

In the embodiment of the application, after the platform of the internet of things receives the tenant stopping operation performed on the management page by the user, the tenant stopping operation is responded, so that all cluster information of the current database cluster is obtained.

Step 903: and determining a server node corresponding to the designated tenant according to all cluster information of the current database cluster.

When node configuration is carried out, configuration information of the tenants and the server nodes is written into the database cluster, so that the server nodes corresponding to the designated tenants can be determined from all cluster information of the current database cluster.

Step 904: and sending the tenant stopping task to the server node corresponding to the designated tenant.

In the embodiment of the application, after the server node corresponding to the designated tenant is determined, the tenant stop task is sent to the server node, so that the designated tenant is stopped. That is, the solution of the present application supports stopping tenants by a designated server node.

In a possible implementation manner, as shown in fig. 10, another schematic flow diagram of stopping tenants provided in the embodiment of the present application is provided, and a specific flow is introduced as follows.

Step 1001: it is determined whether the given tenant is stopped.

Step 1002: and if the specified tenant is determined to be stopped, returning a third user execution result to the management page.

In the embodiment of the present application, the third user execution result is used to indicate that the specified tenant has stopped.

Step 1003: and if the specified tenant is determined not to stop, stopping the tenant component, updating the running state of the specified tenant, and returning a fourth user execution result to the management page.

In the embodiment of the present application, the fourth user execution result is used to indicate that the specified tenant has been stopped.

In a possible implementation manner, as shown in fig. 11, a schematic flow chart of restarting a tenant provided in an embodiment of the present application is described below.

Step 1101: and receiving a tenant restarting operation performed on the management page by the user.

In this embodiment of the application, when a user wants to restart a tenant, a tenant restarting operation may be performed on the management page shown in fig. 7, for example, a "restart" button in an operation bar is clicked, and then, the internet of things platform receives the tenant restarting operation, so that a corresponding tenant component is restarted.

Step 1102: and responding to the operation of restarting the tenant, and acquiring all cluster information of the current database cluster.

In the embodiment of the application, after the internet of things platform receives the tenant restarting operation performed on the management page by the user, the tenant restarting operation is responded, so that all cluster information of the current database cluster is obtained.

Step 1103: and determining a server node corresponding to the designated tenant according to all cluster information of the current database cluster.

Step 1104: and sending the tenant restarting task to the server node corresponding to the designated tenant.

In the embodiment of the application, after the server node corresponding to the designated tenant is determined, the tenant restart task is sent to the server node, so that the designated tenant is restarted. That is, the solution of the present application supports restarting tenants through a designated server node.

In a possible implementation manner, as shown in fig. 12, another schematic flow diagram of restarting a tenant provided in an embodiment of the present application is provided, and a specific flow is introduced as follows.

Step 1201: it is determined whether the specified tenant reboots.

Step 1202: and if the designated tenant is determined to be restarted, returning a fifth user execution result to the management page.

In the embodiment of the present application, the fifth user execution result is used to indicate that the specified tenant has restarted.

Step 1203: and if the specified tenant is determined not to be restarted, restarting the tenant component, updating the running state of the specified tenant, and returning a sixth user execution result to the management page.

In the embodiment of the present application, the sixth user execution result is used to indicate that the specified tenant has been restarted.

In a possible implementation manner, in order to more clearly understand the "tenant restart" process of the present application, the following specifically describes the above embodiment of the present application in detail, and as shown in fig. 13, another schematic flow diagram of the tenant restart provided in the embodiment of the present application is provided, and a specific flow is introduced as follows.

Step 1301: the tenant obtains a list of available server nodes.

In the embodiment of the application, a tenant corresponding to a user can perform query operation on a management platform, and then an internet of things platform can respond to the query operation to acquire all cluster information in a current database cluster, acquire an available server list of the tenant corresponding to the user based on all cluster information, and feed the available server list back to the management platform for the user to check.

Step 1302: the tenant selects a designated server node from the list of available server nodes.

Step 1303: and the tenant performs node configuration on the designated server node.

Step 1304: and determining whether the verification of the tenant and the specified server node is successful.

In the embodiment of the application, the validity of the tenant can be checked, and the validity of the designated server node and the resource occupation condition can be checked. If the verification is determined to be unsuccessful, specific relevant information of "verification failure" such as "tenant illegal" or "node illegal" may be directly displayed on the management page to prompt the user of the verification failure.

Step 1305: and if the verification is successful, determining whether to restart the tenant.

Step 1306: and if the tenant is determined to be restarted, storing the information of the tenant and the designated server node, and sending the tenant restarting task to the designated server node through Hazelcast.

In the embodiment of the application, in the process that the designated server node receives the tenant starting task, Hazelcast is adopted to monitor the task.

Step 1307: and the designated server node executes the tenant restarting task.

Step 1308: and starting the tenant component.

Step 1309: and updating the running state of the tenant.

For example, the tenant state is updated from a "stop" state to a "restart" state.

Step 1310: and if the tenant is determined not to be restarted, the tenant and the designated server node information are persisted.

In the embodiment of the application, if the tenant is not restarted, the information of the tenant and the specified server node can be stored in the database for a long time, so that the tenant can directly call the information when starting the specified server node.

In a possible implementation manner, as shown in fig. 14, a schematic flow chart of the internet of things platform start provided in the embodiment of the present application is described below.

Step 1401: and the user starts an application program corresponding to the Internet of things platform.

Step 1402: and the Internet of things platform acquires all tenant lists and server node information in the current database cluster.

In the embodiment of the application, because tenant information and server node information are more, in order to avoid increasing resource storage cost, the information is not stored in a local memory of an internet of things platform, but stored in a database cluster, and further, at an initial stage of starting the internet of things platform, in order to determine the running state of each tenant, information of the database cluster needs to be initialized, that is, all tenant lists and server node information in the current database cluster need to be acquired, that is, the information is written into the internet of things platform, so that subsequent judgment processing is facilitated.

Step 1403: and the Internet of things platform determines the tenants corresponding to the server nodes and the state information of the tenants.

Step 1404: and determining whether the tenant is in a stop state currently according to the state information of the tenant.

Step 1405: and if the tenant is determined not to be in the stop state, entering a tenant starting process, starting the tenant, loading a tenant configuration file, starting a tenant instance, and writing a server node corresponding to the tenant and the tenant state into a database cluster.

Step 1406: and if the tenant is determined to be in the stop state, the tenant is not started.

In a possible implementation manner, as shown in fig. 15, a schematic flow chart of a server node configuration method provided in this embodiment of the present application may be executed by the user terminal 10 in fig. 1, which is not limited in this embodiment of the present application, and a flow of the method is described as follows.

Step 1501: and responding to the query operation performed by the user, and sending the query operation to the Internet of things platform so that the Internet of things platform determines the available server list of the tenant corresponding to the user.

Step 1502: and receiving the available server list returned by the Internet of things platform.

Step 1503: and responding to configuration operation of any server node in the available server list by a user, and sending the configuration operation to the Internet of things platform so that the Internet of things platform performs node configuration on any server node.

Therefore, in the embodiment of the application, a user can select the server nodes as required, so that each tenant is allocated to run on the server node, and the server node run by the current tenant can be reconfigured/changed no matter whether the current tenant has server node information.

In a possible implementation manner, as shown in fig. 16, there is provided a flowchart of a server node configuration method, which may be executed by the internet of things platform in the user terminal 10 and the server node configuration device 11 in fig. 1, and the flow of the method is described as follows.

Step 1601: and acquiring the query operation performed by the user.

Step 1602: and determining an available server list of the tenant corresponding to the user according to the query operation.

Step 1603: and acquiring the configuration operation of the user on any server node in the available server list.

Step 1604: and carrying out node configuration on any server node according to the configuration operation.

In summary, in the embodiment of the present application, the tenant is used to query the available server list, and then select a server node in the available server list for configuration, that is, the tenant can dynamically configure the server node, so that the tenant can select the server node for configuration according to its resource requirement, and resource availability and resource consumption balance of the server node are greatly improved.

In addition, the tenant starting, stopping and restarting tasks can be sent to the designated server node, the tenants running on each server are dynamically adjusted, the server nodes where the tenants run are distributed as required, the tenants running are distinguished through the servers, the tenants are started as required on given different servers, 1 node is supported to be capable of running a plurality of tenants in a configurable mode, 1 node is supported to be capable of configuring and running a plurality of nodes, whether the current tenant is in a running state or not is supported to configure/change the server node information of the current tenant running, the server node configuration is effective after the tenant is restarted, whether the current tenant has the server node information or not is capable of reconfiguring/changing the server node of the current tenant running, and the server node configuration is effective after the tenant is restarted.

As shown in fig. 17, based on the same inventive concept, an embodiment of the present application provides a server node configuration device, which is applied to an internet of things platform, and includes:

a first receiving unit 1701 for receiving an inquiry operation performed by a user on a management page;

a first determining unit 1702, configured to determine, in response to the query operation, an available server list of a tenant corresponding to the user, and return the available server list to the management page;

a first receiving unit 1701, configured to receive a configuration operation performed by a user on any server node in the available server list on the management page;

a first configuration unit 1703, configured to perform node configuration on any server node in response to the configuration operation.

In a possible implementation, the first determining unit 1702 is specifically configured to:

In a possible implementation, the first configuration unit 1703 is specifically configured to:

responding to configuration operation, and acquiring all cluster information in the current database cluster; the cluster information comprises information related to each server node;

receiving node selection operation of a user on a management page;

responding to the node selection operation, and determining whether a server node selected by a user exists or not according to all cluster information;

In a possible implementation, the apparatus further includes a first sending unit 1704, where the first sending unit 1704 is configured to:

receiving tenant starting operation performed on a management page by a user;

determining a server node corresponding to a designated tenant according to all cluster information of the current database cluster; wherein, the appointed tenant is the tenant to be started by the user;

In a possible embodiment, the apparatus further includes a tenant starting unit 1705, where the tenant starting unit 1705 is configured to:

determining whether a specified tenant starts;

if the designated tenant is determined to be started, returning a first user execution result to the management page; the first user execution result is used for indicating that the designated tenant is started; alternatively, the first and second electrodes may be,

if the specified tenant is determined not to be started, starting the tenant component, updating the running state of the specified tenant, and returning a second user execution result to the management page; and the second user execution result is used for indicating that the specified tenant is started.

In one possible implementation, the first sending unit 1704 is further configured to:

receiving tenant stopping operation performed on a management page by a user;

and sending the tenant stopping task to the server node corresponding to the designated tenant.

In a possible implementation manner, the apparatus further includes a tenant stopping unit 1706, wherein the tenant stopping unit 1706 is configured to:

determining whether the specified tenant is stopped;

if the specified tenant is determined to be stopped, returning a third user execution result to the management page; wherein the third user execution result is used for indicating that the designated tenant has stopped; alternatively, the first and second electrodes may be,

receiving tenant restarting operation performed by a user on a management page;

responding to the operation of restarting the tenant, and acquiring all cluster information of the current database cluster;

In a possible implementation, the apparatus further includes a tenant restart unit 1707, where the tenant restart unit 1707 is configured to:

determining whether a designated tenant reboots;

if the designated tenant is determined to be restarted, returning a fifth user execution result to the management page; wherein the fifth user execution result is used for indicating that the designated tenant is restarted; alternatively, the first and second electrodes may be,

if the specified tenant is determined not to be restarted, restarting the tenant component, updating the running state of the specified tenant, and returning a sixth user execution result to the management page; and the sixth user execution result is used for indicating that the specified tenant is restarted.

The apparatus may be configured to execute the methods described in the embodiments shown in fig. 2 to fig. 14, and therefore, for functions and the like that can be realized by each functional unit of the apparatus, reference may be made to the description of the embodiments shown in fig. 2 to fig. 14, which is not repeated here. Note that the functional units shown by the dashed line blocks in fig. 17 are unnecessary functional units of the apparatus.

As shown in fig. 18, based on the same inventive concept, an embodiment of the present application provides a server node configuration apparatus, which is applied in a user terminal, where the apparatus 180 includes:

a second sending unit 1801, configured to send, in response to a query operation performed by a user, the query operation to the internet of things platform, so that the internet of things platform determines an available server list of a tenant corresponding to the user;

a second receiving unit 1802, configured to receive a list of available servers returned by the internet of things platform;

the second sending unit 1801 is further configured to send, in response to a configuration operation performed by the user on any server node in the available server list, the configuration operation to the internet of things platform, so that the internet of things platform performs node configuration on any server node.

The apparatus may be configured to execute the method in the embodiment shown in fig. 15, and therefore, for functions and the like that can be realized by each functional unit of the apparatus, reference may be made to the description of the embodiment shown in fig. 15, which is not repeated here.

As shown in fig. 19, based on the same inventive concept, an embodiment of the present application provides a server node configuration apparatus, where the apparatus 190 includes:

an obtaining unit 1901, configured to obtain a query operation performed by a user;

a second determining unit 1902, configured to determine, according to the query operation, an available server list of a tenant corresponding to the user;

an obtaining unit 1901, further configured to obtain a configuration operation performed by a user on any server node in the available server list;

a second configuration unit 1903, configured to perform node configuration on any server node according to the configuration operation.

The apparatus may be configured to execute the method in the embodiment shown in fig. 16, and therefore, for functions and the like that can be realized by each functional unit of the apparatus, reference may be made to the description of the embodiment shown in fig. 16, which is not repeated.

Referring to fig. 20, based on the same technical concept, the embodiment of the present application further provides a computer device 200, which may include a memory 2001 and a processor 2002.

The memory 2001 is used for storing computer programs executed by the processor 2002. The memory 2001 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to use of the computer device, and the like. The processor 2002 may be a Central Processing Unit (CPU), a digital processing unit, or the like. The embodiment of the present application does not limit a specific connection medium between the memory 2001 and the processor 2002. In the embodiment of the present application, the memory 2001 and the processor 2002 are connected by a bus 2003 in fig. 20, the bus 2003 is represented by a thick line in fig. 20, and the connection manner between other components is only schematically illustrated and is not limited. The bus 2003 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 20, but this is not intended to represent only one bus or type of bus.

The memory 2001 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 2001 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD), or the memory 2001 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Memory 2001 may be a combination of the above.

A processor 2002 for executing the methods performed by the devices in the embodiments shown in fig. 2-16 when calling the computer program stored in the memory 2001.

In some possible embodiments, various aspects of the methods provided herein may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of the methods according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the methods as described in the embodiments shown in fig. 2-16.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. Alternatively, the integrated unit of the present invention may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A server node configuration method is applied to an Internet of things platform, and comprises the following steps:

receiving query operation of a user on a management page;

2. The method of claim 1, wherein the determining, in response to the query operation, a list of available servers of a tenant corresponding to the user comprises:

3. The method of claim 1, wherein said node configuring any of said server nodes in response to said configuring operation comprises:

receiving node selection operation of the user on a management page;

4. The method of claim 1, wherein after node configuration of the user-selected server node, the method further comprises:

receiving tenant starting operation of the user on a management page;

5. The method of claim 4, wherein after sending the tenant start task to the server node corresponding to the specified tenant, the method further comprises:

determining whether the specified tenant boots;

6. The method of claim 1, wherein after node configuration of the user-selected server node, the method further comprises:

receiving tenant stopping operation of the user on a management page;

7. The method of claim 6, wherein after sending the stop tenant task to the server node corresponding to the specified tenant, the method further comprises:

determining whether the specified tenant is stopped;

8. The method of claim 1, wherein after node configuration of the user-selected server node, the method further comprises:

9. The method of claim 1, wherein after sending a tenant restart task to the server node corresponding to the specified tenant, the method further comprises:

determining whether the designated tenant reboots;

10. A server node configuration method is applied to a user terminal, and the method comprises the following steps:

11. A method for configuring a server node, the method comprising:

acquiring query operation performed by a user;

12. A server node configuration device is applied to an Internet of things platform, and the method comprises the following steps:

13. A server node configuration device is applied to a user terminal, and the method device comprises the following steps:

14. A server node configuration apparatus, characterized in that the method apparatus:

the acquisition unit is used for acquiring query operation performed by a user;

15. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor,

the processor, when executing the computer program, realizes the steps of the method of any of claims 1-11.

16. A computer storage medium having computer program instructions stored thereon, wherein,

the computer program instructions, when executed by a processor, implement the steps of the method of any one of claims 1 to 11.

17. A computer program product comprising, in a computer readable medium,

the computer program product comprises: computer program code which, when run on a computer, causes the computer to perform the method according to any of the preceding claims 1-11.